Reference
Nuclear Command & Control (NC3) Assurance Check glossary
Terms used in Nuclear Command & Control (NC3) Assurance Check and its documentation.
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.
Terms used in Nuclear Command & Control (NC3) Assurance Check and its documentation.
| Term | Meaning |
|---|---|
| Baseline | The approved list of software, file hashes and settings a system is expected to have. |
| Collector | A component in your environment that reads system state with read-only rights and cannot send commands. |
| Verified | A check result where the system was fully read and matched its approved baseline. |
| Unverified | A result where the system could not be reached or fully read. It is never treated as passing. |
| Discrepancy | A difference from the baseline, or a failed test, that a person must investigate and close. |
| Two-person control | The rule that baseline approvals and discrepancy closures need a second person who did not do the work. |
| Pre-activity check | An on-demand check run before an exercise, maintenance window or critical activity. |
| Communication path | A link between systems whose health is recorded from monitoring feeds and operator tests. |
| Signed result | A check result digitally signed when recorded so later alteration can be detected. |
| Evidence package | Baselines, check history, discrepancies and closures assembled for an inspection or authorization review. |
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.