Compliance Configuration Audits
Security > Compliance > Configuration Audits shows Kubernetes configuration findings framed for compliance: unsafe defaults, weak workload settings, missing hardening, and similar checks that map to benchmarks or policies your organization tracks (for example CIS-style controls, Pod Security expectations, or other bundled profiles—exact labels depend on your deployment).
On this page you can expect:
- Resources or report rows with failed or passed checks tied to compliance-relevant configuration.
- Severity and status per check, plus remediation text you can hand to platform or application teams.
- Optional framework or policy context (which standard or chapter the control belongs to), when the product surfaces it.
This is the Compliance entry point for configuration audit detail. For a cluster-wide summary of benchmark pass rates (multiple standards in one list), see Cluster Compliance. For namespace-scoped operational configuration audits, see Namespace Configuration Audits; for cluster-wide operational audits, see Cluster Configuration Audits.