PO.1.3 Communicate Requirements to Third-Party Providers
Communicate the organization's software security requirements to all third parties who provide commercial software components for reuse.
2
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
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
- Security requirements communicated to third-party component providers · Policy repository / GRC workspace
- Contract/agreement clauses · 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
- Third-party security expectations undocumented
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.1.2 Implement Security Requirements in the Toolchain · PO.2.1 Roles and Responsibilities for Secure Development