8.1.2 Roles and responsibilities for performing activities in Requirement 8 are documented, assigned, and understood
Roles and responsibilities for performing activities in Requirement 8 are documented, assigned, and understood.
5
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
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
- Engineering control commissioning records (guarding, LEV, interlocks) · Document repository
- PPE program records (selection, fit, inspection, replacement) · Document repository
governing documentDocuments that govern the control
- Documented hierarchy of controls procedure · Policy repository / GRC workspace
- Elimination and substitution case files (chemical removed, automation introduced) · Document repository
- Administrative controls (rotation, signage, procedures) · 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
- Default to PPE without justification
- Engineering controls not maintained
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 sheet8.1.1 All security policies and operational procedures that are identified in Requirement 8 are: • Documented. • Kept up to date. • In use. • Known to all affected parties · 8.2.1 All users are assigned a unique ID before access to system components or cardholder data is allowed