API 1164vsOregon Consumer Privacy Act
See exactly how API 1164 controls map to Oregon Consumer Privacy Act. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
API 1164 maps to Oregon Consumer Privacy Act with 29% coverage across 13 directly mapped controls. Analysis of 24 API 1164 controls identifies 32 compliance gaps — primarily concentrated in API 1164: Systems Security.
Source: TheArtOfService Knowledge Graph | 24 controls analysed | 718 frameworks | 332K+ cross-framework mappings
Control Mappings
Showing 13 of 13 mapped controls across 8 domains. Sign up to explore all 332K+ mappings across 718 frameworks.
Access(2 mappings)
API 1164: Access Management(3 mappings)
Vulnerability(1 mappings)
Communications(1 mappings)
API 1164: Incident Response & Recovery(3 mappings)
Endpoint(1 mappings)
Safety(1 mappings)
API 1164: Supply Chain & Configuration(1 mappings)
Related Comparisons
Other API 1164 comparisons
Other Oregon Consumer Privacy Act comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 718 frameworks — at a fraction of consulting costs.
Free
- ✓ 718 framework browser
- ✓ Cross-framework mappings (332K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between API 1164 and Oregon Consumer Privacy Act?
API 1164 has 24 controls across its framework, while Oregon Consumer Privacy Act covers 8 controls. Direct mapping analysis identifies 13 overlapping controls (29% coverage). The frameworks diverge most significantly in API 1164: Systems Security, where 5 API 1164 controls have no direct Oregon Consumer Privacy Act equivalent.
How many controls map between API 1164 and Oregon Consumer Privacy Act?
Of 24 total API 1164 controls, 13 map directly to Oregon Consumer Privacy Act controls — representing 29% coverage. The remaining 32 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping API 1164 to Oregon Consumer Privacy Act?
32 API 1164 controls have no direct equivalent in Oregon Consumer Privacy Act. The highest concentration of gaps is in API 1164: Systems Security with 5 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 API 1164 and Oregon Consumer Privacy Act?
The domain with the highest gap count is API 1164: Systems Security (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
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.