Cryptography for CISSP 2026 — Symmetric vs Asymmetric vs Hashing vs PKI

Overview

The Four Pillars of Cryptography

Every CISSP cryptography question maps to one of these four categories. Learn to recognize the signals.

🔴

Symmetric Encryption

One shared secret key encrypts and decrypts. Blazing fast — ideal for bulk data. The challenge: how do you securely share that key?

AES 3DES DES ChaCha20

🔵

Asymmetric Encryption

Public/private key pair. Encrypt with recipient's public key; only their private key decrypts. Solves key distribution — but 1,000× slower.

RSA ECC Diffie-Hellman DSA

🟢

Cryptographic Hashing

One-way function: any input → fixed-size digest. Cannot be reversed. Proves integrity — did the data change? Not confidentiality.

SHA-256 SHA-3 MD5 HMAC

🟣

PKI & Digital Signatures

Combines hashing + asymmetric. Sign with private key → anyone verifies with public key. Provides integrity, authentication, AND non-repudiation.

X.509 Certs CA Hierarchy CRL/OCSP

⚡ Quick Reference — What Each One Provides

Symmetric

🔴

Confidentiality

Fast bulk encryption

Asymmetric

🔵

Confidentiality + Auth

Key exchange & signing

Hashing

🟢

Integrity only

One-way, no key

Digital Sig

🟣

Auth + Integrity + NR

Hash + private key

💡

The Hybrid Model (TLS in practice): Real-world systems combine all four. TLS uses asymmetric (DH/ECDH) to exchange a symmetric key, symmetric (AES) for bulk data, hashing for integrity, and PKI certificates to authenticate the server. Understanding how they work together is key to passing Domain 3.

How It Works

Inside Each Cryptographic Approach

Select a model to see diagrams, algorithm tables, and key CISSP concepts.

🔴 Symmetric

🔵 Asymmetric

🟢 Hashing

🟣 PKI & Digital Sigs

🔴 Symmetric Encryption — One Key Does Both

📄 Plaintext

→

🔑 Secret Key

Encrypts

→

🔒 Ciphertext

→

🔑 Same Key

Decrypts

→

📄 Plaintext

⚠️

The Key Distribution Problem: If sender and receiver both need the same secret key, how do they share it securely without an attacker intercepting it? This is symmetric encryption's fundamental weakness — solved in practice by using asymmetric encryption (or Diffie-Hellman) to first exchange the symmetric key.

Block Cipher Modes of Operation

How the cipher processes data blocks — critical for CISSP exam questions.

Mode	Parallelizable?	Uses IV?	CISSP Verdict
ECB — Electronic Codebook	✅ Yes	❌ No	❌ Insecure — identical blocks = identical ciphertext; patterns leak
CBC — Cipher Block Chaining	❌ No	✅ Yes	⚠️ Common — XORs each block with previous; vulnerable to padding oracle
CTR — Counter Mode	✅ Yes	✅ Yes	✅ Secure — turns block cipher into stream cipher; fast & parallelizable
GCM — Galois/Counter Mode	✅ Yes	✅ Yes	✅ Best — CTR + authentication tag (AEAD); used in TLS 1.3

Common Symmetric Algorithms

Algorithm	Type	Key Size	Block Size	Status
AES (Rijndael)	Block	128/192/256-bit	128-bit	✅ Secure — NIST standard since 2001
3DES / TDEA	Block	112/168-bit	64-bit	⚠️ Deprecated — NIST retired 2023; legacy systems only
DES	Block	56-bit	64-bit	❌ Broken — brute-forceable in hours
Blowfish	Block	32–448-bit	64-bit	⚠️ Aging — 64-bit block susceptible to birthday attacks
ChaCha20	Stream	256-bit	N/A	✅ Secure — TLS 1.3; fast on mobile/embedded
RC4	Stream	40–2048-bit	N/A	❌ Broken — WEP attack; never use

🎯

CISSP Exam Signal: If the question says "fast," "bulk data," "disk encryption," "file encryption," or "both parties share a secret key" — it's Symmetric. AES is the answer unless the question specifically asks about a broken or deprecated algorithm.

🔵 Asymmetric Encryption — Two Keys, One Pair

🔒 FOR ENCRYPTION (Confidentiality)

📄 Plaintext

→

🔓 Bob's
PUBLIC Key

Anyone can encrypt

→

🔒 Ciphertext

→

🔑 Bob's
PRIVATE Key

Only Bob can decrypt

→

📄 Plaintext

✍️ FOR DIGITAL SIGNATURES (Authentication + Non-Repudiation)

📄 Message

→

🔑 Alice's
PRIVATE Key

Signs the hash

→

✍️ Signature

→

🔓 Alice's
PUBLIC Key

Anyone verifies

→

✅ Verified

🚨

Most-Tested CISSP Confusion: Signing vs Encrypting
Signing: uses YOUR private key to sign → anyone verifies with your public key → proves it came from YOU.
Encrypting: uses recipient's public key to encrypt → only their private key decrypts → ensures only they can read it.
Remember: You lock with their public key. You sign with your own private key.

Asymmetric Algorithms

Algorithm	Use Case	Key Size	Security Basis	Notes
RSA	Encrypt + Sign	2048–4096-bit	Integer factorization	✅ Secure — 2048-bit minimum; slow
ECC	Encrypt + Sign	256–521-bit	Elliptic curve discrete log	✅ Secure — 256-bit ECC ≈ 3072-bit RSA strength; faster
DH / DHE	Key Exchange ONLY	2048-bit+	Discrete logarithm	✅ Secure — cannot encrypt; DHE adds forward secrecy
ECDH / ECDHE	Key Exchange ONLY	256-bit+	Elliptic curve DL	✅ Secure — ECC variant; ECDHE = ephemeral, forward secrecy
DSA	Signing ONLY	1024–3072-bit	Discrete logarithm	⚠️ Older — FIPS 186 standard; cannot encrypt
ECDSA	Signing ONLY	256–521-bit	Elliptic curve DL	✅ Secure — used in Bitcoin, TLS certificates

🎯

Diffie-Hellman does NOT provide authentication. It solves key exchange but doesn't tell you WHO you're exchanging keys with. An attacker can perform a man-in-the-middle attack. DH must be combined with certificates (PKI) to authenticate the parties.

🟢 Cryptographic Hashing — One-Way Fingerprint

📄 Any input
(any length)

→

🟢 Hash
Function

One-way · No key

→

🔢 Fixed digest
(always same length)

🔒 Ciphertext

→

❌ Cannot
Reverse

The Four Required Properties of a Cryptographic Hash

1. Pre-image Resistance

Given a hash, you cannot find the original input. One-way function.

2. Second Pre-image Resistance

Given input X, you cannot find a different input Y with the same hash.

3. Collision Resistance

Computationally infeasible to find ANY two inputs with the same hash. MD5 and SHA-1 have FAILED this.

4. Avalanche Effect

Changing even one bit in the input radically changes the entire output hash.

Hash Algorithm Reference

Algorithm	Output Size	Status	Key CISSP Note
SHA-256 (SHA-2 family)	256-bit	✅ Secure	NIST standard; default choice for most uses
SHA-512 (SHA-2 family)	512-bit	✅ Secure	Stronger; used in code signing, certificates
SHA-3 / Keccak	224–512-bit	✅ Secure	Completely different design from SHA-2; sponge construction
SHA-1	160-bit	❌ Broken	Practical collision found 2017 (SHAttered). Avoid for integrity.
MD5	128-bit	❌ Broken	Collisions trivially generated; only safe for non-security checksums
HMAC-SHA256	256-bit	✅ Secure	Hash + secret key → integrity AND authentication (no non-repudiation)
bcrypt / scrypt / Argon2	Variable	✅ Secure	Key stretching for password storage; intentionally slow to resist brute force

⚠️

Hashing ≠ Encryption. A hash is NOT reversible and does NOT provide confidentiality. Storing passwords as hashes (with salt) is correct. Encrypting passwords is wrong — if the key is compromised, all passwords are exposed. If the question asks about password storage, the answer is hashing (specifically bcrypt/scrypt/Argon2 with salt).

🟣 Digital Signature — How It Actually Works

1

Alice hashes her message → produces a message digest (fixed-size fingerprint of the content)

↓

2

Alice encrypts the digest with her PRIVATE key → this is the digital signature

↓

3

Alice sends the message + signature to Bob

↓

4

Bob decrypts the signature using Alice's PUBLIC key → recovers Alice's original hash (Hash A)

↓

5

Bob independently hashes the received message → produces Hash B

↓

✓

If Hash A = Hash B: message is intact ✅ AND it came from Alice ✅ (non-repudiation ✅)

PKI Certificate Chain of Trust

🟣 Root CA

Self-signed · Trust anchor · Offline (air-gapped)

↓ signs

🔵 Intermediate CA

Trusted by Root CA · Issues end-entity certs · Can be revoked without touching Root

↓ signs

🟢 End-Entity Certificate

Your website, your email, your code — what the client actually validates

CRL — Certificate Revocation List

Periodic published list of revoked certificate serial numbers. Downloaded by client. Can be stale between publications.

OCSP — Online Certificate Status Protocol

Real-time query to CA asking "is this cert still valid?" More current than CRL but requires online access.

🎯

X.509 Certificate Contains: Subject (who it belongs to), Issuer (who signed it), Serial number, Public key, Validity dates, Signature algorithm, CA's digital signature. Does NOT contain the private key — that is always kept secret by the subject.

Compare

Side-by-Side Comparison

All four cryptographic approaches across every CISSP-relevant dimension.

Criteria	🔴 Symmetric	🔵 Asymmetric	🟢 Hashing	🟣 PKI / Dig. Sig.
Key TypeBasics	Single shared secret key	Public + Private key pair	No key (hash function only)	Key pair + X.509 certificate
SpeedBasics	⚡ Very fast (hardware-optimized)	🐢 Slow (1,000× slower than symmetric)	⚡ Very fast	🔶 Mixed (hash=fast, sign=slow)
Key DistributionBasics	❌ Hard — must share key securely	✅ Easy — public key is public	✅ None needed	✅ Managed by PKI / CA
Typical Key/Output SizeBasics	128–256-bit (AES)	2048–4096-bit RSA; 256-bit ECC	128-bit (MD5) to 512-bit (SHA-512)	2048-bit RSA or 256-bit ECDSA
Infrastructure RequiredBasics	None (just share the key)	Minimal (generate key pair)	None	Full PKI: CA, CRL/OCSP, cert mgmt
Provides Confidentiality?Security Properties	✅ Yes — encrypts data	✅ Yes — encrypt with public key	❌ No — hashing ≠ encryption	❌ Signing only; add encryption separately
Provides Integrity?Security Properties	❌ No (alone) — use with HMAC/GCM	❌ No (alone)	✅ Yes — detects tampering	✅ Yes — hash in the signature
Provides Authentication?Security Properties	❌ No — both sides share same key	✅ Yes — public key ties to identity	❌ No (use HMAC for this)	✅ Yes — verified against certificate
Non-Repudiation?Security Properties	❌ No	❌ No (alone) — need PKI context	❌ No	✅ Yes — only you have your private key
Primary Use CasesUse Cases	Disk encryption, file encryption, database encryption, VPN tunnels (data phase)	TLS key exchange, email encryption (PGP/S-MIME), SSH authentication	Password storage, file integrity checks, digital signatures (the hash part)	HTTPS certificates, code signing, email signing, document signing
Common AlgorithmsUse Cases	AES-256, AES-128, 3DES (legacy), ChaCha20	RSA, ECC, ECDSA, Diffie-Hellman, ECDH	SHA-256, SHA-3, SHA-512, HMAC-SHA256, bcrypt	RSA-SHA256, ECDSA, X.509 (format)
Primary Attack TypesAttacks	Brute force (short key), meet-in-the-middle (2DES), birthday attack (64-bit block)	Integer factorization (RSA), discrete log, small key, quantum threat (Shor's algorithm)	Collision attack, preimage attack, rainbow table (unsalted passwords), length extension	CA compromise, cert forgery, MITM (if no cert validation), revocation gap
Quantum Computing ThreatAttacks	🟡 Moderate — double key length needed (AES-256 adequate)	🔴 Severe — Shor's algorithm breaks RSA/ECC; post-quantum replacements needed	🟡 Moderate — Grover's algorithm halves effective strength	🔴 Severe — relies on asymmetric; same threat as asymmetric

Real Examples

Cryptography in the Real World

Six real-world scenarios that map directly to CISSP exam questions.

🔵 HTTPS / TLS — The Hybrid Encryption Model (Most Important) ▼

Model: Hybrid (Asymmetric + Symmetric + Hashing + PKI)

When your browser connects to https://bank.com:

1. Certificate Validation (PKI): The server sends its X.509 certificate. Your browser verifies the CA signature and checks CRL/OCSP to confirm it's not revoked.

2. Key Exchange (Asymmetric — ECDHE): Browser and server perform an ephemeral Diffie-Hellman exchange to establish a shared session key. Neither side sends the key — they compute it independently. This provides Perfect Forward Secrecy.

3. Bulk Data Encryption (Symmetric — AES-256-GCM): All actual page content is encrypted using the negotiated symmetric key. AES-GCM provides both confidentiality AND integrity (it's an AEAD cipher).

CISSP takeaway: TLS is the canonical example of hybrid encryption. If asked why we don't just use asymmetric for everything: it's too slow for bulk data.

🟢 Password Storage — Why Hashing (Not Encryption) is Correct ▼

Model: Hashing (with salt + key stretching)

Websites should never store your plaintext password — or even an encrypted version.

Correct approach: Generate a random salt for each user → concatenate salt + password → run through a slow hash function (bcrypt, scrypt, or Argon2) → store only the salt + hash.

Why not encryption? If the encryption key is compromised, all passwords are exposed. A hash has no key to steal. Even with the hash, the attacker must brute-force each password individually.

Why is MD5/SHA-1 wrong for passwords? They're fast — which helps attackers (billions of guesses per second). bcrypt is intentionally slow (configurable cost factor).

CISSP takeaway: "How should passwords be stored?" → Hashed with salt using an adaptive (slow) function like bcrypt. "Encrypt them" is wrong.

🔴 BitLocker / FileVault — Full-Disk Encryption ▼

Model: Symmetric (AES-128 or AES-256)

BitLocker (Windows) and FileVault (macOS) encrypt entire disk volumes using AES symmetric encryption.

Key management: The Volume Master Key (VMK) is protected by a Key Protector — which may be a TPM chip, a PIN, a recovery key, or a combination. The key hierarchy means the actual AES key is never directly exposed.

Why symmetric? Encrypting hundreds of gigabytes in real-time requires the speed of AES. Asymmetric encryption would be thousands of times too slow for disk I/O.

CISSP takeaway: "Encrypt 2TB of data at rest" → Symmetric (AES). The speed requirement and data volume are the giveaways.

🔵 SSH Key-Based Authentication — Asymmetric in Action ▼

Model: Asymmetric (RSA or Ed25519)

SSH key authentication replaces passwords with a public/private key pair:

Setup: You generate a key pair. Your public key is placed on the server (in ~/.ssh/authorized_keys). Your private key stays on your machine — never shared.

Authentication: The server challenges you with a random number encrypted with your public key. You decrypt it with your private key and return it. If successful, you're authenticated — without ever transmitting your private key.

This provides authentication (proves your identity) but NOT non-repudiation in the legal sense — SSH doesn't log who used the private key, and private keys can be shared (though inadvisable).

CISSP takeaway: SSH keys → asymmetric. RSA-2048 or Ed25519 (ECC) recommended. No password = better security (can't be phished or brute-forced).

🟣 Code Signing — Ensuring Software Authenticity ▼

Model: Digital Signatures / PKI (SHA-256 + RSA or ECDSA)

When a software vendor publishes an installer, they sign it:

1. Vendor hashes the installer binary (SHA-256) → gets a digest.
2. Vendor signs the digest with their private key (issued by a Code Signing CA) → creates the digital signature.
3. The signature + vendor's certificate are embedded in or alongside the installer.

When you download it: Your OS decrypts the signature using the vendor's public key (from the certificate), independently hashes the downloaded file, and compares. If they match — the file is authentic and unmodified.

This catches: Tampering in transit (supply chain attack), malware injected into the installer, unauthorized distributors.

CISSP takeaway: Code signing → digital signatures (PKI). Provides integrity + authentication + non-repudiation. Windows SmartScreen, Apple Gatekeeper, and Linux package managers all use this.

🔵 PGP / S/MIME Email Encryption — Full Hybrid Example ▼

Model: Hybrid (Symmetric + Asymmetric + Digital Signature)

PGP (Pretty Good Privacy) and S/MIME both use a hybrid approach for email:

Encryption (confidentiality):
1. Generate a random one-time symmetric session key (AES).
2. Encrypt the email body with the session key (fast symmetric).
3. Encrypt the session key with the recipient's public key (RSA/ECC).
4. Send both together. Only the recipient can decrypt the session key, then decrypt the email.

Signature (authentication + non-repudiation):
1. Hash the email → sign the hash with your private key.
2. Attach the signature. Recipient verifies with your public key.

CISSP takeaway: PGP/S-MIME demonstrates all four primitives working together. If a question asks about securing email with both confidentiality AND non-repudiation, you need both encryption (asymmetric key exchange + symmetric body) AND a digital signature.

Practice Quiz

10 CISSP-Style Scenario Questions

Each question is a scenario-based item modeled on real CISSP exam format. No memorization — you need to reason from the scenario.

Question 1 of 10

QUESTION 1

Score: 0/0

0

/ 10

Decision Tool

Which Cryptographic Approach?

Answer 3 questions to identify the right cryptographic primitive for any CISSP scenario.

Is the primary goal to keep data confidential — to prevent unauthorized parties from reading it?

Think: Does the scenario involve encrypting data? Is the concern about someone reading information they shouldn't? Or is the concern about verifying integrity/identity?

🔒

Yes — I need to encrypt data for confidentiality

Preventing unauthorized reading of data at rest or in transit

✅

No — I need to verify integrity and/or prove identity

Checking that data hasn't been modified, or proving who created/sent something

Do both parties already share a secret key, or do you need to exchange keys with someone with no prior shared secret?

Think: Is this bulk data encryption (disk, database, VPN tunnel) with an established key? Or do you need to first establish a shared key with a stranger?

🔴

We already share a secret key / bulk data encryption

Speed is critical; large volumes of data; key is already established (disk, DB, VPN)

🔵

No prior shared key / need to establish one securely

First-time communication with no pre-shared secret; key exchange needed

Do you need to prove who created or sent the data — providing authentication and non-repudiation?

Think: Is it enough to verify the data is unmodified? Or must you also prove identity — so the sender cannot later deny sending it?

🟣

Yes — need to prove identity + non-repudiation

Code signing, certificate authentication, legal document signing, audit trail

🟢

No — just verify the data is unmodified

File integrity check, password storage, checksum verification — no identity needed

Memory Hooks

Mnemonics & Exam Memory Tricks

Click each card to flip and reveal the mnemonic. Built for rapid recall under exam pressure.

🔴

Symmetric

Click to reveal

"Same Key —
Speed is King"

SYM = Same key. One key encrypts AND decrypts. Lightning fast. Use for big data. Weakness: sharing the key.

🔵

Asymmetric

Click to reveal

"Lock with
Public, Open
with Private"

Encrypt → recipient's PUBLIC key. Decrypt → recipient's PRIVATE key. Sign → YOUR private. Verify → YOUR public.

🟢

Hashing

Click to reveal

"One-Way Street —
Integrity Only"

HASH = Has no reverse. No key. No confidentiality. Only tells you: has this changed? Use for passwords + file integrity.

🟣

PKI / Dig. Sig.

Click to reveal

"Sign Private,
Verify Public —
Can't Deny It"

Hash the message → sign hash with PRIVATE key → anyone verifies with PUBLIC key. Provides non-repudiation.

🎯 The Ultimate Cryptography Exam Cheat Sheet

If the question says… → Think this → Use this

If the question says…	Think…	Answer
"fast" / "bulk data" / "disk encryption" / "large files" / "at rest" / "both have the key"	🔴 Speed + volume. Same key both ways.	Symmetric (AES)
"no prior shared key" / "key exchange" / "public key" / "no pre-shared secret" / "DH" / "RSA"	🔵 No prior relationship. Solve key distribution.	Asymmetric
"integrity" / "detect tampering" / "checksum" / "password storage" / "fingerprint" / "one-way"	🟢 One-way. No key. Did it change?	Hashing (SHA-256)
"non-repudiation" / "prove sender" / "cannot deny" / "code signing" / "certificate" / "digital signature"	🟣 Identity proof. Hash + private key.	Digital Signature / PKI
"integrity AND authentication" / "HMAC"	🟢+🔑 Hash with a shared secret key.	HMAC (no NR)
"Perfect Forward Secrecy" / "ephemeral" / "past sessions safe if key compromised"	🔵 Ephemeral DH. New key per session.	DHE / ECDHE

🚨

The Two Most-Failed CISSP Cryptography Questions:

1. Signing direction: "You sign with your private key" — NOT your public key. Your private key proves it came from YOU because only you have it. The exam often phrases it as "encrypt with private key" which is sign, not encrypt.

2. Hashing ≠ Encryption: A hash cannot be reversed. "Encrypt passwords" is wrong. "Hash passwords" is correct. If asked which provides non-repudiation — hashing alone does NOT. Only digital signatures (hash + private key) provide non-repudiation.

💡

CIA Triad Map for Cryptography:
Confidentiality → Symmetric or Asymmetric encryption
Integrity → Hashing, HMAC, or Digital Signatures
Availability → Not directly a cryptography concern (key management / escrow helps)
Authentication → Asymmetric (PKI) or HMAC
Non-Repudiation → Digital Signatures ONLY (private key is the proof)

Symmetric · Asymmetric
Hashing · PKI & Digital Signatures

The Four Pillars of Cryptography

⚡ Quick Reference — What Each One Provides

Inside Each Cryptographic Approach

🔴 Symmetric Encryption — One Key Does Both

Block Cipher Modes of Operation

Common Symmetric Algorithms

🔵 Asymmetric Encryption — Two Keys, One Pair

Asymmetric Algorithms

🟢 Cryptographic Hashing — One-Way Fingerprint

The Four Required Properties of a Cryptographic Hash

Hash Algorithm Reference

🟣 Digital Signature — How It Actually Works

PKI Certificate Chain of Trust

Side-by-Side Comparison

Cryptography in the Real World

10 CISSP-Style Scenario Questions

Which Cryptographic Approach?

Mnemonics & Exam Memory Tricks

🎯 The Ultimate Cryptography Exam Cheat Sheet

Ready to Pass the CISSP?
Get Everything You Need in One Place.

Symmetric · Asymmetric Hashing · PKI & Digital Signatures

The Four Pillars of Cryptography

⚡ Quick Reference — What Each One Provides

Inside Each Cryptographic Approach

🔴 Symmetric Encryption — One Key Does Both

Block Cipher Modes of Operation

Common Symmetric Algorithms

🔵 Asymmetric Encryption — Two Keys, One Pair

Asymmetric Algorithms

🟢 Cryptographic Hashing — One-Way Fingerprint

The Four Required Properties of a Cryptographic Hash

Hash Algorithm Reference

🟣 Digital Signature — How It Actually Works

PKI Certificate Chain of Trust

Side-by-Side Comparison

Cryptography in the Real World

10 CISSP-Style Scenario Questions

Which Cryptographic Approach?

Mnemonics & Exam Memory Tricks

🎯 The Ultimate Cryptography Exam Cheat Sheet

Ready to Pass the CISSP?Get Everything You Need in One Place.

Symmetric · Asymmetric
Hashing · PKI & Digital Signatures

Ready to Pass the CISSP?
Get Everything You Need in One Place.