AIS-03 Application Security Metrics
Measure application security with technical and operational metrics that tie back to business objectives, security requirements and compliance obligations.
4
artefacts
1
held by a system
0
at each review
moderate
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Evidence metrics drove a decision or action · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- The defined application security metric set with each metric traced to an objective or obligation · Policy repository / GRC workspace
- Recent metric reports and the audience they went to · Policy repository / GRC workspace
- Thresholds or targets set against each metric · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Policy repository / GRC workspace); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Metrics collected because the tool produces them, with no link to any objective
- Reports produced but never read by anyone who can act
- No target, so the metric cannot say whether performance is acceptable
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-02 Application Security Baseline Requirements · AIS-04 Secure Application Design and Development