AIS-01 Application and Interface Security Policy and Procedures
Keep an approved application security policy set that directs how applications are planned, delivered and supported, communicate it to development and operations staff, and refresh it at least annually.
4
artefacts
0
held by a system
1
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
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- The annual review record · Document repository
governing documentDocuments that govern the control
- The approved application security policy with approver and effective date · Policy repository / GRC workspace
- Evidence the policy reached development and operations teams · Policy repository / GRC workspace
- Supporting standards the policy points to, such as a secure coding standard · 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
- Policy written for a previous development model and never updated for current delivery practice
- Development teams unaware the policy exists
- Annual review missed
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 sheetA&A-06 Remediation · AIS-02 Application Security Baseline Requirements