5.1.2 Roles and responsibilities for performing activities in Requirement 5 are documented, assigned, and understood
Roles and responsibilities for performing activities in Requirement 5 are documented, assigned, and understood.
4
artefacts
0
held by a system
3
at each review
hard
to go live
Identity provider / directory
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
- Documented descriptions of roles for Requirement 5 activities, covering deployment, signature currency, alert triage and the periodic evaluation of components not at risk · Identity provider / directory
- Assignment records naming who holds each role · Identity provider / directory
- Interview confirmation that assigned personnel understand their day to day anti-malware duties · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- Escalation path for malware detections, showing who acts outside business hours · 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
- Alert triage assigned to a shared mailbox with no individual accountable for response
- Signature and engine currency assumed to be the vendor's responsibility with nobody checking it
- No owner for the periodic evaluation of components deemed not at risk, so it never happens
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 sheet5.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 · 5.2.1 An anti-malware solution(s) is deployed on all system components, except for those system components identified in periodic evaluations per Requirement 5.2.3 that concludes the system components are not at risk from malware