mcsb

Maps Azure resources to MCSB v2 control domains with NIST 800-53 and CIS crosswalks.

1.4k|284|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/microsoft/hve-core --skill mcsb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcsb
Source: https://github.com/microsoft/hve-core/tree/main/.github/skills/security/mcsb
Command: npx skills add https://github.com/microsoft/hve-core --skill mcsb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Security planners and reviewers need a consistent control vocabulary to assess Azure resources against the Microsoft Cloud Security Benchmark, but the benchmark's per-service details change constantly and are hard to keep current.

Core Features & Use Cases

  • Control-Domain Taxonomy: Provides the durable MCSB v2 structure with 12 control domains (NS, IM, PA, DP, AM, LT, IR, PV, ES, BR, DS, AI), each with objectives, assessment checklists, controls, and anti-patterns.
  • Framework Crosswalk: Maps each domain to representative NIST SP 800-53 Rev. 5 families and CIS Controls v8.1 for compliance alignment.
  • Runtime Lookup Delegation: Excludes volatile per-service baselines and Azure Policy mappings, delegating those lookups to a Researcher Subagent via a defined playbook.
  • Use Case: When planning a new Azure workload, use this Skill to assess the architecture against each MCSB domain checklist, identify gaps such as missing private endpoints or standing privileged access, and map findings to NIST and CIS controls for the compliance report.

Quick Start

Review my Azure architecture against the MCSB control domains and identify security gaps mapped to NIST 800-53 and CIS Controls.

Frequently Asked Questions about mcsb

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assess Azure resources against Microsoft Cloud Security Benchmark?

Use the 12 MCSB v2 control-domain references, each containing an assessment checklist of observable indicators such as private endpoints, managed identities, and diagnostic logging. Map findings back to domains using the control index.

What is the difference between MCSB v1 and MCSB v2?

MCSB v2 replaces v1's Governance and Strategy (GS) domain with an Artificial Intelligence Security (AI) domain. It also updates framework mappings to NIST SP 800-53 Rev. 5 and CIS Controls v8.1, whereas v1 mapped to Rev. 4 and CIS v8.

How does MCSB map to NIST 800-53 and CIS Controls?

Each control domain includes a representative crosswalk to NIST SP 800-53 Rev. 5 families and CIS Controls v8.1. For example, Network Security maps to NIST families AC, CA, CM, SC, SI and CIS Controls 9, 12, 13.

Does this skill include per-service Azure security baselines?

No. Per-service baselines, Azure Policy mappings, and Defender for Cloud specifics are volatile and intentionally excluded. They are retrieved at runtime by delegating to a Researcher Subagent following the lookup playbook.

When should I re-verify MCSB control mappings?

Re-verify before any compliance decision, since MCSB v2 is in preview and Microsoft revises the benchmark and referenced standards on its own release cadence. The skill content is version-pinned and retrieval-dated 2026-07-21.