Mixed commercial and defense work
Selected users and teams
Give the people handling CUI a focused working environment. Keep the wider business separate where the approved design allows.
CMMC for defense manufacturers
From enclave to enterprise.
SecureEnclave™ brings your defense work into one customer-controlled environment. Configure it for selected users, subcontractor enclaves, or your entire organization’s supported IT and OT systems.
Run supported applications on premises, with safeguards, technical evidence, and recovery managed together.
Built around the realities of manufacturing. Explore the MxD project context.
On this pageYour scope
Three ways to deploy
Choose the scope you need.
The same SecureEnclave™ product can serve a defined part of your business or the whole operation. Choose the boundary that matches where defense work happens.
The boundary follows Controlled Unclassified Information (CUI): who uses it, where it travels, and which systems support the work. User count is one part of that picture.
Built around manufacturing
From drawings to delivered parts.
Your protected environment needs to reach the places where the work gets done. SecureEnclave™ is designed around the selected applications, people, and production connections along that path.
Receive
Bring customer drawings, technical data, and supplier communications into the environment through approved paths.
Engineer
Give authorized people access to supported CAD/CAM tools, files, and collaboration services needed to prepare the work.
Plan and produce
Account for work instructions, production systems, connected equipment, and the paths that carry information to the shop floor.
Inspect and test
Connect the selected inspection and test workflow with its equipment, results, quality records, and authorized users.
Deliver and sustain
Control outgoing deliverables, supplier exchanges, continuing access, and retained records through the life of the work.
Review application and equipment fit
Map CAD/CAE/CAM tools, PLM or PDM, ERP or MRP, MES, workstations, printers, production equipment, OT connections, and inspection or test systems wherever they handle or support CUI. The design identifies supported products, versions, interfaces, permitted paths, and operating constraints.
IT and OT can share an overall operating model while retaining distinct network segments and safeguards. Equipment is evaluated for its role and limitations; the final assessment scope follows the information path, asset categorization, architecture, and documentation.
Map your workflow in a planning briefConsidering a cloud enclave?
Compare the complete cost.
Put your cloud proposal beside the environment your shop actually needs. Compare the work each option supports, what is included, and what your team still has to provide.
| What to compare | Include in both proposals |
|---|---|
| Applications and equipment | The engineering and business tools, production connections, printers, and inspection systems the workflow actually uses. |
| Included services | Identity, security monitoring, logging, technical evidence, backup, recovery, support, and any separately licensed software. |
| Work left with your team | Deployment, administration, integration, maintenance, incident handling, and assessment preparation. Identify who performs each task and what it costs. |
| Three-year operating cost | Implementation and migration, hardware or subscriptions, user and application licenses, compute, storage, connectivity, support, and internal labor. |
Compare the same users, applications, equipment, and service responsibilities. Cloud offerings and SecureEnclave™ configurations vary; the complete scope determines the cost.
Where FedRAMP fits
CMMC does not itself require a government-cloud tenancy. Under DFARS 252.204-7012, an external cloud provider used to store, process, or transmit covered defense information must meet security requirements equivalent to the FedRAMP Moderate baseline and the clause’s incident-response obligations.
A contractor-operated environment still has applicable safeguarding and assessment obligations. The service model and data paths determine which cloud requirements apply; an on-premises location alone does not settle that question.
The operating agreement
Know who handles what.
Agree on the platform’s managed scope, the services included in the engagement, and the work your organization retains. Make those responsibilities explicit before deployment.
SecureEnclave™
Maintain the technical environment
Within the agreed scope, the platform maintains managed state, configured safeguards, telemetry, technical checks, evidence context, and supported recovery. The engagement defines support and operating duties.
Your organization
Authorize and oversee the work
Your organization owns policy, access decisions, risk, exceptions, incident responsibilities, affirmations, and the accuracy of submitted information. Subcontractor environments retain their applicable organizational obligations.
Independent assessor
Determine the assessment result
The applicable assessor evaluates the evidence and practices for the defined scope. SecureEnclave™ supports implementation and evidence; buying a platform does not confer certification.
MxD project 23-11-03
A manufacturing development focus.
MxD named NetThunder as the project team for Cybersecure Enclave Infrastructure as Code, focused on simplifying secure-environment provisioning, deployment, and maintenance for small and midsized manufacturers supporting DoD production. NetThunder developed SecureEnclave™ around that manufacturer-centered objective.
The public record identifies the team and objective. It does not establish MxD or government endorsement, a deployment outcome, or an assessment result.
Review the MxD project (opens in a new tab)Plan your deployment
Bring your workflow. Compare options.
Tell us who handles defense work, which applications and equipment they use, and what support you need. Bring a high-level workflow or cloud proposal; we’ll review SecureEnclave™ fit, responsibilities, and complete operating cost.