AWS Well-Architected Security Pillar
Infrastructure Protection

AWS Well-Architected Security Pillar SEC05-BP02: Control traffic flow within your network layers

Restrict traffic within each network layer to only the flows each workload component needs, controlling both traffic entering from external systems and traffic between internal components.

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

What else in your programme already covers this

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

CMMC 2.0 · 7 controls

FedRAMP High · 5 controls

  • AC-4 Information Flow Enforcement
  • CM-7 Least Functionality
  • SC-7 Boundary Protection
  • SC-7(12) Boundary Protection | Host-based Protection (SC-7(12))
  • SC-7(5) Deny by Default Allow by Exception

FedRAMP Moderate · 5 controls

  • AC-4 Information Flow Enforcement
  • CM-7 Least Functionality
  • SC-7 Boundary Protection
  • SC-7(12) Boundary Protection | Host-based Protection (SC-7(12))
  • SC-7(5) Deny by Default Allow by Exception

NIST SP 800-171 Rev 3 · 5 controls

  • 03.01.03 Information Flow Enforcement
  • 03.04.06 Least Functionality
  • 03.13.01 Boundary Protection
  • 03.13.04 Information in Shared System Resources
  • 03.13.06 Network Communications - Deny by Default - Allow by Exception

C5 (Germany) · 4 controls

  • C5-COS-01 Technical safeguards
  • C5-COS-02 Security requirements for connections in the Cloud Service Provider's network
  • C5-COS-03 Monitoring of connections in the Cloud Service Provider's network
  • C5-COS-04 Cross-network access

UK Cyber Essentials · 4 controls

  • CE-FW.1 Boundary Firewalls Deployed
  • CE-FW.4 Approve and Document Inbound Rules
  • CE-FW.5 Remove or Disable Unused Rules
  • CE-FW.6 Host-Based Firewall for Remote Workers

ASD Strategies to Mitigate Cyber Security Incidents · 3 controls

  • ASD37-22 Network segmentation (Excellent)
  • ASD37-25 Software firewall - inbound (Very Good)
  • ASD37-26 Software firewall - outbound (Very Good)

CIS Controls v8 · 3 controls

  • CIS-12.2 Establish and Maintain a Secure Network Architecture
  • CIS-13.4 Perform Traffic Filtering Between Network Segments
  • CIS-4.4 Implement and Manage a Firewall on Servers

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

PCI DSS 4.0 · 3 controls

  • 1.2.5 1.2.5 Allowed services, protocols and ports justified
  • 1.3.1 1.3.1 Inbound CDE traffic restricted
  • 1.3.2 1.3.2 Outbound CDE traffic restricted

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 2 controls

  • ANSSI-HYG-17 Enable and Configure the Local Firewall on Workstations
  • ANSSI-HYG-19 Segment the Network and Partition the Zones

Azure Security Benchmark · 2 controls

  • NS-1 Establish network segmentation boundaries
  • NS-2 Secure cloud services with network controls

ISO 27001:2022 · 2 controls

  • 8.20 Networks security
  • 8.22 Segregation of networks

ISO 27002:2022 · 2 controls

  • 8.20 Networks security
  • 8.21 Security of network services

NIST Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-ID.AM-03 Representations of the organization's authorized network communication and internal and external network data flows are maintained
  • NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage

NIST SP 800-161 Rev 1 · 2 controls

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-2 Secure the network and systems within the data environment

HIPAA Security Rule · 1 control

ISO 27701:2019 · 1 control

  • 6.10.1 Network security management

NIST SP 800-66 Rev 2 · 1 control

SOC 2 · 1 control

  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary

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 Infrastructure Protection

You are reading one control. How much of AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC05-BP02 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar controls already carry evidence.

If you hold NIST SP 800-53 Rev 582.5% covered · 11 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.6% covered · 16 gapsIf you hold ISO 27002:202273% covered · 17 gapsIf you hold FedRAMP Moderate69.8% covered · 19 gapsIf you hold Azure Security Benchmark65.1% covered · 22 gapsIf you hold PCI DSS 4.063.5% covered · 23 gaps

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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll AWS Well-Architected Security Pillar controls