Container Security

Container image scanning

Container image scanning, performed by the Trend Micro Artifact Scanner (TMAS), enables you to scan container images as part of your development pipeline and to perform ongoing scans of images in your registries so that developers can detect and fix security issues early in the container image lifecycle. With container image scanning, DevOps teams can continuously deliver production-ready applications and meet the needs of your business, without impacting build cycles.

Container image scanning checks for vulnerabilities, malware, and secrets.

Container image scanning detects threats in apps installed with a package manager, as well as direct-installed apps, from a variety of publicly available vulnerability data sources.

Container image scanning detects all types of malware, including trojans, ransomware, and spyware. Container image scanning also detects secrets in your installed apps, which helps identify sensitive and confidential data that might have been inadvertently exposed, like passwords and API keys.

The results of the container image scans are also sent to Trend Vision One - Container Security, which determines whether it's safe to deploy the image by checking the scan results against a policy that you define.

To enable container image scanning, you will need to install the Trend Micro™ Artifact Scanner (TMAS) in your local environment.

Policy-based deployment control

Container Security provides policy-based deployment control through a native integration with Kubernetes to ensure the Kubernetes deployments you run in your production environment are safe.

Container Security enables you to create policies that allow or block deployments based on a set of rules. The rules are based on a Kubernetes object's properties and the results of TMAS scans (if you have TMAS integrated with your environment).

When an image is ready to be deployed with Kubernetes, the admission control webhook is triggered, which checks whether the image is safe to deploy and either allows or blocks it from running.

Continuous compliance

After deployment, Container Security can continue to monitor containers. Container Security checks the policy assigned to the cluster on a regular basis, ensuring that running containers continue to conform to the policy you defined. If there are changes to the policy after the initial deployment, the updated policy is enforced. Running containers are also checked for new vulnerabilities as they are discovered.

Runtime Security

Runtime Security provides visibility into any activity of your running containers that violates a customizable set of rules. Currently, runtime security includes a set of predefined rules that provide visibility into MITRE ATT&CK® framework tactics for containers, as well as container drift detection. Container Security can mitigate problems detected by the runtime visibility and control feature, based on a policy that you define. If a pod violates any rule during runtime, the issue is mitigated by terminating or isolating the pod based on the runtime ruleset in the policy.

Runtime Vulnerability Scanning

Runtime Scanning provides visibility of operating system and open source code vulnerabilities that are part of containers running in clusters where you have Container Security installed. It provides a list of vulnerabilities, sorted based on severity, which you can select for additional information. You can search for a vulnerability by name, and filter by severity level or CVE score.

Vulnerability details include:

Runtime Malware Scanning

Runtime Malware Scanning provides detection of malware in your running containers, enabling you to identify and respond to malware threats introduced after deployment. You can configure a schedule to regularly scan for malware. Container Security logs malware events, which you can view from the Events tab.