Objective 1.4 covers applied cryptography: key and certificate management, encryption levels, hardware that protects keys, ways to hide or replace data, and how hashing, signatures, and ledgers prove integrity.
Keys and certificates. PKI lets you trust that a public key belongs to its claimed owner. The public key is shared and verifies or encrypts; the private key stays secret and signs or decrypts. Key escrow gives a third party a key copy under controlled release. A certificate binds a public key to a named entity; it is requested with a certificate signing request (CSR), signed by a third-party CA that chains to a root of trust, or self-signed, and can cover many hosts as a wildcard certificate. Revocation is checked through a downloaded CRL or an on-demand OCSP query.
Encryption and key protection. Encryption applies at the full-disk, partition, volume, file, database, or record level, or in transport. Symmetric encryption uses one shared key; asymmetric encryption uses a public and private pair, which supports key exchange, signatures, and certificates. A TPM ties keys to one device, an HSM performs key operations for many systems, a key management system manages the key lifecycle, and a secure enclave isolates code and data from the main operating system.
Integrity and obfuscation. Hashing is one-way. Salting and key stretching make password hashes harder to crack. A digital signature, made with the signer's private key, proves origin and integrity, and a blockchain is a hash-linked ledger that makes altered history detectable. Steganography hides that data exists, tokenization swaps a value for a token mapped in a vault, and data masking hides or fakes part of a value.
Exam questions ask you to pick the right tool for a scenario: which key encrypts or verifies, why a salt helps, or what a TPM or HSM does.
Written by Knotch · reviewed Nov 15, 2026 · 8 study articles behind this page