AIS-02 Application Security Baseline Requirements
Define and keep current the minimum security requirements each class of application must satisfy before it is built or released.
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Documented application security baselines per application class · Document repository
- Evidence baselines are checked before release, such as a gated checklist · Policy repository / GRC workspace
- A change history showing baselines being updated · Document repository
- Named owner for each baseline · Policy repository / GRC workspace
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
- One generic baseline applied to application types with very different risk
- Baselines documented but never enforced at release
- Baseline last updated years ago and no longer reflects the current stack
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 sheetAIS-01 Application and Interface Security Policy and Procedures · AIS-03 Application Security Metrics