IPY-02 Application Interface Availability
Provide cloud customers with application interfaces they can call programmatically to retrieve their own data.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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 the interface works and returns the customer's full dataset · Document repository
governing documentDocuments that govern the control
- The published interface documentation for customer data retrieval · Document repository
- Access control on the interface · Policy repository / GRC workspace
- Coverage of the data types a customer would expect to retrieve · Document repository
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
- Interface returns a subset of the customer's data with no statement of what is excluded
- Retrieval available only by raising a support request
- Interface documented but not maintained against the current data model
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-01 Interoperability and Portability Policy and Procedures · IPY-03 Secure Interoperability and Portability Management