Course contentsShow
← Security
Lesson 1461 of 3,05229. Operating System Security - HardeningFree lesson

Platform Key, KEK, and Signature Databases

Understanding PK, KEK, db, and dbx databases that control which bootloaders and operating systems can execute.

Platform Key, KEK, and Signature Databases

What You'll Learn

You'll understand the four critical UEFI databases that control which bootloaders and operating systems can execute during Secure Boot.

The UEFI Key Hierarchy

When Secure Boot validates the boot chain, it relies on four specialized databases stored in firmware. Think of these as gatekeepers with different levels of authority that decide what's allowed to run on your system.

Platform Key (PK)

The Platform Key sits at the top of the trust hierarchy—the "root of trust." Typically owned by the hardware manufacturer (like Dell or HP), it controls who can modify the other security databases. Only one PK exists, and it acts like the master key to the entire Secure Boot system.

Key Exchange Key (KEK)

The KEK database contains keys that can update the signature databases below it. Operating system vendors (Microsoft, Canonical, Red Hat) usually have their keys enrolled here. Think of KEKs as authorized administrators who can modify the allow/deny lists.

Signature Database (db)

This is the allowlist of trusted signatures and certificates. Bootloaders, kernel modules, and OS components signed by keys in db are permitted to execute. This database contains public keys and hashes of known-good boot components.

Forbidden Signature Database (dbx)

The denylist that blocks known-malicious or compromised software, even if it was previously trusted. When vulnerabilities are found in bootloaders (like the "BootHole" vulnerability), their signatures get added to dbx through security updates.

The Validation Flow

During boot, UEFI checks each component's signature against db (allowed?), then dbx (blocked?). If signed by a trusted key and not revoked, execution proceeds.

Key Takeaway: PK, KEK, db, and dbx form a hierarchical trust system where PK controls KEK, KEK controls db/dbx, and db/dbx determine what bootloaders and OS components can execute during Secure Boot.