Profile Applicability:
Level 1
Description:
Access to deployment configuration files, including Infrastructure as Code (IaC) templates, Kubernetes manifests, and deployment scripts, must be restricted to authorized personnel only. Proper access controls help prevent unauthorized modifications, reduce the risk of accidental misconfigurations, and protect sensitive deployment information.
Rationale:
Deployment configurations define the structure and security posture of infrastructure and applications. Limiting access reduces the likelihood of malicious or accidental changes that can lead to security breaches, service outages, or compliance violations. Enforcing least privilege access supports auditability and accountability.
Impact:
Pros:
Protects against unauthorized or accidental configuration changes.
Enhances security by enforcing least privilege principles.
Improves compliance with organizational and regulatory policies.
Cons:
May require additional administrative effort to manage access controls.
Could slow down operations if access procedures are too restrictive.
Default value:
By default, deployment configurations may be accessible to a broad group, increasing risk.
Audit:
Review permissions and access control lists on configuration repositories and storage locations. Verify only authorized users have write or modify permissions.
Remediation:
Implement role-based access control (RBAC) or similar mechanisms for configuration files. Enforce strict permission policies and conduct periodic access reviews. Use secure version control systems with branch protection and audit logging.
References:
NIST SP 800-53 – Access Control: https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final
CIS Controls v8, Control 14 – Controlled Access Based on the Need to Know: https://www.cisecurity.org/controls/controlled-access-based-on-need-to-know/
OWASP Secure Configuration Guide: https://owasp.org/www-project-secure-configuration-guide/