ISO 27001:2022 8.31: Separation of development, test and production environments

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 12 controls

NIST800-AC-6 AC-6 Least Privilege
NIST800-CM-2 CM-2 Baseline Configuration
NIST800-SA-15 SA-15 Development Process, Standards, and Tools
NIST800-SA-3 SA-3 System Development Life Cycle
NIST800-SC-2 SC-2 Separation of System and User Functionality
NIST800-SC-3 SC-3 Security Function Isolation
NIST800-SC-32 SC-32 System Partitioning
NIST800-SC-36 SC-36 Distributed Processing and Storage
NIST800-SC-38 SC-38 Operations Security
NIST800-SC-4 SC-4 Information in Shared System Resources
NIST800-SC-49 SC-49 Hardware-enforced Separation and Policy Enforcement
NIST800-SC-50 SC-50 Software-enforced Separation and Policy Enforcement

PCI DSS 4.0 · 6 controls

2.2.3 2.2.3 Primary functions with different security levels managed
6.2.1 6.2.1 Secure development of bespoke and custom software
6.5.5 6.5.5 No live PANs in pre-production
6.5.6 6.5.6 Remove test data and accounts before production
6.5.3 6.5.3 Separate pre-production from production
6.5.4 6.5.4 Separate roles between production and pre-production

CIS Controls v8 · 5 controls

CIS-12.2 Establish and Maintain a Secure Network Architecture
CIS-12.8 Establish and Maintain Dedicated Computing Resources for All Administrative Work
CIS-16.1 Establish and Maintain a Secure Application Development Process
CIS-16.8 Separate Production and Non-Production Systems
CIS-3.12 Segment Data Processing and Storage Based on Sensitivity

COBIT 2019 · 3 controls

BAI03.03 BAI03.03 Develop solution components
BAI03.07 BAI03.07 Prepare for solution testing
BAI07.04 BAI07.04 Establish a test environment

FedRAMP High · 3 controls

CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))
SA-3 System Development Life Cycle
SC-39 Process Isolation

FedRAMP Moderate · 3 controls

CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))
SA-3 System Development Life Cycle
SC-39 Process Isolation

ISO 27701:2019 · 3 controls

6.11 Systems acquisition, development and maintenance
6.11.3 Test data
6.9.1 Operational procedures and responsibilities

AWS Well-Architected Security Pillar · 2 controls

SEC01-BP01 Separate workloads using accounts
SEC11-BP07 Regularly assess security properties of the pipelines

Azure Security Benchmark · 2 controls

ASBv3-DS-3 Secure DevOps infrastructure
ASBv3-GS-2 Define and implement enterprise segmentation/separation of duties strategy

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

CCM-AIS-06 Automated Secure Application Deployment
CCM-IVS-05 Production and Non-Production Environments

ISO 27001:2013 · 2 controls

A.12.1.4 Separation of development, testing and operational environments
A.14.2.6 Secure development environment

ISO 27002:2022 · 2 controls

8.26 Application security requirements
8.31 Separation of development, test and production environments

SOC 2 · 2 controls

SOC2-CC6.1 CC6.1 Logical access security over protected information assets
SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-24 Non-persistent virtualised sandboxed environment (Very Good)

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

AUCDR-IS-3 Securely manage information assets over their lifecycle

C5 (Germany) · 1 control

C5-DEV-10 Separation of environments

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

CFTC-SS-5 Systems Development and Quality Assurance Category

EU AI Act · 1 control

EUAI-Art.59 Further processing of personal data for developing certain AI systems in the public interest in the AI regulatory sandbox

HIPAA Security Rule · 1 control

164.310(a)(2)(iii) Access Control and Validation Procedures (Addressable)

ISO/IEC 42001:2023 · 1 control

8.3 AI risk treatment

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

NIST SP 800-161 Rev 1 · 1 control

161R1-CM-2 Baseline Configuration

NIST SP 800-172 · 1 control

3.13.1e Create Diversity in System Components to Limit Malicious Code Propagation

NIST SP 800-218 · 1 control

SP800-218-PO.5.1 Secure Development Environment Implementation

NIST SP 800-66 Rev 2 · 1 control

164.310(a)(2)(iii) Access Control and Validation Procedures (Addressable)

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 ISO 27001:2022 have you already done?

ISO 27001:2022 8.31 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27001:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27001:2022 controls already carry evidence.

If you hold NIST SP 800-53 Rev 584.9% covered · 14 gaps If you hold ISO 27001:201383.9% covered · 15 gaps If you hold FedRAMP Moderate80.6% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.2% covered · 24 gaps If you hold C5 (Germany)69.9% covered · 28 gaps If you hold NIST Cybersecurity Framework 2.063.4% covered · 34 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. 170 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 each Browse the graph free