Defense & intelligence · Managed environment

Mission Partner Environment (MPE) Builder

Stand up a partner enclave for a mission, run it, and take it down with the evidence to show it is gone

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

The Mission Partner Environment (MPE) Builder is a Moraph-managed service that builds secure network enclaves from approved templates so US forces can share information with mission partners for a defined mission and period. Moraph builds and operates each enclave on infrastructure your organization authorizes, and partner access follows the disclosure decisions your foreign disclosure officers make. When the mission ends, Moraph tears the enclave down, revokes access and sanitizes storage, and records each step as evidence.

The problem it solves

Coalition and partner operations need a place where US forces and allies can work on the same information, but each enclave is often built by hand, under time pressure, with its own one-off configuration. Partner accounts accumulate, data is copied in without a clear record of what was released to whom, and when the mission ends nobody can say with confidence that every account, copy and connection has gone. The same work is repeated for the next mission with little reuse.

  • Each enclave is built from scratch with a different configuration
  • What was released to which partner is hard to trace back to a disclosure decision
  • Partner accounts and connections linger after the mission ends
  • There is no consistent evidence that storage was sanitized at teardown

Who uses it

  • Combatant command and service component staff who plan partner information sharing
  • Foreign disclosure officers who approve what partners may receive
  • Information system security managers responsible for enclave authorization
  • Network operations teams who provide connectivity to partners
  • Assessors and inspectors who review partner access and teardown evidence

Requirements it supports

DoD Instruction 8110.01, Mission Partner Environment Information Sharing Capability Implementation for the DoDDoD Directive 5230.11, Disclosure of Classified Military Information to Foreign Governments and International OrganizationsDoD Instruction 8510.01, Risk Management Framework for DoD SystemsNIST SP 800-53 Rev. 5, Security and Privacy ControlsNIST SP 800-88 Rev. 1, Guidelines for Media SanitizationInternational Traffic in Arms Regulations (22 CFR Parts 120-130)

The product supports these requirements; meeting them remains your organization’s responsibility.

Responsibilities

Who is responsible for what

Moraph builds and runs the enclaves, the infrastructure and software providers you authorize supply the underlying components under their own terms, and your organization decides what is shared, with whom, and under whose authority.

AreaMoraphInfrastructure and software providersYour organization
LicensingProcures or manages the software and cloud subscriptions the enclave templates useSet license terms for their productsApproves purchases and accepts provider terms
Infrastructure availabilityMonitors enclave infrastructure and raises cases with providersOperate their cloud regions, hardware and services under their own commitmentsProvides or authorizes the infrastructure and network connections
Enclave templatesMaintains hardened, versioned templates and the configuration baselinePublish the product capabilities and security guidance the templates useApproves templates for use through your ISSM
Partner identity and accessCreates and removes partner accounts and groups as approvedProvide the identity capabilities of their productsApproves each partner organization and person, and their access level
Disclosure and releaseConfigures sharing so only approved categories of information reach each partnerNoneMakes every disclosure and release decision through your foreign disclosure officer
MonitoringWatches enclave health, access and data movement against agreed rulesProvide platform logs and statusYour security operations team receives escalations and decides on incidents
Incident responseContains issues within the enclave under your runbook and supports your investigationHandle incidents in their own platforms under their termsLeads the incident and notifies partners and authorities
Changes and patchesApplies approved changes and patches, and keeps templates currentRelease patches and updates for their productsApproves changes and change windows
Teardown and sanitizationRevokes access, removes data and sanitizes storage, and records the evidenceProvide the deletion and sanitization mechanisms of their platformsDecides when the mission ends and what records are retained
User supportSecond-line support for enclave usersThird-line support for product defects through MoraphFirst-line support and partner liaison

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of the platform itself, which belongs to its vendor.

  1. Step 1

    The enclave inventory

    Every enclave in one list, with its mission, partners, template version and end date.

    EnclaveMissionPartnersTemplateUsersEndsStatus
    ENC-041Exercise Example Shield (fictional)Partner A, Partner Bv3.2148Fictional date 1Operating
    ENC-043Example Relief Mission (fictional)Partner Cv3.262Fictional date 2Operating
    ENC-044Exercise Example Bridge (fictional)Partner A, Partner Dv3.30Fictional date 3Awaiting ISSM approval
    ENC-038Exercise Example Harbor (fictional)Partner Bv3.10EndedTeardown evidence pending
    Every enclave in one list, with its mission, partners, template version and end date.

  2. Step 2

    A new enclave request

    The request names the mission, partners and period, and links each partner to its disclosure decision before anything is built.

    RQ-0219 · Exercise Example Bridge (fictional)

    Mission owner
    J6 planning cell (fictional)
    Partners
    Partner A, Partner D
    Expected users
    About 90
    Template
    Coalition collaboration v3.3
    Disclosure decisions
    Partner A recorded; !Partner D pending

    Approvals

    • Foreign disclosure officer: Partner A approved, Partner D pending
    • ISSM: template and boundary approved
    • Moraph: build plan confirmed
    The request names the mission, partners and period, and links each partner to its disclosure decision before anything is built.

  3. Step 3

    The build record

    Each build is checked against its template baseline and reviewed by the ISSM before partners are added.

    ENC-044 · Build from template v3.3

    Built from
    Template v3.3, code revision 7f2c (fictional)
    Network segments
    4
    Services
    Chat, file share, common operating picture viewer
    Sharing rules
    Set from disclosure decisions on file
    Baseline differences
    1

    Differences from baseline

    • File share quota raised for this mission at the mission owner's request
    • Recorded as an approved parameter, awaiting ISSM review
    Each build is checked against its template baseline and reviewed by the ISSM before partners are added.

  4. Step 4

    Partner access review

    Partner accounts are reviewed during the mission, and accounts not used or no longer needed are removed.

    PartnerAccountsNot used recentlyExpiringRemovals requestedStatus
    Partner A84606Certified
    Partner B41202Certified
    US users23000Certified
    Partner B liaison accounts333-Awaiting partner administrator
    Partner accounts are reviewed during the mission, and accounts not used or no longer needed are removed.

  5. Step 5

    Teardown

    When the mission ends, each teardown step is carried out and recorded, ending with the ISSM's sign-off.

    ENC-038 · Exercise Example Harbor (fictional)

    1. End of mission confirmed and retained records listedMission owner
    2. All partner and US accounts disabled, keys revokedMoraph engineer
    3. Partner connections removedMoraph engineer and your network team
    4. Retained records transferred with manifestMoraph engineer
    5. Data deleted and storage sanitized by the agreed methodMoraph engineer
    6. Teardown evidence reviewed and signed offISSM
    When the mission ends, each teardown step is carried out and recorded, ending with the ISSM's sign-off.

  6. Step 6

    The monthly service review

    Each month Moraph reviews the service with you: enclaves running and planned, changes, alerts, teardowns and open actions.

    Monthly service review · Example Component Command (fictional)

    Enclaves operating
    2
    Enclaves requested
    1
    Teardowns completed
    1, evidence pending sign-off
    Changes applied
    9
    Alerts escalated
    1

    Actions agreed

    • ISSM to sign off ENC-038 teardown evidence
    • Foreign disclosure office to record decision for Partner D
    • Moraph to retire template v3.1 once ENC-038 is closed
    Each month Moraph reviews the service with you: enclaves running and planned, changes, alerts, teardowns and open actions.

Workflows

The principal workflows

  1. Request and approve

    A mission owner requests an enclave for a named mission, its partners and its period. The foreign disclosure officer records what categories of information may be shared with each partner, and the ISSM approves the template and boundary.

    • Mission owner submits the request with partners, expected users and mission period
    • Foreign disclosure officer records the disclosure decision for each partner
    • ISSM confirms the template, boundary and connections are within the authorization
    • Moraph confirms capacity and the build plan
    • Request approved and the enclave scheduled

  2. Build

    Moraph builds the enclave from an approved, versioned template using infrastructure as code, so each enclave starts from the same hardened configuration and differences are recorded.

    • Template version selected and parameters set for the mission
    • Infrastructure, network segments and services provisioned from code
    • Sharing rules set to match the recorded disclosure decisions
    • Build checked against the configuration baseline
    • ISSM reviews the build record and approves operation

  3. Operate

    Partners are onboarded as your organization approves them, and Moraph runs the enclave: monitoring, patching, change control and user support for the life of the mission.

    • Partner organizations and named users approved and accounts created
    • Information shared into the enclave under the recorded disclosure decisions
    • Moraph monitors health, access and data movement
    • Changes and patches applied through your change process
    • Partner access reviewed on the cycle your procedures set

  4. Tear down

    When the mission owner closes the mission, Moraph revokes every partner account and connection, transfers the records your organization keeps, removes the remaining data and sanitizes storage, and records each step for your ISSM.

    • Mission owner confirms the end of the mission and the records to keep
    • Partner accounts, keys and connections revoked
    • Retained records transferred to your designated repository
    • Remaining data deleted and storage sanitized using the agreed method
    • Teardown record with evidence of each step signed off by the ISSM

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Mission owner

J6 or communications planner, mission commander's staff officer, program lead

Requests the enclave for a mission, names the partners and users, and decides when the mission ends.

Sees

  • Their mission's enclave, partners and users
  • Request, build and change status
  • Access reviews for their enclave
  • Teardown status and evidence

Does

  • Submits enclave requests with partners, users and mission period
  • Requests changes during the mission
  • Confirms partner users are still needed during access reviews
  • Confirms the end of the mission and lists the records to keep

Cannot

  • Approve disclosure to a partner
  • Approve the template or build
  • Extend an enclave past its end date without a recorded approval
Approvals
Their requests need a disclosure decision from the foreign disclosure officer and approval from the ISSM.
Notified about
Request and build status, end dates approaching, access reviews due and teardown complete.

Foreign disclosure officer

Foreign disclosure officer, foreign disclosure representative

Decides what categories of information each partner may receive, and keeps that decision linked to the enclave.

Sees

  • Requests naming partners
  • Disclosure decisions recorded for each enclave
  • Sharing rules configured from those decisions
  • Data movement records by partner

Does

  • Records the disclosure decision for each partner or references an existing one
  • Approves or returns sharing rules
  • Reviews data movement records
  • Withdraws a decision, which triggers the sharing rules to be updated

Cannot

  • Change enclave configuration directly
  • Approve builds or changes outside sharing rules
Approvals
Approves the sharing rules for each partner; their decisions follow your organization's own disclosure procedures.
Notified about
New requests naming partners, sharing rule drafts, and decisions approaching their review date.

ISSM

Information system security manager, cybersecurity lead

Approves the templates, each build and change, and signs off teardown evidence.

Sees

  • Templates and their baselines
  • Build records and baseline differences
  • Changes, alerts and incidents
  • Teardown evidence

Does

  • Approves templates for use
  • Reviews and approves each build before partners are added
  • Approves changes that affect the boundary or security settings
  • Signs off teardown evidence
  • Uses control mappings and evidence in your authorization

Cannot

  • Edit or delete audit records
  • Approve their own change request
Approvals
Approves templates, builds, security-relevant changes and teardowns; their own requests need a second designated approver.
Notified about
Builds awaiting review, baseline differences, escalated alerts and teardown evidence ready for sign-off.

Partner administrator

Partner liaison officer, partner network administrator

Manages their own organization's users in an enclave, within what has been approved.

Sees

  • Their organization's users and accounts in the enclave
  • Access reviews for their users

Does

  • Requests accounts for named users
  • Requests removal of users who leave
  • Completes access reviews for their organization

Cannot

  • See other partners' users
  • Change sharing rules or enclave configuration
  • Create accounts without approval
Approvals
Their account requests are approved by the mission owner.
Notified about
Accounts created or removed, access reviews due and end of mission.

Moraph service manager

Moraph service delivery manager

Runs the managed service: requests, builds, vendor relationships and monthly service reviews.

Sees

  • The enclave inventory, requests and change records
  • Alerts and incidents
  • Vendor cases and license usage
  • Teardown status

Does

  • Schedules builds once approvals are in place
  • Coordinates changes through your process
  • Manages underlying licenses and vendor cases
  • Runs monthly service reviews and tracks actions
  • Prepares evidence packages

Cannot

  • Approve disclosure, builds or changes on your behalf
  • See enclave content beyond what operations require
Approvals
Their work is governed by your approvals; nothing is self-approved.
Notified about
Approvals completed or returned, escalated alerts, vendor notices and overdue actions.

Moraph enclave engineer

Moraph infrastructure engineer, network security engineer

Builds, operates and tears down enclaves from approved templates, within the approvals your organization gives.

Sees

  • Enclave infrastructure and configuration
  • Health and access logs needed for operations
  • Runbooks and change requests assigned to them

Does

  • Builds enclaves from approved templates
  • Creates and removes accounts as approved
  • Applies approved changes and patches
  • Triages alerts and escalates confirmed issues
  • Carries out teardown steps and records the evidence

Cannot

  • Change sharing rules without a recorded disclosure decision
  • Apply an unapproved change
  • Sign off their own teardown
Approvals
Every build, change and teardown they carry out has a recorded approval from your organization.
Notified about
Builds and changes scheduled, alerts assigned to them and teardowns due.

Assessor or inspector (read-only)

Security control assessor, inspector general staff, internal auditor

Reviews access, disclosure, change and teardown records without changing anything.

Sees

  • Enclave inventory and templates
  • Disclosure references, access reviews and data movement records
  • Change records and teardown evidence

Does

  • Reads records within the scope granted
  • Exports evidence, with each export logged
  • Records review notes where enabled

Cannot

  • Change, approve or delete anything
  • Keep access after it expires
Approvals
Their access is approved by the ISSM with a scope and an end date.
Notified about
Nothing by default; access granted and expiring is confirmed to the ISSM.

Permissions at a glance

ActionMission ownerFDOISSMPartner adminMoraph SMMoraph engAssessor
Request an enclaveOwn work onlyNo accessNo accessNo accessFullNo accessNo access
Record a disclosure decisionNo accessFullView onlyNo accessNo accessNo accessView only
Approve sharing rulesNo accessApprovesView onlyNo accessNo accessNo accessNo access
Approve a template or buildNo accessNo accessApprovesNo accessNo accessNo accessNo access
Build an enclave from a templateNo accessNo accessNo accessNo accessNo accessFullNo access
Request partner accountsOwn work onlyNo accessNo accessOwn work onlyNo accessNo accessNo access
Create or remove accountsApprovesNo accessNo accessNo accessNo accessFullNo access
Apply changes and patchesNo accessNo accessApprovesNo accessNo accessFullNo access
View data movement recordsOwn work onlyFullFullNo accessView onlyView onlyView only
Confirm end of missionOwn work onlyNo accessView onlyNo accessView onlyNo accessNo access
Sign off teardown evidenceNo accessNo accessApprovesNo accessView onlyNo accessView only
View audit trailNo accessView onlyView onlyNo accessView onlyNo accessView only
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Disclosure, security and operation are kept apart: the foreign disclosure officer decides what is shared, the ISSM approves builds and teardowns, and Moraph engineers carry out only what has been approved.
  • Roles are scoped to a mission, so a mission owner or partner administrator sees only their own enclave, and partners never see each other's users.
  • Partner accounts carry the mission's end date and are reviewed during the mission; nothing outlives the enclave without a recorded approval.
  • Moraph's administrative accounts are named and role-based, and tickets for defense clients are handled only by US citizens with active clearances.

Features

What it does

Approved enclave templates

Versioned, hardened templates for common partner-sharing patterns, each approved by your ISSM before use.

Infrastructure as code

Enclaves are built from code rather than by hand, so each build is repeatable and its configuration is recorded.

Disclosure-linked sharing

Sharing rules for each partner are configured from the disclosure decision your foreign disclosure officer recorded, and the decision is kept with the enclave.

Partner onboarding

Partner organizations and named users are added only after approval, with each account tied to the mission and its end date.

Mission-bound access

Every account, key and connection carries the mission's end date, and reminders go out before it is reached.

Configuration baseline

Each enclave is compared with its template baseline, and differences are reported for a decision.

Data movement records

Information moved into and out of the enclave is logged with who moved it and under which disclosure decision.

Monitoring and alert triage

Moraph watches enclave health, access and data movement, and escalates confirmed issues to your security operations team.

Controlled teardown

A teardown runbook revokes access, transfers retained records, deletes data and sanitizes storage, step by step.

Teardown evidence

Each teardown produces a record of what was revoked, transferred, deleted and sanitized, signed off by your ISSM.

Change control

Changes to a running enclave are raised, approved through your process, applied and recorded.

Enclave inventory

One view of every enclave: its mission, partners, template version, users and end date.

Integrations

How it connects to your systems

Connects toHowWhat flows
Your identity providerUS users sign in through your identity provider, with groups used to assign enclave roles.In: user identity and group membership.
Partner identityPartner users are given enclave accounts, or federated with a partner's identity service where your ISSM approves it.In: partner user identities approved for the mission.
Disclosure recordsDisclosure decisions are recorded in the service or referenced from the system your foreign disclosure office already uses.In: disclosure decision references and the categories approved per partner.
Cross-domain transferWhere information must move between enclaves or networks, transfers go through the cross-domain solution your organization has approved, including Moraph's Cross-Domain Solution (CDS) Transfer Agent.In and out: transfer requests and their outcomes.
SIEMEnclave access, data movement and administrator events are sent to your SIEM.Out: access, data movement and administrative events.
IT service managementRequests, changes and incidents are tracked in your service management tool, or in Moraph's if you have none.In and out: tickets, approvals and status.
Records repositoryRecords your organization keeps from a mission are transferred to your designated repository before teardown.Out: retained records with a transfer manifest.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Single sign-on

US users and administrators sign in through your identity provider, so your authentication policies apply.

Role-based access

What each person can see and do follows their role and the mission they belong to; partners see only their own enclave.

Encryption and keys

Enclave data is encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization, and keys are destroyed at teardown.

Complete audit trail

Every request, approval, build, change, data movement and teardown step is logged with the person and time.

Cleared US support staff

Tickets for federal and defense clients are handled only by US citizens with active clearances.

Your authority, your networks

Enclaves on classified networks are built and operated under your organization's authority and procedures; Moraph does not hold the authorization.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

11 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Service operations

Enclave inventory

For mission owners, ISSM, Moraph service manager

Every enclave with its mission, partners, template version, user count, end date and status.

Break down by
Mission, Partner, Template version, Status
Delivered as
Live view; monthly service review pack; CSV export
Used for
Knowing what is running, for whom and until when.

Requests and builds

For mission owners and Moraph service manager

Each request with its approvals, build status and any baseline differences.

Break down by
Mission owner, Approval stage, Template, Status
Delivered as
Live view; CSV export
Used for
Seeing which requests are waiting and on whom.

Alerts and outcomes

For security operations, ISSM, Moraph service manager

Alerts triaged, closed and escalated for each enclave, with the outcome.

Break down by
Enclave, Source, Severity, Outcome
Delivered as
Live view; monthly service review pack
Used for
Checking that alerts are worked and escalated as agreed.

Access and disclosure

Partner accounts

For mission owners, partner administrators, ISSM

Accounts by enclave and partner, with last use, expiry and removals requested.

Break down by
Enclave, Partner, Last use, Expiry
Delivered as
Live view; scheduled email; CSV export
Used for
Removing accounts that are no longer needed.

Data movement by disclosure decision

For foreign disclosure officers and ISSM

Information moved into and out of each enclave, by partner and the disclosure decision that covered it.

Break down by
Enclave, Partner, Disclosure decision, Direction, Period
Delivered as
Live view; CSV export
Used for
Confirming that sharing stayed within what was approved.

Access review status

For iSSM and mission owners

The latest access review for each enclave, who certified it, and whether removals were applied.

Break down by
Enclave, Partner, Review cycle, Status
Delivered as
Live view; PDF export
Used for
Showing that partner access is reviewed during the mission.

Change and configuration

Baseline comparison

For iSSM

Differences between each enclave and its template baseline, with how each was resolved.

Break down by
Enclave, Template version, Difference type, Resolution
Delivered as
Scheduled run; PDF and CSV export
Used for
Evidence that enclaves stay as approved.

Change history

For iSSM and assessors

Every change to an enclave or template with its request, approval, implementer and time applied.

Break down by
Enclave, Change type, Approver, Period
Delivered as
Live view; PDF and CSV export
Used for
Showing that each change was requested, approved and recorded.

Assurance

Teardown evidence

For iSSM, assessors, mission owners

For each ended enclave, the accounts revoked, connections removed, records transferred, storage sanitized and the method used, with the sign-off.

Break down by
Enclave, Step, Method, Sign-off status
Delivered as
On completion; PDF export
Used for
Showing that nothing from the enclave remains accessible.

Control evidence package

For iSSM and assessors

Control mappings for the templates and service, with the records that support each control Moraph is responsible for.

Break down by
Control family, Responsibility, Evidence type
Delivered as
On request; PDF and CSV export
Used for
Supporting your organization's authorization of the templates and enclaves.

Monthly service review pack

For program office, ISSM, Moraph service manager

Enclaves running and planned, changes, alerts, teardowns, vendor notices and open actions for the month.

Break down by
Period, Mission
Delivered as
PDF; scheduled email
Used for
Running the monthly service review and recording the actions agreed.

Exports, access and evidence

  • Reports can be exported to CSV and evidence reports to PDF, and scheduled to arrive by email for the people entitled to see them.
  • Access, data movement and administrator events are sent to your SIEM, so your own security tooling holds the primary record under your retention policy.
  • Reports respect each viewer's role: a mission owner sees their own enclave, a partner administrator sees only their own users, and the ISSM sees every enclave.
  • Teardown evidence is kept after the enclave itself is gone, for the retention period your organization sets.
  • Evidence reports can be run as of a past date and give the same result each time. Running and exporting a report is itself recorded.

Deployment

Where and how it runs

Commercial cloud in US regions

Enclaves for unclassified sharing built in the US government cloud regions your organization authorizes, with Moraph's service tooling hosted in the United States region.

Your data centers

Enclaves built on infrastructure you own or operate, with Moraph working under your access procedures.

Classified networks

Where enclaves run on classified networks, Moraph's cleared staff work under your organization's authority and procedures, scoped in the proposal.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Requirements and authority

We work with your mission owners, foreign disclosure office and ISSM to agree the sharing patterns, boundaries and approvals the service must follow.

Template design

We design and harden the enclave templates for those patterns on the infrastructure you authorize, and document them for your ISSM.

Template approval

Templates are built in a test environment, assessed by your team, and approved before any mission uses them.

Runbooks

Request, build, onboarding, change, incident and teardown runbooks are agreed, including the sanitization method for each type of storage.

Exercise

A full lifecycle is run on an exercise mission, from request to teardown evidence, before the first operational enclave.

Transition to operations

Escalation paths, reporting and service reviews are agreed, and the service moves into steady-state management.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • Moraph is not the vendor of the cloud, network or software products the enclaves are built on. Those vendors' own service commitments, roadmaps and outages apply.
  • Licenses for underlying products are subject to each vendor's terms.
  • Moraph does not make disclosure or release decisions. Your foreign disclosure officers decide what each partner may receive; the service configures and records what they approve.
  • Moraph does not authorize enclaves. Your authorizing official makes that decision; Moraph maps controls and supplies evidence.
  • Build time depends on the template, the infrastructure and your approvals, and is agreed per mission rather than guaranteed.
  • Teardown removes data from the enclave's own storage. Copies a partner has legitimately taken out under an approved disclosure are governed by your agreements with that partner, not by the service.
  • Connectivity to partner networks is provided by your organization and its partners; Moraph configures the enclave side.
  • The service is not a cross-domain solution; information moving between classification levels uses the cross-domain solution your organization has approved.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. Pick a recent or planned partner mission and walk it through the request, build, operate and teardown steps
  2. Check that each sharing rule can be traced to a recorded disclosure decision
  3. Review a template with your ISSM against your authorization boundary
  4. Run an exercise teardown and review the evidence it produces
  5. Agree with your foreign disclosure office how decisions are recorded and referenced
  6. Read the responsibilities table against your existing support and network arrangements

Questions

Frequently asked questions

Who decides what partners can see?

Your foreign disclosure officers. The service records their decisions and configures sharing to match, but it never makes a disclosure decision.

What platforms are enclaves built on?

On the cloud regions, data centers and software products your organization authorizes. Moraph designs the templates around them with your ISSM during implementation.

Is the service accredited for classified networks?

No accreditation is held by Moraph. Work on classified networks is carried out under your organization's authority and procedures, and Moraph supplies control mappings and evidence for your authorization.

How do we know an enclave is really gone?

Each teardown follows the agreed runbook and produces a record of every account revoked, connection removed, record transferred, and storage location deleted and sanitized, which your ISSM reviews and signs off.

How is it priced?

A managed service fee based on the templates maintained and the enclaves run, plus underlying infrastructure and licenses, with implementation charged separately. See Working with Moraph for what drives a quotation.

Can our own staff build enclaves from the templates?

Yes, if you choose. The templates and runbooks are yours, and Moraph can support your team rather than operate every enclave.

Next steps

Evaluate Mission Partner Environment (MPE) Builder

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Mission Partner Environment (MPE) Builder guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Mission Partner Environment (MPE) Builder support guide.

Related products