CISSP Domain 3: Public Key Infrastructure (PKI) & Digital Signatures — Mindmap Review Study Guide
═══════════════════════════════════
PART 1: MERMAID MINDMAP
═══════════════════════════════════
mindmap
root((Digital Signatures, Certs, PKI, Keys))
Digital Signatures
Services
Integrity
Authenticity
Non-repudiation
Use Cases
Emails
Code signing
Legal documents
Non-repudiation Types
Origin
Delivery
Digital Certificates
Purpose and Contents
Issuers
Comodo
Symantec
Digicert
Entrust
Company internal
Self-signed
X.509 Standard
Lifecycle
Replacement
Revocation
Revocation Checks
CRL
OCSP
Certificate Pinning
DigiNotar
Certificate Transparency
PKI
Definition
Certificate Authority
Root of Trust
Registration Authority
Intermediate and Issuing CA
Chain of trust
Certificate DB
Certificate Store
Key Management
Kerckhoffs Principle
Generation
Distribution
Diffie-Hellman
Out-of-band
Hybrid cryptography
TLS
Storage
TPM
HSM
Rotation
Disposition
Crypto-shredding
AES
Recovery
Split Knowledge
Dual Control
Key Escrow
═══════════════════════════════════
PART 2: TECHNICAL DEFINITIONS & CONCEPTS
═══════════════════════════════════
Digital Signatures
Digital Signatures — Provide three major services: Integrity, Authenticity, and Non-repudiation. Used for sending emails, code signing (e.g., verifying iPhone updates from Apple), and signing legal documents (e.g., PDFs).
Integrity — The ability to tell if a message or file has been changed or modified in any way.
Authenticity — The ability to know who the message came from and confirm the sender’s identity.
Non-repudiation — The assurance that someone cannot deny the validity of something.
Non-repudiation of Origin — The sender cannot deny that they sent exactly the message that was received.
Non-repudiation of Delivery — The receiver cannot deny that they received a specific message.
Digital Certificates
Digital Certificates — Used to verify the owner of a public key, preventing attackers from intercepting and swapping keys. Contains the name of the owner and a copy of their public key.
Big Certificate Authorities — Organizations like Comodo, Symantec, Digicert, or Entrust that issue certificates trusted globally.
Company Certificates — Certificates issued by a company, trusted only within that company.
Self-signed Certificates — Certificates created by an individual, trusted only by the creator.
X.509 — The standard that ensures all digital certificates created by different entities are interoperable.
Replacement — The regular replacement of expired certificates. Certificates are typically valid for one to two years, with the expiry date noted in the certificate itself.
Revocation — The process of invalidating a digital certificate before its expiry date, typically because the associated private key has been compromised. Requires contacting the CA to add it to a revocation list.
| Protocol | Description | Efficiency |
|---|---|---|
| CRL (Certificate Revocation List) | CA sends a large file of all revoked certs; client searches it. | Older, less efficient, lots of overhead. |
| OCSP (Online Certificate Status Protocol) | Client queries CA for status of a specific cert; CA responds. | Newer, more efficient. |
Certificate Pinning — Trusting a local, pre-installed certificate rather than downloading one, to prevent attackers from intercepting and forwarding spoofed certificates. ⚠️ EXAM TIP: The speaker explicitly notes to know about pinning in case it appears on the exam, even though it has been superseded by Certificate Transparency.
DigiNotar — A real-world example of a spoofed certificate attack where an attacker intercepted and forwarded a spoofed certificate.
Certificate Transparency — A protocol that has superseded certificate pinning due to significant issues found with pinning.
PKI
PKI (Public Key Infrastructure) — The broad set of roles, policies, procedures, hardware, and software used to create, distribute, use, store, replace, and revoke digital certificates to bind a public key to its owner.
Certificate Authority (CA) — The Root of Trust in a PKI. Uses its private key to encrypt data (owner name and public key) to create a digital certificate. Its public keys are pre-installed in browsers.
Registration Authority (RA) — The role within the CA that performs identity proofing to confirm a user’s identity before a certificate is created.
Intermediate CA — Certificates signed by the Root CA’s private key, which are then used to sign issuing certificates. The Root CA’s private key is kept offline and air-gapped to prevent compromise.
Issuing CA — The role that actually signs and creates the entity certificates that users pay a CA to make. ⚠️ EXAM TIP: If a question asks which role in the CA issues certificates, the perfect answer is the Issuing CA.
Chain of Trust — The hierarchy where the Root CA signs intermediate certificates, which sign issuing certificates, which sign entity certificates, allowing you to trace back to the Root CA’s private key.
Certificate DB — The database maintained by each CA that stores a list of all certificates they have ever issued and which have been revoked.
Certificate Store — The local secure storage place on end-point systems (desktops, laptops, mobile phones) for private keys, other keys, and certificates (like big CA public keys).
Key Management
Key Management — The process of generating, distributing, storing, rotating, disposing, and recovering keys. Considered the hardest part of cryptography.
Kerckhoffs’s Principle — A principle from 1883 stating that a cryptosystem should be secure even if everything about the system, except the key, is public knowledge. An attacker can know the algorithm, initialization vector, and ciphertext, but the information remains secure as long as the key is secret.
Generation — Creating new symmetric or asymmetric key pairs. Each new key must be randomly selected out of the entire keyspace to avoid the “plague of cryptography”: patterns.
Distribution — Securely transmitting new keys to whoever needs them.
| Method | Description |
|---|---|
| Diffie-Hellman | Uses asymmetric crypto to generate the same key for two people without sending the key itself. |
| Out-of-band | Sending keys through a separate communications channel (e.g., letter, phone). |
| Hybrid Cryptography | Encrypting a symmetric key with the receiver’s public key, sending it, then switching to symmetric crypto for data. (Used by TLS). |
TLS — A super popular protocol that uses hybrid cryptography to securely distribute a symmetric key and then use it for data encryption.
Storage — Keeping created or received keys in an extremely secure location.
| Hardware | Description |
|---|---|
| TPM (Trusted Platform Module) | Tiny chips built into end-point devices to securely store keys. Required for whole drive encryption. |
| HSM (Hardware Security Module) | External standalone devices that store keys and act as cryptographic accelerators (encryption/decryption/signatures). |
Rotation — Periodically changing encryption keys to a new symmetric key or asymmetric key pair. Frequency depends on the value of the data and the risk of compromise.
Disposition — Securely and defensibly destroying every single copy of an encryption key.
Crypto-shredding — Securely destroying data by destroying the encryption keys used to encrypt it (e.g., using an excellent algorithm like AES). If all copies of the key are destroyed, the data is rendered unrecoverable.
AES — An excellent encryption algorithm mentioned in the context of crypto-shredding.
Recovery — Methods to recover a lost key.
| Method | Description |
|---|---|
| Split Knowledge | Key knowledge split among 2+ people; must combine bits to recover the key. |
| Dual Control | 2+ people must perform an action together to recover the key (e.g., turning two keys simultaneously). |
| Key Escrow | Copy of the key stored with a trusted third party; requested when recovery is needed. |