TechclickCISSP Prep
☰

CISSP cheat sheet · Domain 3 · 13% of exam

Security Architecture and Engineering

How to design systems that are secure by default: design principles, formal security models, cryptography, cloud and embedded architectures, and physical security.

Crypto goal decoder

Goal word in the stemGoalAnswer
secret / only X can read / not interceptedConfidentialityEncrypt — receiver’s public key or AES (symmetric)
preserve / not altered / veracity / validateIntegrityHash (SHA-256). Ignore “Top Secret” background noise
integrity + authenticity with a shared keyIntegrity + authenticationHMAC
cannot deny sending / non-repudiationNon-repudiationDigital signature with the sender’s private key (no confidentiality!)
unbreakable when implemented correctlyPerfect secrecyOne-time pad (Vernam)
agree a key over an insecure channelKey exchangeDiffie-Hellman / ECDH (no data encryption; MITM risk without authentication)

Security models

ModelProtectsRule / hook
Bell-LaPadulaConfidentialityNo read up, no write down (*-property). Does NOT stop covert channels
BibaIntegrityNo read down, no write up
Clark-WilsonCommercial integrityWell-formed transactions + separation of duties (subject → program → object)
Brewer-NashConflict of interestChinese Wall: access to Bank A blocks Bank B
Information flowFlow between levelsDetects covert channels
Take-Grant / Graham-Denning / HRURightsHow rights are passed, created and deleted

Rule cards

Design principlesLeast privilege · defense in depth · secure defaults · fail securely (fail-safe for people) · separation of duties · keep it simple · zero trust · privacy by design · trust but verify · shared responsibility.
Trusted computingTCB = all components enforcing security · Reference monitor = always invoked, tamper-proof, verifiable · Security kernel = its implementation.
Symmetric vs asymmetricSymmetric: one shared key, fast, bulk data (AES 128-bit block; 128/192/256 keys; keys needed n(n−1)/2) · Asymmetric: key pair, slow, key exchange + signatures (RSA, ECC, DH; keys needed 2n).
Keys ruleConfidentiality → receiver’s PUBLIC key · Signature → sender’s PRIVATE key (“Lock for THEM, sign as ME”).
PKIRA verifies identity · CA issues, signs and revokes · CRL = periodic revocation list · OCSP = real-time check · never escrow signing keys.
Post-quantumNIST FIPS 203 (ML-KEM), 204 (ML-DSA), 205 (SLH-DSA). Build crypto-agility and a crypto inventory now.
NIST cloud characteristicsOn-demand self-service · broad network access · resource pooling (multi-tenant) · rapid elasticity · measured service.
Cloud modelsIaaS (you manage OS and up) · PaaS (apps and data) · SaaS (data and access) · Private / community / public / hybrid · CSA STAR: Level 1 self-assessment · Level 2 third-party · Level 3 continuous.
EvaluationCommon Criteria (ISO 15408): Protection Profile (needs) · Security Target (claims) · TOE · EAL1–EAL7 (EAL7 formally verified).
FireStages: incipient → smoke → flame → heat · earliest detection = incipient (aspirating/VESDA) · rate-of-rise = heat detector · data centre water = pre-action · classes (US): A ordinary, B liquids, C electrical, D metals, K kitchen · human life first.
Power / HVACUPS = instant bridge; generator = startup gap · low humidity = static, high = corrosion · positive pressure keeps dust and smoke out.
Physical layersDeter → Deny → Detect → Delay · 8 ft fence + barbed wire deters a determined intruder · mantrap stops tailgating · CPTED: natural surveillance, natural access control, territorial reinforcement.

Hard words made simple

TermSimple meaningExample / analogyExam hook
HashOne-way fingerprint of dataFile checksumIntegrity only
HMACHash + shared secret keyAPI message checkIntegrity + authenticity, no non-repudiation
Salt vs IVSalt: random value added before hashing passwords · IV: random start value for encryptionSame password → different hashesPasswords → salt; encryption → IV
Kerckhoffs’s principleOnly the key must be secret, not the algorithmAES is public and still secureOpposite of security through obscurity
ECB / CBC / GCMECB leaks patterns · CBC chains blocks · GCM encrypts + authenticatesThe “ECB penguin” imageECB = weakest mode
Perfect forward secrecyFresh key per session; an old key leak does not expose past sessionsECDHE in TLSStolen server key ≠ old traffic exposed
Birthday attackFinding two inputs with the same hashHash collisionCollisions → birthday
Meet-in-the-middleAttack double encryption from both endsWhy 2DES is weak—
Side-channelSteal secrets from timing, power or soundMeasuring CPU power drawPhysical leakage
TEMPESTProtection against electromagnetic emanationsShielded roomsEM leakage
Covert channelHidden, unauthorised path for dataLeaking bits via CPU timing→ information flow model
VM escapeBreak out of a VM to the hypervisorA tenant attacks the hostBiggest virtualisation risk
TPM / HSMChip on the motherboard for keys / dedicated key applianceBitLocker uses a TPMKeys belong here, never in code
ICS / SCADASystems that run physical processesPower plant controlAvailability + safety first
MantrapTwo-door booth letting one person through at a timeBank vault entryAnti-tailgating (preventive)
IncipientVery first stage of fire, before visible smokeAspirating detector (VESDA)Earliest detection

Ready for the full bank?

2,000+ explained questions, timed mocks and a CAT simulator that behaves like the real exam.