RS.CO-03 Information is shared with designated internal and external stakeholders
Information is shared with designated internal and external stakeholders. Control from NIST Cybersecurity Framework 2.0 framework, domain: RS - Respond.
5
artefacts
1
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
- Internal sharing logs across business units · SIEM / log platform
periodic reviewEvidence produced at each review
- Records of intelligence shared with ISAC and peers · Document repository
- Sharing effectiveness review records · Document repository
governing documentDocuments that govern the control
- Information sharing agreements with partners · Vendor register / contract repository
- Sharing playbook with content controls · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Sharing agreements signed but unused
- Sharing one way (consume only)
- Internal sharing fragmented across teams
- Effectiveness reviewed only after incidents
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 sheetRS.CO-02 Internal and external stakeholders are notified of incidents · RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared