Skip to content

Reference

Security, data and compliance in "Air-Gapped" Mission Planning Suite

Security controls, supported requirements, hosting and limitations of "Air-Gapped" Mission Planning Suite.

Applies to "Air-Gapped" Mission Planning Suite 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. Security controls
  2. Sign-in on the device
  3. Role-based access
  4. Encryption at rest and in transit
  5. Approved connections only
  6. Complete audit trail
  7. Your authority, cleared support
  8. Requirements it supports
  9. Where it runs
  10. Limitations

How "Air-Gapped" Mission Planning Suite protects data and supports your compliance obligations.

Security controls

Sign-in on the device

Users sign in with credentials your organization issues, and roles come from your identity provider at each sync.

Role-based access

What each person can see and do follows their role and unit; building a plan is separate from approving it.

Encryption at rest and in transit

Data on the device and during sync is encrypted, using the cryptographic modules your organization approves for the device.

Approved connections only

Sync runs only over connections and to sync points your organization has approved; the application never reaches out to the internet.

Complete audit trail

Every change, approval, export and sync is logged with the person and time, and cannot be edited on the device or at home station.

Your authority, cleared support

On classified networks and devices the Suite is operated under your authority. Support tickets for defense clients are handled only by US citizens with active clearances.

Requirements it supports

  • Joint Publication 5-0, Joint Planning
  • MIL-STD-2525, Joint Military Symbology
  • DoD Instruction 8510.01, Risk Management Framework for DoD Systems
  • CNSSI 1253, Security Categorization and Control Selection for National Security Systems
  • NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations
  • FIPS 140-3, Security Requirements for Cryptographic Modules

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

Where it runs

  • Disconnected devices: Installed on your organization's ruggedized laptops, running fully offline.
  • Client-hosted sync point: The sync service runs in your environment at unit or home station, including classified networks, operated under your authority.
  • Training environment: An unclassified training and exercise environment can be hosted in Moraph's United States region.
  • With edge infrastructure: Optionally deployed with Moraph's Tactical Edge Compute Node Manager to manage devices and updates in the field.

Limitations

  • The Suite is a planning tool. It does not compute firing solutions, control weapons or replace your organization's command and control or fire support systems.
  • It does not track forces in real time. Positions on the map are what planners enter or import, not live feeds.
  • Offline data is only as current as the last load or sync; the Suite shows the date of each data package but cannot update it without a connection.
  • Conflicting edits made on separate devices are not merged automatically; a person decides which change stands.
  • Maps, imagery and unit data come from sources your organization provides and is authorized to use; their accuracy is outside Moraph's control.
  • Ruggedized hardware, device hardening and procedures for lost or captured devices are your organization's responsibility; the Suite supports them with encryption and audit records.
  • Moraph does not claim accreditation for any classified environment. Use on classified devices and networks is under your authority and authorization.
  • Plans and approvals in the Suite support the commander's decisions; they do not replace orders issued through your organization's procedures.
Note

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

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.