CCR §7050 Service Provider and Contractor Obligations
A service provider or contractor shall only process PI on behalf of a business for a business purpose specified in the written contract. It shall not retain, use, or disclose PI for any purpose other than the business pu
4
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
- Service provider acknowledgement of restrictions in contract · Policy repository / GRC workspace
- Subcontractor flowdown agreements · Policy repository / GRC workspace
- Consumer request assistance procedure (forwarding requests, providing data extracts) · Policy repository / GRC workspace
- Combining-data prohibition controls · 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
- Service provider commingles client data
- No request assistance workflow
- Subcontractors not bound to same restrictions
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 sheetCCR §7027 Requests to Limit Use of Sensitive PI Handling · CCR §7060 Consumer Identity Verification