You've already forked documentation
mirror of
https://github.com/Dasharo/documentation.git
synced 2026-03-06 15:26:51 -08:00
* Add documentation for firmware resiliency This change adds a section for firmware resiliency as well as updates existing sections that are related to firmware resiliency Signed-off-by: Sean McGinn <sean.mcginn@intel.com> * Fix grammatical errors in resiliency and recovery section Signed-off-by: Sean McGinn <sean.mcginn@intel.com> * Add in test tool tutorials for SBL resiliency Signed-off-by: Sean McGinn <sean.mcginn@intel.com> * Add in block diagrams for SBL resiliency Signed-off-by: Sean McGinn <sean.mcginn@intel.com> * Make minor improvements to resiliency and update sections Signed-off-by: Sean McGinn <sean.mcginn@intel.com> * Mention non-overlapping region requirement for FW update capsule tool Signed-off-by: Sean McGinn <sean.mcginn@intel.com> * Give example for building FW update capsule with TMAC:IPFW Signed-off-by: Sean McGinn <sean.mcginn@intel.com> * Add note that corruptcomp tool should be disabled in prod builds Signed-off-by: Sean McGinn <sean.mcginn@intel.com> Signed-off-by: Sean McGinn <sean.mcginn@intel.com>
22 lines
510 B
ReStructuredText
Executable File
22 lines
510 B
ReStructuredText
Executable File
Security Features
|
|
===================
|
|
|
|
.. epigraph::
|
|
|
|
`Simplicity is prerequisite for reliability.` -- **Edsger Dijkstra**
|
|
|
|
A critical requirement for firmware is security and the chain of trust should be maintained through the boot process.
|
|
|
|
Security is a built-in feature in |SPN| to ensure the boot integrity.
|
|
|
|
.. toctree::
|
|
:maxdepth: 2
|
|
|
|
boot-guard
|
|
verified-boot
|
|
key-management
|
|
measured-boot
|
|
firmware-update
|
|
container-security
|
|
firmware-resiliency-and-recovery
|