← SI-2

Time to Remediate Flaws and Benchmarks for Corrective Actions

LOW MODERATE HIGH
1 Overlay 0 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

Discussion (NIST Supplemental Guidance)

Organizations determine the time it takes on average to correct system flaws after such flaws have been identified and subsequently establish organizational benchmarks (i.e., time frames) for taking corrective actions. Benchmarks can be established by the type of flaw or the severity of the potential vulnerability if the flaw can be exploited.

Implementation Guidance

Engineering Interpretation

Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.

No engineering interpretation has been authored for SI-2(3) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.

Assessment

NIST SP 800-53A REV 5.2.0

Assessment Objectives

  1. the benchmarks for taking corrective actions are defined;
  2. the time between flaw identification and flaw remediation is measured;
  3. <SI-02(03)_ODP benchmarks> for taking corrective actions have been established.

Examine

[SELECT FROM: System and information integrity policy; system and information integrity procedures; procedures addressing flaw remediation; system design documentation; system configuration settings and associated documentation; list of benchmarks for taking corrective action on identified flaws; records that provide timestamps of flaw identification and subsequent flaw remediation activities; system security plan; other relevant documents or records].

Interview

[SELECT FROM: System/network administrators; organizational personnel with information security responsibilities; organizational personnel installing, configuring, and/or maintaining the system; organizational personnel responsible for flaw remediation].

Test

[SELECT FROM: Organizational processes for identifying, reporting, and correcting system flaws; mechanisms used to measure the time between flaw identification and flaw remediation].

Overlays

Showing the OT/ICS overlay for the parent control SI-2 — see the SI-2(3) entries within each baseline below.

OT/ICS Overlay SP 800-82r3

NIST SP 800-82r3 Appendix F, Table 22. Blank baseline means the control/control enhancement is not selected in that initial OT baseline.

LOW

  • Base control: Included (matches standard baseline)

MODERATE

  • Base control: Included (matches standard baseline)
  • Included: (2)

HIGH

  • Base control: Included (matches standard baseline)
  • Included: (2)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for SI-2(3). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.

Learn more about STIG/CCI integration →

Evidence

Potential Evidence — Derived

Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.

Policy

  • System and information integrity policy
  • system security plan

Configuration

  • system design documentation
  • system configuration settings and associated documentation

Testing

  • Organizational processes for identifying, reporting, and correcting system flaws
  • mechanisms used to measure the time between flaw identification and flaw remediation

Other Records

  • system and information integrity procedures
  • procedures addressing flaw remediation
  • list of benchmarks for taking corrective action on identified flaws
  • records that provide timestamps of flaw identification and subsequent flaw remediation activities
  • other relevant documents or records