Wargaming & Simulation Sandbox

Moraph builds and operates the virtual environments your organization uses for wargames and large simulations: compute that scales for the event, the simulation software you license, and separation between exercises so data from one cannot be seen from another. Each exercise is provisioned from an approved template, run, and then archived or destroyed according to your rules. Your organization decides who takes part, what data goes in and what happens to the results; Moraph runs the environment under your authority.

The problem it solves

Wargaming and simulation teams need large amounts of compute for short periods, and each event brings its own participants, scenarios and data sensitivities. Environments are often assembled by hand for each exercise, left running afterwards, and shared between events in ways that make it hard to show that one exercise's data could not be reached from another. Aggregated simulation results can reveal more about capabilities than any single input, so who can see what, and what is kept, matters as much as the compute.

Who it’s for

• Wargaming and analysis organizations that plan and run exercises
• Modeling and simulation program offices
• Exercise directors and control cells who run events
• Information system security managers and authorizing officials responsible for the environment
• Security officers who manage compartmented access and classification guidance

1. Request an exerciseAn exercise director requests an environment from the catalog of approved templates, with dates, participant cells, simulation software and the data that will be loaded.
2. ProvisionMoraph builds the exercise environment from the approved template as a separate compartment, with its own network segment, accounts and storage, and verifies it before participants arrive.
3. RunDuring the event, compute scales within the reserved limits, Moraph monitors the environment, and the control cell manages the scenario without platform work getting in the way.
4. Close outWhen the exercise ends, results are delivered to the people entitled to them, and the environment is archived or destroyed according to your rules, with a record of what was done.

Approved templates

Exercise environments built from templates your ISSM has approved, so each build matches a known baseline.

Compartment per exercise

Each exercise runs in its own isolated network segment, accounts and storage, separate from every other exercise.

Cell separation

Participant cells inside an exercise can be separated from one another, with the control cell given the views the director decides.

Scalable compute

Compute reserved for each event and scaled within those limits, so large simulations get capacity when they run without paying for it all year.

Simulation software hosting

The simulation and wargaming software your organization licenses or develops is installed and maintained in each environment.

Data loading controls

Only data sets approved by their owner are loaded into an exercise, and every load is recorded.

Roster-based access

Participant accounts are created from an approved roster and removed when the exercise ends.

Archive or destroy

At close-out the environment is archived or destroyed according to your instruction, with a record of what was kept and what was removed.

Build records

Each environment's template, configuration, software versions and data loads are recorded, so results can be traced to the setup that produced them.

Exercise calendar

Planned events, reserved capacity and build dates in one calendar, so conflicts are seen early.

Event support

A service desk for participants and the control cell during the event, with escalation to Moraph engineers.

Control evidence

Control mappings and evidence for your RMF package, including separation testing results for each build.

Exercise director

Requests environments, approves participants and directs the event

Security officer

Sets classification guidance and compartments and confirms close-out

Participant

Uses the simulation within their cell for the duration of the exercise

ISSM

Approves templates, changes and departures from the baseline

Moraph platform engineer

Builds, runs and closes out environments without access to exercise content

Auditor (read-only)

Reviews build, access and close-out records

Simulation and wargaming software

The commercial, government or in-house simulation software your organization licenses or develops, installed in each environment under its own licence terms.

Identity provider

Participants sign in through your identity provider, including certificate-based sign-in where required, and rosters can follow its groups.

Data sources

Approved data sets for an exercise, such as terrain, order-of-battle or scenario data, loaded through your approved transfer process.

Results repository

At close-out, results and logs are delivered to the repository or analysis environment your organization designates.

Security monitoring

Platform and access logs forwarded to your security operations tooling.

Moraph Work API

Exercise requests, service tickets and change records available to your service management tools.

Single sign-on

Participants and staff sign in through your identity provider, so your authentication policies apply.

Compartmented access

Each exercise and each cell is separated by network, accounts and storage, and access follows the approved roster.

Encryption and keys

Data is encrypted at rest and in transit, with keys Moraph staff cannot use without explicit, time-bound authorization from your organization.

Complete audit trail

Builds, sign-ins, data loads, changes, exports and destruction are logged with the person and time, and cannot be edited.

Cleared US staff

Federal and defense work is handled only by US citizens with active clearances, and environments are hosted only in the United States.

Tested releases

Security testing gates every change to Moraph's templates and tooling, and a software bill of materials is kept for the components Moraph supplies.

On your premises

Built in your data center or enclave, including classified environments, and operated under your organization's authority by cleared Moraph staff where the contract provides for it.

US government cloud region

Built in a US government cloud region your organization has approved, hosted only in the United States, with compute reserved for each event.

Hybrid

A standing on-premises platform that draws on approved cloud capacity for the largest events, scoped in the proposal.

Discovery

We review your exercise program, simulation software, typical event sizes and classification needs. We need your recent and planned exercises and a contact from your security office.

Platform design

The shared platform and compartment model are designed for your network and security domain, with the control mapping your ISSM needs.

Templates

Exercise templates are built for your common event types and simulation software, tested, and approved by your ISSM.

Build and separation testing

The platform is built on your premises or in a US government cloud region, and separation between environments is tested and documented.

Pilot exercise

A first exercise is run end to end, from request to close-out, and the process adjusted with your exercise and security staff.

Authorization support and operations

We supply evidence for your assessment, then move to steady-state operations with the exercise calendar, runbooks and monthly service reviews.

• Moraph is not the maker of the simulation software, hardware or cloud services. Their own service commitments, roadmaps and outages apply, and licences are subject to their terms.
• Moraph does not hold an accreditation or authorization for the environment. Your authorizing official decides whether it operates; Moraph maps controls and supplies evidence to support that decision.
• Work in classified environments happens under your organization's authority and only where the contract provides for it, by US citizens with the required clearances.
• Moraph does not design scenarios, adjudicate games or analyze results. Exercise design, play and conclusions belong to your organization.
• Verification, validation and accreditation of models and simulations under DoD Instruction 5000.61 remain your organization's responsibility; Moraph keeps the build records that support it.
• Compute is available within the capacity reserved for each event; exceeding it depends on what the platform or cloud provider can supply at the time.
• Moving data between security domains is not included; it uses the cross-domain solution your organization has approved.
• Classification guidance and decisions about aggregated results are your security office's responsibility; the environment enforces the separation they specify.

• Give us a recent exercise and review how it would be requested, built, run and closed out
• Ask to see a sample build record and separation test results
• Check how participant access is created from a roster and removed at the end
• Walk through an archive and a destruction close-out with your security officer
• Confirm that Moraph engineers can operate environments without seeing exercise content
• Review the responsibilities table against your operating model and contract