What evidence do auditors commonly ask for on IPY-02 Application Interface Availability?

Published API catalogue and documentation for data retrieval; Customer-facing export guide listing data objects and formats available; Test record of a full data export through the API; Change notices for API versions and deprecations.

What is the most common gap auditors find on IPY-02?

Some data types (logs, configurations, metadata) not exportable by API

CSA CCM v4.1 · IPY - Interoperability & Portability

`IPY-02` Application Interface Availability

Give service customers application interfaces through which they can pull their own data programmatically, so that it can move to or work with other systems.

Source: CSA CCM v4.1, IPY-02. 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.

artefacts

held by a system

at each review

moderate

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

Customer-facing export guide listing data objects and formats available · Document repository

periodic reviewEvidence produced at each review

Test record of a full data export through the API · Document repository

governing documentDocuments that govern the control

Published API catalogue and documentation for data retrieval · Document repository
Change notices for API versions and deprecations · Document repository

First move

Start with the 1 of 4 artefacts that already live in a system (Document repository); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Some data types (logs, configurations, metadata) not exportable by API
Export available only through a support ticket
API documentation out of date with the live service

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 sheet

IPY-01 Interoperability and Portability Policy and Procedures · IPY-03 Secure Interoperability and Portability Management