Skip to content

Getting started

Getting started with Mission Partner Environment (MPE) Builder

What Mission Partner Environment (MPE) Builder is for, who uses it, what you need before you start, and your first steps.

Applies to Mission Partner Environment (MPE) Builder as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 2 min readReport a problem
On this page
  1. What it is for
  2. Who uses it
  3. Before you start
  4. Steps to get started
  5. Where to go next

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.

What it is for

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

Before you start

  • Your organization uses Mission Partner Environment (MPE) Builder as a managed platform from Moraph, under an agreement that covers it.
  • Licences for the platform vendor, bought through Moraph or under your own agreement with the vendor.
  • A Moraph account in your organization for each person who works with Moraph on the service.
  • Named technical and security contacts, recorded in the Moraph Portal.

Steps to get started

  1. Agree the scope of the managed service for Mission Partner Environment (MPE) Builder with Moraph, including which environments and teams it covers.

  2. Name your administrators, technical contact and security contact in the Moraph Portal under People and access.

  3. Review the configuration baseline Moraph proposes for your regulations, and record any changes you need.

  4. Confirm how users will sign in, through your identity provider where the platform supports it.

  5. Agree the pilot group and the cut-over plan with your Moraph delivery lead.

Where to go next

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.