[un]prompted · Event date October 27, 2026 - October 29, 2026

[un]prompted II

Why it matters
October 27, 2026 - October 29, 2026
Scheduled event

[un]prompted II is a practitioner-led AI-security conference in San Francisco organized around building, breaking, operating, governing, and training AI systems. Its review criteria favor production architecture, metrics, failures, demonstrations, code, and prompts over pre-deployment speculation; organizers warn that the dates may shift by one day.

My takeaway: This is a strong source for field evidence if the final agenda maintains that bar. Capture concrete attack preconditions, control failures, detection and recovery data, and implementation artifacts from accepted talks; retain the date caveat and verify the final schedule before travel.
Keep exploring

More curated notes connected through AI Red Teaming and Agent Security.

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.

OECD.AI Wonk · guide

A five-step roadmap to closing the AI evaluation gap

The roadmap addresses evaluation results that overstate real-world performance or fail to transfer across deployment contexts. Its five steps balance standardized and local tests, evaluate throughout the lifecycle, build qualified assurance and communication capacity, tailor tests to each value-chain actor and technology, and use a coordinated, trusted process for updating methods.