← SI-3
SI-3(4) SI · System and Information Integrity

Updates Only by Privileged Users

LOW MODERATE HIGH
1 Overlay 1 Related Control
Graph
Export ▾

Requirements NIST SOURCE

Update malicious code protection mechanisms only when directed by a privileged user.

Discussion (NIST Supplemental Guidance)

Protection mechanisms for malicious code are typically categorized as security-related software and, as such, are only updated by organizational personnel with appropriate access privileges.

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-3(4) 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. malicious code protection mechanisms are updated only when directed by a privileged user.

Examine

[SELECT FROM: System and information integrity policy; system and information integrity procedures; procedures addressing malicious code protection; list of privileged users on system; system design documentation; malicious code protection mechanisms; records of malicious code protection updates; system configuration settings and associated documentation; system audit records; system security plan; other relevant documents or records].

Interview

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

Test

[SELECT FROM: Mechanisms supporting and/or implementing malicious code protection capabilities].

Overlays

Showing the OT/ICS overlay for the parent control SI-3 — see the SI-3(4) 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)

HIGH

  • Base control: Included (matches standard baseline)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for SI-3(4). 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

  • Mechanisms supporting and/or implementing malicious code protection capabilities

Other Records

  • system and information integrity procedures
  • procedures addressing malicious code protection
  • list of privileged users on system
  • malicious code protection mechanisms
  • records of malicious code protection updates
  • system audit records
  • other relevant documents or records