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

OperTraitor: audit the permissions behind Kubernetes and AI operators

analysis Agent SecurityAI Red TeamingAI Engineering
Why it matters

Unit 42’s open-source OperTraitor compares operator RBAC manifests with documented functionality to flag excessive privileges for review. Its case studies distinguish an IBM secret-access issue that received a patch from Datadog permissions documented as an architectural tradeoff. The attack prerequisite is compromise or misuse of an already privileged operator; this is not evidence that an LLM independently breached a cluster. Model-generated risk scores are triage aids, while actual service-account permissions determine the reachable resources.

My takeaway: Inspect maintained manifests and namespace scope before installing an operator. Verify flagged access manually, reduce unnecessary secret and RBAC permissions, and alert on service accounts reaching unexpected namespaces or endpoints.
Keep exploring

More curated notes connected through Agent Security 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.