NASA Best Practices Guide for Mission Cybersecurity
MI-DCO-02

Mission Fault Management Function

Parent: MI

Description

The mission should incorporate fault management bypass protection in its requirements and resulting system.

Mapped SPARTA techniques

5 techniques

  • The practice is fault management bypass protection and the technique is disabling fault management. The pairing is literal: the practice exists to make the technique fail.

  • Falsifying watchdog indicators to conceal activity is a bypass of the fault-management function's reporting arm. Moderate rather than high because the practice is written against bypass of the function, and this sub-technique bypasses the visibility of the function rather than its action.

  • Driving the vehicle into safe mode to shed protections uses fault management rather than bypassing it. Bypass protection governs the boundary the technique operates near without covering the induced-transition mechanism itself, which is MI-MA-02's subject.

  • Manipulating watchdog timeout windows, reset actions, or enable bits is bypassing fault management by editing its parameters. Bypass protection covers the technique's defining vector and its whole scope.

  • REC-0001.09Fault ManagementST0001
    addresses
    low

    Reconnaissance of the fault management design is what makes a later bypass practical. The practice does not impede the reconnaissance itself, so this is a weak governance relationship recorded at low confidence rather than omitted, because the design-knowledge dependency is real.

Cite as SafeMode Space, nasa-bpg MI-DCO-02.

Built 2026-07-25 from 216 techniques, 334 regulation articles, 125 ENISA controls, 2,610 framework controls, and 90 countermeasures.