RidgeRun Platform Security Manual/Platform Security/Secure Boot: Difference between revisions
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
=== Secure Boot === | === Secure Boot === | ||
Secure Boot is one of the fundamental security features that can be implemented on embedded systems. Also known as High Assurance Boot(HAB) or Advanced High Assurance Boot(AHAB) depending of the platform, such as NXP's latest SoCs, it basically consists on ensuring that all software in the system comes from a trusted source and hasn't been tampered with. If this can not be ensured, the system won't be able to boot. | Secure Boot is one of the fundamental security features that can be implemented on embedded systems. Also known as High Assurance Boot(HAB) or Advanced High Assurance Boot(AHAB) depending of the platform, such as NXP's latest SoCs, it basically consists on ensuring that all software in the system comes from a trusted source and hasn't been tampered with. If this can not be ensured, the system won't be able to boot normally, which prevents that the final application of the system is maliciously manipulated. | ||
<noinclude> | <noinclude> | ||
Revision as of 20:41, 22 January 2025
 | RidgeRun Platform Security Manual RidgeRun documentation is currently under development. |
Secure Boot
Secure Boot is one of the fundamental security features that can be implemented on embedded systems. Also known as High Assurance Boot(HAB) or Advanced High Assurance Boot(AHAB) depending of the platform, such as NXP's latest SoCs, it basically consists on ensuring that all software in the system comes from a trusted source and hasn't been tampered with. If this can not be ensured, the system won't be able to boot normally, which prevents that the final application of the system is maliciously manipulated.