Skip to main content

FAQs: CMMC scoping before you start

Written by Brady Price

Before you start scoping

Use these questions with your team or CSM before you lock a CMMC assessment boundary. Each answer stands alone, so you can jump to the topics that match where you are today.

New to CMMC or evaluating Secureframe? Our sales team and CMMC Registered Practitioners help DIB organizations get CMMC ready faster, from scoping through assessment readiness. Learn more about Secureframe Defense, or talk to an expert to schedule a call.


Getting started

I'm new to CMMC or not a Secureframe customer yet. Who can help?

  • If you are evaluating Secureframe or just getting started with CMMC, our sales team is ready to help. CMMC Registered Practitioners on the Secureframe Defense team guide organizations from scoping to SPRS submission.

  • Learn more at secureframe.com/cmmc, or talk to an expert to book a demo / schedule a call.

  • If you are already a Secureframe customer, start with your CSM and the CMMC Scoping module in Defense Navigator.

What should I figure out before I start scoping for CMMC?

  • Start with six things: which CMMC level applies, whether you handle CUI or only FCI, where that information lives and moves, which systems and people touch it, which outside providers can reach it, and what deadline you are working toward.

  • Those answers set your assessment boundary, and the boundary drives cost, effort, and timeline.

Do I need CMMC if no customer has asked for it yet?

  • If you hold or plan to bid on DoD contracts or subcontracts involving FCI or CUI, expect it.

  • CMMC requirements appear in DoD solicitations through DFARS 252.204-7021, and primes flow them down to subcontractors.

  • You need the required CMMC status at the time of award, so treat upcoming bids as a real deadline.

How long does it take to get ready for CMMC?

  • It depends mostly on your starting point.

  • A company with an asset inventory, documented policies, and a defined CUI boundary can move in a few months.

  • A company starting from scratch on Level 2 should plan for 6 to 12 months or more, especially if it needs to migrate platforms or build an enclave.

  • Work backward from your bid or contract dates.

Who should own CMMC at our company?

  • Someone with the time and authority to drive it, backed by an executive sponsor.

  • CMMC touches IT, facilities, HR, contracts, and operations, not just IT.

  • A senior official must also affirm compliance in SPRS, so leadership needs to be involved from the start.

  • If CMMC is an add-on to an already full IT role, plan for outside help or a longer timeline.

Does the size of my company affect CMMC scope?

  • Total headcount matters less than how many people and systems touch CUI.

  • Everyone with CUI access needs training, MFA-protected accounts, and access controls.

  • If only a small group works with CUI, isolating that group in an enclave can shrink your scope considerably.

Does having one location versus several change anything?

  • Yes. Every facility where CUI is accessed, stored, or printed is in scope for physical protection requirements such as visitor control, access logs, and managing keys and badges.

  • Remote work brings home offices and personal networks into the discussion.

  • Fewer locations usually means a simpler assessment.

Tip: When you are ready to answer scoping questions in Secureframe, open the CMMC Scoping module in Defense Navigator. See CMMC Scoping for how those answers drive requirements, tests, policies, and your SSP.

Note: This article is educational guidance for scoping conversations. Your contract, contracting officer, or prime decides the required CMMC level and assessment type. For additional CMMC / DFARS readiness FAQs, see FAQs: FedRAMP, CMMC, and DFARS.


Contracts and CMMC level

How do I know which CMMC level I need?

  • Your contract or solicitation specifies it.

  • In general, Level 1 applies when you handle only Federal Contract Information (FCI), Level 2 applies when you handle Controlled Unclassified Information (CUI), and Level 3 applies to a smaller set of contracts with the most sensitive CUI.

  • If you are unsure, ask your contracting officer or prime to confirm in writing.

What is the difference between a Level 2 self-assessment and a Level 2 certification?

  • Both cover the same 110 NIST SP 800-171 requirements.

  • With a self-assessment, you assess yourself and post the results in SPRS.

  • With a certification, an authorized third-party assessor (C3PAO) performs the assessment.

  • Your contract decides which one you need.

  • Both are repeated every three years, with an annual affirmation in between.

What is SPRS and do I need to submit a score?

  • The Supplier Performance Risk System (SPRS) is where DoD records your NIST SP 800-171 score and CMMC status.

  • If your contracts include DFARS 252.204-7019 or 7020, you should already have a current score posted.

  • Scores range from -203 to 110. If you have never submitted one, that is a priority gap.

Which company or CAGE code should our CMMC assessment be tied to?

  • The legal entity that actually holds the contract.

  • CMMC status in SPRS is recorded against CAGE codes.

  • If you have a parent company, sister companies, a recent acquisition, or a name change, confirm which entity and CAGE code holds each DoD contract before you scope.

How do I know if I actually have CUI?

  • The government should identify CUI, usually through contract clauses, CUI marking guidance, or markings on the documents themselves (such as CUI banners or legacy markings like FOUO).

  • If a customer tells you something is CUI but nothing is in writing, ask your contracting officer or prime to confirm in writing.

  • Scoping without that confirmation risks protecting too much or too little.

What is the difference between FCI and CUI?

  • FCI is non-public information provided by or generated for the government under a contract, such as contract details or schedules.

  • CUI is a more sensitive category that requires safeguarding under law, regulation, or policy, such as controlled technical drawings and specifications.

  • FCI alone points to Level 1. CUI points to Level 2 or higher.

Does ITAR or EAR data change my CMMC approach?

  • It adds requirements on top of CMMC.

  • Export-controlled technical data generally must be restricted to U.S. persons, which affects where you can store it and who can support those systems.

  • Many companies with ITAR data choose platforms built for it, such as Microsoft 365 GCC High.

  • Confirm with your export compliance contact before choosing a platform.

Why does it matter how many people work with CUI?

  • It is one of the biggest drivers of your boundary choice.

  • If only a handful of people touch CUI, an enclave for those users is often cheaper and easier than bringing the whole company into scope.

  • If most of the company touches CUI, an enterprise-wide approach may make more sense.


Where CUI lives and moves

Why do I need to map how CUI comes in, where it is stored, and where it goes?

  • Every system CUI passes through is in scope.

  • Tracing the full path (inbound, storage, processing, outbound) shows which email systems, file shares, devices, printers, and people need to meet CMMC requirements.

  • Gaps here are among the most common surprises in an assessment.

Can we receive or send CUI by email?

  • Only if the email system is in scope and meets the requirements, including encryption.

  • Many companies reduce scope by receiving and returning CUI through the prime's portal or a secure file transfer tool instead.

  • Whatever method you use, document it.

Does printing CUI or saving it to USB drives affect CMMC?

  • Yes. Printers, paper copies, and removable media fall under media protection and physical protection requirements.

  • You will need to control who can print or use removable media, mark media containing CUI, encrypt CUI on portable storage or physically protect it in transit, and sanitize or destroy media properly.

We have a shop floor. How does that affect CMMC scope?

  • Drawings, travelers, job packets, and machine programs often contain CUI, so the floor is frequently in scope.

  • Map how that information gets to the floor (printouts, file shares, USB drives, DNC systems, or workstation screens) and who can see it.

  • Printed packets need physical controls, and connected machines may need to be documented as in-scope assets.

Why does it matter where and on what devices people access CUI?

  • Each access point adds to scope.

  • Company-managed devices on site are the simplest to control.

  • Remote access, personal devices, or home networks add requirements such as secure remote access, session controls, and device management.

  • Decide where access is allowed before you finalize your boundary.

What documentation should I have before scoping?

  • Useful starting points are a data flow diagram showing how CUI moves, a network diagram, an asset inventory, and any existing security policies.

  • For Level 2 you will ultimately need a System Security Plan (SSP) describing your boundary and how each requirement is met.

  • If none of these exist yet, building them is part of scoping.

  • Secureframe can help you build and manage an SSP: Building and Managing a System Security Plan (SSP).


Boundary and enclave

What is a CMMC assessment boundary?

  • The people, systems, facilities, and providers that process, store, or transmit CUI, plus the systems that protect them.

  • Everything inside the boundary gets assessed.

  • A smaller, well-defined boundary usually means less cost and effort.

Should we put our whole company in scope or build an enclave?

  • An enterprise-wide approach brings everything into scope and works well when CUI is everywhere.

  • An enclave isolates CUI in a dedicated environment (a separate network, a separate cloud tenant such as GCC High, or a secure virtual desktop) used only by the people who need it.

  • The right choice depends on how many people, systems, and locations touch CUI.

  • For Secureframe enclave setup, see CUI Enclave Setup.

Does our in-scope network need to be separated from the rest of the business?

  • It is not required, but separation is how you keep scope small.

  • If CUI systems sit on the same flat network as everything else, connected systems may be treated as in scope.

  • Segmentation through VLANs, firewalls, or a separate cloud environment lets you limit the assessment to what actually handles CUI.

Why does the number of in-scope systems matter?

  • Each system or application in scope must be inventoried, securely configured, monitored, and documented in your SSP.

  • Fewer systems means less work.

  • Count anything that stores, processes, or transmits CUI, plus the security tools that protect those systems.


Platforms and identity

Can we use Microsoft 365 Commercial for CUI?

  • It is generally not recommended.

  • Microsoft contractually commits to DFARS 252.204-7012 requirements in Microsoft 365 GCC High and Azure Government, not in Commercial.

  • If CUI is in a Commercial tenant today, even occasionally, address it during scoping, usually by moving CUI into a compliant environment or building an enclave.

Does our cloud provider need FedRAMP authorization?

  • If a cloud service stores, processes, or transmits CUI, DoD requires it to meet the FedRAMP Moderate baseline or an equivalent.

  • Check every cloud service that touches CUI, including email, file storage, collaboration, and backups.

If CUI only goes into a system occasionally, is it still in scope?

  • Yes. Any system that processes, stores, or transmits CUI is in scope, even if it happens rarely.

  • To take a system out of scope, remove the CUI and put controls in place to keep it from returning.

Why does our identity provider matter for CMMC?

  • Identity is central to the access control and authentication requirements, including multifactor authentication.

  • If your identity provider controls access to CUI, it needs to be in a compliant environment.

  • For example, Microsoft Entra ID in a Commercial tenant and Entra ID in GCC High are different environments.

Do we need a compliance tool to get CMMC?

  • It is not required, but Level 2 involves 110 requirements, an SSP, policies, evidence, and ongoing monitoring.

  • A compliance platform like Secureframe helps you track gaps, collect evidence, and keep documentation current, which is hard to manage in spreadsheets.


Assets and physical security

Why do I need an asset inventory for CMMC?

  • CMMC requires a baseline inventory of the hardware, software, and systems in scope.

  • It is also how you prove your boundary.

  • Without one, you cannot show what is in scope or that each asset is protected.

What security tools does CMMC expect?

  • CMMC is requirement-based, not tool-based, but most organizations need endpoint protection, centralized logging, vulnerability scanning, MFA, and device management to meet Level 2.

  • Knowing what you already have shows where your biggest gaps are.

Are CNC machines, PLCs, and other operational technology in scope?

  • If they receive or display CUI, they are typically treated as Specialized Assets.

  • At Level 2, Specialized Assets must be documented in your asset inventory and SSP, shown on your network diagram, and managed under your policies, but they are not assessed against every requirement.

  • How CUI reaches them affects how you document and protect them.

If operators retype data from a printout or screen into a machine, is the machine in scope?

  • If CUI ends up on the machine, it is handling CUI and should be documented as an in-scope or Specialized Asset.

  • Manual transfer avoids network connections but does not remove the machine from consideration.

  • Document the process so assessors can see how CUI is controlled at each step.

Can we intentionally keep systems out of scope?

  • Yes, and it is a good way to reduce effort.

  • Out-of-scope assets must be unable to process, store, or transmit CUI, and you need to show how they are separated, through network segmentation, separate tenants, or physical separation.

  • Document the separation, because assessors will ask.

What physical security does CMMC require?

  • Limit physical access to systems and CUI to authorized people, escort and monitor visitors, keep logs of physical access, and control keys, badges, and other access devices.

  • Locked rooms with tracked keys are a good start.

  • Assessors will also look at visitor logs and how printed CUI is protected.


Outside providers

Is our MSP in scope for our CMMC assessment?

  • If your MSP manages in-scope systems or can access CUI or security data, its services are in scope for your assessment.

  • Document what they do in your SSP and a shared responsibility matrix, and confirm their practices meet the requirements for the services they provide.

Does our MSP need CMMC certification or FedRAMP authorization?

  • A cloud provider that stores, processes, or transmits CUI needs FedRAMP Moderate or equivalent.

  • An MSP that is not a cloud provider is not required to hold its own CMMC certification, but its services are assessed as part of yours.

  • Being "ready" is not the same as being authorized, so ask for a shared responsibility matrix and evidence of how they meet each requirement.

Does it matter whether we or our MSP owns our cloud tenant?

  • Yes. Owning the tenant gives you control over accounts, data, and logs, and makes it easier to change providers.

  • If the MSP owns it, you depend on them for evidence and access.

  • Either way, document who is responsible for what.

What about subcontractors or partners who receive CUI from us?

  • You must flow down DFARS 252.204-7012 and the applicable CMMC requirement to subcontractors who will handle CUI or FCI, and they need to meet the level required for the information they receive.

  • List every outside party that touches your in-scope systems or data, including subcontractors, consultants, vendors with remote access, and support providers.

Did this answer your question?