CCPA/CPRA
Risk assessments (11 CCR Article 10) – CCPA/CPRA

CCPA/CPRA CCR 7150: Conduct a risk assessment before high-risk processing

Any business, whatever its size, must carry out a risk assessment before starting processing that the regulation treats as a significant privacy risk: selling or sharing personal information; processing sensitive personal information (other than routine employee administration such as payroll, benefits, work authorisation and legally required accommodation or wage reporting); using ADMT for a significant decision; automated inference about applicants, students, employees or contractors from systematic observation; automated inference from presence at a sensitive location; and processing data intended to train ADMT for significant decisions or facial, emotion or identity recognition technology. The duty applies to processing begun on or after 1 January 2026; processing already under way then must be assessed by 31 December 2027 (7155(b)).

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-580 A When a data protection assessment is required

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 Risk assessments (11 CCR Article 10) – CCPA/CPRA

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

CCPA/CPRA CCR 7150 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.