NASA Best Practices Guide for Mission Cybersecurity
GR-SOFT-01

Software Installation Function

Parent: GR

Description

The mission should provide the capability for each system owner to configure the flight and ground system to require a user to possess an explicit identified privilege to install software.

Mapped SPARTA techniques

1 techniques

  • DE-0006Modify WhitelistST0006
    addresses
    moderate

    Modifying the allowlist to admit adversary software is defeated where installation requires an explicit identified privilege, which is what the practice mandates for flight and ground configuration alike. [Curation] Requiring an explicit identified privilege to INSTALL software does not govern editing the allowlist itself, which is a policy object rather than an installation. The practice is adjacent to the technique and constrains what the modified allowlist can then admit, which is governance rather than interdiction.

Cite as SafeMode Space, nasa-bpg GR-SOFT-01.

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