IVS-07 Migration to Cloud Environments
Migrate servers, services, applications and data to cloud environments over encrypted channels using current, approved protocols only.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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
- Evidence of the channels used for recent migrations · Document repository
governing documentDocuments that govern the control
- The migration procedure specifying approved protocols · Policy repository / GRC workspace
- The approved protocol list and its currency · Document repository
- Records of any migration performed outside the standard path · 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
- Bulk data migrations performed over unencrypted or legacy channels for speed
- Approved protocol list not maintained, so deprecated versions remain approved
- Migration procedure exists but large one-off moves bypass it
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-06 Segmentation and Segregation · IVS-08 Network Architecture Documentation