2.1.1 All security policies and operational procedures that are identified in Requirement 2 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
All security policies and operational procedures that are identified in Requirement 2 are: • Documented. • Kept up to date. • In use. • Known to all affected parties.
5
artefacts
0
held by a system
2
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
- Annual review attestation · Vendor register / contract repository
- Distribution and acknowledgement records · HR system / LMS
governing documentDocuments that govern the control
- Secure configuration policy with version control · Policy repository / GRC workspace
- Linked configuration standards · Policy repository / GRC workspace
- Training material · HR system / LMS
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
- Outdated policy
- No acknowledgement
- Missing operational detail
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 sheet1.5.1 Security controls on dual-connected computing devices · 2.1.2 Roles and responsibilities for performing activities in Requirement 2 are documented, assigned, and understood