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
Cloudflare AI Security · September 29, 2026

Adaptive WAF testing: validate edge passes before calling them exploits

analysis AI Red TeamingModel EvaluationAgent Security
Why it matters

Cloudflare describes a bounded proposal-and-review loop that mutates known blocked requests against one authorized staging configuration. Code enforces the hostname allowlist, disables redirects, limits attempts and logs evidence; response content remains untrusted. The run recorded 1,107 attempts, with human triage retaining 49 findings for investigation. A request passing the edge, including a redirect in the SSRF example, does not establish origin exploitation. The results characterize that configuration and test setup, not a universal WAF protection rate.

My takeaway: Reproduce the relevant production controls in staging, log every attempt and validate candidate bypasses at the origin. Keep enforcement changes outside the agent, test legitimate traffic before blocking, and patch the underlying application.
Keep exploring

More curated notes connected through AI Red Teaming and Model Evaluation.

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.