From b61719c91d2bb6d22c74039ef9b6f3607ff523de Mon Sep 17 00:00:00 2001 From: NicholasWoodIMG <142398143+NicholasWoodIMG@users.noreply.github.com> Date: Tue, 4 Jun 2024 15:32:02 +0100 Subject: [PATCH] Boot attack clarification. Signed-off-by: NicholasWoodIMG <142398143+NicholasWoodIMG@users.noreply.github.com> --- specification/src/chapter2.adoc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/specification/src/chapter2.adoc b/specification/src/chapter2.adoc index ee56577..2340c37 100644 --- a/specification/src/chapter2.adoc +++ b/specification/src/chapter2.adoc @@ -480,9 +480,7 @@ a| Implement robust power management, and adopt glitch-safe software techniques. + Industry best practice should be followed. For example: ensuring un-initialized variables are not used; implementing integrity checking of critical data and hardware provisioned parameters; implementing redundancy in encoding, verification, branching, and critical logic. + + -Adopt randomization techniques between boot sessions. + - + -For example: cryptographic memory protection with at least boot freshness; register randomization. +Adopt randomization techniques between boot sessions. For example: cryptographic memory protection with at least boot freshness; register randomization. | SR_PHY_004 | Subverting supply chains