IPY-03 Secure Interoperability and Portability Management
Use cryptographically secure, standardised network protocols for managing data and for importing and exporting it.
4
artefacts
2
held by a system
0
at each review
easy
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
- Protocol configuration for management, import and export paths · Cloud console / configuration management
- Testing evidence such as a transport security scan · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Evidence deprecated or non-standard protocols are disabled · Policy repository / GRC workspace
- The protocol standard and version in use · Policy repository / GRC workspace
First move
Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.
Common gaps auditors find
- Legacy transfer protocols retained for a single customer or system
- Encryption present but with weak cipher suites still enabled
- Import and export paths overlooked while the main service is hardened
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 sheetIPY-02 Application Interface Availability · IPY-04 Data Portability Contractual Obligations