6.1.2 Roles and responsibilities for performing activities in Requirement 6 are documented, assigned, and understood
Roles and responsibilities for performing activities in Requirement 6 are documented, assigned, and understood.
4
artefacts
0
held by a system
3
at each review
hard
to go live
Source control / CI pipeline
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
- Assignment records naming who holds each role · Identity provider / directory
- Interview confirmation that development personnel understand their day to day security responsibilities · Source control / CI pipeline
- Evidence that responsibility for public facing web application protection is explicitly assigned · Source control / CI pipeline
governing documentDocuments that govern the control
- Documented descriptions of roles for Requirement 6 activities, covering secure coding, vulnerability ranking, patching and change approval · 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
- Vulnerability ranking assigned to nobody, so severity is taken from the scanner default
- Security responsibilities described for the security team rather than for the developers who perform the activities
- Release approval authority undocumented, so changes ship on informal sign off
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 sheet6.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 · 6.2.1 Bespoke and custom software are developed securely, as follows: • Based on industry standards and/or best practices for secure development. • In accordance with PCI DSS (for example, secure authentication and logging). • Incorporating