6.1.1 All security policies and operational procedures that are identified in Requirement 6 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
All security policies and operational procedures that are identified in Requirement 6 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 and acknowledgement evidence for development, quality assurance and release personnel · Source control / CI pipeline
governing documentDocuments that govern the control
- Documented policies and operational procedures for secure software development, vulnerability identification and change management · Policy repository / GRC workspace
- Review record showing the development security procedures are kept up to date against current languages and platforms · Policy repository / GRC workspace
- Evidence of use, such as change tickets and code review records citing 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 written for the previous technology stack and never revised for current frameworks and pipelines
- Formal change procedure documented while emergency and pipeline driven changes proceed under no procedure at all
- Third party and outsourced developers not covered by the documented 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 sheet5.4.1 Processes and automated mechanisms are in place to detect and protect personnel against phishing attacks · 6.1.2 Roles and responsibilities for performing activities in Requirement 6 are documented, assigned, and understood