privacyguides/privacyguides.org
1
1 Fork 0
mirror of https://github.com/privacyguides/privacyguides.org.git synced 2026-10-27 07:08:23 +00:00
Code Issues Activity

update: Add a quote from the Android Verified Boot documentation and … (#3284)

Browse Source
This commit is contained in:
fria authored and GitHub committed 2026-10-21 07:27:05 -05:00
1 parent 4c69c45f66
commit e23f2d4367
1 file changed
+6 -2
Download Patch File Download Diff File Expand all files Collapse all files
docs/os/android-overview.md
+6 -2
View File
@@ -20,9 +20,13 @@ 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. From the documentation:
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.
>Verified Boot strives to ensure all executed code comes from a trusted source (usually device OEMs), rather than from an attacker or corruption. It establishes a full chain of trust, starting from a hardware-protected root of trust to the bootloader, to the boot partition and other verified partitions including system, vendor, and optionally oem partitions. During device boot up, each stage verifies the integrity and authenticity of the next stage before handing over execution.
It provides protection against 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).
Verified Boot ensures the integrity of the operating system files, thereby preventing an adversary with physical access from tampering or installing malware on the device. In the unlikely case that malware is able to exploit other parts of the system and gain higher privileged access, Verified Boot will prevent and revert changes to the system partition upon rebooting the device.