Protection of Boot Firmware
LOW MODERATE HIGHRequirements NIST SOURCE
Implement the following mechanisms to protect the integrity of boot firmware in [system components]: [mechanisms].
Discussion (NIST Supplemental Guidance)
Unauthorized modifications to boot firmware may indicate a sophisticated, targeted attack. These types of targeted attacks can result in a permanent denial of service or a persistent malicious code presence. These situations can occur if the firmware is corrupted or if the malicious code is embedded within the firmware. System components can protect the integrity of boot firmware in organizational systems by verifying the integrity and authenticity of all updates to the firmware prior to applying changes to the system component and preventing unauthorized processes from modifying the boot firmware.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for SI-7(10) 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
Assessment Objectives
- mechanisms to be implemented to protect the integrity of boot firmware in system components are defined;
- system components requiring mechanisms to protect the integrity of boot firmware are defined;
- <SI-07(10)_ODP[01] mechanisms> are implemented to protect the integrity of boot firmware in <SI-07(10)_ODP[02] system components>.
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; integrity verification tools and associated documentation; records of integrity verification scans; 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: Software, firmware, and information integrity verification tools; mechanisms supporting and/or implementing protection of the integrity of boot firmware; safeguards implementing protection of the integrity of boot firmware].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for SI-7(10). 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
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
- Software, firmware, and information integrity verification tools
- mechanisms supporting and/or implementing protection of the integrity of boot firmware
- safeguards implementing protection of the integrity of boot firmware
Other Records
- system and information integrity procedures
- procedures addressing software, firmware, and information integrity
- integrity verification tools and associated documentation
- records of integrity verification scans
- system audit records
- other relevant documents or records