← All integrations
Cloud · integration
Kubernetes
RBAC and workload hardening for a Kubernetes cluster.
ISO 27001SOC 2PCI DSSDPDPARBISEBI CSCRFIRDAI
What ProofLayer proves
Read-only evidence, evaluated against versioned rules.
- cluster-admin bindings are limited
- No privileged containers; images are pinned (no :latest); workloads run as non-root
Configure in ProofLayer
Live in minutes.
- Connections → New connection → pick this provider and name the account.
- Enter the API server URL and the cluster CA, and paste a read-only service-account token (write-only).
- Click Test connection — ProofLayer verifies read access from the control plane and reports a clear reason if anything is off.
- Set the scan schedule; every run appends to the evidence chain for this account.
- Choose the framework mapping(s) and, optionally, a push target (CISO Assistant, a Jira/ServiceNow ticket on failure, or a scheduled auditor pack).
Grant access from your side
Read-only, least-privilege, revocable.
You create the access in your own console and paste a credential ProofLayer stores sealed — it never writes to your systems.
- Create a read-only ServiceAccount bound to the built-in `view` ClusterRole.
- Provide the API server URL, the cluster CA certificate (PEM) and the token.
In-account agent option. Run the collector in-cluster with the `view` ServiceAccount; it needs no external credential. The collector posts evidence outbound-only, so ProofLayer holds no credential into your environment.