Skip to content

Deployment Overview

Directory Inventory

See the Deployment Directory Inventory for a complete listing of files and resources in this directory.

This document provides an overview of deploying the Secure CINC Auditor Kubernetes Container Scanning solution in various environments.

Deployment Methods

The container scanning solution can be deployed in several ways:

  1. Script-based Deployment: Using helper scripts for direct deployment
  2. Helm Charts Deployment: Using modular Helm charts for production deployment
  3. CI/CD Pipeline Integration: Integrating scanning into existing CI/CD workflows

Each deployment method has its own advantages and is suitable for different scenarios.

Deployment Scenarios

We provide guidance for several common deployment scenarios:

Advanced Deployment Topics

For specialized environments and requirements:

Deployment Prerequisites

Before deploying, ensure you have:

  1. Kubernetes Cluster Requirements:
  2. Kubernetes 1.16+ (for all features including ephemeral containers)
  3. RBAC enabled

  4. Service account support

  5. Tool Requirements:

  6. kubectl with cluster access
  7. Helm 3+ (for Helm-based deployment)
  8. CINC Auditor/InSpec

  9. SAF CLI (for threshold validation)

  10. Access Requirements:

  11. Permissions to create namespaces, service accounts, and roles
  12. Permissions to create and manage pods

Getting Started

To get started with deployment, follow these steps:

  1. Review the deployment prerequisites
  2. Choose the appropriate deployment method for your environment
  3. Follow the detailed instructions for your chosen method
  4. Verify your deployment using the verification procedures