EvidenceSheet

7.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

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.

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

  • Distribution evidence to system owners, managers who approve access and administrators who provision it · Identity provider / directory

governing documentDocuments that govern the control

  • Documented policies and operational procedures for restricting access to system components and cardholder data by business need to know · Policy repository / GRC workspace
  • Review record showing the access control procedures are kept up to date · Policy repository / GRC workspace
  • Evidence of use, such as access request records that follow the documented procedure · 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

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 sheet

6.5.6 Test data and accounts removed before production · 7.1.2 Roles and responsibilities for performing activities in Requirement 7 are documented, assigned, and understood