ISO 27001:2022 · Technological controls
ISO 27001:2022 8.31: Separation of development, test and production environments
ISO 27001:2022 8.31 covers Separation of development, test and production environments. The held text names 5 evidence records for it, the first being Statement of Applicability entry for control A.8.31, showing inclusion or justified exclusion, implementation status and the risks it.... The common gap an assessor flags is Developers hold standing administrative access to production.
Development, test and production environments are to be kept apart and secured. Purpose (stated in ISO/IEC 27002:2022): keeps development and testing work from harming production systems and data. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 8.31.
What evidence supports 8.31?
- Annex A technological controlStatement of Applicability entry for control A.8.31, showing inclusion or justified exclusion, implementation status and the risks it treats
- Annex A technological controlArchitecture showing development, test and production in separate domains, accounts or subscriptions
- Annex A technological controlDocumented promotion rules and authorization records for moving software into production
- Annex A technological controlAccess rights showing that no individual can change both development and production without review, or monitoring that detects it
- Annex A technological controlEvidence that development tools are absent from production and environment labels are displayed
Where this requirement comes from
This is our own statement of ISO 27001:2022 8.31, read from the copy we hold (licensed complete copy) and stated in our words, not the standard verbatim. The framework as we hold it.
Common gaps an assessor flags
- Developers hold standing administrative access to production
- Test environments contain unmasked copies of production data with weak access controls
- Development and test tools are unpatched because they are seen as low risk
- Production and test consoles look identical, leading to changes in the wrong environment
How it maps to SOC 2
- CC8.1 high Separating development, test and production is core change control hygiene.
A link is a topical overlap with a confidence and a reason. It does not establish that meeting one requirement satisfies the other, and it is not certification.