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
Wiz AI Security · June 6, 2025

Wiz publishes stack-specific instruction files for safer AI-assisted coding

tool Prompt EngineeringAI EngineeringAgent Security
Why it matters

Wiz’s 2025 article and public repository provide baseline security instructions for common language and framework combinations, formatted for several coding assistants. The repository exposes the generation prompt and script and clearly identifies the rules as AI-generated. The proposed method keeps guidance close to a project’s actual stack and coding practices. The release does not independently establish that these files prevent vulnerabilities or measure their effectiveness in a production repository. They are reviewable prompt material, whose usefulness depends on rule quality, context selection and subsequent code verification.

My takeaway: Review and adapt a small set of rules to the project’s actual framework. Test generated changes with independent security checks, and treat instructions as guidance rather than an enforced permission boundary.
Keep exploring

More curated notes connected through Prompt Engineering and AI Engineering.

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.

Microsoft Security Blog · guide

AI vulnerability research: measure reproducible findings and completed fixes

Microsoft’s FORGE account describes the work between a model’s vulnerability claim and a useful repair: reusable builds, duplicate removal, reachability checks, project-specific verification, reproducible triggers and regression tests. Structured rejection reasons help improve later searches. The useful operational measure is the flow of findings that survive verification and reach a fix, rather than the number of candidates generated. Reported successful-case costs exclude parts of screening, failed attempts and human work, so they are not the total cost of operating this pipeline.

OpenAI News · framework

Frontier training safety cases: connect evidence to enforced pause and rollback controls

OpenAI proposes training-run safety cases combining alignment evaluations, containment and monitoring with explicit operational ownership. Concrete measures include immutable transcripts, held-out incident tests, checks for evaluation gaming, response deadlines and fail-closed monitoring. Independent internal challenge, leadership vetoes and tracking downstream uses support stopping a run and reversing affected work. The article describes recommendations still being implemented, rather than audited proof that every safeguard already operates or that residual risk has been eliminated.