Azure Security Benchmark ASBv3-GS-2: Define and implement enterprise segmentation/separation of duties strategy

What else in your programme already covers this

This control maps to 52 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.

FedRAMP High · 5 controls

AC-1 Policy and Procedures
AC-5 Separation of Duties
CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))
PL-8 Security and Privacy Architectures
SC-7 Boundary Protection

FedRAMP Moderate · 5 controls

AC-1 Policy and Procedures
AC-5 Separation of Duties
CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))
PL-8 Security and Privacy Architectures
SC-7 Boundary Protection

NIST SP 800-53 Rev 5 · 4 controls

NIST800-AC-1 AC-1 Policy and Procedures
NIST800-AC-5 AC-5 Separation of Duties
NIST800-PL-8 PL-8 Security and Privacy Architectures
NIST800-SC-7 SC-7 Boundary Protection

AWS Well-Architected Security Pillar · 3 controls

SEC01-BP01 Separate workloads using accounts
SEC03-BP08 Share resources securely within your organization
SEC11-BP06 Deploy software programmatically

C5 (Germany) · 3 controls

C5-COS-06 Segregation of data traffic in jointly used network environments
C5-OIS-04 Segregation of Duties
C5-OPS-24 Separation of Datasets in the Cloud Infrastructure

CIS Controls v8 · 3 controls

CIS-12.2 Establish and Maintain a Secure Network Architecture
CIS-16.8 Separate Production and Non-Production Systems
CIS-3.12 Segment Data Processing and Storage Based on Sensitivity

CMMC 2.0 · 3 controls

AC.L2-3.1.4 Separation of Duties
SC.L2-3.13.1 Boundary Protection
SC.L2-3.13.3 Role Separation

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

CCM-IAM-04 Separation of Duties
CCM-IVS-05 Production and Non-Production Environments
CCM-IVS-06 Segmentation and Segregation

ISO 27001:2022 · 3 controls

5.3 Segregation of duties
8.22 Segregation of networks
8.31 Separation of development, test and production environments

ISO 27002:2022 · 3 controls

5.3 Segregation of duties
8.22 Segregation of networks
8.31 Separation of development, test and production environments

PCI DSS 4.0 · 3 controls

11.4.5 11.4.5 Annual segmentation penetration testing
6.5.3 6.5.3 Separate pre-production from production
6.5.4 6.5.4 Separate roles between production and pre-production

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

ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles
ANSSI-HYG-19 Segment the Network and Partition the Zones

NIST SP 800-171 Rev 3 · 2 controls

03.01.04 Separation of Duties
03.13.01 Boundary Protection

NIST SP 800-172 · 2 controls

3.1.1e Dual Authorization for Sensitive System Operations
3.13.4e Physical and Logical Isolation Techniques

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-22 Network segmentation (Excellent)

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-3 Information Security Category

HIPAA Security Rule · 1 control

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

ISO 27701:2019 · 1 control

6.6.1 Business requirements of access control

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

NIST SP 800-161 Rev 1 · 1 control

161R1-AC-5 Separation of Duties

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.3 CC6.3 Role-based access, least privilege and segregation of duties

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 Azure Security Benchmark have you already done?

Azure Security Benchmark ASBv3-GS-2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.

If you hold NIST SP 800-53 Rev 583.5% covered · 14 gaps If you hold FedRAMP Moderate78.8% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.172.9% covered · 23 gaps If you hold ISO 27002:202269.4% covered · 26 gaps If you hold C5 (Germany)65.9% covered · 29 gaps If you hold ISO 27001:202261.2% covered · 33 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