CMMC Compliant ERP: Is Your ERP in Scope, and What It Needs for Level 2
By The Defense Compliance Report Editorial Team · Last verified: November 18, 2026
General information for the defense industrial base, not legal, contractual or compliance advice. Not affiliated with DoD, the Department of War, NIST, The Cyber AB, Microsoft, Oracle, Infor, SAP, Workday, Deltek or any government agency. Your contract and your own scoping decisions control what applies to you.
Short answer: No ERP is "CMMC certified." CMMC assesses your company's systems, so a CMMC compliant ERP is one you have scoped, configured and documented. If your ERP stores controlled drawings, specifications, parts lists, process sheets or other controlled technical information, it is a CUI Asset and all 110 Level 2 requirements apply to it. A cloud ERP that holds CUI must be FedRAMP Authorized at Moderate or higher, or meet DoD's FedRAMP Moderate equivalency standard. On November 18, 2026 the FedRAMP Marketplace listed FedRAMP Authorized ERP offerings from Microsoft (Dynamics 365 in Azure Government), Oracle, Infor, SAP NS2 and Workday, while Deltek's Costpoint GovCon Cloud Moderate was FedRAMP Ready, which is not the same as Authorized. CMMC Phase II is still suspended, but Level 2 (Self) assessments and DFARS 252.204-7012 still apply.
Who this page is for
- Manufacturers and machine shops whose ERP holds job travelers, routings, bills of materials or customer drawings for defense work.
- Government contractors on a GovCon accounting system or ERP who need to know whether it belongs in their Level 2 boundary.
- Companies replacing or upgrading an ERP who want to pick one that won't create a scope problem.
- IT managers and MSPs filling in an SSP who aren't sure how to treat the ERP, its database, its integrations and its hosting partner.
If you are still deciding whether you handle CUI at all, start with who needs CMMC certification. This page assumes you hold CUI and have a Level 2 obligation now or soon.
Is your ERP in scope for CMMC?
Scope follows the information, not the software category. 32 CFR 170.19 calls assets that "process, store, or transmit CUI" CUI Assets and assesses them against all Level 2 requirements. An asset is out of scope only if it cannot process, store or transmit CUI and gives no security protection to CUI Assets.
An ERP qualifies the moment controlled technical information lands in it. DFARS 252.204-7012 lists examples of technical information that read like an ERP module list: "engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications" (DFARS 252.204-7012). Technical information with a military or space application becomes controlled technical information when it is subject to controls on access, use or release, which in practice means a distribution statement B through F.
Here is how each part of a typical ERP lines up with the asset categories.
| ERP component | Likely asset category if CUI is present | Why |
|---|---|---|
| Item master with drawing or spec attachments | CUI Asset | Stores controlled technical information |
| Bill of materials that came from a controlled drawing | CUI Asset | An "associated list" from a drawing can carry the same control |
| Routings, job travelers and work instructions | CUI Asset | Process sheets are named in the 7012 definition |
| Purchase orders that send drawings to suppliers | CUI Asset | They transmit CUI to an outside party |
| Quality module (inspection plans, first article reports) | CUI Asset if the records hold controlled dimensions or specs | Inspection data can copy the drawing |
| Financials, payroll and AR with no technical data | Possibly Contractor Risk Managed or out of scope | Depends on whether policy and configuration keep CUI out |
| ERP database server and file store for attachments | CUI Asset | Holds the stored CUI |
| Admin console, identity provider and backup system | Security Protection Asset | Controls who can reach CUI and protects copies of it |
| Supplier or customer portal | CUI Asset if drawings move through it | It transmits CUI to external users |
| Reporting tool or data warehouse fed by the ERP | CUI Asset if CUI fields are copied in | Copies of CUI are CUI |
The CMMC scoping guide explains the five asset categories in full, and the CMMC asset inventory page shows how to record each one.
Field-level analysis: decide where CUI sits
An ERP is a set of modules and tables, not one asset. Before you call the whole system a CUI Asset, map which fields, attachments and reports hold CUI and which never do. That map drives everything else on this page.
| Question | If yes | If no |
|---|---|---|
| Do users attach customer drawings or models to items, jobs or POs? | The attachment store and the modules that show it are in scope | Check whether drawings live in a separate PLM or file share instead |
| Do routings or travelers copy dimensions, tolerances or process steps from controlled drawings? | Those records are CUI | Routings that only reference a drawing number may not be |
| Do POs to suppliers include controlled specs or attachments? | Purchasing is transmitting CUI and DFARS 7012(m) flowdown applies | The supplier may still need the clause if they receive CUI another way |
| Do reports or exports pull CUI fields into spreadsheets? | Every place those exports land is in scope | Document that reports exclude CUI fields |
| Is part of the ERP used only by finance and HR? | It can be argued as Contractor Risk Managed if CUI is kept out by policy and configuration | It shares the same scope as the rest |
Add the results to your CUI data flow diagram. The CMMC for machine shops and CMMC for manufacturers pages show the same data path from RFQ to shipment.
There is no "CMMC certified ERP"
CMMC certifies an organization's information systems within a defined assessment scope, not a software product. An ERP vendor can sell you a service that makes your assessment easier: a FedRAMP authorized government cloud, a customer responsibility matrix, logging and role controls. It cannot hand you a CMMC status. When a vendor says its ERP is "CMMC compliant," read that as "you can configure this to support your Level 2 requirements," and ask for the documents in the vendor questions table below.
The same rule applies to accounting software. A GovCon accounting system that holds only labor, billing and cost data may never touch CUI, while a manufacturing ERP with controlled drawing attachments does. The test is what information reaches the system, not what the product is called. If you run an accounting or CPA firm, the CMMC for CPA and accounting firms page covers that situation.
Cloud ERP: the FedRAMP Moderate test
If your ERP runs as a cloud service and holds CUI, two rules apply at once.
- DFARS 252.204-7012(b)(2)(ii)(D) says a contractor that uses an external cloud service provider to store, process or transmit covered defense information must "require and ensure" that the provider meets security requirements equivalent to the FedRAMP Moderate baseline and complies with the clause's incident reporting, malicious software, media preservation, forensic access and damage assessment paragraphs.
- 32 CFR 170.16(c)(2) says a Level 2 (Self) contractor may use a cloud service with CUI if the offering is FedRAMP Authorized at Moderate or higher on the FedRAMP Marketplace, or meets equivalent requirements under DoD policy. Your own systems that connect to the cloud service stay in scope, and the provider's customer responsibility matrix must be documented or referred to in your SSP (32 CFR 170.16).
The DoD CIO's December 21, 2023 memo sets the equivalency bar. An offering that is FedRAMP Moderate Authorized on the Marketplace "can be leveraged without further assessment." An offering that is not must show 100 percent compliance with the latest FedRAMP Moderate baseline through an assessment by a FedRAMP-recognized third party assessment organization, hand the contractor a full body of evidence, and carry no open POA&M items from that assessment. The memo also puts the burden on you: the contractor, not the cloud provider, is held responsible for reporting if the offering is compromised (DoD CIO FedRAMP Moderate equivalency memo, PDF). The FedRAMP equivalency guide walks through the body of evidence.
ERP offerings on the FedRAMP Marketplace
We searched the FedRAMP Marketplace data on November 18, 2026 (data last changed November 16, 2026) for offerings whose descriptions cover ERP, financials or supply chain management. The table lists the ERP-related offerings we found.
| Offering (FedRAMP Marketplace listing) | Status and level | ERP scope in the listing description |
|---|---|---|
| Microsoft Azure Government (includes Dynamics 365) | FedRAMP Authorized, High | Dynamics 365 runs in Azure Government; see the Dynamics 365 section below |
| Oracle Fusion Cloud | FedRAMP Authorized, Moderate (authorized January 13, 2020) | ERP, supply chain management, inventory, manufacturing and maintenance. Oracle's Government Cloud is limited to government agencies and select federal contractors with a demonstrated need |
| Infor Government Solutions (IGS) Software as a Service | FedRAMP Authorized, Moderate (authorized July 10, 2018) | Financial and supply management, manufacturing ERP and asset management, hosted in AWS GovCloud (US) |
| SAP NS2 Cloud Intelligent Enterprise | FedRAMP Authorized, Moderate | SAP S/4HANA Private Cloud Edition and related SAP cloud solutions; the description is written for federal civilian agencies |
| SAP NS2 DoD Cloud Intelligent Enterprise | FedRAMP Authorized, Moderate | SAP S/4HANA Cloud Private Edition and Integrated Business Planning; the description is written for defense agencies and mission partners |
| Workday Government Cloud | FedRAMP Authorized, Moderate (authorized July 11, 2022) | Core financial management, projects, procurement and inventory; customers include U.S. government contractors |
| Deltek Costpoint GovCon Cloud Moderate | FedRAMP Ready, Moderate (Ready since December 12, 2025) | Project management, accounting, labor and material management for government contractors |
Two other listings sometimes come up. Accenture Federal Cloud ERP is FedRAMP Authorized at Moderate, but its description says it serves U.S. federal customers. AWS GovCloud is FedRAMP Authorized at High as infrastructure, which matters if you host an ERP yourself (covered below).
Confirm three things before you rely on any listing: that the exact government offering you are buying is the one listed, that the modules you plan to use are inside the authorization boundary, and that you have the provider's customer responsibility matrix. Marketplace status can change, so check the live listing on the day you sign.
FedRAMP Ready is not FedRAMP Authorized
FedRAMP Ready is a readiness designation on the Marketplace, not an authorization. 32 CFR 170.16(c)(2)(i) asks for an offering that is "FedRAMP Authorized at the FedRAMP Moderate (or higher) baseline in accordance with the FedRAMP Marketplace." A Ready offering does not meet that first test. To use it for CUI today, the provider would need to give you a body of evidence that meets DoD's equivalency memo, or you would wait for the authorization. Deltek's own listing description says Costpoint GovCon Cloud Moderate is designed to help contractors handle CUI and ITAR data, so ask Deltek directly which path it supports for your contract.
If your ERP vendor has no listing
A search of the FedRAMP Marketplace data on November 18, 2026 for Epicor, NetSuite, Acumatica and Unanet returned no listings. That does not mean those vendors can't be part of a compliant setup. It means the hosted cloud versions can't rely on the Marketplace route for CUI. You have three options:
| Option | What it takes | Watch out for |
|---|---|---|
| Ask for a FedRAMP Moderate equivalency body of evidence | A full 3PAO assessment against the Moderate baseline, no open 3PAO POA&M items, a CRM you can give assessors | A SOC 2 report or a "CMMC ready" one-pager is not equivalency |
| Run the vendor's on-premises or customer-hosted version | You host it in your own environment or in a FedRAMP authorized IaaS such as AWS GovCloud or Azure Government | You now own every Level 2 requirement for the servers, database and application |
| Keep CUI out of the ERP | Drawings and controlled specs live in a separate CUI environment; the ERP holds only part numbers and business data | It only works if users stop attaching CUI, and you document how you enforce it |
Dynamics 365 in GCC High
If you are moving email to GCC High, Microsoft's ERP apps can run in the same government cloud. Microsoft's Dynamics 365 US Government documentation, updated November 10, 2026, lists Dynamics 365 Finance and Dynamics 365 Supply Chain Management as available in GCC, GCC High and DoD, with the DoD versions marked pending IL5 approval (Microsoft, Dynamics 365 US Government). The same page says the GCC High option "enables and requires the customer to use Microsoft Entra Government for customer identities," and that for DoD contractors Microsoft operates the service in a way that enables them to meet ITAR and DFARS requirements.
| Dynamics 365 product | US Government cloud availability (Microsoft Learn, November 2026) | What it means for CUI |
|---|---|---|
| Dynamics 365 Finance | GCC, GCC High, DoD (DoD pending IL5) | A government cloud option exists |
| Dynamics 365 Supply Chain Management | GCC, GCC High, DoD (DoD pending IL5) | A government cloud option exists, including manufacturing and inventory |
| Dynamics 365 Business Central | Listed for commercial geographies, including the United States; no US Government cloud listed | The commercial service is not in a government cloud, so treat it like any cloud ERP without a Marketplace listing |
| Copilot features in Finance and Supply Chain Management | Not currently supported in GCC and GCC High | Don't plan AI features into a GCC High ERP rollout |
Sources: Microsoft, Dynamics 365 product availability and Microsoft, Finance and Supply Chain Management in GCC.
The Business Central row matters if you run it. If your Business Central tenant holds drawings or controlled specs, you are in the same position as any vendor without a listing: get an equivalency body of evidence, move CUI out, or move to an offering that has one. The GCC High CMMC page explains the tenant side, and Azure Government for CMMC covers the infrastructure side.
On-premises and self-hosted ERP
Running your ERP on a server in the building or on virtual machines in a cloud you manage is allowed. It shifts the work from checking a vendor's authorization to proving your own controls.
| Hosting model | Who carries the Level 2 requirements | FedRAMP question |
|---|---|---|
| On a server in your building | You, for the hardware, operating system, database, application and network | None for the ERP itself; the physical site is in scope |
| On virtual machines you run in AWS GovCloud or Azure Government | Shared: the cloud provider covers the infrastructure it lists in its CRM; you cover everything you configure | The IaaS must meet the FedRAMP Moderate rule; both listed here are Authorized at High |
| On virtual machines in a commercial cloud region | Shared, but the infrastructure must still meet the FedRAMP Moderate rule if CUI is stored there | Check the exact region and service listing |
| Hosted and run by your ERP partner or MSP | Depends on whether the partner is a cloud service provider or an external service provider | See the next section |
Self-hosting gives you control over patching, logging and encryption, and it also makes them your findings if they are missing. The ERP's database server, application server, attachment file share and backups are all CUI Assets. An old ERP version on an unsupported operating system is a flaw remediation problem under SI.L2-3.14.1. See AWS GovCloud for CMMC for the IaaS side.
When an ERP partner hosts or manages it
A value-added reseller or MSP that hosts your ERP or has admin access to it may be part of your scope. 32 CFR 170.4 defines an External Service Provider as external people, technology or facilities used for IT or cybersecurity services, and it only counts as an ESP if CUI or security protection data is processed, stored or transmitted on its assets. 170.19 then splits the rules:
| Partner role | CMMC treatment | What you need |
|---|---|---|
| Partner runs a cloud service that stores your ERP data with CUI | Cloud service provider; must meet the FedRAMP requirements in DFARS 7012 | A Marketplace listing at Moderate or higher, or an equivalency body of evidence |
| Partner hosts or manages your ERP on its own assets and CUI passes through them (not a cloud service) | ESP; its services are assessed as part of your assessment against all Level 2 requirements | SSP entries, the partner's service description and CRM |
| Partner holds only security protection data, such as logs or configuration | Assessed as Security Protection Assets | SSP entries and CRM |
| Partner never touches CUI or security protection data | Not an ESP under CMMC | Document why |
A partner with remote admin access to the ERP server is also a remote access path you must monitor and control under AC.L2-3.1.12. The CMMC external service provider requirements and shared responsibility matrix pages go deeper.
The Level 2 requirements an ERP touches most
Every one of the 110 requirements applies to a CUI Asset, but these are the ones that map most directly to ERP settings. Point values come from 32 CFR 170.24.
| Requirement | NIST SP 800-171 Rev 2 text (short) | What it means in an ERP | Points |
|---|---|---|---|
| AC.L2-3.1.1 | Limit system access to authorized users, processes and devices | Named accounts only; disable shared shop-floor logins and service accounts nobody owns | 5 |
| AC.L2-3.1.2 | Limit access to the types of transactions and functions users may execute | Role permissions decide who can open drawings, edit routings or approve POs | 5 |
| AC.L2-3.1.3 | Control the flow of CUI in accordance with approved authorizations | Stop CUI attachments flowing to suppliers, portals or reports that aren't approved | 1 |
| AC.L2-3.1.5 | Least privilege, including privileged accounts | Few ERP administrators; super-user rights not handed out for convenience | 3 |
| AC.L2-3.1.7 | Prevent non-privileged users from executing privileged functions and log them | Security setup, role changes and user creation logged and limited to admins | 1 |
| AC.L2-3.1.20 | Verify and control connections to external systems | EDI links, supplier portals and integrations approved and documented | 1, never on a POA&M |
| AU.L2-3.3.1 | Create and retain audit logs | The ERP and database log access and changes, and you keep them | 5 |
| AU.L2-3.3.2 | Actions traceable to individual users | No generic logins, so each change ties to a person | 3 |
| AU.L2-3.3.8 | Protect audit information from unauthorized access, modification and deletion | ERP admins can't quietly purge the logs | 1 |
| CM.L2-3.4.1 | Baseline configurations and inventories | ERP version, modules, servers and integrations documented | 5 |
| IA.L2-3.5.3 | MFA for privileged accounts and network access | MFA for ERP admins and for remote or cloud ERP logins | 3 or 5 |
| SC.L2-3.13.8 | Cryptography to protect CUI in transit | Encrypted connections to the ERP, the database and integrations | 3 |
| SC.L2-3.13.11 | FIPS-validated cryptography when protecting CUI | The encryption modules must be FIPS-validated | 3 if not FIPS, 5 if none |
| SC.L2-3.13.16 | Protect the confidentiality of CUI at rest | Database and attachment storage protected at rest | 1 |
| SI.L2-3.14.1 | Identify, report and correct flaws in a timely manner | ERP, database and server patches applied on schedule | 5 |
The CMMC encryption requirements and FIPS 140-2 requirements pages cover what counts as validated cryptography, and the MFA requirements page covers the 3-or-5 scoring.
Roles and least privilege inside the ERP
Build ERP roles around who needs to open CUI fields and attachments to do their job, not around who has always had access.
| ERP role | Typical CUI need | Access to set |
|---|---|---|
| Engineering and quality | View and edit drawings, specs, inspection plans | Full access to CUI attachments for assigned programs |
| Production and shop floor | View travelers and work instructions for jobs in progress | Read-only access to CUI on active jobs; no export |
| Purchasing | Send controlled specs to approved suppliers | Attach CUI only to POs for suppliers that have accepted DFARS 7012 flowdown |
| Sales and estimating | Read RFQ packages to quote | Access during quoting, removed or archived after award or loss |
| Finance, payroll and HR | Usually none | No access to CUI attachments or CUI fields |
| ERP administrators | System setup, not daily CUI use | Separate admin accounts with MFA; daily work done in a normal account (AC.L2-3.1.6) |
| Partner or vendor support | Troubleshooting | Time-limited, logged access approved per session |
Shared logins on shop-floor terminals and ERP accounts left active for former employees each break AC.L2-3.1.1 and AU.L2-3.3.2 at once. The privileged access management page covers admin accounts in detail.
Audit logs: when the ERP doesn't log what assessors ask for
AU.L2-3.3.1 asks you to create and retain audit logs "to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity," and AU.L2-3.3.2 asks that actions be traceable to individual users. Some ERPs record financial transactions in detail but few security events. Check what yours records.
| Event | Why an assessor cares | Where to look if the ERP doesn't log it |
|---|---|---|
| Successful and failed logins | Detects account misuse | Identity provider or single sign-on logs |
| User created, disabled or role changed | Shows access control is enforced | ERP security audit table, database triggers, or a change ticket trail |
| CUI attachment opened, downloaded or exported | Shows who touched CUI | Document management or file share logs if attachments are stored there |
| Configuration changes | Supports CM.L2-3.4.1 and 3.4.3 | Change management records |
| Administrator actions | AC.L2-3.1.7 requires logging privileged functions | Database and server logs |
| Integration and API activity | Shows which external systems pulled data | Integration platform or firewall logs |
Send what you can to a central log tool and protect it from ERP admins under AU.L2-3.3.8. Where the ERP can't log an event, document the compensating source in your SSP. The SIEM for CMMC page explains what to forward and how long to keep it.
Integrations, exports and reports
CUI that enters the ERP can leave it through supplier POs, spreadsheets, portals and integrations. Each path is either controlled or a finding.
| Data path | Requirement it touches | Control to put in place |
|---|---|---|
| POs with drawings emailed to suppliers | AC.L2-3.1.3, SC.L2-3.13.8, DFARS 7012(m) | Send through an approved encrypted channel; confirm flowdown first |
| EDI and customer portals | AC.L2-3.1.20 | Approve each connection; list it in the SSP and network diagram |
| Report exports to Excel or PDF | AC.L2-3.1.3, MP family | Restrict export rights on CUI reports; label exports; store them only in the CUI environment |
| Integrations with PLM, CAD or MES | AC.L2-3.1.20, CM.L2-3.4.1 | Document the interface; both ends are in scope if CUI passes |
| Public-facing web store or catalog fed by the ERP | AC.L2-3.1.22 (never on a POA&M) | Confirm no CUI fields reach anything public |
| ERP backups | MP.L2-3.8.9 | Protect backup copies of CUI at the storage location |
For the file transfer side, see CMMC compliant file sharing. For backup storage, see CMMC compliant backup solutions. DFARS 7012(m) requires you to flow the clause to subcontractors whose performance involves covered defense information, and the CMMC flowdown checklist covers that paperwork.
Keeping CUI out of the ERP
Another option is an ERP that never holds CUI. If drawings and specs live in a separate CUI environment, such as a GCC High tenant, a managed enclave or a PLM system you have scoped, the ERP can store only the part number, revision and a pointer.
That only holds up if three things are true:
- Policy and configuration keep CUI out. Attachment fields are disabled or restricted for controlled parts, and users are trained on the rule.
- You can show it. A sample of items, jobs and POs proves there are no controlled attachments or copied specs.
- You document the treatment. 170.19 lets an asset that "can, but [is] not intended to" hold CUI be treated as a Contractor Risk Managed Asset, but it still goes in your asset inventory, SSP and network diagram, and an assessor can run a limited check if the documentation raises questions.
The CMMC scope reduction and enclave vs enterprise pages compare the approaches. If CUI is already spread across years of ERP records, cleaning it out may cost more than securing the ERP.
How an ERP gap affects your SPRS score
A Level 2 self-assessment starts at 110 points and subtracts each NOT MET requirement's value. Under 32 CFR 170.21, you can reach Conditional Level 2 (Self) status with open items only if your score is at least 88 (0.8 of 110), every open item is worth 1 point (or is 3.13.11 with non-FIPS encryption), none of them is on the excluded list, and you close them within 180 days.
| ERP gap | Requirement | Points lost | Can it go on a POA&M for Conditional status? |
|---|---|---|---|
| Shared shop-floor logins on the ERP | AC.L2-3.1.1 and AU.L2-3.3.2 | 5 + 3 | No |
| Everyone can open drawings regardless of job | AC.L2-3.1.2 | 5 | No |
| ERP does not keep audit logs | AU.L2-3.3.1 | 5 | No |
| ERP admins can delete logs | AU.L2-3.3.8 | 1 | Yes |
| MFA missing for ERP users | IA.L2-3.5.3 | 3 if only remote and privileged users have MFA, 5 if no users do | No |
| Unpatched ERP or database server | SI.L2-3.14.1 | 5 | No |
| Encryption on, but not FIPS-validated | SC.L2-3.13.11 | 3 | Yes, this is the one 3-point exception |
| Undocumented supplier portal connection | AC.L2-3.1.20 | 1 | No, it is on the excluded list |
| ERP left out of the SSP | CA.L2-3.12.4 | No point value; 170.24 says an assessment can't be completed without an up-to-date SSP | No, it is on the excluded list |
A cloud ERP that holds CUI without a Marketplace authorization or an equivalency body of evidence isn't a point deduction you can plan around. The service doesn't meet 32 CFR 170.16(c)(2) or DFARS 7012. Move the CUI or move providers. The SPRS score guide explains how the score is posted, and the POA&M 180-day rule explains the closeout clock.
Evidence to keep for your ERP
Your Affirming Official signs off on the score, and DoD can still run government-led assessments during the suspension. Keep evidence you could hand over.
| Evidence | What it proves |
|---|---|
| Field-level CUI map of the ERP (modules, attachments, reports) | You know where CUI sits |
| Asset inventory and network diagram entries for ERP servers, database, portals and integrations | The ERP is in your scope documents |
| FedRAMP Marketplace listing or equivalency body of evidence, plus the CRM | The cloud rule is met |
| Role matrix and a current user list with roles | Access is limited by job function |
| Admin account list and MFA settings | Privileged access is controlled |
| Sample audit log entries for logins, role changes and attachment access | Logging works and ties actions to people |
| Patch records for the ERP, database and servers | Flaws are fixed on schedule |
| Encryption settings and FIPS validation references | CUI is protected in transit and at rest |
| Integration and export inventory | CUI flow is controlled |
| SSP section describing the ERP and its asset category | The scope decision is documented |
The CMMC Level 2 documentation checklist shows where these fit in your SSP.
Step by step: making your ERP CMMC ready
- List every module and connected system. Include the ERP, its database, attachment storage, reporting tools, portals, EDI and anything that syncs with it.
- Map CUI at the field level. Ask engineering, purchasing, quality and production where drawings, specs and controlled data enter and leave the ERP.
- Pick the asset category. Decide CUI Asset, Contractor Risk Managed Asset or out of scope for each component, and write down why.
- Check the hosting rule. For a cloud ERP, find the Marketplace listing at Moderate or higher or get an equivalency body of evidence. For self-hosting, confirm the infrastructure meets the rule.
- Fix accounts and roles. Remove shared logins, disable stale accounts and build roles around CUI need.
- Turn on MFA and encryption. MFA for admins and remote access; FIPS-validated encryption for CUI in transit and at rest.
- Get the logs flowing. Log logins, role changes, admin actions and attachment access, and protect the logs.
- Control exports and integrations. Restrict CUI exports, approve each external connection and confirm supplier flowdown before sending drawings.
- Patch and baseline. Document the ERP version and configuration and add it to your patch cycle.
- Update the SSP and score. Describe the ERP in your SSP, score each requirement from evidence and post the result in SPRS.
Buying a CMMC compliant ERP: questions to ask the vendor
No vendor can sell you CMMC compliance, because CMMC assesses your systems. These questions separate a vendor that can support your Level 2 scope from one that only uses the term in marketing.
| Ask the vendor | A good answer | A red flag |
|---|---|---|
| Is this exact offering FedRAMP Authorized at Moderate or higher? | A Marketplace listing for the government version you'd buy | "We're CMMC compliant" with no listing |
| Are the modules I need inside the authorization boundary? | A written boundary naming manufacturing, inventory, purchasing and attachments | Only the core financials are covered |
| If not authorized, can you give me a FedRAMP Moderate equivalency body of evidence? | A 3PAO assessment with no open 3PAO POA&M items | A SOC 2 report offered as a substitute |
| Can I see your customer responsibility matrix? | A CRM mapped to NIST SP 800-171 | A marketing one-pager |
| Where are attachments and backups stored, and who can reach them? | U.S. government cloud regions and screened, logged support access | General global support with no access logs |
| What security events does the ERP log, and can I export them? | Logins, role changes, admin actions and document access, exportable to my SIEM | Transaction history only |
| Does it support MFA and my identity provider? | MFA for all users, single sign-on with a government identity service where needed | Passwords only |
| Is the encryption FIPS-validated? | A validation reference for the modules used | "Bank-grade encryption" |
| How will you notify me of an incident in time for DFARS 7012's 72-hour report? | A documented notification process | No answer |
If you're also choosing a GCC High tenant, the best GCC High providers for CMMC page covers resellers, and CUI enclave providers covers enclaves that can hold drawings outside the ERP.
What the CMMC suspension changes for your ERP
The suspension changed the assessment type. The ERP requirements stayed the same. On July 13, 2026 the Department of War suspended the move to CMMC Phase II. The implementing memo says requiring activities may include only CMMC Level 1 (Self) or Level 2 (Self) and may not designate Level 2 (C3PAO) or Level 3 (DIBCAC) (suspension memo, PDF). The DoD CIO CMMC page still says that "All Phase I self-assessment requirements remain firmly in place" and that the suspension "does not eliminate the requirement for companies to protect information in accordance with DFARS clause 252.204-7012." Class Deviation 2026-O0025, Revision 3, dated September 3, 2026, tells contracting officers to remove or revise CMMC requirements to match, and newer contracts may show 7012 dated (JUN 2026)(DEVIATION 2026-O0025). As of November 18, 2026, no restart date has been announced. CMMC phases tracks the status.
| Item | Status on November 18, 2026 | Source |
|---|---|---|
| Level 2 (Self) in new contracts | Allowed | Suspension memo; Class Deviation 2026-O0025, Revision 3 |
| Level 2 (C3PAO) designations | Not allowed during the suspension | Suspension memo |
| All 110 requirements for an ERP that holds CUI | Still part of Level 2 | 32 CFR 170; NIST SP 800-171 Rev 2 |
| FedRAMP Moderate rule for a cloud ERP with CUI | Still in force | DFARS 252.204-7012; 32 CFR 170.16 |
| Government-led assessments | May still happen | DoD CIO CMMC page |
NIST SP 800-171 Revision 3 was published in May 2024, but 32 CFR 170 is built on Revision 2 and DoD says it is enforcing Revision 2 during the suspension. Score your ERP against Revision 2 unless your contract says otherwise. See NIST 800-171 Rev 2 vs Rev 3.
What it costs
ERP licensing and migration costs vary too much by vendor, module count and user count for us to publish a reliable range, and we don't quote prices we can't source. These are the drivers that move the number.
| Cost driver | Why it matters |
|---|---|
| Moving from a commercial cloud ERP to a FedRAMP authorized government offering | Government editions are separate products with their own pricing, eligibility rules and module lists |
| Migrating years of records and attachments | Data cleanup decides whether old CUI moves with you or gets purged |
| Self-hosting in AWS GovCloud or Azure Government | You pay for the infrastructure and for the admin work you now own |
| Role redesign and account cleanup | Internal hours, plus partner time if the ERP is heavily customized |
| Log forwarding and retention | Your SIEM or log service may charge by volume |
| MFA and identity integration | Licenses for a government identity service if you move to GCC High |
| SSP, policy and evidence work | Internal hours or consultant time |
For the assessment itself, DoD's final rule estimates $34,277 for a small entity's Level 2 self-assessment and affirmation and $37,196 over three years (CMMC final rule, 89 FR 83092). Those figures assume the requirements are already in place, so ERP work costs extra.
Common ERP mistakes with CMMC
- Calling the ERP "accounting" and leaving it off the asset inventory. If drawings are attached anywhere in it, it is a CUI Asset.
- Assuming the vendor's brand name covers your edition. The government offering, and the modules you use, must be inside the authorization.
- Treating FedRAMP Ready as authorized. Ready does not meet 170.16(c)(2)(i).
- Accepting a SOC 2 report as FedRAMP equivalency. The DoD memo requires a FedRAMP 3PAO assessment against the full Moderate baseline.
- Moving email to GCC High but leaving the ERP on a commercial cloud. Drawings attached to POs then sit outside your boundary.
- Shared logins on shop-floor terminals. They break unique identification and audit traceability at the same time.
- Forgetting the ERP partner's remote access. A reseller with admin rights is part of your scope and your remote access controls.
- Exporting CUI reports to personal drives. Every export location joins your scope.
Which provider category fits
| If you need | Provider category | Start here |
|---|---|---|
| A field-level scope decision and SSP language for the ERP | Readiness consultant or RPO | CMMC consultant |
| A government cloud tenant for email, files and Dynamics 365 | GCC High provider or MSP | GCC High CMMC |
| A place to keep drawings out of the ERP | CUI enclave provider | CUI enclave providers |
| Ongoing patching, logging and MFA for a self-hosted ERP | Managed service provider | CMMC provider categories |
| Help with ITAR data in the ERP | ITAR-experienced consultant | CMMC for ITAR companies |
The CMMC provider categories page explains how these differ. Find My CMMC Path is free; we may receive a referral fee from providers, and providers can't pay for placement in a recommendation.
CMMC compliant ERP: FAQ
Is my ERP in scope for CMMC?
Yes, if it processes, stores or transmits CUI. In practice that means drawings, specs, parts lists, process sheets or other controlled technical information in items, jobs, routings, POs, quality records or attachments. An ERP that never holds CUI may be treated as a Contractor Risk Managed Asset or out of scope, with documentation.
Is there such a thing as a CMMC certified ERP?
No. CMMC assesses your company's information systems, not software products. An ERP vendor can give you a FedRAMP authorized government offering and a customer responsibility matrix, but your configuration and evidence decide your score.
Which cloud ERPs are FedRAMP authorized?
On November 18, 2026 the FedRAMP Marketplace listed Azure Government including Dynamics 365 (High), Oracle Fusion Cloud, Infor Government Solutions, two SAP NS2 offerings and Workday Government Cloud (all Moderate) as Authorized. Eligibility differs by offering, so check the live listing, who it is sold to and the modules inside the boundary before you buy.
Is Deltek Costpoint FedRAMP authorized?
On November 18, 2026 the Marketplace listed Costpoint GovCon Cloud Moderate as FedRAMP Ready, not Authorized. Ready doesn't meet the first test in 32 CFR 170.16(c)(2), so ask Deltek for an equivalency body of evidence or confirm its authorization status before you put CUI in it.
Can I use Dynamics 365 Business Central for CUI?
Microsoft's product availability page lists Business Central for commercial geographies and no US Government cloud. If it will hold CUI, you need a FedRAMP Moderate equivalency body of evidence, a different offering such as Dynamics 365 Finance and Supply Chain Management in GCC High, or a design that keeps CUI out of it.
Is Dynamics 365 Supply Chain Management available in GCC High?
Yes. Microsoft lists Dynamics 365 Finance and Supply Chain Management in GCC, GCC High and DoD. The GCC High option requires Microsoft Entra Government, and Copilot features for those apps aren't currently supported in GCC or GCC High.
Does my on-premises ERP need FedRAMP?
No. FedRAMP applies to cloud services. An ERP on your own server is a CUI Asset that you secure yourself against all 110 requirements. If you host it on virtual machines in a cloud, the infrastructure service must meet the FedRAMP Moderate rule.
What if my ERP doesn't log user activity?
Log what you can from the surrounding systems, such as single sign-on, the database, the file store for attachments and the server, and send it to a central log tool. AU.L2-3.3.1 is worth 5 points and can't go on a POA&M, so a logging gap needs a fix, not a plan.
Does putting drawings in a separate system take the ERP out of scope?
It can. If policy and configuration keep CUI out of the ERP and you can show it, the ERP may be treated as a Contractor Risk Managed Asset. It still goes in your inventory, SSP and network diagram.
Does the CMMC suspension mean I can wait on ERP changes?
No. The suspension stopped Level 2 (C3PAO) and Level 3 designations, but Level 2 (Self) assessments, annual affirmations and DFARS 252.204-7012 still apply, and DoD says it is enforcing NIST SP 800-171 Rev 2 through self-assessments and select government-led assessments.
What we verified
On November 18, 2026 we opened each source linked on this page: the DoD CIO CMMC page, the July 13, 2026 suspension memo, Class Deviation 2026-O0025 Revision 3, 32 CFR 170.4, 170.16, 170.19, 170.21 and 170.24 on eCFR (current through November 16, 2026), DFARS 252.204-7012, 7020, 7021 and 7025, NIST SP 800-171 Revision 2, NIST SP 800-171A, NIST SP 800-171 Revision 3, the DoD CIO FedRAMP Moderate equivalency memo, the FedRAMP Marketplace listings in the tables (Marketplace data last changed November 16, 2026), Microsoft's Dynamics 365 US Government, product availability and Finance and Supply Chain Management in GCC documentation, and the CMMC final rule cost estimates. The vendor search for Epicor, NetSuite, Acumatica and Unanet covered the provider, offering and description fields of the Marketplace data. We did not test any vendor's product, and vendor features and Marketplace status can change.
Sources
- DoD CIO, About CMMC
- Implementing the DoW CIO's Suspension of CMMC Phase 2 Requirements, memo 26-P-1023 (July 13, 2026)
- Class Deviation 2026-O0025, Revision 3 (September 3, 2026)
- 32 CFR 170.4, Acronyms and definitions
- 32 CFR 170.16, CMMC Level 2 self-assessment
- 32 CFR 170.19, CMMC scoping
- 32 CFR 170.21, Plan of Action and Milestones requirements
- 32 CFR 170.24, CMMC Scoring Methodology
- DFARS 252.204-7012
- DFARS 252.204-7020
- DFARS 252.204-7021
- DFARS 252.204-7025
- NIST SP 800-171 Rev 2 (PDF)
- NIST SP 800-171A, Assessing Security Requirements for CUI
- NIST SP 800-171 Rev 3 (May 2024)
- DoD CIO, FedRAMP Moderate Equivalency for Cloud Service Provider's Cloud Service Offerings (December 21, 2023)
- FedRAMP Marketplace
- Microsoft, Dynamics 365 US Government
- Microsoft, Dynamics 365 product availability
- Microsoft, Dynamics 365 Finance and Supply Chain Management in US Government Community Cloud
- CMMC Program final rule, 89 FR 83092 (October 15, 2024)
- Hunton, CMMC Phase 2 Remains Paused (November 10, 2026)