164.310(a)(2)(iii) Access Control and Validation Procedures (Addressable)
Implement procedures to control and validate access to facilities based on role or function, including visitor control and access to software programs for testing and revision.
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
- Periodic access review of physical zones · Physical access / facilities
governing documentDocuments that govern the control
- Visitor procedures · Policy repository / GRC workspace
- Role-to-zone mapping · Policy repository / GRC workspace
- Badge access reports · 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
- All staff have facility-wide access
- Visitor escorts not enforced
- Physical access reviews not performed
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 sheet164.310(a)(2)(ii) Facility Security Plan (Addressable) · 164.310(a)(2)(iv) Maintenance Records (Addressable)