Integration · Cloud & infrastructure

Kubernetes integration for continuous SOC 2, ISO 27001 & PCI DSS compliance

CATAAM connects to Kubernetes with read-only access and runs 3 automated checks against your real configuration. The results map to 6 controls across 7 frameworks, including SOC 2, ISO 27001, PCI DSS, GDPR, NIST CSF, SOC 1.

automated checks: 3
controls mapped: 6
frameworks: 7

What happens when you connect Kubernetes

Connect with read-only access
Add a read-only role, OAuth scope or API token for Kubernetes. The credential is encrypted at rest.
Discover assets
CATAAM pulls the accounts, users, repositories or devices it finds into one asset inventory.
Run 3 automated checks
Every check runs against your real configuration, then keeps running on a schedule.
Map results to 6 controls
Each result lands on the controls it proves — and counts for every framework that shares them.
Store evidence and raise issues
Passing checks become audit evidence. Failures show up for the control owner and can open a Jira issue.

The 3 checks CATAAM runs on Kubernetes

Each check runs against your real Kubernetes configuration and keeps running on a schedule. Check names are shown as they appear in the CATAAM platform.

Kubernetes RBAC enabled and no wildcard cluster-admin bindings
Kubernetes anonymous or unauthenticated access not granted via RBAC bindings
Kubernetes network policies defined for all non-system namespaces

Controls these checks support (6)

A passing check becomes evidence for each control below, and counts for every framework that shares the control.

Control	Requirement	Frameworks
CHG-2	Production deployment access restricted	SOC 2, ISO 27001, SOC 1, ITIL
IAC-1	Production application access restricted	SOC 2, ISO 27001, SOC 1
IAC-3	Production database access restricted	SOC 2, ISO 27001, SOC 1
IAC-6	Production network access restricted	SOC 2, ISO 27001, SOC 1
NET-2	Network segmentation implemented	SOC 2, ISO 27001, PCI DSS, NIST CSF
NET-38	Network segmentation implemented	GDPR

Kubernetes integration: frequently asked questions

What does CATAAM check in Kubernetes?

CATAAM runs 3 automated checks on Kubernetes, for example: Kubernetes RBAC enabled and no wildcard cluster-admin bindings; Kubernetes anonymous or unauthenticated access not granted via RBAC bindings; Kubernetes network policies defined for all non-system namespaces. The full list is on this page.

Which compliance frameworks does the Kubernetes integration support?

The Kubernetes checks map to 6 controls and count toward SOC 2, ISO 27001, PCI DSS, GDPR, NIST CSF, SOC 1.

Does CATAAM need write access to Kubernetes?

No. Connectors use read-only roles, scopes or API tokens, and credentials are encrypted at rest. The only optional write anywhere in CATAAM is opening Jira issues for failed checks.

How do I connect Kubernetes to CATAAM?

Add a read-only role, OAuth scope or API token for Kubernetes in CATAAM. CATAAM then discovers your assets, runs the checks and keeps running them on a schedule, storing each result as audit evidence.