AWS Well-Architected Security Pillar SEC05-BP01: Create network layers

What else in your programme already covers this

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

C5 (Germany) · 5 controls

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
C5-COS-05 Networks for administration
C5-COS-06 Segregation of data traffic in jointly used network environments

FedRAMP High · 5 controls

AC-17(3) Managed Access Control Points
AC-4 Information Flow Enforcement
AC-4(21) Physical or Logical Separation of Information Flows
SC-7 Boundary Protection
SC-7(3) Access Points

FedRAMP Moderate · 5 controls

AC-17(3) Managed Access Control Points
AC-4 Information Flow Enforcement
AC-4(21) Physical or Logical Separation of Information Flows
SC-7 Boundary Protection
SC-7(3) Access Points

NIST SP 800-53 Rev 5 · 4 controls

NIST800-AC-4 AC-4 Information Flow Enforcement
NIST800-PL-8 PL-8 Security and Privacy Architectures
NIST800-SC-32 SC-32 System Partitioning
NIST800-SC-7 SC-7 Boundary Protection

PCI DSS 4.0 · 3 controls

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.4 1.4.4 Cardholder data stores not reachable from untrusted networks

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

ANSSI-HYG-19 Segment the Network and Partition the Zones
ANSSI-HYG-23 Partition Internet Facing Services from the Rest of the Information System

ASD Strategies to Mitigate Cyber Security Incidents · 2 controls

ASD37-08 Deny direct internet connectivity (Excellent)
ASD37-22 Network segmentation (Excellent)

CIS Controls v8 · 2 controls

CIS-12.2 Establish and Maintain a Secure Network Architecture
CIS-3.12 Segment Data Processing and Storage Based on Sensitivity

CMMC 2.0 · 2 controls

SC.L2-3.13.1 Boundary Protection
SC.L2-3.13.5 Public-Access System Separation

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

CCM-IVS-03 Network Security
CCM-IVS-06 Segmentation and Segregation

ISO 27001:2022 · 2 controls

8.22 Segregation of networks
8.27 Secure system architecture and engineering principles

ISO 27002:2022 · 2 controls

8.20 Networks security
8.22 Segregation of networks

NIST SP 800-171 Rev 3 · 2 controls

03.01.03 Information Flow Enforcement
03.13.01 Boundary Protection

Azure Security Benchmark · 1 control

NS-1 Establish network segmentation boundaries

HIPAA Security Rule · 1 control

164.308(a)(4)(ii)(A) Isolating Health Care Clearinghouse Functions (Required if applicable)

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage

NIST SP 800-161 Rev 1 · 1 control

161R1-SC-7 Boundary Protection

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(4)(ii)(A) Isolating Health Care Clearinghouse Functions (Required if applicable)

SOC 2 · 1 control

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

UK Cyber Essentials · 1 control

CE-SCOPE.1 Scope Definition

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.

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

AWS Well-Architected Security Pillar SEC05-BP01 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 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.6% covered · 16 gaps If you hold ISO 27002:202273% covered · 17 gaps If you hold FedRAMP Moderate69.8% covered · 19 gaps If you hold Azure Security Benchmark65.1% covered · 22 gaps If 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 each Browse the graph free