Update Software

Description

Perform regular software updates to mitigate exploitation risk. Software updates may need to be scheduled around operational down times. Release updated versions of the software/firmware systems incorporating security-relevant updates, after suitable regression testing, at a frequency no greater than mission-defined frequency [i.e., 30 days]. Ideally old versions of software are removed after upgrading but restoration states (i.e., gold images) are recommended to remain on the system.

Mapped techniques

SPARTA techniques

EX-0009 Exploit Code FlawsST0004
Mapped by SPARTA, not curated by SafeMode Space.
EX-0009.02 Operating SystemST0004
Mapped by SPARTA, not curated by SafeMode Space.
EX-0009.03 Known Vulnerability (COTS/FOSS)ST0004
Mapped by SPARTA, not curated by SafeMode Space.
EXF-0006 Modify Communications ConfigurationST0008
Mapped by SPARTA, not curated by SafeMode Space.
EXF-0006.01 Software Defined RadioST0008
Mapped by SPARTA, not curated by SafeMode Space.
EXF-0006.02 TransponderST0008
Mapped by SPARTA, not curated by SafeMode Space.
IA-0001 Compromise Supply ChainST0003
Mapped by SPARTA, not curated by SafeMode Space.
IA-0001.01 Software Dependencies & Development ToolsST0003
Mapped by SPARTA, not curated by SafeMode Space.
IA-0001.02 Software Supply ChainST0003
Mapped by SPARTA, not curated by SafeMode Space.
IA-0002 Compromise Software Defined RadioST0003
Mapped by SPARTA, not curated by SafeMode Space.
PER-0002 BackdoorST0005
Mapped by SPARTA, not curated by SafeMode Space.
PER-0002.02 Software BackdoorST0005
Mapped by SPARTA, not curated by SafeMode Space.

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

# Description

›Mapped techniques

SPARTA techniques

Description

Mapped techniques