EvidenceSheet
CSA CCM v4.1 · AIS - Application & Interface Security

AIS-08 API Security

Processes, procedures and technical measures for protecting APIs are defined and implemented, and they are revisited for improvement every year as a minimum or when a significant change occurs.

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

6
artefacts
2
held by a system
2
at each review
moderate
to go live
Identity provider / directory
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

  • API gateway or WAF configuration showing authentication, throttling and schema validation · Identity provider / directory
  • API access and error logs feeding monitoring · SIEM / log platform

periodic reviewEvidence produced at each review

  • API security test results (for example tests against the OWASP API Security Top 10) · Source control / CI pipeline
  • Annual review record of the API security measures · Document repository

governing documentDocuments that govern the control

  • API security standard covering authentication, authorisation, rate limiting and input validation · Policy repository / GRC workspace
  • API inventory listing internal, partner and public APIs with owners · Policy repository / GRC workspace

First move

Start with the 2 of 6 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

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

AIS-07 Application Vulnerability Remediation · BCR-01 Business Continuity Management Policy and Procedures