I&S-07 Migration to Cloud Environments
Move servers, services, applications or data into cloud environments only over secure, encrypted channels that use current, approved protocols.
Source: CSA CCM v4.1, I&S-07. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CSA CCM v4.1 in the compliance library.
Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Migration logs or transfer tool configuration showing encrypted transfer · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Migration plan stating transfer method and encryption · Policy repository / GRC workspace
- Approved protocol list with versions · Policy repository / GRC workspace
- Inventory of migration targets · Policy repository / GRC workspace
First move
Common gaps auditors find
- Bulk transfers over unencrypted channels for speed
- Outdated TLS versions allowed on migration endpoints
- Physical transfer appliances shipped without encryption
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 sheetI&S-06 Segmentation and Segregation · I&S-08 Network Architecture Documentation