What evidence do auditors commonly ask for on AIS-02 Application Security Baseline Requirements?

Application security baseline document (for example authentication, logging, input validation and encryption requirements); Mapping of applications to the baseline that applies to them; Design review or release checklist showing baseline items checked; Baseline revision history with approvals; Deviation or exception records against the baseline.

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

Baseline defined but not enforced at design review or release

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

`AIS-02` Application Security Baseline Requirements

The organisation sets down and keeps up to date the baseline security requirements that applications must meet.

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

hard

to go live

Policy repository / GRC workspace

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

Baseline revision history with approvals · Cloud console / configuration management

periodic reviewEvidence produced at each review

Deviation or exception records against the baseline · Cloud console / configuration management

governing documentDocuments that govern the control

Application security baseline document (for example authentication, logging, input validation and encryption requirements) · Policy repository / GRC workspace
Mapping of applications to the baseline that applies to them · Policy repository / GRC workspace
Design review or release checklist showing baseline items checked · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

Baseline defined but not enforced at design review or release
Single generic baseline applied to applications with very different risk
Baseline not updated after new threats such as API abuse or supply chain attacks

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-01 Application and Interface Security Policy and Procedures · AIS-03 Application Security Metrics