PO.3.1 Supporting Toolchain Selection
Select tools that meet the security needs of the development environment. Evaluate tools for their own security and for the assurance they provide about the software they process.
4
artefacts
0
held by a system
2
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
none for this control
periodic reviewEvidence produced at each review
- Vendor security assessments · Vendor register / contract repository
- Configuration review for chosen tools · Cloud console / configuration management
governing documentDocuments that govern the control
- Tool selection criteria document · Document repository
- Deprecation policy for unsupported tools · 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
- tools selected on price without security review
- vendor self attestations not validated
- deprecated tools remain in pipelines
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.2.3 Obtain Management Commitment to Secure Development · PO.3.2 Toolchain Configuration and Integration