Attorneys general from eight US states have filed separate lawsuits against OpenAI, alleging that ChatGPT harmed residents, including teenagers, by reinforcing delusions or assisting dangerous behaviour. Reuters reported that the bipartisan group includes Iowa, Kansas, Arizona, Arkansas, Idaho, Montana, Nebraska and West Virginia. The cases allege violations of state consumer-protection laws and public-nuisance rules.

These are allegations, not findings of liability. OpenAI had not responded to Reuters before publication. That distinction matters because the claims are broad: the states seek monetary penalties and changes to how ChatGPT works, with some asking courts to restrict development of self-improving models unless alignment can be demonstrated.

The governance significance is the shift from general safety commitments to legally testable representations. Product teams may need to show how age assurance, risk detection, escalation, refusal behaviour and incident review operate in practice. Marketing and safety statements will also be tested against internal evidence and actual user outcomes.

For enterprise buyers, especially banks and insurers deploying conversational systems, the lesson is not to treat consumer AI litigation as remote. Procurement records should identify the intended user population, foreseeable misuse, monitoring thresholds and the owner who can change or withdraw a risky feature. A safety case must connect public claims to release gates and post-deployment evidence.

Execution Level Governance- What audit-ready agent governance actually looks like
David Girvin, founder and CEO of Assury argues that model-in-the-loop review, AI governing AI, is fundamentally unreliable for regulated environments: even the best-performing models miss a meaningful share of violations, the reviewing model is typically provided by the same vendor being reviewed, and prompt injection or context poisoning can compromise both the acting agent and its supposed overseer simultaneously. He makes the case for deterministic, architecturally enforced controls instead, walking through Assury's approach of autonomy zones, session risk accumulation, and credential starvation, which lets a compromised agent be cut off from its tools instantly rather than relying on time-boxed access. The conversation touches on why David is sceptical of just-in-time credentialing as a solution for agent security more broadly, since agent sessions don't run on predictable human timescales, along with the current gap between how identity and security vendors are pitching agent protection and what he sees happening at the execution layer in practice. He also discusses the compliance and audit implications of probabilistic decision-making, arguing that regulated industries will increasingly need tamper-evident, hash-chained audit trails that can withstand scrutiny from auditors and regulators who are only beginning to understand agentic risk, and reflects on a named frontier lab's own published framework as an example of the gap between research and practitioner reality. Elsewhere, David reflects candidly on building a bootstrapped security company in an increasingly crowded market, why he turned down aggressive VC funding to stay in control of the product, and what a credible third-party assessment of his own gateway would need to look like given that Assury sits directly in the execution path for every customer's agents.
BrightTALK
Share this post
The link has been copied!