SA-9 External system services
Requires providers of external system services to meet the organization's security and privacy requirements and to operate organization-defined controls, requires oversight and user roles and responsibilities for those s
4
artefacts
0
held by a system
1
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
- Ongoing monitoring evidence such as reviewed assurance reports or service reviews · SIEM / log platform
governing documentDocuments that govern the control
- Contracts or agreements imposing the organizational requirements and defined controls · Vendor register / contract repository
- Documented oversight roles and responsibilities for each external service · Policy repository / GRC workspace
- Register of external system services in use and their assessed risk · 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
- Assurance report collected once at onboarding and never reviewed again
- Shadow services adopted by teams without any oversight arrangement
- Requirements imposed contractually but nothing monitors whether they hold
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 sheetSA-8 Security and privacy engineering principles · SA-10 Developer configuration management