Skip to main content

AB 869 — California

State agencies: information security: Zero Trust architecture.

Passed one chamber 20252026 session Assembly

This page lists STATE bills only. Open States, our source for this data, tracks state legislatures -- it has no visibility into city councils, county commissions or school boards. We don't yet have a free, storable source for local measures; see the About page for why.

Summary

Existing law establishes the Office of Information Security within the Department of Technology for the purpose of ensuring the confidentiality, integrity, and availability of state systems and applications and to promote and protect privacy as part of the development and operations of state systems and applications to ensure the trust of the residents of this state. Existing law requires specified state entities to implement the policies and procedures issued by the office. Existing law additionally authorizes the office to conduct, or require to be conducted, an independent security assessment of every state agency, department, or office, as specified. Existing law requires every state agency, as specified, to certify, by February 1 annually, to the office that the agency is in compliance with all adopted policies, standards, and procedures and to include a plan of action and milestones, as specified.

This bill would require every state agency, as specified, and subject to specified exceptions, to implement Zero Trust architecture for all data, hardware, software, internal systems, and essential third-party software, including for on-premises, cloud, and hybrid environments, to achieve prescribed levels of maturity based on the Cybersecurity and Infrastructure Security Agency (CISA) Maturity Model, as defined, by specified dates. In implementing Zero Trust architecture, the bill would require state agencies to prioritize the use of solutions that comply with, are authorized by, or align to federal guidelines, programs, and frameworks and, at a minimum, prioritize multifactor authentication for access to all systems and data, enterprise endpoint detection and response solutions, and robust logging practices, as specified. The bill would require the office's chief to develop or revise uniform technology policies, standards, and procedures for use by all state agencies in Zero Trust architecture to achieve specified maturity levels on all systems in the State Administrative Manual and Statewide Information Management Manual. The bill would require the chief to update requirements for existing annual reporting activities to collect information relating to the progress state agencies are making to increase internal defenses of agency systems. The bill would authorize the chief to update existing annual reporting activities to include how a state agency is progressing with respect to specified goals. The bill would also state the Legislature's intent that the bill's provisions be implemented in a manner consistent with the state's timely compliance with requirements that are conditions to receipt of federal funds. The bill would also make related legislative findings and declarations.

Official abstract, as published by the legislature.

  • AB 869 is a bill in the California Assembly, 20252026 session, introduced February 19, 2025.
  • Current status: passed one chamber.
  • Most recent action (August 29, 2025): In committee: Held under submission.
  • 5 recorded votes; the most recent, on August 18, 2025, passed 7-0.
  • Subjects: Stateagencies, ZeroTrustarchitecture, informationsecurity.

Contact your legislator about this bill

Bill text & documents

Sponsors

Cosponsors (1): Irwin

History

  1. Introduced, completed
  2. Passed Assembly, completed
  3. Passed Senate, in progress
  4. Sent to Governor, not reached yet
  5. Signed into law, not reached yet
  1. Assembly Read first time. To print.
  2. Assembly From printer. May be heard in committee March 22.
  3. Assembly Referred to Com. on P. & C.P.
  4. Assembly Do pass and be re-referred to the Committee on [Appropriations] with recommendation: To Consent Calendar

    15 yes 0 no Passed, 100% yes

  5. Assembly From committee: Do pass and re-refer to Com. on APPR. with recommendation: To Consent Calendar. (Ayes 15. Noes 0.) (April 1). Re-referred to Com. on APPR.
  6. Assembly In committee: Set, first hearing. Referred to suspense file.
  7. Assembly From committee: Do pass. (Ayes 14. Noes 0.) (May 23).

    Do pass.: 14 yes 0 no, 1 other Passed, 100% yes

  8. Assembly Read second time. Ordered to third reading.
  9. Assembly Read third time. Passed. Ordered to the Senate. (Ayes 78. Noes 0. Page 1860.) Milestone

    AB 869 Irwin Assembly Third Reading: 78 yes 0 no, 1 other Passed, 100% yes

  10. Senate In Senate. Read first time. To Com. on RLS. for assignment.
  11. Senate Referred to Com. on G.O.
  12. Senate From committee: Do pass and re-refer to Com. on APPR. with recommendation: To Consent Calendar. (Ayes 15. Noes 0.) (July 8). Re-referred to Com. on APPR.

    Do pass, but first be re-referred to the Committee on [Appropriations] with the recommendation: To Consent Calendar: 15 yes 0 no Passed, 100% yes

  13. Senate In committee: Referred to suspense file.

    Placed on suspense file: 7 yes 0 no Passed, 100% yes

  14. Senate In committee: Held under submission. Latest

Source: Open States. Last checked November 17, 2026. How we keep this accurate ›