A security-hardened CLAUDE.md that governs how Claude Code behaves inside a Microsoft GCC High environment — CUI boundary rules, endpoint enforcement, MCP security, and CMMC control mapping in one file.
When Claude Code finds a CLAUDE.md at the repository root, it reads and follows those instructions for the entire session. This configuration turns a general-purpose AI coding assistant into one that understands your GCC High boundary, refuses to write code that violates it, and flags DFARS-reportable events when it spots them.
It covers 14 sections — from CUI boundary enforcement and hardcoded-secret prohibition to MCP server security and GitHub Enterprise Server integration. References the NSA AISC Cybersecurity Information Sheet on MCP security published May 2026 and aligns with the new OWASP Agentic AI Top 10.
Drop it in your repo root. That's it.
630 lines · UNCLASSIFIED // FOUO · CMMC L2 · NIST 800-171 R2 · DFARS 252.204-7012
Every API call Claude Code generates uses these endpoints. Commercial .com endpoints fail silently or route data outside your authorization boundary. This table is embedded in the config so Claude Code never gets it wrong.
The full config embeds this table plus authentication code patterns in Python, PowerShell, and TypeScript so Claude Code generates the correct endpoint in every language.
These prohibited patterns are embedded in the config. Claude Code refuses to generate them and explains why — keeping your developers from accidentally violating CMMC controls or routing CUI outside the boundary.
.com Microsoft endpointsverify=False, InsecureSkipVerify)The config enforces Key Vault patterns and flags any generated code that puts a secret in plain text — even in a comment.
The May 2026 NSA AISC advisory on MCP security is embedded directly. Claude Code enforces authorized-only MCP server lists, input sanitization before every MCP call, and audit logging of all tool invocations.
Covers all 14 sections including CMMC control mapping patterns, WORM evidence storage, DFARS incident detection, GitHub Enterprise Server integration, and the full NSA MCP security framework applied to Claude Code in GCC High.
Fulcrum Advisory also builds custom CLAUDE.md configurations tailored to your specific GCC High tenant, CMMC scope, and development stack.
Defense contractors are adopting AI coding tools — GitHub Copilot, Claude Code, Cursor — faster than their security teams can assess them. The risk isn't that the tools are malicious. The risk is that they're trained on commercial patterns and will confidently generate code that routes data to graph.microsoft.com instead of graph.microsoft.us, stores a connection string in plain text, or calls a commercial Azure OpenAI endpoint from inside your GCC High boundary.
A CLAUDE.md at the repo root changes the behavior before any code is written. It's the equivalent of a new developer reading your security policy on day one — except Claude Code actually follows it, every session, without exception.
This configuration was built from experience deploying production AI systems inside a CMMC-scoped GCC High environment, combined with the NSA's May 2026 guidance on MCP server security and the new OWASP Agentic AI Top 10. It's not a theoretical framework — it's what we use.
We build CLAUDE.md configurations tailored to your specific GCC High tenant, CMMC scope, and development stack.