FedRAMP Moderate
SC - System and Communications Protection

FedRAMP Moderate SC-7(5): Deny by Default Allow by Exception

Deny network communications by default; allow by exception.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 40 controls across 19 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 7 controls

  • 1.3.1 1.3.1 Inbound CDE traffic restricted
  • 1.3.2 1.3.2 Outbound CDE traffic restricted
  • 1.4.1 1.4.1 NSCs between trusted and untrusted networks
  • 1.4.2 1.4.2 Restricting traffic entering trusted networks from outside
  • 1.4.3 1.4.3 Anti-spoofing measures at trusted boundary
  • 1.4.4 1.4.4 Cardholder data stores not reachable from untrusted networks
  • 7.3.3 7.3.3 Access control default deny all

CIS Controls v8 · 5 controls

  • CIS-12.8 Establish and Maintain Dedicated Computing Resources for All Administrative Work
  • CIS-13.4 Perform Traffic Filtering Between Network Segments
  • CIS-13.9 Deploy Port-Level Access Control
  • CIS-16.10 Apply Secure Design Principles in Application Architectures
  • CIS-4.4 Implement and Manage a Firewall on Servers

SOC 2 · 4 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary
  • SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal
  • ASD37-22 Network segmentation (Excellent)
  • ASD37-25 Software firewall - inbound (Very Good)
  • ASD37-26 Software firewall - outbound (Very Good)
  • ASBv3-NS-7 Simplify network security configuration
  • NS-1 Establish network segmentation boundaries
  • NS-2 Secure cloud services with network controls

UK Cyber Essentials · 3 controls

  • CE-FW.1 Boundary Firewalls Deployed
  • CE-FW.4 Approve and Document Inbound Rules
  • CE-FW.5 Remove or Disable Unused Rules

C5 (Germany) · 2 controls

  • C5-COS-02 Security requirements for connections in the Cloud Service Provider's network
  • C5-COS-04 Cross-network access

ISO 27002:2022 · 2 controls

  • 8.20 Networks security
  • 8.22 Segregation of networks
  • SEC05-BP02 Control traffic flow within your network layers

CMMC 2.0 · 1 control

ISO 27001:2022 · 1 control

  • 8.22 Segregation of networks
  • NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage
  • 03.13.06 Network Communications - Deny by Default - Allow by Exception

NIST SP 800-172 · 1 control

  • 3.13.1e Create Diversity in System Components to Limit Malicious Code Propagation
  • SC-7(5) SC-7(5) Boundary Protection | Deny by Default: Allow by Exception
  • SC-7(5) SC-7(5) Boundary Protection | Deny by Default: Allow by Exception

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in SC - System and Communications Protection

You are reading one control. How much of FedRAMP Moderate have you already done?

FedRAMP Moderate SC-7(5) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP Moderate your existing evidence covers. Hold ISO 27002:2022 and 182 of 323 FedRAMP Moderate controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 348 were rejected on the ISO 27002:2022 pair alone.

Query this from an agent

The graph holds this control, the 40 it maps to, and the evidence behind each claim, over MCP and REST.