Quality, Expert-Derived Cybersecurity Documentation To Keep Organizations Secure, Compliant & Resilient  |  Got Questions? +1-307-241-8740
ComplianceForge

What Does the CCPA Cybersecurity Audit Assess for Antivirus and Antimalware Protections (§ 7123(c)(9))?

Short Answer

CCPA regulation § 7123(c)(9) requires the cybersecurity audit to assess, if applicable, antivirus and antimalware protections. Article 9 does not name a product type, so the auditor evaluates whether malware protection covers the systems that process personal information and how it is managed and monitored.

CCPA § 7123(c)(9) at a Glance

  • Regulation: California Consumer Privacy Act (CCPA) regulations, California Code of Regulations, Title 11, Division 6, Chapter 1, Article 9 (Cybersecurity Audits).
  • Section: 11 CCR § 7123(c)(9) Antivirus and Antimalware Protections, one of the 18 components in § 7123(c) Scope of Cybersecurity Audit and Audit Report.
  • Status: New. Added by the CCPA Updates, Cybersecurity Audits, Risk Assessments, ADMT and Insurance regulations, effective January 1, 2026.
  • Who it applies to: Businesses whose processing of consumers' personal information presents significant risk to consumers' security under § 7120(b).
  • When it is assessed: If applicable. The auditor decides which § 7123(c) components apply to the business's information system (§ 7123(b)(2)), and the report must identify them (§ 7123(e)(2)).
  • Deadlines: First cybersecurity audit report due April 1, 2028, April 1, 2029 or April 1, 2030 depending on annual gross revenue (§ 7121). Certification of completion due by April 1 after each audit year (§ 7124).

Component (9) is one line, but coverage matters more than the label. Servers, endpoints and cloud workloads that process personal information or can provide access to it are part of the information system the audit examines.

Malware protection connects to other components: the hardware and software inventory in § 7123(c)(4) shows where protection should be installed, and alerts feed incident response under § 7123(c)(17).

What Does CCPA § 7123(c)(9) Say?

The following is the text of 11 CCR § 7123(c)(9), shown with the § 7123(c) lead-in, from the final regulation text published by CalPrivacy and effective January 1, 2026. Only the formatting has been adjusted for readability.

  • (c) The cybersecurity audit must assess the following components, if applicable:
  • (9) Antivirus and antimalware protections.

Source: CalPrivacy, CCPA Updates, Cybersecurity Audits, Risk Assessments, ADMT and Insurance Regulations (final regulation text). Authority cited: Section 1798.185, Civil Code. Reference: Section 1798.185, Civil Code.

How Does CCPA § 7123(c)(9) Map to the Secure Controls Framework (SCF)?

The SCF publishes a NIST IR 8477 Set Theory Relationship Mapping (STRM) between the CCPA as amended by the CPRA (statute and regulations as of January 2026) and SCF version 2026.3. It maps CCPA § 7123(c)(9) to 1 SCF control through 1 relationship (1 "equal").

How to read the mapping: each relationship runs from the CCPA text to the SCF control. "Equal" means the CCPA requirement and the SCF control are semantically equivalent. The strength of relationship runs from 1 (nominal) to 10 (strongest), where 5 is moderately strong and 10 is typically reserved for "equal" and "subset of" relationships.

  • END-04 Malicious Code Protection (Antimalware). Equal (strength 10): 7123(c)(9). SCF control: Mechanisms exist to utilize antimalware, or similar technologies, to detect and eradicate malicious code.

Mapping taken from the STRM published with SCF version 2026.3. Download it at no cost: SCF STRM for the CCPA and CPRA (2026). The SCF explains the method in its Set Theory Relationship Mapping (STRM) guidance.

Common Pitfalls With CCPA § 7123(c)(9)

The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:

  • Coverage gaps. Servers, Linux hosts and cloud workloads are often missed when protection is rolled out to laptops first.
  • Disabled or outdated agents. Agents that are switched off or not updating leave gaps that inventory reconciliation can reveal.
  • Alerts nobody reviews. Detections need triage and follow-up to protect personal information.

What Is Reasonable Evidence for CCPA § 7123(c)(9)?

Article 9 does not publish a fixed evidence list. Under § 7122(d), audit findings must rely primarily on specific evidence such as documents reviewed, sampling and testing, and interviews, and under § 7122(g) the business and the auditor must keep all documents relevant to each audit for at least five years.

The SCF Evidence Request List (ERL) ties evidence artifacts to SCF controls. ERL items linked to the SCF controls mapped to CCPA § 7123(c)(9) include:

  • E-END-01 Endpoint Security Tools. Documented evidence of endpoint security tools employed by the organization to ensure secure, compliant and resilient Technology Assets, Applications and/or Services (TAAS) (e.g., antimalware, FIM, etc.).
  • E-END-03 Antimalware Scanning Results. Documented evidence of scan results from malicious code protection mechanisms.
  • E-MON-02 Malware Activity. Documented evidence of malware activity being logged and included as part of the centralized event log collection and review/analysis process.

Records specific to CCPA § 7123(c)(9) that typically show the requirement is met:

  • Coverage report. Malware protection deployment compared with the hardware and software inventory.
  • Update status. Engine and signature update status across protected systems.
  • Alert handling records. Detections, quarantine actions and follow-up.
  • Tamper protection settings. Settings that stop users or malware from disabling protection.

Which ComplianceForge Documents Support CCPA § 7123(c)(9)?

ComplianceForge documentation helps a business build and document the cybersecurity program the audit assesses. Under § 7122(a)(2), the auditor itself must not prepare the business's documents or implement its program. The following documents support CCPA § 7123(c)(9):

  • SCF Policies & Standards (SCRP): editable SCF-based cybersecurity policies, standards and control objectives covering all 34 SCF domains.
  • SCF Procedures (CSOP): editable SCF-aligned cybersecurity procedures covering all 34 SCF domains, mapped 1-to-1 to the SCRP standards.

Frequently Asked Questions (FAQ)

Does the CCPA require EDR? No specific technology is named. § 7123(c)(9) covers antivirus and antimalware protections, and an endpoint detection and response platform is one way to provide them.

Which systems need malware protection for the CCPA cybersecurity audit? Systems that process personal information or can provide access to it, including servers and cloud workloads, since they are part of the information system the audit examines.

What evidence shows antimalware coverage? Typical evidence includes deployment reports reconciled with the asset inventory, update status and alert handling records.

How does this component relate to the asset inventory? The hardware and software inventory assessed under § 7123(c)(4) shows which systems should be protected, so the two are usually reviewed together.

Bottom Line on CCPA § 7123(c)(9)

Antimalware is familiar ground, which is why gaps go unnoticed. Reconcile coverage against the inventory, keep agents current and tamper-protected, and make sure alerts are handled.

Authoritative sources:

This page reproduces California regulatory text from Title 11 of the California Code of Regulations. It is educational, not legal advice. Last reviewed: 2026-11-16.

Other CCPA Article 9 Requirements

Previous: § 7123(c)(8) Network Monitoring and Defenses. Next: § 7123(c)(10) Segmentation of an Information System. The rest of the CCPA and CPRA, including Article 10 risk assessments, is covered in the CCPA and CPRA Compliance Guide.