Kaspersky Container Security
- Kaspersky Container Security 2.0 Help
- About the Kaspersky Container Security platform
- Solution architecture
- Standard deployment schemes
- Preparing to install the solution
- Solution installation
- Installing the basic business logic module and scanner
- First launch of the Management Console
- Viewing and accepting the End User License Agreement
- Checking solution functionality
- Agent deployment
- Viewing and editing agent groups
- Configuring a proxy server
- Connecting to external data storage resources
- Installing private fixes
- Removing the solution
- Updating the solution
- Solution interface
- Licensing the solution
- Data provisioning
- Working with clusters
- View the list of clusters
- Namespaces in the cluster
- Pods in the cluster
- Visualization of cluster resources
- Working with images from registers
- Investigating security events
- Analyzing container forensics
- Searching container forensics
- Detailed information about a running process
- Detailed information about file operations
- Details information about network traffic
- Detailed information about detected malicious objects
- Restrictions on runtime policies
- Investigating container forensics while accounting for adjacent events
- Analyzing detected vulnerabilities
- Analyzing container forensics
- Integration with third-party resources
- Setting up integration with external image registries
- Minimum sufficient rights for integration with registries
- Working with public registries without authorization
- Adding integrations with external image registries
- Viewing information about integrations with registries
- Deleting integration with external registry
- Harbor integration
- Creating an integration upon Harbor request
- Viewing and editing the Harbor External Integration settings
- Rescanning
- Integration with CI/CD
- Artifact scanning in CI/CD processes
- Configuring integration with GitLab CI/CD
- Configuring integration with Jenkins CI/CD
- Configuring integration with TeamCity CI/CD
- Defining the path to container images
- Monitoring the integrity and origin of images
- Running the scanner in SBOM mode
- Running the scanner in lite SBOM mode
- Getting scan results in JSON or HTML format
- Specifying secrets when starting a scan
- Configuring integration with image signature validators
- Setting up integration with notification outputs
- Configuring LDAP server integration
- Configuring integration with SIEM systems
- Integrating with HashiCorp Vault
- Setting up integration with external image registries
- Security policies configuration
- Scanner policies
- Assurance policies
- Response policies
- Runtime policies
- Creating a runtime policy
- Editing runtime policy settings
- Managing container runtime profiles
- Managing runtime autoprofiles
- Deleting policies
- Compliance check
- Configuring and generating reports
- File Threat Protection
- Users, roles, and scopes
- Managing users
- About user roles
- Working with system roles
- Displaying list of roles
- About scopes
- Scopes and enforcement of security policies
- Switching between scopes
- Adding users, roles, and scopes
- Resetting password for user accounts
- Changing settings for users, roles, and scopes
- Removing users, roles, and scopes
- Using Kaspersky Container Security OpenAPI
- Security event log
- Information about the status of solution components
- Ensuring safety and reliability of components
- Managing the dynamics of data accumulation
- Backing up and restoring data
- Contacting Technical Support
- Sources of information about the application
- Limitations and warnings
- Vulnerabilities in third-party services
- Glossary
- Third party code information
- Trademark notices
- ATT&CK MITRE Terms of Use
Solution installation > Installing private fixes
Installing private fixes
Installing private fixes
Due to specifics of various corporate networks where Kaspersky Container Security is deployed, sometimes there is a need to install private fixes for the solution. A private fix is one or several customized Docker images. Such private fixes are not published on the official Kaspersky image source, and are transferred directly to the customer for putting in the corporate image registry.
To put the received Docker image to an image registry:
- Save the archive with the Docker image in the selected directory.
- Run the
docker load -i <
archive_name
>
command. - Run the
docker tag <
hash name obtained in step 2
> <
customer registry
/<
component
>:fix>
command. - Run the
docker push <
customer registry
/<
component
>:fix>
command. - Depending on the component for which the fix is installed, replace the image tag from
<
component
>:2.0
to<
customer registry
/<
component
>:fix>
in one of the following configuration files:- In the YAML file with instructions for agents deployment in the cluster if the fix is installed for agents (node-agent and kube-agent). For example,
node-agent:2.0
must be changed to<
customer registry
/node-agent:fix>
. - In the values.yaml file, if the fix is installed for the core components of the solution. For example,
kcs-ih:2.0
must be changed to<
customer registry
/kcs-ih:fix>
- In the YAML file with instructions for agents deployment in the cluster if the fix is installed for agents (node-agent and kube-agent). For example,
Article ID: 298784, Last review: May 20, 2025