IVS-05 Production and Non-Production Environments
Keep production workloads and the environments used for development and testing apart, so that activity in one cannot reach the systems or data of the other.
4
artefacts
0
held by a system
3
at each review
hard
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Architecture evidence of separation, such as distinct accounts, networks or clusters · Identity provider / directory
- Evidence non-production cannot reach production data or services · Cloud console / configuration management
- Review of any permitted connection between them · Cloud console / configuration management
governing documentDocuments that govern the control
- Access control differences between the environments · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Shared identity or network paths that make separation nominal
- Non-production holding production data, defeating the purpose of separation
- Separation at the network layer only while the control plane is shared
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetIVS-04 OS Hardening and Base Controls · IVS-06 Segmentation and Segregation