OpenAI News · August 19, 2026

Offering Zero Data Retention for frontier models

Why it matters

OpenAI previews Private Safety Processing for eligible Zero Data Retention deployments: automated systems correlate risk across related interactions while content stays on customer infrastructure or in OpenAI storage encrypted with customer-controlled keys. OpenAI receives a limited risk signal rather than prompt content; the design is still in early testing.

My takeaway: Treat the preview as an architecture to validate, not an implemented assurance. Document retention exceptions, key custody, attestation, signal contents, enforcement and appeal paths, customer-visible audit data, deletion behavior, and failure modes; verify those claims against the promised technical paper before using them for regulatory or incident-response decisions.
Keep exploring

More curated notes connected through AI Compliance and Agent Security.

OpenAI News · framework

Pacing model development in an era of cyber-critical capabilities

OpenAI says preliminary evidence that Astra may meet its Critical cybersecurity threshold led it to pause frontier reinforcement-learning work for two weeks and keep its largest planned run on hold. New safeguards include stronger workload and network isolation, continuous boundary testing, token-level monitoring that escalates suspicious tool activity, and broader alignment checks for deception, reward hacking, and unauthorized access.

OpenAI News · framework

OpenAI’s Frontier Governance Framework

OpenAI's 22-page Frontier Governance Framework maps its frontier-model processes to California's Transparency in Frontier AI Act and the EU AI Act's general-purpose AI code. It documents lifecycle risk assessment, cyber-offense and other risk tiers, mitigation and residual-risk decisions, critical-incident handling, security risk management, model reporting, external review, responsibility allocation, and change control.

OWASP GenAI Security Project · guide

OWASP Top 10 for Agentic Applications for 2026

OWASP's community guide organizes agentic-system risk into ten categories, including goal hijacking, tool misuse, identity and privilege abuse, memory poisoning, insecure inter-agent communication, cascading failures, and rogue-agent behavior. It provides a shared taxonomy and mitigation starting point rather than a certification checklist or evidence that a deployed system is secure.