Container violated compliance standards

Set up the twistlock integration.

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Goal

Detect when a container is not running within compliance standards.

Strategy

This rule lets you monitor Twistlock logs to detect when a High or Critical severity compliance issue is discovered in a running container.

Triage and response

  1. Determine the impact of the compliance finding.
  2. Remediate the compliance finding.

Change Log

27 Jun 2022 - Updated rule and added findings for critical vulnerabilities.

PREVIEWING: piotr_wolski/update-dsm-docs