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
NVIDIA AI Red Team · July 11, 2024

Defending AI Model Files from Unauthorized Access with Canaries

guide AI Red TeamingAI EngineeringAdversarial ML
Why it matters

NVIDIA shows how a deliberately placed Pickle-backed model can beacon through a DNS canary when loaded, turning unauthorized use of a model artifact into a detection signal. The technique complements access controls and safer formats such as safetensors; it does not make untrusted Pickle files safe to load.

My takeaway: Prefer non-executable model formats, signed provenance, least-privilege storage, and data-loss prevention. For residual-risk detection, place clearly governed canary artifacts where legitimate workflows will not load them, route alerts into an incident playbook, and test the full signal path. Never add executable beaconing to production models or treat a canary as prevention.
Keep exploring

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

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

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.

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.