- Kaspersky Container Security 2.0 Help
- About the Kaspersky Container Security platform
- Solution architecture
- Standard deployment schemes
- Preparing to install the solution
- Solution installation
- 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
- Минимально достаточные права для интеграции с реестрами
- 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
- Image 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
- Getting scan results in JSON or HTML format
- Running the scanner in lite SBOM mode
- 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
- Действия в рамках системных ролей
- 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
- Creating a user for an external PostgreSQL database
- Backing up and restoring data
- Contacting Technical Support
- Sources of information about the application
- Limitations and warnings
- Glossary
- Third party code information
- Trademark notices
- ATT&CK MITRE Terms of Use
Compliance check
Kaspersky Container Security lets you check cluster nodes and resources for compliance with the following benchmarks:
- Kubernetes benchmarks. The solution checks cluster nodes for compliance with recommendations for creating a robust security system for Kubernetes-based software.
The results of the check are displayed in the Compliance → Kubernetes benchmarks section.
- Cluster benchmarks. The solution checks how well resources in clusters are protected. Clusters are checked using rules described in MITREand
The MITRE ATT&CK matrix, developed by the MITRE Corporation, describes the techniques and tactics used in attacks on information systems. It helps ensure the necessary level of protection, identify attacks on infrastructure, determine their purpose and detection method.
NSA/The National Security Agency (NSA) is a division of the US Department of Defense that (among other things) is responsible for cyber intelligence and protecting US government information systems from cyber attacks.
CISAbenchmarks, as well as Kubernetes benchmarks, which are used to assess threats and develop resource protection strategies.The Cybersecurity and Infrastructure Security Agency (CISA) is a federal agency in the USA tasked with enhancing national cybersecurity at all levels of government, developing and coordinating the implementation of cybersecurity programs in the USA, and improving the protection of the information infrastructure from hacker attacks.
The results of the check are displayed in the Compliance → Cluster benchmarks section.
In Kaspersky Container Security, you can also generate reports based on the results of benchmark compliance checks. The list of generated reports is displayed under Administration → Reports.
In this Help section |