{
	"id": "7a530a61-5a0f-4066-a2eb-2da507fc7a75",
	"created_at": "2026-04-06T00:09:29.022825Z",
	"updated_at": "2026-04-10T03:24:29.299353Z",
	"deleted_at": null,
	"sha1_hash": "1c425ff082a83ea856b2974251b57e2416df98eb",
	"title": "Verified Boot",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 33130,
	"plain_text": "Verified Boot\r\nArchived: 2026-04-02 12:41:39 UTC\r\nVerified Boot strives to ensure all executed code comes from a trusted source (usually device OEMs), rather than\r\nfrom an attacker or corruption. It establishes a full chain of trust, starting from a hardware-protected root of trust\r\nto the bootloader, to the boot partition and other verified partitions including system , vendor , and optionally\r\noem partitions. During device boot up, each stage verifies the integrity and authenticity of the next stage before\r\nhanding over execution.\r\nIn addition to ensuring that devices are running a safe version of Android, Verified Boot checks for the correct\r\nversion of Android with rollback protection. Rollback protection helps to prevent a possible exploit from\r\nbecoming persistent by ensuring devices only update to newer versions of Android.\r\nIn addition to verifying the OS, Verified Boot also allows Android devices to communicate their state of integrity\r\nto the user.\r\nBackground\r\nAndroid 4.4 added support for Verified Boot and the dm-verity kernel feature. This combination of verifying\r\nfeatures served as Verified Boot 1.\r\nWhere previous versions of Android warned users about device corruption, but still allowed them to boot their\r\ndevices, Android 7.0 started strictly enforcing Verified Boot to prevent compromised devices from booting.\r\nAndroid 7.0 also added support for forward error correction to improve reliability against non-malicious data\r\ncorruption.\r\nAndroid 8.0 and higher includes Android Verified Boot (AVB), a reference implementation of Verified Boot that\r\nworks with Project Treble. In addition to working with Treble, AVB standardized partition footer format and added\r\nrollback protection features.\r\nSource: https://source.android.com/security/verifiedboot/\r\nhttps://source.android.com/security/verifiedboot/\r\nPage 1 of 1",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://source.android.com/security/verifiedboot/"
	],
	"report_names": [
		"verifiedboot"
	],
	"threat_actors": [
		{
			"id": "aa73cd6a-868c-4ae4-a5b2-7cb2c5ad1e9d",
			"created_at": "2022-10-25T16:07:24.139848Z",
			"updated_at": "2026-04-10T02:00:04.878798Z",
			"deleted_at": null,
			"main_name": "Safe",
			"aliases": [],
			"source_name": "ETDA:Safe",
			"tools": [
				"DebugView",
				"LZ77",
				"OpenDoc",
				"SafeDisk",
				"TypeConfig",
				"UPXShell",
				"UsbDoc",
				"UsbExe"
			],
			"source_id": "ETDA",
			"reports": null
		}
	],
	"ts_created_at": 1775434169,
	"ts_updated_at": 1775791469,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/1c425ff082a83ea856b2974251b57e2416df98eb.pdf",
		"text": "https://archive.orkl.eu/1c425ff082a83ea856b2974251b57e2416df98eb.txt",
		"img": "https://archive.orkl.eu/1c425ff082a83ea856b2974251b57e2416df98eb.jpg"
	}
}