DefenseEye.ai

CMMC Compliance

CMMC Level 2 for Small Businesses: What You Actually Need (and What You Don't)

A practical guide for small defense contractors facing CMMC Level 2's 110 controls. Covers what Microsoft 365 GCC High inherits on your behalf, what your team must actually implement, realistic cost ranges, and the documentation burden that surprises most small businesses. Based on DoD, NIST, and Microsoft FedRAMP documentation.

CMMC Level 2 requires full implementation of all 110 NIST SP 800-171 Rev. 2 controls — and for a small defense contractor with 10 to 50 employees, that number can feel overwhelming. The DoD's own CMMC 2.0 final rule explicitly acknowledges small business concerns and requires the DoD to consider CMMC's impact on small entities under the Regulatory Flexibility Act. Despite that, the compliance requirements themselves do not scale with company size — a 15-person defense manufacturer handling CUI faces the same 110-control standard as a 10,000-person prime.

The good news is that the implementation burden is much lower than it appears if your organization already uses Microsoft 365 GCC High or Azure Government. Microsoft holds FedRAMP High authorization for GCC High, and its FedRAMP customer responsibility matrix documents which of the underlying controls Microsoft satisfies on your behalf — reducing the controls you must independently implement. The remaining burden for most small businesses is largely documentation and operational discipline, not large capital expenditure.

The Microsoft Inheritance Advantage

If your small company uses Microsoft 365 GCC High or Azure Government for cloud storage, email, and collaboration, Microsoft inherits responsibility for a significant portion of physical security, infrastructure, and platform-level controls. Under FedRAMP Moderate authorization (which M365 GCC High holds), Microsoft's Customer Responsibility Matrix documents exactly which controls Microsoft satisfies on your behalf.

Controls where Microsoft handles the heavy lifting include: physical access controls to data centers (PE domain controls), certain encryption at rest controls for data stored in Microsoft services, platform availability and redundancy, and certain audit log retention for the Microsoft infrastructure layer. You still need to configure these features correctly in your tenant and document the inheritance in your SSP — but you're not building the infrastructure from scratch.

What a Small Company Actually Needs to Implement

For a typical 10–50 person defense contractor using M365 GCC High as the primary environment, the implementation burden falls into three buckets:

Bucket 1: Microsoft Configuration (Medium Effort)

  • Enable and enforce Multi-Factor Authentication (MFA) for all accounts — native to M365, no additional cost
  • Configure Conditional Access policies: block legacy authentication, require compliant devices
  • Enable Microsoft Defender for Endpoint on all workstations — included in M365 Business Premium or GCC High E3/E5
  • Enable Microsoft Purview compliance features: Data Loss Prevention (DLP), sensitivity labels for CUI
  • Configure Microsoft 365 Unified Audit Log retention to 1 year (requires E3 or higher)
  • Enable BitLocker encryption on all Windows endpoints via Intune policy
  • Configure Azure AD Password Protection: minimum 14-character passwords, banned password list
  • Set up Entra ID Identity Protection for risky sign-in detection

Bucket 2: Written Documentation (High Effort, No Cost)

The most underestimated CMMC cost for small businesses is the documentation burden — not the technology. You need written policies and procedures for everything, even simple things. Many small companies have informal practices that work fine but have never been written down.

  • System Security Plan (SSP) covering all 110 controls — this is a significant document (typically 60–120 pages for a small company)
  • Acceptable Use Policy (AUP) — how employees must handle CUI, acceptable use of company systems
  • Incident Response Plan — who does what when you suspect a breach, DoD reporting procedures
  • Configuration Management Plan — how you approve and track changes to CUI systems
  • Access Control Procedures — user provisioning, reviews, and de-provisioning processes
  • Security Awareness Training records — completion tracking for all staff with CUI access
  • Risk Assessment — annual formal assessment, documented results
  • Media Sanitization Procedures — what to do with drives, USB sticks, and mobile devices

Bucket 3: Operational Disciplines (Ongoing Effort)

  • Monthly vulnerability scanning on your endpoints and any on-premises systems
  • Quarterly user access reviews — confirm every account still needs its current level of access
  • Annual tabletop incident response exercise — even a 2-hour internal discussion with notes counts
  • Patch management — critical patches within 30 days, documented and tracked
  • Audit log review — alerts for high-priority security events reviewed weekly

The Real Cost Breakdown for a Small Company

Cost ItemEstimated RangeNotes
M365 GCC High E3 licenses (20 users)$3,600–$4,800/yrRequired for proper CUI handling environment
Microsoft Defender for Endpoint P2Included in E5 or ~$84/user/yrEDR capability for CMMC SI domain
CMMCLens — Level 2 automationQuoted to scopeEvidence automation, control mapping, SSP/POA&M workflows; contact DefenseEye for pricing
Gap assessment (pre-assessment)$3,000–$8,000One-time consultant engagement to identify gaps
C3PAO formal assessment$30,000–$60,000For a 10–50 person company
Remediation (varies widely)$5,000–$30,000Depends on gap size — bigger gaps cost more
Total (Year 1)Varies widelyDepends on your environment, scope, existing security posture, and providers chosen

The Controls You Can Probably Skip (Or Simplify)

Some NIST 800-171 controls are written for large enterprise environments but have lightweight equivalents that a small company can satisfy without enterprise-grade tooling:

  • Security Orchestration (SC.L2-3.13.1 through 3.13.4): For a small company in M365 GCC High, native Microsoft network security features (Defender for Cloud, NSGs in Azure, Exchange transport rules) satisfy most SC domain controls without a dedicated network security stack.
  • Privileged Access Management (AC.L2 controls): You don't need a PAM tool like CyberArk. Admin accounts in Azure AD with Privileged Identity Management (PIM) — just-in-time admin access — satisfies the intent at much lower cost.
  • Tape backups and air-gapped media: NIST 800-171 requires backup and recovery (control 3.8.9), but a cloud-based backup solution (M365 Backup, Azure Backup) qualifies without physical tape infrastructure.
  • On-premises SIEM: If everything is in M365 GCC High, the native Microsoft Sentinel (SIEM) or even just the Microsoft Secure Score + Compliance Center reports provide audit and monitoring capabilities without a separate SIEM deployment.

One Mistake That Sinks Small Companies

The most common reason small businesses fail C3PAO assessments is not missing technology — it's missing documentation. Assessors find that MFA is enabled (good), but there's no policy document specifying it's required. Or vulnerability scans are running, but there's no evidence anyone reviews the results. Or an incident response plan exists but was never tested or approved by leadership.

Every technical control needs a corresponding policy or procedure document AND evidence that the control is operating as documented. CMMCLens generates the documentation framework automatically from your M365 configuration — mapping what's actually deployed to the relevant NIST 800-171 controls and generating SSP language for each — so your documentation matches reality.

Timeline Expectation for a Small Business Starting From Scratch

  • Month 1–2: Gap assessment, M365 GCC High tenant configuration, MFA enforcement
  • Month 3–4: Write SSP, policies, and procedures; set up CMMCLens for automated evidence collection
  • Month 5–6: Remediate identified gaps; conduct annual risk assessment and tabletop IR exercise
  • Month 7–8: Submit SPRS score; select and engage C3PAO
  • Month 9–12: C3PAO pre-assessment review, formal assessment, receive CMMC Level 2 certificate

Organizations that successfully compress the CMMC compliance timeline focus on getting documentation right from day one. The most common small business failure mode is implementing controls correctly but documenting them poorly — which fails assessments even when the technical posture is sound. Match every technical control to a written policy, generate evidence that the control is operating, and link both to the relevant NIST 800-171 practice number in your SSP.

Authoritative Sources

  • CMMC 2.0 Final Rule Regulatory Flexibility Analysis — federalregister.gov: the DoD's analysis of CMMC's impact on small entities, including cost estimates
  • Microsoft FedRAMP Documentation — microsoft.com/en-us/trust-center: Microsoft's FedRAMP authorizations for GCC and GCC High, including Customer Responsibility Matrices
  • NIST SP 800-171 Rev. 2 — csrc.nist.gov: the 110-control framework that defines CMMC Level 2 requirements
  • DoD CMMC Small Business FAQ — dodcio.defense.gov/CMMC: the CMMC program office's official guidance for small business contractors
  • SBA Office of Advocacy — sba.gov/advocacy: resources on regulatory impact assessments for small businesses in federal contracting
  • CMMC Marketplace — cyberab.org/Catalog: the Cyber AB's official directory of authorized C3PAOs