CCPA/CPRA
Service providers, contractors and third parties – CCPA/CPRA

CCPA/CPRA 1798.100(d): Put an agreement in place with every recipient of personal information

A business that sells or shares data with a third party, or hands data to service providers or contractors for business purposes, must have an agreement that limits the data to specified purposes, binds the recipient to the Act and to the same level of protection, lets the business take reasonable steps to check compliant use, requires the recipient to say if it can no longer comply, and lets the business, on notice, stop and remedy unauthorised use.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 2 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

GDPR · 1 control

Virginia CDPA · 1 control

  • 59.1-579 B Mandatory controller and processor contract terms

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Service providers, contractors and third parties – CCPA/CPRA

You are reading one control. How much of CCPA/CPRA have you already done?

CCPA/CPRA 1798.100(d) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CCPA/CPRA your existing evidence covers. Hold GDPR and 17 of 89 CCPA/CPRA controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the GDPR pair alone.

Query this from an agent

The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.