PW.4.4 Verify Acquired Components Meet Security Requirements
Verify that third party and open source components meet the same security requirements applied to in house code. Use static analysis, dependency analysis, and known vulnerability databases to support the decision.
4
artefacts
1
held by a system
1
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Software Composition Analysis configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Component approval workflow records · Document repository
governing documentDocuments that govern the control
- Vulnerability database integration · Policy repository / GRC workspace
- License compliance checks · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- vulnerability scans run but findings never break the build
- license risks not assessed
- newly added dependencies bypass review
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 sheetPW.4.2 Maintain Well-Secured In-House Components · PW.5.1 Secure Coding Practices