5.1.1 All security policies and operational procedures that are identified in Requirement 5 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
All security policies and operational procedures that are identified in Requirement 5 are: • Documented. • Kept up to date. • In use. • Known to all affected parties.
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
- Distribution and awareness evidence for the endpoint, server and operations personnel affected · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- Documented policies and operational procedures for anti-malware protection, covering which system components are in scope and the evaluation for those deemed not at risk · Policy repository / GRC workspace
- Review record showing the anti-malware procedures are kept up to date · Policy repository / GRC workspace
- Evidence of use, such as the periodic evaluation records the procedures require · 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
- Procedures cover workstations and servers while the periodic evaluation for components deemed not at risk is undefined
- Written once and not updated when the organisation moved to container and serverless workloads
- Kept by the security team and unknown to the platform teams who build the images
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 sheet4.2.2 PAN is secured with strong cryptography whenever it is sent via end-user messaging technologies · 5.1.2 Roles and responsibilities for performing activities in Requirement 5 are documented, assigned, and understood