Many security incidents are not cyber-attacks.
They are changes made in the wrong environment.
Annex A 8.31 exists to help organisations reduce operational and security risk by separating development, testing, and production environments, protecting live systems and real data from accidental or unauthorised impact.
This control is about containment and discipline, not slowing delivery.

Annex A 8.31 focuses on separating environments used for development, testing, and live operations.
In practice, this includes:
The control does not require physical separation.
It supports logical, technical, or procedural separation appropriate to risk.
Development and testing activities naturally involve:
If these activities interact directly with production:
Annex A 8.31 helps organisations preserve confidentiality, integrity, and availability by isolating risky activities from live operations.
This control replaces ISO 27001:2013 Annex A 12.1.4 and A 14.2.6, consolidating environment separation into a single, clearer requirement.
Organisations should clearly define:
Environment purpose should be obvious to users, including clear labelling in menus and interfaces, to reduce the likelihood of error.
Ambiguity leads to mistakes.
Separation may be achieved through:
The degree of separation should reflect:
Higher risk environments justify stronger segregation.
Access to each environment should be:
Individuals should not routinely have unrestricted access across development and production environments.
Where access overlaps, additional approval and oversight helps reduce risk.
This supports separation of duties and accountability.
Testing activities are generally more appropriate in non-production environments.
Where testing in production is unavoidable:
Unplanned testing in live environments introduces unnecessary risk.
Production data is particularly sensitive.
Organisations should consider:
Uncontrolled use of live data is a common source of data protection failures.
Movement of software, configuration, or code between environments should be:
This helps ensure:
Direct changes in production bypass essential safeguards.
Development tools such as:
are generally unnecessary in production environments.
Limiting these tools reduces attack surface and accidental misuse.
Although non-production, development and test environments still require protection.
Organisations should consider:
Lower criticality does not mean no security.
Access and activity across environments should be:
Monitoring supports detection of misuse, misconfiguration, and policy drift.
Annex A 8.31 applies equally to:
Suppliers should operate segregated environments and follow agreed access and data-handling rules.
External delivery does not reduce internal accountability.
Environment separation failures are predictable and preventable.
Annex A 8.31 is about keeping instability away from live systems.
When development, test, and production environments are separated effectively:
Development is where experimentation belongs.
Production is where control matters most.
Annex A 8.31 ensures organisations do not blur that line.
We can help you understand your actual security needs and even if we cant help we can point you in the right direction
Talk to a security expert today