What it means
GitOps security treats version-controlled declarations and automated reconciliation as a production control plane that requires protected repositories, signed changes, policy checks, and trustworthy deployment identities.
Why it matters
When reconciliation is automatic, a repository change can become an infrastructure change; source-control governance therefore becomes operational security.
Practical focus
- Define the repositories, branches, controllers, and identities that can change environments and the security outcome it must support
- Apply reviewed pull requests, protected branches, signed artifacts, policy gates, and scoped reconciliation through documented, reviewable configuration
- Verify commit provenance, controller actions, drift, policy failures, and emergency changes after changes and on a scheduled basis
- Plan for a compromised repository or controller applying an unauthorized desired state, including rollback, ownership, and escalation
Common mistakes
- Enabling a feature without defining what it should protect
- Relying on defaults or one-time validation
- Granting broad exceptions that erase the control boundary
- Treating a compromised repository or controller applying an unauthorized desired state as an operational surprise instead of a test case
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: