[CMMC L2 Compliance]

Custom CMMC
Enclaves

For the Defense Industrial Base (DIB).

A contract defines what you deliver. Your business processes produce it. An enclave lets those processes run while protecting the controlled information they touch.

  1. 01Business Modeling[Current State]
  2. 02Enclave Proposal[Target State]
  3. 03Implementation
  4. 04Assessment Support
[What is an enclave?]

A protected environment with two jobs.

An enclave is the bounded, access-controlled environment where you store, process, and transmit Controlled Unclassified Information (CUI), kept separate from the rest of the business so less is in scope for assessment.

01 [Enable]

Enable your organization to perform its operational work.

This requirement carries equal weight to CUI protection, because an enclave that impedes legitimate work will either be circumvented, which can expose your organization to False Claims Act (FCA) liability, or require reassessment to incorporate the needed functionality.

02 [Comply]

Satisfy CUI protection requirements under NIST SP 800-171 and applicable LRGWPs.

The enclave must meet the security requirements of NIST SP 800-171 Revision 2, the baseline for any non-federal system handling CUI. The laws, regulations, or government-wide policies (LRGWPs) that apply to your data may add more.

[What does custom mean?]

Not sacrificing business functionality
for compliance.

Out-of-the-box SaaS suits a simple use case. It becomes a risk when it is bought before anyone checks it against how the business works.

Input Trace starts by understanding your business requirements first, then builds a solution around how your organization actually operates. Depending on those requirements, the solution may take the form of one of the three architectural patterns outlined below.

Problems that can arise from not understanding your business needs:

  • 01 Functionality gaps surface after a SaaS product is procured, and get patched in after the fact.
  • 02 Mature internal processes are sacrificed to fit the technical features the tool provides.
  1. [Type 01]Simplest

    SaaS

    The provider manages everything and gives your users access to a tenant in its environment. It is best for lightweight software requirements.

    Example requirements
    • Office Suite
    • Lightweight VDI Apps
  2. [Type 02]More complicated

    Cloud

    Our specialty

    Part of the work needs an application SaaS cannot host. IaaS/PaaS extends the boundary to run it, and the SaaS runs alongside it.

    Example requirements
    • PostgreSQL-Backed App
    • Custom Service Integrations
  3. [Type 03]Most complicated

    Cloud + On-Prem

    Our specialty

    Part of the CUI workflow needs to exist onsite. The enclave has to extend to the room where that work happens, which in turn captures many additional device types into the scope of assessment.

    Example requirements
    • CAD
    • Real Time Software
    • Embedded Firmware Flashing
[How does our engagement process work?]

Reduce risk.
Clarity before you implement.

Every organization handles CUI differently, so an accurate design, budget, and implementation timeline cannot be responsibly developed before the business is understood.

We begin with a fixed-price, $5,000 architecture engagement: two phases that model how you operate today and define the target-state architecture, with recommended technologies, projected costs, and an implementation roadmap, before you commit to purchasing products or deploying infrastructure.

  • Control cost

    Understand the full cost before implementation begins.

    Enclave costs can extend far beyond the initial technology purchase. We consolidate infrastructure, licensing, managed services, facilities, implementation, and ongoing operations into a transparent cost model.

  • Protect operations

    Design compliance around how your business works.

    We model your workflows first so the enclave enables your operations rather than restricting them.

  • Establish a roadmap

    Know what must happen and when.

    We develop a sequenced implementation roadmap so you can understand the work ahead, plan around business priorities, and prepare for assessment.

  1. 01
    [P-01]Current State

    Business Modeling

    Map how FCI and CUI enter, move, mutate, and leave the business.

    • Current-state data-flow diagram
    • External-org inventory
    • In-scope asset list
  2. 02
    [P-02]Target State

    Enclave Proposal

    Fix the physical and logical boundary, then propose the target state.

    • Target Design Package (TDP)
    • Shared Responsibility Matrix
    • SSP skeleton
  3. 03
    [P-03]

    Implementation

    Build the target state in your tenant and at your site.

    • Deployed enclave
    • Hardening baselines
    • As-built documentation
  4. 04
    [P-04]

    Assessment Support

    Assemble evidence, walk the mock assessment, and sit with the C3PAO through the actual audit.

    • Evidence package
    • Mock assessment
    • C3PAO audit support
[Process]

Discipline is what makes the artifacts defensible.

Every workflow produces a named artifact. Every artifact traces to a control. Every control traces to an assessor question.

  • Treat the business as an information system.

    It takes inputs, transforms them through business processes, and produces deliverables. Every component inside it is the same kind of thing.

  • Run one set of questions, recursively.

    The same questions apply to every component. Follow the data from node to node until you reach a base case.

  • The data-flow diagram is the artifact.

    Roles with CUI access read off the diagram. In-scope networks come from superimposing it over the topology, physical rooms from the floor plan.

  • Plan for the contract you have not won yet.

    DoD's CMMC final rule (89 FR 83092) says significant architectural or boundary changes to the assessment scope require a new assessment. We design the enclave so growth inside the pattern stays inside that scope.

[Trust]

Plenty of providers say they can take you end to end.
Few actually can.

Getting to CMMC Level 2 certification takes a specific stack of capabilities: the regulation, the architecture, and the shop floor.

  • Enterprise background

    Our security architects have designed and deployed environments at global-enterprise scale. We bring the discipline that complexity requires to shops of five to five hundred.

  • Veteran-owned

    Co-founded by a Navy veteran. We know what it means to serve. The Defense Industrial Base is the community we come from, not one we recently discovered.

  • Assessor-defensible by construction

    The methodology is built to hold up under assessment, not just compliant on paper. Input Trace is not a C3PAO. We build and support the environment. An independent C3PAO assesses it, and nobody can promise that outcome.

[Start]

Ready to map your CUI flow?

A discovery conversation is the fastest way to understand whether Input Trace is a fit. We will walk the current state and scope the engagement from there.

See the engagement, phase by phase