A policy enforcement level defines how strongly a policy violation affects approval or deployment. It separates required controls from exceptions and guidance. section 8.3.4
Classify policies by their effect on the delivery pipeline:
- Hard mandatory: blocks production changes until the violation is fixed. section 8.3.4
- Soft mandatory: permits an exception only after manual analysis and approval. section 8.3.4
- Advisory: shares best practices without requiring correction before production. section 8.3.4
Firewall access exception
A firewall rule allowing 0.0.0.0/0 can be soft mandatory when public load balancers need endpoint access. A security team member reviews and approves the exception before production. section 8.3.4
Figure 8.9 You can divide policy as code into three enforcement categories that gate changes before production.
Use the enforcement-category figure to compare how policies gate changes before production. section 8.3.4
