Movaci Movaci CISSP Study
CISSP Domain 3 · 12.8% of the exam

Security Architecture and Engineering

Domain 3 of the ISC2 CISSP exam outline effective 15 April 2027 carries 12.8% of the exam weight. It covers 10 objectives and 82 study topics, listed below with short explanations written for exam preparation.

Open the Domain 3 mindmap Take the practice test Study the flashcards

3.1 Research, implement, and manage engineering processes using secure design principles

Threat modeling
Identify threats early in design, when fixes are cheapest.
Principle of Least Privilege (PoLP)
Grant only the access required for the task.
Defense in Depth (DiD)
Layered controls so one failure does not lead to compromise.
Secure defaults
Systems ship locked down; users opt in to less secure settings.
Fail securely
On failure, default to a safe state, for example deny access (fail closed) unless life safety requires fail open.
Separation of Duties (SoD)
No single person controls all steps of a sensitive process.
Keep it simple and small
Smaller attack surface and less complexity means fewer flaws.
Zero Trust (ZT)
No implicit trust from network location. Verify explicitly for every request (NIST SP 800-207).
Privacy by design
Build privacy in from the start, including privacy-enhancing technologies such as anonymization, differential privacy and homomorphic encryption.
Shared responsibility
Cloud provider and customer split duties; the split shifts across IaaS, PaaS, SaaS.
Secure Access Service Edge (SASE)
Converges SD-WAN with cloud security services such as SWG, CASB, ZTNA and FWaaS.
Well-architected framework
Cloud provider design guidance with security as a pillar (AWS, Azure, Google Cloud).
Rotation of duties
Rotating people through roles exposes fraud and reduces single-person dependency.
Two-person integrity
Critical actions require two authorized people present, for example key ceremonies.

3.2 Understand the fundamental concepts of security models (e.g., Biba, Star, Bell-LaPadula)

Bell-LaPadula
Confidentiality. Simple security: no read up. Star (*) property: no write down.
Biba
Integrity. Simple integrity: no read down. Star integrity: no write up.
Star properties
The * rules in Bell-LaPadula and Biba govern writing: no write down for confidentiality, no write up for integrity.
Clark-Wilson Study topic
Integrity via well-formed transactions, the access triple (subject, program, object) and separation of duties.
Brewer-Nash (Chinese Wall) Study topic
Dynamic access that prevents conflicts of interest.

3.3 Select controls based upon systems security requirements

Requirements to controls Study topic
Derive controls from security and privacy requirements, risk and classification.
Evaluation criteria Study topic
Common Criteria (ISO/IEC 15408) with EAL1 to EAL7 and protection profiles.

3.4 Understand security capabilities of information systems (e.g., memory protection, TPM, HSM, encryption/decryption)

Memory protection
Process isolation, ASLR, DEP/NX and protection rings keep code from touching other memory.
Trusted Platform Module (TPM)
Hardware chip on the device for key storage, measured boot and attestation.
Hardware Security Module (HSM)
Dedicated, tamper-resistant appliance or cloud service that generates and protects keys and performs crypto operations.
Encryption and decryption
Built-in capabilities such as self-encrypting drives and hardware acceleration.

3.5 Assess and mitigate the vulnerabilities of security architectures, designs, and solution elements

Client-based systems
Endpoint malware, browser risks, local caches.
Server-based systems
Unpatched services, data flow control, misconfiguration.
Database systems
Aggregation, inference, injection. Countermeasures: polyinstantiation, views, cell suppression.
Cryptographic systems
Weak algorithms, poor key management, implementation flaws.
OT and Industrial Control Systems
SCADA, PLCs and DCS often run legacy protocols without authentication. Safety and availability come first.
Cloud-based systems
SaaS, IaaS, PaaS, serverless and FaaS. Misconfiguration and identity are leading causes of breach.
Distributed systems
Many nodes and trust boundaries; consistency and communication security issues.
Internet of Things (IoT)
Weak defaults, limited patching, long lifespan. Segment them.
Microservices and containerization
Many APIs and service identities, shared kernels, image provenance, orchestration security.
Embedded systems
Firmware with limited update paths and constrained resources.
High-performance computing
Performance often prioritized over security controls.
Edge computing systems
Processing near the data source; physical exposure and distributed management.
Virtualized systems
Hypervisor compromise, VM escape, VM sprawl.
Supply chain risk
Compromised components, firmware or updates introduced before delivery.
Autonomous systems
Systems acting without human input (vehicles, drones, AI agents): safety, manipulation and accountability risks.
Quantum computing
Threatens current public key cryptography; plan crypto agility and migration to post-quantum algorithms.

3.6 Select and determine cryptographic solutions

Cryptographic life cycle
Key generation, distribution, storage, use, rotation, revocation and destruction; algorithm selection and retirement.
Cryptographic methods
Symmetric (AES), asymmetric (RSA, DH), elliptic curve, and post-quantum (NIST FIPS 203 ML-KEM, FIPS 204 ML-DSA, FIPS 205 SLH-DSA).
Public Key Infrastructure (PKI)
CAs, RAs, X.509 certificates, key distribution, CRL and OCSP for revocation.
Key management practices
Rotation, access management, separation, escrow, HSM storage, split knowledge and dual control.
Digital signatures and certificates
Sign a hash with the private key; verify with the public key. Gives integrity, authenticity and non-repudiation.

3.7 Understand methods of cryptanalytic attacks

Brute force
Try every key. Defeated by sufficient key length.
Ciphertext only
Attacker has only ciphertext.
Known plaintext
Attacker has plaintext and matching ciphertext.
Frequency analysis
Exploits letter frequency in simple substitution ciphers.
Chosen ciphertext
Attacker can obtain decryptions of chosen ciphertexts.
Implementation attacks
Target flaws in code or hardware rather than the algorithm.
Side-channel
Power, electromagnetic or acoustic leakage.
Fault injection
Induce errors (voltage, clock, laser) to leak secrets.
Timing
Measure operation time to infer keys. Use constant-time code.
Adversary-in-the-Middle (MITM)
Intercept and relay. Defeated by authenticated key exchange.
Pass the hash
Reuse captured NTLM hashes without cracking them.
Kerberos exploitation
Golden ticket, silver ticket, Kerberoasting, pass the ticket.
Ransomware
Malicious encryption of victim data for extortion, often with data theft.
Zero-day attacks
Exploits for flaws with no available patch. Rely on defense in depth, behavior detection and fast response.
AI threats
Adversarial AI inputs, model poisoning and deepfake attacks used for fraud and impersonation.

3.8 Apply security principles to site and facility design

CPTED Study topic
Crime Prevention Through Environmental Design: natural surveillance, natural access control, territorial reinforcement.
Site selection Study topic
Consider crime, natural hazards, utilities, emergency services and visibility.

3.9 Design site and facility security controls

Wiring closets and IDFs
Lock, monitor and restrict access to intermediate distribution frames.
Server rooms and data centers
Interior location, no windows, access control, monitoring, hot and cold aisles.
Media storage facilities
Controlled environment and access for backup and archive media.
Evidence storage
Secure, logged access to preserve chain of custody.
Restricted and work area security
Badging, mantraps, clean desk, visitor escort.
Utilities and HVAC
Positive pressurization, temperature and humidity control within ASHRAE ranges.
Environmental issues
Natural (flood, earthquake) and human-made (fire, sabotage) threats.
Fire prevention, detection and suppression
Fire classes; wet pipe, dry pipe, pre-action and deluge sprinklers; clean agents. Pre-action suits data centers.
Power
Redundant and backup: UPS, generators, dual feeds. Know blackout, brownout, sag, spike, surge, noise.

3.10 Manage the information system lifecycle

Stakeholder needs and requirements
Capture business and security needs first.
Requirements analysis
Turn needs into verifiable system requirements.
Secure architectural design
Define structure and security architecture.
Development and implementation
Build to design with secure practices.
Integration
Combine components and test interfaces.
Verification and validation
Verification: built right. Validation: built the right thing.
Continuous security review
Reassess security at every stage and after significant change, not only at go-live.
Transition and deployment
Move into production with authorization where required.
Operations and maintenance
Sustain, patch, monitor.
Retirement and secure disposal
Migrate data, sanitize media, update inventory.

Key concepts for Domain 3

Bell-LaPadula versus Biba
BLP protects confidentiality (no read up, no write down). Biba protects integrity and is the inverse (no read down, no write up).
What crypto provides
Symmetric: confidentiality. Hash: integrity. Digital signature: integrity, authenticity, non-repudiation. Asymmetric enables key exchange.
Signing and encrypting keys
Encrypt with the recipient's public key. Sign with your own private key.
Life safety first
People come before assets. Doors may fail open for evacuation even if that lowers security.
TPM versus HSM
A TPM is bound to one device. An HSM is a dedicated, high-assurance key service for many systems.
Post-quantum readiness
Inventory crypto use, build crypto agility, and plan migration to NIST post-quantum standards.

Key terms and acronyms

PoLP
Principle of Least Privilege.
DiD
Defense in Depth.
TCB
Trusted Computing Base.
TPM
Trusted Platform Module.
HSM
Hardware Security Module.
AES
Advanced Encryption Standard (128-bit block; 128, 192, 256-bit keys).
ECC
Elliptic Curve Cryptography.
PQC
Post-Quantum Cryptography.
ML-KEM
Module-Lattice Key Encapsulation Mechanism, FIPS 203.
ML-DSA
Module-Lattice Digital Signature Algorithm, FIPS 204.
PKI
Public Key Infrastructure.
OCSP
Online Certificate Status Protocol.
OT
Operational Technology.
SCADA
Supervisory Control and Data Acquisition.
FaaS
Function as a Service.
SASE
Secure Access Service Edge.
PET
Privacy-Enhancing Technology.
CPTED
Crime Prevention Through Environmental Design.
PUF
Physically Unclonable Function.
MITM
Adversary-in-the-Middle (formerly man-in-the-middle).

Where candidates lose marks

  • Security models
  • Cryptography services, key use and post-quantum
  • Cryptanalytic and AI-enabled attacks
  • Physical and environmental controls
  • Cloud, OT and emerging architectures

Sample practice questions

Q1. Alice wants Bob to know a message came from her and was not altered. What should she do?

  1. Encrypt it with Bob's public key
  2. Sign it with her private key
  3. Encrypt it with her public key
  4. Hash it and send the hash separately
Show answer

B. Sign it with her private key A digital signature uses the sender's private key and gives integrity, authenticity and non-repudiation.

Q2. Which model property prevents a Secret-cleared subject from writing to a Confidential file?

  1. Simple security property
  2. Star (*) property of Bell-LaPadula
  3. Biba simple integrity
  4. Clark-Wilson integrity
Show answer

B. Star (*) property of Bell-LaPadula The BLP star property forbids writing down, which would leak higher classified data.

Practice all Domain 3 questions