standards-mapping — Claude Code rule: what it does, how to install
standards-mapping maps architecture components to OWASP, NIST, CIS, and cloud security frameworks during security planning workflows in Claude Code.
MIT ★ 1,627 updated 2026-10-25
.github/instructions/standards-mapping.instructions.mdWhat standards-mapping does
This rule orchestrates Phase 3 of security planning under .copilot-tracking/security-plans/**. Foundational standards such as OWASP, NIST 800-53, OWASP LLM Top 10, and NIST AI RMF load from durable files in the security-planning skill. When specific scopes match, targeted skills like owasp-agentic, owasp-infrastructure, or owasp-cicd take precedence.
Cloud frameworks and rapidly evolving specifications delegate lookups to rpi-research at runtime. This group covers Microsoft WAF, CAF, PCI-DSS, SOC 2, HIPAA, FedRAMP, S2C2F, SLSA, per-service MCSB baselines, and CIS Controls due to license restrictions prohibiting redistribution.
If rpi-research is unavailable, the rule requires halting the dependent mapping rather than synthesizing compliance controls from training data. Output for each component includes applicable standards with justification, research findings, and a gap analysis.
What it helps with
- map system components against OWASP and NIST security controls
- query compliance baselines for PCI-DSS, HIPAA, or FedRAMP via rpi-research
- identify security gaps between existing controls and official standards
- evaluate build integrity and software dependencies against SLSA and S2C2F
Example prompts for the agent
- Map the payment gateway component to PCI-DSS requirements
- Generate the standards mapping block for our cloud database component
- Evaluate the container build pipeline against SLSA level standards
How to install standards-mapping
Manually: put the files in place
.github/instructions/standards-mapping.instructions.mdThe applyTo field sets which files it applies to
Manually: put the files in place
.claude/rules/standards-mapping.mdThe paths frontmatter field limits the files: move applyTo from the source into paths
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.cursor/rules/standards-mapping.mdcFrontmatter: description, globs, alwaysApply. Move applyTo from the source into globs, or the rule will not attach on its own
Manually: put the files in place
.devin/rules/standards-mapping.mdManually: put the files in place
.clinerules/standards-mapping.mdStep by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use
Questions about standards-mapping
How to install standards-mapping in Claude Code?
Save the rule file to .claude/rules/standards-mapping.md in your project root. It activates automatically for files matching .copilot-tracking/security-plans/**.
What does standards-mapping do?
It guides the assistant during security planning to map components to OWASP and NIST baselines while routing dynamic cloud and regulatory lookups through rpi-research.
Why does the rule delegate CIS and WAF lookups instead of bundling them?
WAF changes rapidly across cloud services, while CIS terms prohibit redistribution, making on-demand lookup necessary.
Source text
standards-mapping.instructions.md · MIT
---
description: "OWASP and NIST security standards references with rpi-research activation for CIS, WAF, CAF, and other runtime lookups"
applyTo: '**/.copilot-tracking/security-plans/**'
---
# Standards Mapping
Frequently-used security standards are referenced from the durable skill material during Phase 3 of the security planning workflow. Specialized cloud frameworks (WAF and CAF) activate `rpi-research` at runtime instead of duplicating large, version-sensitive content.
At least one standard from each applicable framework should map to every component in the security plan. The Security Planner's Skill Reference Contract loads the durable standards references (`standards-cross-reference.md` and `nist-control-families.md` from the `security-planning` skill) via a mandatory `read_file` on Phase 3 entry, so the OWASP, NIST, and AI RMF mapping tables are not restated here. This instruction file stays orchestration-focused and defers the versioned standard tables to the skill loaded by that contract.
## Research Activation
Microsoft Well-Architected Framework (WAF) and Cloud Adoption Framework (CAF) lookups activate `rpi-research` at runtime. These frameworks evolve frequently and contain extensive cloud-specific guidance best retrieved on demand.
The following standards are also delegated for runtime lookup due to version sensitivity, domain specificity, or rapid evolution:
| Standard | Rationale for Delegation |
|---------------------------------------------------|------------------------------------------------------------|
| WAF / CAF | Cloud-specific, frequently updated, extensive content |
| MCSB per-service control mappings | Azure-specific, frequently updated per-service baselines |
| PCI-DSS | Domain-specific, version-dependent compliance requirements |
| S2C2F (Secure Supply Chain Consumption Framework) | Emerging standard, evolving maturity levels |
| SLSA (Supply Chain Levels for Software Artifacts) | Version-dependent build integrity requirements |
| SOC 2 | Audit-framework specific, organization-dependent scope |
| HIPAA | Regulated domain, requires current interpretation |
| FedRAMP | Government-specific, dynamic control baselines |
| CIS Critical Security Controls | License terms prohibit redistribution; use runtime lookup |
Do NOT delegate OWASP, NIST 800-53, OWASP LLM Top 10, or NIST AI RMF lookups. Those standards are covered by the durable skill references listed above.
### Conditional Standards Skills
When buckets or AI components from Phases 1–2 match, prefer the matching specialized security skill over a runtime delegation:
* AI/ML components → `owasp-agentic`, and `owasp-mcp` when MCP tooling is used (alongside the always-loaded `owasp-llm`)
* `infrastructure` bucket → `owasp-infrastructure`
* Azure cloud resources → `mcsb` (stable MCSB control-domain taxonomy and crosswalk; delegate volatile per-service control lookups)
* `build` / `devops-platform-ops` buckets → `owasp-cicd`, `supply-chain-security`
* Cross-cutting GS overlay → `secure-by-design`
These skills are loaded by the Security Planner's Conditional Skill Map. Activate `rpi-research` only for standards with no matching skill (WAF, CAF, PCI-DSS, and the others listed above) and for the volatile per-service layer of MCSB.
### When to Activate Research
* User requests WAF or CAF alignment for a component.
* Phase 3 identifies cloud-specific controls that require runtime research beyond the baseline standards references.
* Compliance requirements demand cloud framework mapping beyond the current baseline standards references.
* Supply chain security analysis requires S2C2F or SLSA level mapping.
* Regulatory context requires PCI-DSS, HIPAA, SOC 2, or FedRAMP mapping.
### Activation Inputs
Provide `rpi-research` with the specific framework topic and mapping purpose; security authors, reviewers, control owners, and downstream consumers as the audience and intended use; explicit mapping questions and evidence criteria; component, bucket, technology, cloud, source, version, jurisdiction, and date scope plus non-goals; risk, licensing, privacy, deadline, phase-gate, and write-boundary constraints; supplied component, bucket, state, standards, control, and user evidence; requested outputs; and output mode (`analysis` or `comparison`).
Explicitly identify `.copilot-tracking/security-plans/{project-slug}/` as a trusted alternate evidence root.
Read the completed primary research artifact and synthesize applicable Standards Coverage, Findings, and Recommendations into the component mapping. Treat `Blocked` and `Needs clarification` as unresolved evidence, not permission to infer a mapping. If `rpi-research` or a required lookup capability is unavailable, inform the user and stop the dependent mapping rather than synthesizing standards from training data. The skill decides whether independent questions warrant parallel research.
### Query Templates
Use these templates when defining questions for `rpi-research`:
* WAF/CAF: "Map {component} to WAF {pillar} and CAF {area} controls for {technology stack} on {cloud platform}."
* MCSB: "Identify MCSB controls applicable to {component} of type {resource type} in {Azure service}."
* PCI-DSS: "Map {component} handling {data classification} to PCI-DSS v{version} requirements."
* S2C2F: "Evaluate {component} dependency consumption against S2C2F maturity levels."
* SLSA: "Assess {component} build pipeline against SLSA v{version} level requirements."
* SOC 2: "Map {component} to SOC 2 Trust Services Criteria relevant to {trust principle}."
* HIPAA: "Identify HIPAA Security Rule requirements for {component} handling {PHI context}."
* FedRAMP: "Map {component} to FedRAMP {impact level} baseline controls."
Research evidence stays under the active Security Planner's mirrored `research/` structure. Read the returned primary artifact and incorporate applicable findings into the component's standards mapping under the WAF/CAF Findings section.
## Mapping Output Format
For each component, produce the standards mapping block defined in the skill reference and adapt it to the current component context.
```markdown
### {Component Name} ({Bucket})
**Applicable Standards:**
- OWASP: {items with justification}
- NIST: {families with justification}
- CIS: {researched, include primary-artifact evidence or N/A}
**WAF/CAF Findings:** {delegated RPI evidence or N/A}
**Gap Analysis:** {identified gaps between current controls and standard requirements}
```
Include justification for each mapped standard, explaining why the control is relevant to the specific component. Flag gaps where a standard should apply based on the cross-reference table but no corresponding control exists in the current architecture.
© microsoft · MIT · microsoft/hve-core