Kaspersky Container Security

What's new

December 4, 2024

ID 275547

Kaspersky Container Security 1.2 offers the following new features and improvements:

Kaspersky Security for Containers 1.2.1 has the following updates:

  • LDAP-based authentication method was improved.
  • Operations for working in Telegram (sending messages, chat searching) were improved.
  • Application of filters for results of checking for compliance with the Kubernetes standard was corrected.
  • The Vendor Fix field in the Risk acceptance report was amended.
  • Capability to work with vulnerabilities in Java dependencies for the CI agent was added.
  • Performance of the following controls in runtime policies was improved: Block non-compliant images and Block unregistered images.
  • Logic of deleting scopes with policies assigned to them was improved.
  • Work with image signature validators was optimized.
  • Procedure for authentication of Kaspersky Container Security users was improved.
  • API token reissue functionality was corrected.
  • Display of a large number of tags when adding images for analysis was corrected.
  • Adding a new registry using API was improved (the logic of saving information about tags was fixed).
  • Image report templates were amended (links to vulnerabilities in images are displayed).
  • Work with email servers when using CRAM-MD5 authentication was ijmproved.
  • Capability to configure the frequency of accessing an image registry was added.
  • Web interface was improved.

Kaspersky Security for Containers 1.2.2 has the following updates:

  • Yandex Registry support was implemented.
  • General way to support image registries using the Docker V2 API was added.
  • Work with the JFrog Artifactory image registry to support accounts with reduced privileges was improved.
  • Mechanism for saving artifacts in CI/CD was improved.
  • Agent operation errors in older versions of Kubernetes (version 4.18) were fixed.
  • Scheduled scanning of image registries in case of errors with codes 4XX and 5XX was corrected.
  • Logic of operation during an integration with a subdomain (using names other than standard names) in the JFrog Artifactory was improved.
Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.