From faaa777c6d0d35548eaccee4e30a09bed94e5ee3 Mon Sep 17 00:00:00 2001 From: ignoramous Date: Thu, 25 Dec 2025 06:58:50 +0530 Subject: [PATCH] docs/os: AVB does not prevent evil maid AVB may help deter rouge firmware changes and prevent tampering of the OS. Signed-off-by: ignoramous --- docs/os/android-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/os/android-overview.md b/docs/os/android-overview.md index 402dc84c8..05c9f1250 100644 --- a/docs/os/android-overview.md +++ b/docs/os/android-overview.md @@ -20,7 +20,7 @@ Key components of the Android security model include [verified boot](#verified-b ### Verified Boot -[**Verified Boot**](https://source.android.com/security/verifiedboot) is an important part of the Android security model. It provides protection against [evil maid](https://en.wikipedia.org/wiki/Evil_maid_attack) attacks, malware persistence, and ensures security updates cannot be downgraded with [rollback protection](https://source.android.com/security/verifiedboot/verified-boot#rollback-protection). +[**Verified Boot**](https://source.android.com/security/verifiedboot) is an important part of the Android security model. It protects from boot path changes, deters firmware tampering, prevents malware persistence, and ensures security updates cannot be downgraded with [rollback protection](https://source.android.com/security/verifiedboot/verified-boot#rollback-protection). Android 10 and above has moved away from full-disk encryption to more flexible [file-based encryption](https://source.android.com/security/encryption/file-based). Your data is encrypted using unique encryption keys, and the operating system files are left unencrypted.