9.1.1 All security policies and operational procedures that are identified in Requirement 9 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
All security policies and operational procedures that are identified in Requirement 9 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 facilities, reception, operations and any third party providing physical security · Physical access / facilities
governing documentDocuments that govern the control
- Documented policies and operational procedures for physical access to the cardholder data environment, media handling and point of interaction device protection · Policy repository / GRC workspace
- Review record showing the physical security procedures are kept up to date · Policy repository / GRC workspace
- Evidence of use, such as visitor logs and media transport records completed under the 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
- Procedures held by security with reception and facilities staff, who actually perform the activities, unaware of them
- Written for the primary data centre with branch sites, offices and storage locations uncovered
- Media handling and device inspection procedures thinner than the entry control procedures
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.6.3 Passwords/passphrases for any application and system accounts are protected against misuse as follows: • Passwords/passphrases are changed periodically (at the frequency defined in the entity's targeted risk analysis, which is performed according to all · 9.1.2 Roles and responsibilities for performing activities in Requirement 9 are documented, assigned, and understood