Skip to content

Administration

Roles and permissions in Wargaming & Simulation Sandbox

Each role in Wargaming & Simulation Sandbox: what it sees, does and cannot do, its approvals, and a permissions matrix.

Applies to Wargaming & Simulation Sandbox as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 5 min readReport a problem
On this page
  1. Roles
  2. Exercise director
  3. Security officer
  4. Participant
  5. ISSM
  6. Moraph platform engineer
  7. Moraph service manager
  8. Auditor (read-only)
  9. Permissions at a glance
  10. How access is controlled

Who can see and do what in Wargaming & Simulation Sandbox. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in the platform vendor as part of the managed service.

Roles

Exercise director

Exercise director, wargame lead, analysis team lead. Owns the event: what is simulated, who takes part and what happens to the results.

  • Sees: Their exercises, templates available and reserved capacity; Participant rosters and cell structure; Build records and environment status; Service requests raised during the event
  • Does: Requests an environment from a template, with dates and scale; Approves the participant roster and cell structure; Directs the control cell's views across cells; Approves changes requested during the event; Decides, with the data owner, which results are exported
  • Cannot: Load data sets that their owners have not approved; Change the security baseline without ISSM approval; Extend an exercise's access beyond the agreed end without the security officer
  • Approvals: Their requests need security officer confirmation of classification guidance and ISSM approval for any departure from the template.
  • Notified about: Build complete, capacity close to reserved limits, open service requests during the event and close-out records.

Security officer

Security manager, special security officer, information security officer. Makes sure each exercise is set up and closed out in line with the classification guidance and compartments that apply.

  • Sees: Classification guidance and compartments for each exercise; Rosters and the access each participant holds; Separation test results for each build; Archive and destruction records
  • Does: Confirms the classification guidance and compartments for each request; Checks rosters against access eligibility; Approves extensions to participant access; Confirms close-out: archive or destruction of the environment; Reviews access logs after the event
  • Cannot: Build or change environments; Approve their own access; Edit or delete audit records
  • Approvals: Confirms each exercise's guidance and compartments and signs off close-out.
  • Notified about: New exercise requests, roster changes, separation test failures and close-out records waiting for confirmation.

Participant

Player, analyst, subject-matter expert, control cell member. Takes part in the exercise, using the simulation from within their assigned cell.

  • Sees: The simulation and data available to their cell; Their own account and session information; Event support contacts
  • Does: Signs in for the duration of the exercise; Runs and interacts with the simulation within their cell; Raises support requests to the service desk; Saves work to the exercise's storage
  • Cannot: See other cells' views unless the director grants it; Reach other exercises or the internet from the environment; Copy data out except through approved export
  • Approvals: Their access is approved through the roster by the exercise director and checked by the security officer.
  • Notified about: Account ready, exercise start and end times, and responses to their support requests.

ISSM

Information system security manager, ISSO. Answers for the security of the environment and controls changes to its baseline and templates.

  • Sees: Templates, baselines and their change history; Change requests and patch status; Separation test results and audit logs; Control mappings and evidence
  • Does: Approves templates and changes to them; Approves departures from a template for a specific exercise; Approves patch schedules and emergency changes after review; Reviews security alerts escalated by Moraph; Prepares continuous monitoring submissions with Moraph's evidence
  • Cannot: Approve a change they raised themselves without a second approver; Edit or delete audit records; Load exercise data
  • Approvals: Approves templates, baseline changes, patch schedules and security exceptions.
  • Notified about: Changes awaiting approval, separation test failures, security alerts and patches due.

Moraph platform engineer

Moraph platform and simulation environment engineers. Builds, monitors and closes out exercise environments and keeps the shared platform healthy.

  • Sees: Platform health, capacity and reservations; Build and close-out tasks; Platform logs and alerts; Approved changes and maintenance windows
  • Does: Builds environments from approved templates and runs separation tests; Scales compute within reserved limits during events; Monitors the platform and triages alerts; Applies approved patches and changes; Archives or destroys environments as instructed and produces the record
  • Cannot: View exercise scenarios, results or participant work; Add participants or change rosters; Make an unapproved change, except emergency actions recorded and reviewed under the incident process
  • Approvals: Planned changes need ISSM approval; changes during an event also need the exercise director.
  • Notified about: Builds scheduled, platform alerts, capacity near reserved limits and close-out instructions.

Moraph service manager

Moraph service delivery manager. Is accountable for the service across all exercises, and runs the monthly service review.

  • Sees: The exercise calendar and capacity reservations; Service performance, incidents and requests; Change and patch calendars
  • Does: Plans builds and capacity against the exercise calendar; Runs the monthly service review and agrees actions; Coordinates requests between your teams and Moraph engineers; Manages escalations to infrastructure and software providers
  • Cannot: Open exercise content; Approve changes on your organization's behalf; Change rosters
  • Approvals: Nothing they do changes an environment without the approvals above.
  • Notified about: Calendar conflicts, major incidents, escalations and overdue close-outs.

Auditor (read-only)

Inspector general staff, security control assessor, internal auditor. Reviews how exercises were built, accessed and closed out, without being able to change anything.

  • Sees: Build records, separation test results and close-out records; Rosters and access logs within the scope granted; Change and patch history; Control evidence and service reports
  • Does: Searches and reads records within their scope; Exports records, with each export logged; Records review notes where enabled
  • Cannot: Change, approve or delete anything; See exercise content unless separately granted
  • 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

ActionDirectorSecurity off.ParticipantISSMMoraph eng.Service mgrAuditor
Request an exercise environmentOwn workView–View–View–
Approve participant rosterApprovesApproves––––View
Approve data sets to loadOwn workView––––View
Build environment from templateViewView–ViewFullViewView
Run the simulationFull–Own work––––
Change templates or baseline–––ApprovesOwn workViewView
Scale compute during an eventApproves–––FullView–
Apply patches and updates–––ApprovesFullViewView
Export results at close-outApprovesApproves––Own work–View
Archive or destroy environmentApprovesApproves–ViewFullViewView
View audit logsViewFull–FullView–View

"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.

How access is controlled

  • Moraph engineers build and run environments but do not see exercise scenarios, results or participant work; exports at close-out are approved by the exercise director and security officer and handed over through your approved channels.
  • No single person controls an exercise end to end: the director requests, the security officer confirms guidance and close-out, the ISSM approves departures from the baseline, and Moraph builds.
  • Roles are configured with you. Rosters can come from your identity provider's groups, and participant access ends automatically at the agreed close of the exercise.
  • Work in classified environments happens under your organization's authority.

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.