Study ISC2 CISSP Cryptography and Resilience: key concepts, common traps, and exam decision cues.
On this page
The second half of Domain 3 is about choosing the right trust and protection mechanism. CISSP wants you to know what each cryptographic or resilience control is actually solving.
Crypto-choice map
Requirement
Better first instinct
bulk confidentiality
symmetric encryption
digital signature and nonrepudiation
asymmetric signature
tamper detection with shared secret assurance
HMAC
strong key custody
HSM or managed key service
resilience against component or site failure
redundancy and resilience design matched to recovery goals
What the exam is really testing
If the stem says…
Strong reading
“key protection”
custody and management matter, not just algorithm selection
“integrity plus source assurance”
HMAC or signature logic matters
“availability or fault tolerance”
resilience design may matter more than crypto
Decision order that usually wins
Separate confidentiality, integrity, authentication, nonrepudiation, and availability.
Decide whether the real problem is cryptographic protection or resilience design.
If crypto is needed, choose the primitive family before the product.
If the stem mentions keys, focus on generation, storage, rotation, and custody.
If the stem mentions outages or component failure, shift to redundancy and recovery design.
The wrong CISSP answer often sounds technical but solves the wrong objective. Encryption, signatures, HMACs, and redundancy all matter, but they do not solve the same problem.
Scenario triage
Scenario
Better first move
large-volume data needs confidentiality
use symmetric encryption
sender must prove authorship and resist repudiation
use digital signatures
message integrity with shared-secret assurance is enough
use HMAC
organization worries about key theft or poor key custody
use HSM or managed key protection
service must survive device or site failure
design for redundancy and resilience
Common traps
Trap
Better rule
using encryption when the question is really about integrity or nonrepudiation
separate the objective first
treating key generation, storage, and rotation as one blur
key lifecycle matters
solving availability with confidentiality tools
resilience and crypto are different control families