ComplianceNIST 800-53 control

NIST-SI-14 Non-persistence

Official page ↗
Framework
NIST SP 800-53 rev5 (5.2.0)
Family
SI System and Information Integrity
Control
SI-14
ATT&CK techniques mitigated
7

Control statement

Implement non-persistent [Assignment: system components and services] that are initiated in a known state and terminated [Selection (one or more of): upon end of session of use; {{ insert: param, si-14_odp.03 }} ].

Discussion

Implementation of non-persistent components and services mitigates risk from advanced persistent threats (APTs) by reducing the targeting capability of adversaries (i.e., window of opportunity and available attack surface) to initiate and complete attacks. By implementing the concept of non-persistence for selected system components, organizations can provide a trusted, known state computing resource for a specific time period that does not give adversaries sufficient time to exploit vulnerabilities in organizational systems or operating environments. Since the APT is a high-end, sophisticated threat with regard to capability, intent, and targeting, organizations assume that over an extended period, a percentage of attacks will be successful. Non-persistent system components and services are activated as required using protected information and terminated periodically or at the end of sessions. Non-persistence increases the work factor of adversaries attempting to compromise or breach organizational systems. Non-persistence can be achieved by refreshing system components, periodically reimaging components, or using a variety of common virtualization techniques. Non-persistent services can be implemented by using virtualization techniques as part of virtual machines or as new instances of processes on physical machines (either persistent or non-persistent). The benefit of periodic refreshes of system components and services is that it does not require organizations to first determine whether compromises of components or services have occurred (something that may often be difficult to determine). The refresh of selected system components and services occurs with sufficient frequency to prevent the spread or intended impact of attacks, but not with such frequency that it makes the system unstable. Refreshes of critical components and services may be done periodically to hinder the ability of adversaries to exploit optimum windows of vulnerabilities.

ATT&CK mappings (CTID)

• T1505 Server Software Component • T1505.001 SQL Stored Procedures • T1505.002 Transport Agent • T1505.004 IIS Components • T1546.003 Windows Management Instrumentation Event Subscription • T1547.004 Winlogon Helper DLL • T1547.006 Kernel Modules and Extensions

Related

Mitigates · MITRE ATT&CK (7)

  • T1505.004 IIS Components sub-technique
  • T1546.003 Windows Management Instrumentation Event Subscription sub-technique
  • T1547.004 Winlogon Helper DLL sub-technique
  • T1547.006 Kernel Modules and Extensions sub-technique
  • T1505.001 SQL Stored Procedures sub-technique
  • T1505.002 Transport Agent sub-technique
  • T1505 Server Software Component technique

Related control · Compliance (3)

  • NIST-SC-30 Concealment and Misdirection NIST 800-53 control
  • NIST-SC-34 Non-modifiable Executable Programs NIST 800-53 control
  • NIST-SI-21 Information Refresh NIST 800-53 control

Referenced by Compliance · enhancement of (3)

  • NIST-SI-14(1) Refresh from Trusted Sources NIST 800-53 enhancement
  • NIST-SI-14(2) Non-persistent Information NIST 800-53 enhancement
  • NIST-SI-14(3) Non-persistent Connectivity NIST 800-53 enhancement

Referenced by Compliance · has member (1)

  • NIST-SI System and Information Integrity NIST 800-53 family

Referenced by Compliance · related control (4)

  • NIST-SA-24 Design For Cyber Resiliency NIST 800-53 control
  • NIST-SC-30 Concealment and Misdirection NIST 800-53 control
  • NIST-SC-34 Non-modifiable Executable Programs NIST 800-53 control
  • NIST-SI-21 Information Refresh NIST 800-53 control