IPY-03 Secure Interoperability and Portability Management
Use cryptographically secure network protocols that follow industry standards when data is managed, imported or exported.
Source: CSA CCM v4.1, IPY-03. 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
- Approved protocol list (for example, TLS 1.2 or later, SFTP) for management, import and export interfaces · Document repository
- TLS configuration scan results for export and management endpoints · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Records showing insecure protocols disabled · Document repository
governing documentDocuments that govern the control
- Policy for secure transmission of requests and data · Policy repository / GRC workspace
First move
Common gaps auditors find
- Legacy FTP or unencrypted endpoints still available for bulk import
- Weak cipher suites allowed on management APIs
- No periodic scan of endpoint protocol settings
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