PO.3.2 Toolchain Configuration and Integration
Configure and integrate development tools so they enforce the secure development policy. Treat configuration as code and version control changes to it.
4
artefacts
3
held by a system
0
at each review
easy
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration repository for CI and security tools · Source control / CI pipeline
- Drift detection alerts · SIEM / log platform
- Change approval log for tool configuration · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Rollback procedure · Policy repository / GRC workspace
First move
Automate the pull from your SIEM / log platform. Retention and alert rules exported from the SIEM; review evidence is the closed-alert record with reviewer and time.
Common gaps auditors find
- configuration drifts because changes are made in the UI
- no drift detection in place
- rollback procedure untested
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 sheetPO.3.1 Supporting Toolchain Selection · PO.3.3 Toolchain Generates Security Artifacts