← SI-7

Code Authentication

LOW MODERATE ✓ HIGH
1 Overlay 3 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

Implement cryptographic mechanisms to authenticate the following software or firmware components prior to installation: [software or firmware components].

Discussion (NIST Supplemental Guidance)

Cryptographic authentication includes verifying that software or firmware components have been digitally signed using certificates recognized and approved by organizations. Code signing is an effective method to protect against malicious code. Organizations that employ cryptographic mechanisms also consider cryptographic key management solutions.

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-7(15) 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. software or firmware components to be authenticated by cryptographic mechanisms prior to installation are defined;
  2. cryptographic mechanisms are implemented to authenticate <SI-07(15)_ODP software or firmware components> prior to installation.

Examine

[SELECT FROM: System and information integrity policy; system and information integrity procedures; procedures addressing software, firmware, and information integrity; system design documentation; system configuration settings and associated documentation; cryptographic mechanisms and associated documentation; system audit records; system security plan; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel responsible for software, firmware, and/or information integrity; organizational personnel with information security responsibilities; system/network administrators; system developer].

Test

[SELECT FROM: Cryptographic mechanisms authenticating software and firmware prior to installation].

Overlays

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

Not applicable at this tier.

MODERATE

  • Base control: Included (matches standard baseline)
  • Included: (1) (7)

HIGH

  • Base control: Included (matches standard baseline)
  • Included: (1) (2) (5) (7) (15)

STIGs & CCIs

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

  • Cryptographic mechanisms authenticating software and firmware prior to installation

Other Records

  • system and information integrity procedures
  • procedures addressing software, firmware, and information integrity
  • cryptographic mechanisms and associated documentation
  • system audit records
  • other relevant documents or records