7.3.1 An access control system(s) is in place that restricts access based on a user's need to know and covers all system components
An access control system(s) is in place that restricts access based on a user's need to know and covers all system components.
1
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Workflow diagrams for each right (access, rectification, erasure, portability, restriction, objection) · Document repository
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
- No documented process for handling each principal right (access, rectification, erasure, portability, objection)
- Identity verification for rights requests not standardised
- Response timelines not tracked against statutory deadlines
- Rights request log and outcomes not retained as evidence
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 sheet7.2.6 All user access to query repositories of stored cardholder data is restricted as follows: • Via applications or other programmatic methods, with access and allowed actions based on user roles and least privileges. • · 7.3.2 The access control system(s) is configured to enforce permissions assigned to individuals, applications, and systems based on job classification and function