diff options
| author |   mudcam <v.nieutin@live.fr> | 2018-06-28 16:58:17 +0200 |
|---|---|---|
| committer |   ronan [iot.bzh] <ronan.lemartret@iot.bzh> | 2018-07-02 09:24:07 +0200 |
| commit | e16226588be32962c1019b86f73e61d3e9fbec2d (patch) | |
| tree | 8768fdd5e7257fbb5c5fcdad27f7d3100a192d68 /security-blueprint/part-2 | |
| parent | 217f394066ce97a13d385cf12bb6957da49ab7c7 (diff) | |
Added content from the hidden chapter of the "old" security-blueprint.
Diffstat (limited to 'security-blueprint/part-2')
| -rw-r--r-- | security-blueprint/part-2/0_Abstract.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/security-blueprint/part-2/0_Abstract.md b/security-blueprint/part-2/0_Abstract.md index da9daee..fa99d89 100644 --- a/security-blueprint/part-2/0_Abstract.md +++ b/security-blueprint/part-2/0_Abstract.md @@ -10,6 +10,11 @@ Boot-Abstract-1 | More generic and add examples (The chain of trust). <!-- end-section-todo --> +Secure boot refers to preventing malicious software applications and +“unauthorized” operating systems from loading during the system start-up process. +The goal is to protect users from rootkits and other low-level malware attacks. +Modern bootloaders come with features that can be used to enable secure boot in the system. + **Boot Hardening**: Steps/requirements to configure the boot sequence, in order to restrict the device from executing anything other than the approved software image. |