An insecure configuration sets infrastructure or system controls in ways that create unintended exposure. Common failures include public object storage, default database passwords, and firewall rules that permit unknown inbound sources. section 1.4.4
Infrastructure as code makes configuration reviewable and testable before deployment. Security checks can verify that storage is not public, access policies grant only required reads, and firewalls accept traffic only from known sources. section 1.4.4
Reduce exposure through a practical workflow:
- Audit configuration and access control before production deployment. section 1.4.4
- Use standardized, hardened infrastructure modules approved by the security team. section 10.0
- Assess external modules for functionality, security, and lifecycle, then reassess them after releases. section 13.1
- After a breach, examine configuration, assess blast radius, and remediate affected infrastructure. section 1.4.4

