PL-8 Security and Privacy Architectures
Builds supply chain considerations into architecture, including diversity, provenance and the ability to replace a supplier.
3
artefacts
0
held by a system
1
at each review
hard
to go live
Vendor register / contract 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
- Architecture decision records · Cloud console / configuration management
governing documentDocuments that govern the control
- Architecture artefacts addressing supplier dependency and diversity · Vendor register / contract repository
- Analysis of substitutability for critical components · 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
- architecture locks the organization to a single supplier with no analysis
- diversity considered for hardware but not software 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 sheet