SC-7 (05)—Boundary Protection | Deny by Default -- Allow by Exception
Moderate
High
>Control Description
Deny network communications traffic by default and allow network communications traffic by exception [Selection (one or more): at managed interfaces; for ⚙organization-defined systems].
>FedRAMP Baseline Requirements
Parameter Values
>Discussion
Denying by default and allowing by exception applies to inbound and outbound network communications traffic. A deny-all, permit-by-exception network communications traffic policy ensures that only those system connections that are essential and approved are allowed. Deny by default, allow by exception also applies to a system that is connected to an external system.
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What policies govern the implementation of deny by default -- allow by exception?
- •How are system and communications protection requirements defined and maintained?
- •Who is responsible for configuring and maintaining the security controls specified in SC-7(5)?
Technical Implementation:
- •How is deny by default -- allow by exception technically implemented in your environment?
- •What systems, tools, or configurations enforce this protection requirement?
- •How do you ensure that deny by default -- allow by exception remains effective as the system evolves?
- •What network boundary protections are in place (firewalls, gateways, etc.)?
Evidence & Documentation:
- •What documentation demonstrates the implementation of SC-7(5)?
- •Can you provide configuration evidence or system diagrams showing this protection control?
- •What logs or monitoring data verify that this control is functioning correctly?
- •Can you provide network architecture diagrams and firewall rulesets?
Ask AI
Configure your API key to use AI features.