Skip to content

Getting started

Getting started with Nuclear Command & Control (NC3) Assurance Check

What Nuclear Command & Control (NC3) Assurance Check is for, who uses it, what you need before you start, and your first steps.

Applies to Nuclear Command & Control (NC3) Assurance Check 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 NC3 Assurance Check runs scheduled, read-only integrity checks on the software and configurations of critical command and communication systems, comparing what is installed with the baseline your approving authority has signed off. It records the results of link health checks drawn from your existing monitoring and test procedures, and turns every difference into a discrepancy that a person investigates and closes. It runs entirely in your environment, under your authority.

What it is for

For the most critical systems, operators need confidence that the software and configurations in service are exactly the ones that were approved, and that communication paths are working. In practice, verification often relies on manual checklists, separate tools for each system type, and results recorded in logs and spreadsheets. Differences can go unnoticed between inspections, and assembling evidence for an inspection or authorization review takes weeks of effort.

  • Integrity and configuration checks are manual, periodic and inconsistent across system types
  • Approved baselines live in documents rather than in something a check can compare against
  • Link health results are scattered across monitoring tools and test logs
  • Evidence for inspections and authorization reviews is assembled by hand

Who uses it

  • System owners and operations centers responsible for critical command and communication systems
  • Configuration managers who maintain approved baselines
  • Information system security managers and officers
  • Authorizing officials and approving authorities who sign off baselines
  • Inspectors and auditors who review integrity and configuration evidence

Before you start

  • Your organization licenses Nuclear Command & Control (NC3) Assurance Check from Moraph.
  • A Moraph client account in that organization, signed in.
  • Access to Nuclear Command & Control (NC3) Assurance Check in Moraph Apps, given by an administrator in the Moraph Portal under People and access.
  • For setup: the product administrator role.

Steps to get started

  1. Agree with Moraph and your program office where the assurance tool will be installed. It runs only inside your own environment, under your authority, and is not used from app.moraph.com.

  2. Arrange the accounts, approvals and access your environment requires for the people who will install, configure and run checks.

  3. Install the tool from the release package Moraph provides through the channel agreed for your program, and verify the package before installation.

  4. Load the check definitions and baselines agreed for your systems, then run a trial check in a test enclave.

  5. Review the results with your system owners, then agree the schedule and who reviews each run.

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.