Reference
Mission Partner Environment (MPE) Builder glossary
Terms used in Mission Partner Environment (MPE) Builder and its documentation.
Applies to Mission Partner Environment (MPE) Builder as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.
Terms used in Mission Partner Environment (MPE) Builder and its documentation.
| Term | Meaning |
|---|---|
| Mission Partner Environment (MPE) | A network environment set up so US forces can share information with mission partners for a defined mission. |
| Enclave | One isolated environment built for a mission, with its own partners, users, sharing rules and end date. |
| Template | A versioned, hardened enclave design approved by your ISSM, from which enclaves are built. |
| Disclosure decision | The decision by your foreign disclosure officer on what information a partner may receive. |
| ISSM | Information System Security Manager, who approves templates, builds, changes and teardown evidence. |
| Baseline comparison | A check of a running enclave against its template baseline, reporting any differences for a decision. |
| Mission end date | The date the mission ends, carried by every account, key and connection in the enclave. |
| Teardown | The controlled process of revoking access, transferring retained records, deleting data and sanitizing storage when a mission ends. |
| Cross-domain solution | An approved system for moving information between networks or classification levels. |
| Authorizing official | The person in your organization who decides whether an enclave may operate. |
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.