
On September 29, 2025, Governor Newsom signed into law Senate Bill 53 (“SB 53” or the “Act”), officially titled the “Transparency in Frontier Artificial Intelligence Act”. This legislation is the first U.S. state statute to impose broad transparency, reporting, and whistleblower protections for developers of advanced frontier AI models. In doing so, once again, California strengthens its position as a regulatory leader in artificial intelligence by placing new obligations on large-scale developers while providing a blueprint for national and international AI oversight.
The Act targets large frontier developers including specifically any company with annual gross revenues exceeding $500 million that trains, fine-tunes, or deploys a frontier model. Under SB 53, a “frontier model” is essentially a very large, general-purpose AI engine trained on vast amounts of data so it can do many things and requires massive computer-power (i.e. more than 10²⁶ operations) to build and refine. Once an AI model crosses that scale, the developer must meet stricter transparency, safety, and governance obligations under in order to avoid creating a potentially catastrophic risk including loss of human control, bioweapon assistance, or large-scale damage. SB 53 applies specifically to large frontier developers and their models focusing on a narrow group of high-performing AI systems rather than the entire AI industry.
SB 53 requires that large frontier model developers create, implement, and publish on their websites a “frontier AI framework.” This framework must describe how the developer adheres to national and international standards, industry best practices, governance controls, risk assessment protocols, third-party evaluations, and cybersecurity measures. Moreover, before deploying a new frontier model, developers must publish a transparency report that includes: the release date, intended uses, supported languages, and conditions of use of the model; summaries of any catastrophic-risk assessments; The identity and role of third-party evaluators; and steps taken to fulfill the obligations of the frontier AI framework. The aforementioned notwithstanding, developers may redact trade secrets, cybersecurity, or national security information but must explain and retain the redacted content for at least five years.
Large frontier developers must also protect employees who disclose concerns that their employer’s activities pose potentially catastrophic risk or otherwise violate SB 53. To that end, frontier model developers may not retaliate against any employees who report concerns to internal channels, the California Attorney General, or federal authorities. The statute also (i) mandates reporting mechanisms through the California Office of Emergency Services for critical safety incidents, such as loss of model control, unauthorized access, or deceptive behavior; and (ii) establishes a consortium within the California Government Operations Agency tasked with creating a framework for CalCompute, a public computing cluster intended to promote safe and equitable AI research.
There are several steps that large frontier developers themselves should take in order to comply with SB 53 including: (i) Publishing a compliant frontier AI framework; (ii) Establishing governance, risk-assessment, and third-party evaluation protocols; (iii) Updating their frameworks annually and disclosing material changes; (iv) Maintaining internal reporting channels for employees and ensuring protection for whistleblowers; (v) Publishing transparency reports for each covered model; (vi) Retain redacted materials for five years; and (vii) Monitoring ongoing legislative and regulatory developments to ensure consistent compliance moving forward.
Legal, compliance, and product development teams should work collaboratively to review whether a company constitutes a “large frontier developer” and/or is developing a “frontier model.” In addition, covered entities should evaluate disclosure workflows, website design, and version control; map data flows from model training to deployment and documenting audit trails; revise internal whistleblower and non-retaliation policies; update contracts with third-party evaluators to ensure audit access; create governance dashboards that track model releases, incident reports, redactions, and transparency updates; train staff on AI risk management and regulatory obligations; and integrate AI compliance into broader privacy and governance programs under the California Consumer Privacy Act (“CCPA”) and California Privacy Rights Act (“CPRA”).
SB 53 does not specify per-instance civil penalties but does authorize state enforcement mechanisms and public transparency obligations that carry reputational and regulatory risk. Non-compliance by a covered entity could trigger investigations, whistleblower actions, or conflicts with federal AI regulations. The law also aims to strike a balance between promoting innovation and protecting the public, and showcases California’s leadership in AI research while acknowledging the need to mitigate potential harm from large, advanced models. By emphasizing transparency instead of overly prescriptive regulation, SB 53 establishes a compliance baseline that encourages responsible innovation. Passage of this law is a clear indication that AI governance has entered a new era of accountability in California with compliance and transparency at the forefront of doing business in the AI sector.
Developers and deployers of high-compute AI models should promptly assess whether they fall under SB 53. Moreover, businesses using frontier AI should review their contracts and audit rights with vendors and partners. And companies with a global footprint should evaluate how SB 53 interacts with the EU AI Act and other emerging international legal and regulatory frameworks. Executives of large frontier developers should treat AI governance as a core regulatory and risk management issue, and in-house counsel should prepare for new compliance challenges, ongoing oversight, and potential disputes arising from transparency and whistleblower provisions.
Ultimately, SB 53 marks a turning point in artificial intelligence regulation in California. By prioritizing transparency and safety, and providing explicit whistleblower protections, the law places accountability at the center of the AI development process. Frontier developers must align their internal frameworks with these new statutory requirements and recognize that AI risk is no longer only a technological matter. Rather, it is a legal, regulatory, and enterprise governance issue as well.
- Partner
Jeffrey R. Glassman is Partner and Chair of the Intellectual Property and Technology Law Department and has earned the esteemed designation of Certified Information Privacy Professional (CIPP/US).
Jeffrey has spent the last two ...
Subscribe
Recent Posts
- California’s SB 53: A New Era of Frontier AI Transparency and Accountability Introduction | By: Jeffrey R. Glassman
- California Enacts AB 656: Enhancing Account Deletion Rights for Social Media Users | By: Jeffrey R. Glassman
- The High Price of Delay: California's SB 261 and the Triple Penalty | By: Jared W. Slater, Esq.
- New Law Adds Job Categories to Required Annual Pay Data Reporting and Imposes Mandatory Penalties for Non-Reporting | By: Kelly O. Scott
- How Limited Is The Ultra Vires Exception To The Barton Doctrine? | By: Peter A. Davidson
- SB 642 Clarifies Pay Transparency Requirements and Expands The Equal Pay Act | By: Kelly O. Scott
- The “Net Effect” Rule That Can Sink Arbitration Agreements | By: Jared W. Slater
- The Hidden Cost of Fine Print: A Warning to Employers Drafting Arbitration Agreements | By: Jared W. Slater
- Another Crucial Win for Employers re: Untimely Arbitration Fee Payments | By: Jared W. Slater
- Can the Use of a Trademark on “Swag” Establish First Use in Commerce and Trademark Priority? Possibly, under the Totality of the Circumstances Approach Used by the Ninth Circuit | By: Eric Levinrad
Blogs
Contributors
- Kelly O. Scott
- Peter A. Davidson
- Jeffrey R. Glassman
- Pooja S. Nair
- Gary Q. Michel
- Kenneth A. Luer
- Byron Z. Moldo
- Geoffrey M. Gold
- Julie R. Zaligson
- Banu Naraghi
- Catherine A. Veeneman
- Elliot Z. Chen
- Eric Levinrad
- Jared W. Slater
- Jason L. Haas
- Kelly W. Cunningham
- Kenny Hsu
- Tanner Hosfield
- Vanja Habekovic
Archives
- November 2025
- October 2025
- September 2025
- August 2025
- July 2025
- June 2025
- May 2025
- April 2025
- March 2025
- February 2025
- January 2025
- December 2024
- November 2024
- October 2024
- September 2024
- August 2024
- July 2024
- June 2024
- May 2024
- April 2024
- March 2024
- February 2024
- January 2024
- December 2023
- November 2023
- October 2023
- September 2023
- August 2023
- July 2023
- June 2023
- May 2023
- April 2023
- March 2023
- February 2023
- January 2023
- December 2022
- November 2022
- October 2022
- September 2022
- August 2022
- July 2022
- June 2022
- May 2022
- April 2022
- March 2022
- February 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- August 2021
- July 2021
- June 2021
- May 2021
- April 2021
- March 2021
- February 2021
- January 2021
- December 2020
- November 2020
- October 2020
- September 2020
- August 2020
- July 2020
- June 2020
- May 2020
- April 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
- July 2019
- June 2019
- May 2019
- March 2019
- February 2019
- January 2019
- November 2018
- October 2018
- September 2018
- August 2018
- July 2018
- June 2018
- May 2018
- April 2018
- February 2018
- January 2018
- December 2017
- November 2017
- October 2017
- September 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
