AI Red Team Engineering notes, research references, and field notes on AI systems, responsible AI, governance, and compliance.
Global search

Search AI Red Team

Search across the complete knowledge base.

Enter at least two characters to begin.
↑↓ select Enter open Browse the full research archive
Trail of Bits Blog · October 21, 2026

Agent-written patches: verify the original, fixed, and reverted behavior

analysis AI EngineeringAI Red TeamingModel Evaluation
Why it matters

Trail of Bits’ patching workflow runs the same reproduction on original, patched, and fully reverted code, then checks for new regressions. Findings carry pinned revisions and raw evidence for independent replay. Its preliminary regression study reduced false positives but left some known failures unconfirmed, illustrating the cost of strict evidence requirements.

My takeaway: Define the supported behavior and threat model before patching. In an isolated test environment, require the original and reverted versions to fail the same check while the patched version passes. Save commands, revisions, and raw results; independently replay them and test neighboring behavior. Treat missing reproduction evidence as inconclusive.
Keep exploring

More curated notes connected through AI Engineering and AI Red Teaming.

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.

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.

OpenAI News · framework

A blueprint for democratic governance of frontier AI

OpenAI proposes a three-part U.S. frontier-AI governance model: harmonize emerging state safety laws into a federal baseline, strengthen CAISI as an evaluation and standards institution, and coordinate a broader resilience program. Proposed controls include severe-risk evaluations, transparency reports, independent audits, safety-incident reporting, model-weight security, whistleblower protection, and periodic technical assessments.