Contact Us
Services
Services
Crypto and Digital Trust
Crypto and Digital Trust
Schellman Training
Schellman Training
Sustainability Services
Sustainability Services
AI Services
AI Services
About Us
About Us
Leadership Team
Leadership Team
Corporate Social Responsibility
Corporate Social Responsibility
Careers
Careers
Strategic Partnerships
Strategic Partnerships

How to Leverage Your Current Compliance Program for CCPA Cybersecurity Audits

Compliance and Certification | Privacy Assessments

Published: May 28, 2026

The California Consumer Privacy Act (CCPA) has fundamentally reshaped how organizations approach data protection, but the recent cybersecurity audit regulation has added a new layer of complexity to compliance obligations. For many companies, this represents both a challenge and an opportunity to build a unified compliance strategy that addresses multiple regulations, standards, and frameworks simultaneously.

You likely already understand the CCPA’s core privacy requirements if your organization operates in California or serves California residents, but the cybersecurity audit provisions introduce a compliance dimension that extends beyond privacy into operational security.  

While the audit may, at first glance, be seen as yet another checkbox to mark, what makes it particularly valuable is that the requirements don't exist in isolation. They share remarkable overlap with established security frameworks like NIST Cybersecurity Framework, ISO 27001, SOC 2, and others.

The real power lies in mapping these requirements strategically. Rather than treating the CCPA audit mandate as just another separate compliance task, forward-thinking organizations are recognizing it as a catalyst for building a cohesive security and compliance program. By understanding how the CCPA audit requirements align with broader security standards, your organization can create processes and controls that satisfy multiple regulatory demands simultaneously to reduce duplication, streamline audits, and ultimately build stronger security practices.

In this blog post, Emily Heintz, Privacy Technical Fellow, outlines the CCPA cybersecurity audit regulation and examines how they map to other major frameworks and standards to get maximum value from a single, unified effort.

California's Privacy Laws Explained: CCPA, CPRA, and CalPrivacy 

The CCPA represented a watershed moment in American privacy legislation as the first comprehensive state-level privacy law in the United States, which became the standard for privacy compliance. The law, which went into effect January 1, 2020, granted California residents rights over their personal information, and initiated a shift in the balance of power between American consumers and corporations.  

In 2020, the CCPA was amended by the California Privacy Rights Act (CPRA), which expanded and refined the law, including the creation of a dedicated enforcement agency, the California Privacy Protection Agency or CalPrivacy.

CalPrivacy, which has been operational since 2023, is tasked with developing regulations that interpret and operationalize the CCPA, investigating consumer complaints, bringing enforcement actions against violators, and providing guidance to help businesses understand their obligations.  

Notably, CalPrivacy has the authority to issue civil penalties of up to $2,663 per violation or $7,988 per intentional violation*. The cybersecurity audit regulation was approved by CalPrivacy on July 24, 2025, as part of their tasks to interpret the law, and the regulation became effective January 1, 2026.

*Please note: this amount is adjusted every other year to reflect increases in the Consumer Price Index. You can monitor those updates here

The Cybersecurity Audit Requirements 

The cybersecurity audit regulation mandates that businesses who pose a “significant risk” to consumers must assess and document their security posture to create accountability for the systems and practices that protect personal information.  

Significant risk is defined as: 

  • The business derives 50% or more of its annual revenue from selling or sharing consumers’ personal information; OR  
  • The business has an annual gross revenue more than $26,625,000* in the preceding calendar year, and:  
  • Processed the personal information of 250,000 or more consumers or households in the preceding calendar year; OR  
  • Processed the sensitive personal information of 50,000 consumers in the preceding calendar year
*Please note: this amount is adjusted every other year to reflect increases in the Consumer Price Index. You can monitor those updates here

The Cybersecurity Audit Requirements 

The cybersecurity audit regulation mandates that businesses who pose a “significant risk” to consumers must assess and document their security posture to create accountability for the systems and practices that protect personal information.  

Significant risk is defined as: 

  • The business derives 50% or more of its annual revenue from selling or sharing consumers’ personal information; OR  
  • The business has an annual gross revenue more than $26,625,000* in the preceding calendar year, and:  
  • Processed the personal information of 250,000 or more consumers or households in the preceding calendar year; OR 
  • Processed the sensitive personal information of 50,000 consumers in the preceding calendar year 

*Please note: this amount is adjusted every other year to reflect increases in the Consumer Price Index. You can monitor those updates here.

The regulation is not prescriptive and is intended rather to allow for interpretation based on the business’ size, complexity, and the nature and scope of its processing activities as well as room to continually improve to match the fast pace of emerging technology and their associated threats.  

There are 18 components and subcomponents in-scope of the audit, including but not limited to: 

  • Access and authentication, including multi-factor authentication that is resistant to phishing attacks and restrictions for privileged accounts;  

  • Personal information, hardware, and software inventories;
  • Secure configurations, including software updates, securing on-prem and cloud-based environments, masking, patch management, and change management; 
  • Vulnerability scans, penetration tests, and vulnerability disclosure and reporting; 
  • Audit log management; 
  • Secure development and coding best practices; 
  • Retention and disposal of personal information; 
  • Cybersecurity awareness, education, and training; and   
  • Incident response 

The timeline for completing the audit is dependent on the business’ revenue, as outlined below: 

Revenue Criteria Cybersecurity Audit Deadline
Annual gross revenue for 2026 was more than $100 million as of January 1, 2027.

The audit is required to cover the period of January 1, 2027, through January 1, 2028.
April 1, 2028
Annual gross revenue for 2027 was between $50 million and $100 million as of January 1, 2028.

The audit is required to cover the period of January 1, 2028, through January 1, 2029.
April 1, 2029
Annual gross revenue for 2028 was less than $50 million as of January 1, 2029.

The audit is required to cover the period of January 1, 2029, through January 1, 2030.
April 1, 2030
The processing of personal information poses a significant risk as of January 1 of the preceding year.

The audit is required to cover January 1 of the current year, through January 1 of the following year. The report must be completed by April 1 of the following year.
Thereafter 

How the Cybersecurity Audit Requirements Map to Other Compliance Frameworks 

As mentioned, the cybersecurity audit requirements do not exist in a vacuum, and many readers may feel relieved after reviewing the required controls above and realizing their extent of overlap across frameworks.  

To assist organizations that may be strategizing how to satisfy the new obligation while juggling their other compliance objectives, Schellman has provided an analysis of how the CCPA requirements map to SOC 2 criteria, NIST CSF 2.0, and ISO 27001:2022, below:

CCPA Cybersecurity Component

 
Multi-factor authentication that is resistant to phishing attacks
SOC 2 Criteria CC6.1
NIST CSF 2.0 PR.AA-03
ISO 27001:2022 5.178.5
Strong, unique passwords or passphrases
SOC 2 Criteria CC6.1
NIST CSF 2.0 PR.AA-03
ISO 27001:2022 5.17
Encryption of personal information, at-rest and in-transit
SOC 2 Criteria CC6.7
NIST CSF 2.0 PR.DS-01PR.DS-02
ISO 27001:2022 5.148.24
Restricting employee, independent contractor, and other personnel privileges and access to personal information to what is necessary to perform the respective job functions of each individual
SOC 2 Criteria CC6.1CC6.2CC6.3
NIST CSF 2.0 PR.AA-01PR.AA-05
ISO 27001:2022 5.155.188.38.4
Revoking employee, independent contractor, and other personnel privileges and access when their job functions no longer require them, including when their employment or contract is terminated
SOC 2 Criteria CC6.1CC6.2CC6.3
NIST CSF 2.0 PR.AA-01PR.AA-05
ISO 27001:2022 5.187.2
Restricting service provider or contractor privileges and access to personal information to what is necessary for the specific business purpose(s) set forth in the written contract
SOC 2 Criteria CC6.1CC6.2CC6.3
NIST CSF 2.0 PR.AA-01PR.AA-05PR.DS-10
ISO 27001:2022 5.155.185.195.208.38.4
Restricting third parties' privileges and access to whom the business sells or shares personal information to that which is necessary for the limited and specified purpose(s) set forth within the written contract
SOC 2 Criteria CC6.1CC6.2CC6.3
NIST CSF 2.0 PR.AA-01PR.AA-05PR.DS-10
ISO 27001:2022 5.145.155.188.3
Restricting the number of privileged accounts
SOC 2 Criteria CC6.1
NIST CSF 2.0 PR.AA-01PR.AA-05
ISO 27001:2022 5.155.188.2
Restricting privileged accounts' access functions to only those necessary to perform the account-holder's job
SOC 2 Criteria CC6.1CC6.3
NIST CSF 2.0 PR.AA-01PR.AA-05
ISO 27001:2022 5.155.188.28.38.4
Restricting the use of privileged accounts to when they are necessary to perform functions
SOC 2 Criteria CC6.1CC6.3
NIST CSF 2.0 PR.AA-01PR.AA-05
ISO 27001:2022 5.155.188.28.38.4
Using a privileged-access management solution
SOC 2 Criteria CC6.1
NIST CSF 2.0 PR.AA-01PR.AA-05
ISO 27001:2022 8.2
Restricting and monitoring the creation of new accounts for employees, independent contractors, or other personnel; service providers or contractors; and privileged accounts, and ensuring that the accounts' access and privileges are limited
SOC 2 Criteria CC6.1CC6.2CC6.3
NIST CSF 2.0 PR.AA-01PR.AA-05
ISO 27001:2022 5.155.165.175.188.2
Restricting and monitoring physical access to personal information
SOC 2 Criteria CC6.4
NIST CSF 2.0 PR.AA-01PR.AA-05PR.AA-06
ISO 27001:2022 5.155.187.2
Personal information inventories
SOC 2 Criteria C1.1
NIST CSF 2.0 ID.AM-07
ISO 27001:2022 5.9
Classification and tagging of personal information
SOC 2 Criteria C1.1
NIST CSF 2.0 ID.AM-05ID.AM-07
ISO 27001:2022 5.125.13
Hardware and software inventories
SOC 2 Criteria CC3.2
NIST CSF 2.0 ID.AM-01ID.AM-02
ISO 27001:2022 5.9
The use of allowlisting
SOC 2 Criteria CC6.6
NIST CSF 2.0 PR.PS-05
ISO 27001:2022 8.78.208.21
Hardware and software approval processes
SOC 2 Criteria CC7.1
NIST CSF 2.0 ID.AM-08
ISO 27001:2022 8.98.198.26
Preventing the connection of unauthorized hardware and devices to the business' information system
SOC 2 Criteria CC6.6CC6.7CC6.8CC7.1
NIST CSF 2.0 DE.CM-01DE.CM-03DE.CM-06DE.CM-09
ISO 27001:2022 8.18.98.208.21
Secure configuration of hardware and software
SOC 2 Criteria CC6.1CC6.8CC7.1
NIST CSF 2.0 PR.PS-01DE.CM-09
ISO 27001:2022 8.98.19
Software updates and upgrades
SOC 2 Criteria CC6.1CC6.8
NIST CSF 2.0 PR.PS-02
ISO 27001:2022 8.18.88.19
Securing on-premises and cloud-based environments
SOC 2 Criteria CC6.4CC6.6CC6.8
NIST CSF 2.0 PR.DS-01PR.DS-02PR.DS-10PR.DS-11PR.IR-01PR.IR-03PR.IR-04
ISO 27001:2022 5.237.38.98.208.21
Masking the sensitive personal information and other personal information as appropriate by default in applications
ISO 27001:2022 8.11
Security patch management
SOC 2 Criteria CC6.8CC7.1CC7.5
NIST CSF 2.0 PR.PS-02
ISO 27001:2022 8.88.19
Change management
SOC 2 Criteria CC7.1CC8.1
NIST CSF 2.0 ID.RA-07PR.PS-06
ISO 27001:2022 8.32
Internal and external vulnerability scans
SOC 2 Criteria CC4.1CC7.1
NIST CSF 2.0 ID.RA-01ID.RA-06ID.IM-04
ISO 27001:2022 8.88.16
Internal and external penetration testing
SOC 2 Criteria CC4.1CC7.1
NIST CSF 2.0 ID.IM-02
ISO 27001:2022 8.88.168.258.34
Internal and external vulnerability disclosure and reporting
SOC 2 Criteria CC4.1CC7.1
NIST CSF 2.0 ID.RA-06ID.RA-08
ISO 27001:2022 8.8
Audit log management:
  • Centralized storage
  • Retention
  • Monitoring
SOC 2 Criteria CC7.2
NIST CSF 2.0 PR.PS-04DE.AE-02DE.AE-03
ISO 27001:2022 8.158.16
Network monitoring and defenses
SOC 2 Criteria CC6.8CC7.1
NIST CSF 2.0 DE.CM-01
ISO 27001:2022 8.168.208.21
Technologies, such as bot-detection, intrusion-detection, and intrusion-prevention
SOC 2 Criteria CC6.8
NIST CSF 2.0 DE.CM-01DE.CM-09
ISO 27001:2022 8.168.21
Data loss prevention system
SOC 2 Criteria CC6.7
NIST CSF 2.0 DE.CM-03DE.CM-09
ISO 27001:2022 8.12
Antivirus and anti-malware
SOC 2 Criteria CC6.8
NIST CSF 2.0 RS.MI-01
ISO 27001:2022 8.78.16
Segmentation of information systems
SOC 2 Criteria CC6.6
NIST CSF 2.0 PR.IR-01
ISO 27001:2022 8.22
Limitation and control of ports, services, and protocols
SOC 2 Criteria CC6.6
NIST CSF 2.0 ID.AM-03
ISO 27001:2022 8.98.208.21
Cybersecurity awareness
SOC 2 Criteria CC2.2
NIST CSF 2.0 PR.AT-01
ISO 27001:2022 6.3
How the business maintains current knowledge of changing cybersecurity threats and countermeasures
SOC 2 Criteria CC2.2
NIST CSF 2.0 ID.RA-02
ISO 27001:2022 5.6
Cybersecurity education and training, including training for each employee, independent contractor, and any other personnel to whom the business provides access to its information system
SOC 2 Criteria CC1.4CC2.2
NIST CSF 2.0 PR.AT-01
ISO 27001:2022 6.3
Secure development and coding best practices
SOC 2 Criteria CC8.1
NIST CSF 2.0 PR.PS-06
ISO 27001:2022 8.258.268.278.288.298.308.31
Code reviews
SOC 2 Criteria CC8.1
NIST CSF 2.0 ID.RA-01
ISO 27001:2022 8.288.29
Code testing
SOC 2 Criteria CC8.1
NIST CSF 2.0 ID.RA-01
ISO 27001:2022 8.288.29
Oversight of service providers, contractors, and third parties
SOC 2 Criteria CC4.1CC9.2
NIST CSF 2.0 DE.CM-06GV.SC-05GV.SC-06GV.SC-07
ISO 27001:2022 5.22
Retention schedules and proper disposal of personal information no longer required to be retained through:
  • Shredding
  • Erasing
  • Otherwise modifying the personal information in those records to make it unreadable or undecipherable
SOC 2 Criteria C1.2P4.3
NIST CSF 2.0 ID.AM-08
ISO 27001:2022 8.108.11
Incident response management and incident response plan
SOC 2 Criteria CC7.4CC7.5
NIST CSF 2.0 ID.IM-04RS.MA-01RS.MA-02RS.MA-03RS.MA-04RS.MA-05RS.AN-03RS.AN-06RS.AN-07RS.AN-08RS.CO-02RS.CO-03RS.MI-01RS.MI-02RC.RP-01RC.RP-02RC.RP-04RC.RP-05RC.RP-06RC.CO-03RC.CO-04
ISO 27001:2022 5.245.255.265.275.286.8
Incident response tests
SOC 2 Criteria CC4.1CC7.4CC7.5
NIST CSF 2.0 ID.IM-02ID.IM-04
ISO 27001:2022 5.24
Business continuity and disaster-recovery plans
SOC 2 Criteria CC9.1A1.2A1.3
NIST CSF 2.0 ID.IM-04
ISO 27001:2022 5.295.30
Data recovery capabilities
SOC 2 Criteria CC9.1A1.2A1.3
NIST CSF 2.0 RC.RP-01RC.RP-02RC.RP-03RC.RP-04RC.RP-05RC.RP-06
ISO 27001:2022 5.265.308.138.14
Backups
SOC 2 Criteria CC9.1A1.2A1.3
NIST CSF 2.0 PR.DS-11
ISO 27001:2022 8.13

Moving Forward with Your CCPA Cybersecurity Audit 

Understanding the CCPA cybersecurity audit requirements and mapping them to your organization's existing security framework is one thing. Implementing a unified compliance strategy is another. The complexity lies not just in understanding the regulations, but in translating them into concrete security practices, audit procedures, and documentation processes that work for your specific organization, industry, and risk profile. 

This is where expertise matters. Navigating the intersection of CCPA compliance, cybersecurity best practices, and alignment with multiple frameworks requires specialized knowledge and experience. That's where Schellman comes in. Our team can help you conduct comprehensive readiness assessments that evaluate your existing security controls against CCPA audit requirements, identifying gaps and opportunities for improvement before official audits begin.  

Organizations interested in conducting a readiness assessment against the regulation can contact us today for more information on how Schellman can assist in navigating their complex security and privacy regulatory environment. 

In the meantime, check out additional privacy compliance insights in these helpful resources:  

About Emily Heintz

Emily Heintz is a technical fellow with Schellman based in New Orleans, Louisiana. She currently manages privacy assessments and certifications across the full suite of offerings, including CBPR / PRP, ISO 27701, EU Cloud Code of Conduct, and Microsoft SSPA. Prior to joining Schellman in 2020, Emily worked as a Project Manager on the U.S. Privacy team at a Fortune 50 retailer focusing on designing controls to comply with the CCPA and conducting privacy reviews of emerging technology solutions. She also has experience implementing a privacy impact assessment and artificial intelligence impact assessment process at a Future 50 recognized company. She is an active member of the International Association of Privacy Professionals (IAPP), is a Fellow of Information Privacy (FIP), holding both the CIPP/US and CIPM certifications, and has obtained her CISSP.