CISSP Domain 3: Zero Hour Exam Cram Series

---

Security Architecture & Engineering | Final 48-Hour Decision System

Most candidates don’t fail Domain 3 because it’s technical

They fail because they fix problems instead of preventing them in design. Domain 3 is not about crypto or models. It’s about ensuring the architecture is right before anything is built.

The Secure Design Bias™

Design decides outcome. Controls only enforce it. If architecture is flawed:

• Encryption won’t save it
• Monitoring won’t detect it in time
• Controls become reactive
  ✓ CISSP rewards design-first thinking

The CISSP Decision Stack™

1. Human Safety
2. Legal / Compliance
3. Architecture Integrity (Design First)
4. Risk Optimization
5. Technical Implementation
   ✓ If a design flaw exists, eliminate all implementation answers immediately

The Elimination Engine™

Eliminate This First

• If design flaw exists → ✗ Eliminate monitoring, patching, tuning → ✓ Choose redesign or architecture fix
• If crypto is misused → ✗ Eliminate “add more encryption” → ✓ Fix the purpose (integrity, authentication, key management)
• If multiple controls exist → ✗ Eliminate reactive controls → ✓ Choose preventive architecture
• If system trust is questioned → ✗ Eliminate application-level fixes → ✓ Choose TCB or reference monitor
• If physical exposure exists → ✗ Eliminate software-only answers → ✓ Choose layered or environmental protection

Core Concepts

Security Models

• Bell-LaPadula → Confidentiality
• Biba → Integrity
• Clark-Wilson → Transaction integrity
  ✓ Use models based on intent, not memorization

Crypto Decision Layer

• Confidentiality → Encryption
• Integrity → Hashing
• Non-repudiation → Digital Signature
  Decision logic:
• ✓ Public verification → Digital Signature
• ✓ Performance constraint → Symmetric encryption
• ✓ Key distribution issue → Asymmetric encryption
  ✓ Most errors come from wrong purpose mapping

Key Management

Encryption fails if:

• Keys are exposed
• Keys are poorly stored
• Keys are not rotated
  ✓ CISSP tests key management more than encryption itself

Secure Design Principles

• Least privilege
• Defense in depth
• Fail secure
• Separation of duties
  ✓ These outweigh tool-based answers

Trusted Computing

• TCB
• Reference Monitor
• Security Kernel
  ✓ Focus on enforcement integrity

Assurance vs Functionality

• Assurance = confidence
• Functionality = capability
  ✓ Higher assurance does not automatically mean stronger security

Kill-Zone Confusions

Encryption vs Hash vs Signature

• Encryption is not integrity
• Hash is not confidentiality
• Signature is not encryption
  ✓ Wrong mapping = instant loss

Architecture vs Implementation

• Architecture prevents
• Implementation fixes
  ✓ CISSP prefers prevention

Prevention vs Detection

✓ Prevention is always preferred

Strong Crypto vs Correct Crypto

✓ Correct usage matters more than strength

Exam Psychology Layer

Rule 1: Design over Fix

✓ If redesign is an option, it is usually correct

Rule 2: Prevention over Detection

✓ Do not monitor a flawed design

Rule 3: Purpose over Technology

✓ Crypto must match intent

Rule 4: System Thinking over Component Thinking

✓ Think architecture, not feature

Rule 5: Simplicity Wins

✓ Over-engineered answers are often wrong

Scenario Drill

Scenario 1

A system uses strong encryption but leaks data due to exposed keys → ✓ Best Answer: Fix key management architecture

Scenario 2

An application logs user actions but cannot prevent unauthorized access → ✓ Best Answer: Redesign access control architecture

Scenario 3

Data integrity is compromised during transmission → ✓ Best Answer: Use hashing or integrity validation

Scenario 4

Users deny performing financial transactions → ✓ Best Answer: Digital signature for non-repudiation

Scenario 5

System built without least privilege and later patched with monitoring tools → ✓ Best Answer: Redesign with least privilege

Scenario 6

Sensitive system depends entirely on intrusion detection → ✓ Best Answer: Implement preventive controls in architecture

Scenario 7

High-performance system struggles with encryption overhead → ✓ Best Answer: Use symmetric encryption appropriately

Scenario 8

Secure system fails due to poor trust enforcement between components → ✓ Best Answer: Apply TCB or reference monitor principles

Scenario 9

Strong crypto implemented but incorrect algorithm used for integrity → ✓ Best Answer: Switch to hashing or digital signature

Scenario 10

System designed with single-layer security → ✓ Best Answer: Implement defense in depth

60-Second War Recall

✓ Design over implementation
✓ Prevention over detection
✓ Encryption is not integrity
✓ Signature enables non-repudiation
✓ Key management is critical
✓ Architecture comes first
✓ Models define behavior
✓ Simplicity wins

Final Insight

Domain 3 is not about technology. It is about ensuring the design eliminates risk before controls are applied. If your answer:

• fixes architecture
• aligns with purpose
• prevents failure
  ✓ You are aligned with CISSP thinking

Closing Line

Eliminate fast. Think Architect. Design secure—controls follow.