Cross-Framework Mapping

Virginia CDPAvsUtah Consumer Privacy Act

See exactly how Virginia CDPA controls map to Utah Consumer Privacy Act. Pre-computed mappings, identified gaps, and coverage analysis.

22
Controls Mapped
13
Gaps Found
54%
Coverage

Need this as a report you can hand to an assessor? A coverage crosswalk for this pair can be built to order.

According to the TheArtOfService Compliance Knowledge Graph:

Virginia CDPA maps to Utah Consumer Privacy Act with 54% coverage across 19 directly mapped controls. Analysis of 35 Virginia CDPA controls identifies 16 compliance gaps, primarily concentrated in VCDPA 59.1-579 to 580: Data Protection Assessments and Processors.

Source: TheArtOfService Knowledge Graph | 35 controls analysed | 692 frameworks | 306K+ cross-framework mappings

Control Mappings

Showing 20 of 22 mapped controls across 8 domains. Sign up to explore all 306K+ mappings across 692 frameworks.

VCDPA 59.1-575 to 576: Definitions, Scope and Exemptions(2 mappings)

VCDPA-59-1-576Applicability Threshold for Controllers
§13-61-102Scope and Applicability Thresholds
VCDPA-59-1-576-EXEMPTEntity and Data Level Exemptions
§13-61-304Statutory Exemptions for Specific Data and Activities

VCDPA 59.1-577: Consumer Rights(5 mappings)

VCDPA-59-1-577-A1Consumer Right to Confirm and Access Personal Data
§13-61-201Consumer Right to Confirm and Access Personal Data
VCDPA-59-1-577-A3Right to Delete Personal Data
§13-61-201(1)(b)Right to Delete Personal Data Provided by Consumer
VCDPA-59-1-577-A4Right to Data Portability
§13-61-201(1)(c)Right to Data Portability
VCDPA-59-1-577-A5-SALERight to Opt Out of Sale of Personal Data
§13-61-201(1)(d)Right to Opt Out of Sale of Personal Data
VCDPA-59-1-577-A5-TARGETEDRight to Opt Out of Targeted Advertising
§13-61-201(1)(e)Right to Opt Out of Targeted Advertising

VCDPA 59.1-578: Controller Duties(8 mappings)

VCDPA-59-1-578-NONDISCRIMNondiscrimination for Rights Exercise
§13-61-302(5)Non-Discrimination for Exercising Rights
VCDPA-59-1-578-OPTOUT-DISCLOSUREDisclosure of Sale and Targeted Advertising Activities
§13-61-302(3)Sale and Targeted Advertising Disclosure
VCDPA-59-1-578-PRIVACYNOTICEPrivacy Notice Content Requirements
§13-61-302(1)Privacy Notice Requirements
VCDPA-59-1-578-RESPONSEResponse Timing and Authentication2 targets
§13-61-202Authentication of Consumer Requests
§13-61-203Response Timeline and Appeals Absence
VCDPA-59-1-578-SECURITYReasonable Data Security Practices
§13-61-301(1)Controller Duty of Data Security
VCDPA-59-1-578-SENSITIVE-OPTINSensitive Data Opt In Consent2 targets
§13-61-302(2)Biometric and Precise Geolocation Express Consent
§13-61-302(4)Sensitive Data Notice and Opt-Out (No Opt-In)

VCDPA 59.1-579 to 580: Data Protection Assessments and Processors(1 mappings)

VCDPA-59-1-579-PROCESSOR-DUTIESProcessor Duties to Assist Controller
§13-61-303Processor Duties and Controller-Processor Contracts

VCDPA 59.1-581 to 582: De-identified Data and Exceptions(1 mappings)

VCDPA-59-1-581-DEIDENTDeidentified Data Standards
§13-61-301(2)Deidentified Data Obligations

VCDPA 59.1-583 to 584: Enforcement(3 mappings)

VCDPA-59-1-583-CURE-SUNSET30 Day Cure Period and 2025 Sunset
§13-61-40230-Day Cure Period (Permanent, No Sunset)
VCDPA-59-1-584-ENFORCEMENTAttorney General Exclusive Enforcement2 targets
§13-61-402(3)Civil Penalties and Damages
§13-61-403Attorney General Enforcement and Notice

+2 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 692 frameworks.

Create Free Account →

Free forever, no credit card required

Coverage crosswalk

A Virginia CDPA to Utah Consumer Privacy Act crosswalk, built to order

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which Utah Consumer Privacy Act controls your existing Virginia CDPA work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.

Virginia CDPA into Utah Consumer Privacy Act
Not published yet

This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.

If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.

Utah Consumer Privacy Act into Virginia CDPA
Not published yet

This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.

If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.

Virginia CDPA to Utah Consumer Privacy Act (built to order)
$299
per framework pair, one time
  • Every evidenced control, with the reasoning behind it
  • Every gap, with what it requires
  • Its level of review stated plainly, not a bare number

Why this page shows two different percentages. The 54% in the header counts how many Virginia CDPA controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many Utah Consumer Privacy Act controls are actually evidenced, after a pass that argued against each mapping and kept only what survived. They answer different questions and they are not meant to agree.

A crosswalk narrows the work. It does not replace an audit, and your assessor may take a different view on individual controls. Mappings between frameworks are judgements, not text printed in either standard, which is why every claim in the report shows its reasoning. Questions go to support@theartofservice.com.

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 692 frameworks, at a fraction of consulting costs.

$0/forever

Free

  • 692 framework browser
  • Cross-framework mappings (306K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$149/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between Virginia CDPA and Utah Consumer Privacy Act?

Virginia CDPA has 35 controls across its framework, while Utah Consumer Privacy Act covers 26 controls. Direct mapping analysis identifies 19 overlapping controls (54% coverage). The frameworks diverge most significantly in VCDPA 59.1-579 to 580: Data Protection Assessments and Processors, where 3 Virginia CDPA controls have no direct Utah Consumer Privacy Act equivalent.

How many controls map between Virginia CDPA and Utah Consumer Privacy Act?

Of 35 total Virginia CDPA controls, 19 map directly to Utah Consumer Privacy Act controls, representing 54% coverage. The remaining 16 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping Virginia CDPA to Utah Consumer Privacy Act?

16 Virginia CDPA controls have no direct equivalent in Utah Consumer Privacy Act. The highest concentration of gaps is in VCDPA 59.1-579 to 580: Data Protection Assessments and Processors with 3 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between Virginia CDPA and Utah Consumer Privacy Act?

The domain with the highest gap count is VCDPA 59.1-579 to 580: Data Protection Assessments and Processors (3 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.