SEC11-BP05 Centralize services for packages and dependencies
Use private package repositories such as CodeArtifact or ECR with curation, scanning and provenance so applications consume only approved dependencies.
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- CodeArtifact domain and repos · Document repository
- ECR repository policies · Policy repository / GRC workspace
- Approved package list · Document repository
- Vulnerability scanning on pull · 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
- direct pulls from public registries
- no SBOM
- unpatched transitive dependencies
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 sheetSEC11-BP04 Conduct code reviews · SEC11-BP06 Deploy software programmatically