7.1.2 Roles and responsibilities for performing activities in Requirement 7 are documented, assigned, and understood
Roles and responsibilities for performing activities in Requirement 7 are documented, assigned, and understood.
4
artefacts
0
held by a system
4
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 7 activities, covering definition of the access control model, approval of privileges and periodic review · Identity provider / directory
- Assignment records naming who holds each role · Identity provider / directory
- Interview confirmation that assigned personnel understand their day to day access control responsibilities · Identity provider / directory
- Evidence that authority to approve privileged access is explicitly assigned and bounded · Identity provider / directory
governing documentDocuments that govern the control
none for this control
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
- Approval authority assumed by line managers with no documented assignment or limit
- Ownership of the access control model itself unassigned, so it ages without review
- Administrators provision access on request with nobody accountable for whether need to know was applied
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.1.1 All security policies and operational procedures that are identified in Requirement 7 are: • Documented. • Kept up to date. • In use. • Known to all affected parties · 7.2.1 An access control model is defined and includes granting access as follows: • Appropriate access depending on the entity's business and access needs. • Access to system components and data resources that is based