Research briefs · Cloud infrastructure · Updated 2026-11-08
What belongs in a Kubernetes security baseline?
A baseline should combine workload restrictions, identity, network policy, image controls, secrets, and auditability.
Thesis
Kubernetes security is a layered control problem; a pod policy alone cannot cover cluster identity, supply chain, network, secrets, and operational access.
Market context
Editorial analysis: A baseline should combine workload restrictions, identity, network policy, image controls, secrets, and auditability. A useful decision framework considers ownership, exceptions, evidence, and change control alongside the technology itself.
Editorial analysis: standards and frameworks can provide shared terminology, but a citation to a standard does not establish how a particular product or organization implements it.
Kubernetes Pod Security Standards define three profiles: Privileged, Baseline, and Restricted.
Evidence
- Kubernetes Pod Security Standards define Privileged, Baseline, and Restricted profiles for security-sensitive pod settings. They provide a portable starting point for workload admission, including controls around privilege, host namespaces, capabilities, and security contexts.
- Kubernetes' security checklist also covers authentication and authorization, network policies, secrets, audit logging, updates, and image security. That wider scope shows why the pod profile should be one testable section of a versioned cluster baseline.
- Editorial analysis: implementation controls should be mapped to the system, users, data, and consequences in scope; the cited sources do not establish that any particular deployment has passed those controls.
- Editorial analysis: reviewers may find it useful to preserve dated implementation evidence and distinguish policy, configuration, and exception records.
Competing viewpoints
Editorial analysis: a standardization-first approach may improve consistency and supplier comparability, but should not be treated as proof that an implementation is effective.
Editorial analysis: a context-first approach can better reflect local risk, but may reduce consistency and require more governance. Neither position is established by the cited sources as universally preferable.
Implications
- Use the Restricted profile by default and document necessary exceptions.
- Test role bindings, network policies, secret access, and audit collection.
- Version the baseline with supported Kubernetes releases.
- Budget for evidence collection, exception handling, and periodic retesting; these are continuing operating costs, not one-time implementation tasks.
- Use procurement and architecture review to expose dependencies early, because a technically valid control can still fail when ownership or supplier obligations are ambiguous.
Actionable takeaways
- Write a one-page scope statement naming the covered systems, data, users, environments, and explicit exclusions. Give the scope an owner and review date.
- Convert each cited principle into a testable requirement with an evidence source, pass condition, collection cadence, and escalation route.
- Run one representative end-to-end test, including an adverse or exception case, and retain the configuration, inputs, outputs, and decision record.
- Add relevant requirements to supplier evaluation and contracts. Ask for product-specific evidence and change notification rather than provider-wide assurances.
- Review the control after material releases, architecture changes, incidents, and supplier changes; close expired exceptions or renew them with fresh evidence.
Limitations and risks
Generic guidance cannot account for every workload or managed-service boundary. Some controls may require platform-specific implementations or carefully reviewed exceptions. The primary sources define mechanisms, practices, or reference models; they do not measure this organization's implementation or guarantee an outcome. This is not a product comparison, legal opinion, penetration test, or audit conclusion. Applicability changes with architecture, versions, contracts, jurisdiction, threats, and data sensitivity. Validate assumptions against current source editions and product documentation, test representative failures, and obtain specialist advice for regulated or high-consequence decisions.
Sources and citations
- Pod Security Standards — Kubernetes, accessed 2026-09-06
- Security Checklist — Kubernetes, accessed 2026-09-06