Skip to content
← Scoping Worksheet

Worked example · Level 2 · fictional

A managed-service provider and its shared-responsibility split

A managed-service provider supports several defense contractors. It holds no CUI, but its remote-management platform, ticket system and technicians hold its clients' Security Protection Data: configurations, logs and passwords.

This organization is invented. Its names, systems and decisions show how the worksheet is filled in; the reasoning under each item is Expert CMMC's, resting on the definition quoted beside it, and is not a determination about any real organization.

Each choice and the definition it rests on

  • Remote-management platform (vendor-hosted)

    Placed in: Security Protection Assets

    A cloud provider holding Security Protection Data without CUI is assessed as a Security Protection Asset.

    “Assets that provide security functions or capabilities to the OSA's CMMC Assessment Scope”

    “Security Protection Data means data stored or processed by Security Protection Assets that are used to protect an OSA's assessed environment.”

  • Password vault

    Placed in: Security Protection Assets

    It holds passwords that grant access to clients' in-scope environments: Security Protection Data.

    “Assets that provide security functions or capabilities to the OSA's CMMC Assessment Scope”

    “Security Protection Data means data stored or processed by Security Protection Assets that are used to protect an OSA's assessed environment.”

  • Ticket system

    Placed in: Security Protection Assets

    Ticket notes hold client configuration details.

    “Assets that provide security functions or capabilities to the OSA's CMMC Assessment Scope”

    “Security Protection Data means data stored or processed by Security Protection Assets that are used to protect an OSA's assessed environment.”

  • Technicians and the security operations desk (9)

    Placed in: Security Protection Assets

    The guide's own examples of Security Protection Assets include managed service provider personnel who implement system maintenance.

    “Assets that provide security functions or capabilities to the OSA's CMMC Assessment Scope”

    “Security Protection Data means data stored or processed by Security Protection Assets that are used to protect an OSA's assessed environment.”

  • Billing and sales systems

    Placed in: Out-of-Scope Assets

    The provider placed them out of scope and wrote how they are separated.

    Its written reason: Logically separated: they run in a separate cloud account with no network path, shared accounts or shared passwords to the platform, the vault or the ticket system, and hold invoices only.

    “Assets that cannot process, store, or transmit CUI; and do not provide security protections for CUI Assets”

    “Assets that are physically or logically separated from CUI assets”

    “Assets that fall into any in-scope asset category cannot be considered an Out-of-Scope Asset”

    “An endpoint hosting a VDI client configured to not allow any processing, storage, or transmission of CUI beyond the Keyboard/Video/Mouse sent to the VDI client is considered an Out-of-Scope Asset”

Level 2 scoping worksheet

Draft scope statement, Level 2

Draft for review, not a determination. Prepared November 20, 2026 with the CMMC Scoping Guide, Level 2, Version 2.13 (September 2024).

It records what was decided and why. Whether anything is outside the CMMC Assessment Scope is the organization's decision to justify to its assessor, under 32 CFR 170.19 and the scoping guide.

Boundary

Example D: MSP services to defense clients

The provider's remote-management platform, ticket system and password vault, the technicians who use them, and the security operations desk; each client's customer responsibility matrix says which requirement objectives the provider meets and which stay with the client.

Information flows

  • Clients' configuration data, logs and administrator passwords (FCI or CUI not yet known). Received: From client systems by the remote-management agent. Stored: Remote-management platform; password vault; ticket notes. Processed: Technicians' workstations. Sent: Reports to each client.

Items by category

Security Protection Assets (in the assessment scope)

  • Remote-management platform (vendor-hosted) (outside providers)The example's reasoning: A cloud provider holding Security Protection Data without CUI is assessed as a Security Protection Asset.
  • Password vault (systems and devices)The example's reasoning: It holds passwords that grant access to clients' in-scope environments: Security Protection Data.
  • Ticket system (systems and devices)The example's reasoning: Ticket notes hold client configuration details.
  • Technicians and the security operations desk (9) (people)The example's reasoning: The guide's own examples of Security Protection Assets include managed service provider personnel who implement system maintenance.

Out-of-Scope Assets (placed outside the assessment scope by this organization)

  • Billing and sales systems (systems and devices)Placed here because: Logically separated: they run in a separate cloud account with no network path, shared accounts or shared passwords to the platform, the vault or the ticket system, and hold invoices only.The example's reasoning: The provider placed them out of scope and wrote how they are separated.

Outside providers

Remote-management platform (vendor-hosted): Patching, monitoring and remote access for client devices (a cloud service provider)

“The services provided by the CSP are in the OSA's assessment scope and shall be assessed as Security Protection Assets”

Still yours to configure and document: Who on staff has access, multifactor sign-in, which clients' devices each technician reaches, the audit log

Obtain from the provider: The vendor's documentation of what it secures in the hosted platform, and its customer responsibility matrix

Open questions

  • Find out whether your contracts carry FAR 52.204-21 (Basic Safeguarding of Covered Contractor Information Systems).
  • Find out whether your contracts carry DFARS 252.204-7012 (Safeguarding Covered Defense Information and Cyber Incident Reporting).
  • Find out whether your contracts carry DFARS 252.204-7019 (Notice of NIST SP 800-171 DoD Assessment Requirements).
  • Find out whether your contracts carry DFARS 252.204-7020 (NIST SP 800-171 DoD Assessment Requirements).
  • Find out whether your contracts carry DFARS 252.204-7021 (Contractor Compliance With the Cybersecurity Maturity Model Certification Level Requirements).
  • Find out whether "Clients' configuration data, logs and administrator passwords" is FCI or CUI.