RidgeRun Platform Security Manual/Platform Security/Secure Boot: Difference between revisions

RidgeRun Platform Security Manual/Platform Security/Secure Boot (view source)

880 bytes added , 22 January

no edit summary

298

edits

❯

@@ Line 18: / Line 18: @@
 The Secure Boot process follows a Chain of Trust in which each set of components is in charge of verifying the integrity of the next set of components, starting with the most critical system components. This process starts by verifying system's bootloader for authenticity and integrity, after that it moves to other firmware components such as the kernel and drivers, and usually if finishes at user space applications. If the verification fails at any step of the process, the Secure Boot process is going to be stopped and the system won't boot.
+<br>
+As this verification relies that on cryptographic keys that are going to be burned onto the system, it is very important to correctly configure Secure Boot with the correct desired keys and ensure that these keys are stored safely. Is the configuration is done with an incorrect key, this can lead to failures when trying to use the system as the expected key is different from the key provided by the image being tested. On the other hand, is Secure Boot was correctly configured but the keys were not stored securely, malicious parties can gain access to the keys which can lead to the creation of malicious software that is signed with the keys expected by the system. In this case the secure boot process won't fail and the system could be tampered with, so it is very important to ensure that only authorized developers have access to the keys burned on the system.
 <noinclude>