TWL400-Using-AI-to-Secure-the-Modern-SOC is a hands-on training lab that teaches learners to investigate and respond to a coordinated attack spanning identity, AI, data, infrastructure, and endpoints. It is intended for security professionals acting as cloud solution architects and uses Microsoft security services to complete the exercise.
Borrowing it
Nothing to install: this file belongs to microsoft/TWL400-Using-AI-to-Secure-the-Modern-SOC. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/TWL400-Using-AI-to-Secure-the-Modern-SOC/main/AGENTS.mdgit clone --depth 1 https://github.com/microsoft/TWL400-Using-AI-to-Secure-the-Modern-SOCWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/microsoft/twl400-using-ai-to-secure-the-modern-soc/agents-md)<a href="https://agentmods.dev/instructions/microsoft/twl400-using-ai-to-secure-the-modern-soc/agents-md"><img src="https://agentmods.dev/badge/instructions/microsoft/twl400-using-ai-to-secure-the-modern-soc/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/microsoft/twl400-using-ai-to-secure-the-modern-soc/agents-md"><img src="https://agentmods.dev/badge/instructions/microsoft/twl400-using-ai-to-secure-the-modern-soc/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.04113 | $0.04113 |
| Opus 5 | $0.02056 | $0.02056 |
| Sonnet 5 | $0.00823 | $0.00823 |
| Haiku 4.5 | $0.00411 | $0.00411 |
Grade A, and why
TWL400-Using-AI-to-Secure-the-Modern-SOC AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI coding agents (and any human author) working in this repository. This file is the single source of truth for the lab's scenario facts ("canon") and its MCAP authoring conventions. Read it before editing any page under docs/.
Project overview
This repository is a Jekyll-based training lab (just-the-docs theme, published to GitHub Pages) in Microsoft's MCAP TechWorkshop format. It is the Module 3 hands-on lab — Cross-Layer Attack Lab (End-to-End) — of the L300/L400 workshop Using AI to Secure the Modern SOC.
Instructional content lives under docs/; image assets under media/. There is no src/ companion application — this is a browser-only lab delivered in a pre-provisioned, hosted tenant (learners need only a browser and assigned credentials).
Draft status — read this
This is a full first draft authored from the lab outline before the lab tenant exists. Portal navigation paths, KQL queries, Security Copilot prompts, screenshots, and every seeded entity below are illustrative and must be validated against the provisioned environment during the build (the JAM-208 hand-off). When the build resolves an open decision differently from this draft, update the canon here first, then the pages.
The recommended build (per the outline's Appendix A — the Variant 4: Azure/Sentinel, No-Purview design) is: unified SecOps portal, Microsoft Sentinel as the data backbone (commodity signals + the ~25 decoy noise incidents injected via the Logs Ingestion API into a custom Log Analytics table, raised as incidents by Sentinel analytics rules), with the AI-layer (S3) signal detonated for real against an Azure OpenAI endpoint by a scripted openai-package call (PyRIT optional — dropped in validation for Python 3.13 / Windows path issues) and detected by Microsoft Defender for Cloud — AI threat protection. Pages are written for that surface.
{: .warning }
Open decisions (flag in any affected page):
- S4 form — default is the injected service-principal infra/inference-reach (max determinism). An optional build alternative is OAuth illicit-consent + inbox rules (more realistic; would change the Ex03 infra-containment action). Pages stay on the injected default unless the build chooses otherwise.
- Runtime — this draft targets the Variant-4 schedule (45-min core hunt + support, ~1h35m for Ex00–Ex04, Ex05 separate/post-delivery). Microsoft's 30–40 min ask may force later compression.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 145 lines · 4,113 tokens per session scan A a6558c6b6744
TWL400-Using-AI-to-Secure-the-Modern-SOC AGENTS.md is an instructions file published in the GitHub repository microsoft/TWL400-Using-AI-to-Secure-the-Modern-SOC (2 stars, last pushed today), licensed MIT. It adds 4,113 tokens to every session, about $0.0206 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).