What CMMC looks like in a job shop
A typical Tier 3 precision shop has 20 to 120 employees, a front office on commercial Microsoft 365, a handful of engineers and programmers running CAD/CAM, an ERP or job-tracking system, a quality lab with a CMM, and a floor of CNC machines that receive programs over the network or by USB. CUI enters as technical drawings and models from primes, gets turned into CAM programs and inspection plans, and leaves as first-article reports and certs.
The compliance mistake is to treat the whole building as one system. The engineering mistake is to assume the CNC controllers must meet all 110 requirements. Neither is necessary when the boundary is drawn on purpose.
The Swiss Automation lesson
Swiss Automation, a precision-machining subcontractor, resolved False Claims Act allegations that it failed to safeguard DoD technical drawings as DFARS 252.204-7012 requires. The data at issue was the most ordinary data in any machine shop: the prints.
The pattern is common: drawings arrive by commercial email, get saved to a shared drive everyone can open, printed for the floor, and copied to USB sticks for older controls. Each step is a requirement failure (3.1.1, 3.1.3, 3.8.1, 3.8.7, 3.13.16) and, once a score is posted to SPRS, a potential false statement. See the settlement tracker.
Draw the boundary around the engineers
In most shops only 3 to 10 people actually handle CUI: the estimator who reads RFQ drawings, the programmers, the quality engineer, and a program manager. Put those people, and only those people, inside an enclave for email, files and engineering applications. Everyone else stays on commercial tools, out of scope.
- Email and files: an encrypted overlay such as PreVeil, a GCC High enclave tenant, or a managed VDI.
- CAD/CAM: engineering workstations inside the enclave, or CAD/CAM running in VDI.
- ERP: keep part numbers and schedules (FCI) in ERP; keep drawings out of ERP attachments unless the ERP is in scope.
- Printing: a dedicated in-scope printer in the engineering area, with marked hard copies controlled under 3.8.1–3.8.5.
Use the cost estimator to compare: a 40-person shop with 6 CUI users pays a small fraction for an enclave of what a full GCC High migration costs.
CNC controllers and CMMs as Specialized Assets
32 CFR § 170.19 defines Specialized Assets, which include Operational Technology, Industrial IoT, test equipment and restricted information systems. CNC controllers, CMMs, robots and test stands that receive CUI-derived programs usually fall here. Specialized Assets must be documented in the asset inventory and SSP, shown on the network diagram, and managed using the contractor’s risk-based policies. They are not assessed against all 110 requirements.
- Put machines on a segmented OT VLAN with no internet route (supports 3.13.1, 3.13.6)
- Transfer programs from the enclave through a controlled DNC server or a single managed, encrypted USB process
- Delete programs from controls when jobs close where practical; record it
- List every controller, CMM and DNC server in the SSP with its owner and location
See the full category breakdown in the CUI scoping guide.
Handling prime flow-downs and supplier questionnaires
Primes such as Lockheed Martin, RTX, Northrop Grumman, General Dynamics, Boeing, BAE Systems and L3Harris flow DFARS 7012, 7019/7020 and increasingly 7021 into POs. Expect supplier cybersecurity questionnaires, requests for your SPRS score and date, and sometimes a requirement for a specific CMMC status before award.
- Keep a register of POs that carry DFARS cyber clauses and the CUI they deliver.
- Answer questionnaires from your SSP, never from memory. Inconsistent answers are discoverable.
- Report the score you can defend with evidence. A lower honest score with a dated plan is safer than a high score you cannot support.
- Flow the same clauses to your own sub-tier suppliers (heat treat, plating, inspection) when they receive drawings, and verify their SPRS entries under 7020.
ITAR on top of CMMC
ITAR-controlled technical data adds a different rule: access by foreign persons is an export unless authorized. Enclave choice matters here. GCC High offers U.S.-person support and U.S. data residency; end-to-end encryption overlays keep data unreadable to the provider; managed VDI keeps data in a U.S. environment. Whatever the platform, your access control lists and onboarding must confirm U.S.-person status for anyone inside the ITAR boundary.
A 90-day starting plan
- Weeks 1–2: list CUI-bearing contracts, identify CUI users, inventory machines and DNC paths.
- Weeks 3–4: choose the enclave path and order it; obtain the ECA certificate for incident reporting.
- Weeks 5–8: move drawings and engineering email into the enclave; segment the OT network.
- Weeks 9–12: write the SSP, score with the SPRS calculator, build the POA&M, and post an honest score.