A.5.8 Information security in project management
Bake security requirements into every project from initiation, whatever the delivery method.
15
artefacts
1
held by a system
6
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Issue log entry for security defects · SIEM / log platform
periodic reviewEvidence produced at each review
- Stakeholder security requirement sign-off register · Policy repository / GRC workspace
- Risk assessment worksheet for the project · Policy repository / GRC workspace
- Design review minutes with security focus · Policy repository / GRC workspace
- Peer review report on secure coding practices · Document repository
- Change request record with security impact analysis · Ticketing / ITSM
- Approved change implementation evidence · Document repository
governing documentDocuments that govern the control
- Project charter including security objectives · Policy repository / GRC workspace
- Security requirements specification document · Document repository
- Risk treatment plan linked to security controls · Policy repository / GRC workspace
- Risk register entry showing identified security risks · Policy repository / GRC workspace
- Implementation checklist confirming security controls · Document repository
- Project closure report summarizing security outcomes · Document repository
- Final security testing results · Document repository
- Lessons-learned document highlighting security findings · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Security requirements added after project start
- Risk assessments not linked to project milestones
- Design reviews lacking documented security focus
- Change records missing security impact analysis
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 sheetA.5.7 Threat intelligence · A.5.9 Inventory of information and other associated assets