Skip to content
ISC2 CISSP · CISSP

CISSP Domain 3: Security Architecture and Engineering

Domain 3.0: Security Architecture and Engineering · 13% of the exam

The engineering domain: all 10 objectives (3.1–3.10), from the eleven secure design principles and the formal security models through system security capabilities, the vulnerabilities of fifteen architecture types, cryptographic selection and cryptanalytic attack, site and facility design, and the information system lifecycle objective added in 2024.

10 modules · 45 topics 160-page PDF 100 practice questions
Read a free sample By the author of 51 Pluralsight courses · 4.6/5 from 2,007 ratings
Best value
$29/ month

All study guides, current and every new one.

or own the whole exam
$129one-time · all 8 domains
or just this guide
$24.95one-time · lifetime access
  • Interactive online guide
  • Downloadable PDF
  • Lifetime updates
  • 30-day money-back guarantee

Secure checkout via Stripe · no account needed · instant access

13% of your exam score

Domain 3.0 is worth 13% of the CISSP exam. Walk in having mastered it, not hoping it doesn't come up.

Every objective, nothing extra

Built line by line from the official ISC2 CISSP objectives 3.1–3.10: 45 in-depth topics with worked scenarios and exam tips, in a 160-page guide you'll actually finish.

100 exam-style questions

Every question comes with instant feedback and a full explanation, so a wrong answer teaches you as much as a right one.

The cert that changes what you're paid

CISSP is the management-track credential for security: five years of experience to hold it, eight domains wide, and the one most senior security job descriptions name by itself.

Serving, transitioning, or a military spouse?

CISSP appears in the DoD 8140 qualification matrix. See how it maps to work roles, which credentialing program your branch runs, and what it will and will not pay for. Read the DoD 8140 guide →

Read a real excerpt, free

This is the actual opening of Module 3.1, Secure design principles, not marketing copy. If you like how it teaches, the rest of the guide reads the same way.

Objective 3.1

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

The eleven named principles, what each looks like when genuinely applied, and the discriminations the exam tests — including fail secure against fail safe.

Wei Zhang, Aurora's principal security architect, kept a single slide for design reviews. It listed eleven principles and one question: which of these does this design rely on, and which does it violate? The slide existed because architecture arguments otherwise become taste, and because almost every serious design failure he had seen in twenty years was a named principle that had been assumed rather than implemented.

The classic seven

PrincipleMeaningApplied correctly
Threat modelingSystematic design-time analysis of what can go wrong, per objective 1.10.A model produced during architecture, revisited on significant change, whose output is requirements and test cases.
Least privilegeEvery subject gets only the access it needs, only for as long as it needs it.Just-in-time elevation, scoped service accounts, no standing domain administrator.
Defence in depthIndependent layers of different control types, so one failure is not total failure.Network control, host control, application control and monitoring, none of which shares a single point of failure.
Secure defaultsThe state a system arrives in is the safe state; security is opt-out, not opt-in.Encryption on by default, sharing off by default, no default credentials, ports closed unless declared.
Fail securelyWhen something breaks, the result denies rather than permits.An authorization service outage denies access; a certificate validation error rejects the connection.
Segregation of dutiesNo individual controls an entire sensitive process end to end.The person who writes the payment file cannot approve it; the developer cannot deploy to production unreviewed.
Keep it simple and smallComplexity defeats assurance. Minimise the trusted computing base and the attack surface.Fewer components, fewer privileged paths, fewer exceptions — a design you can hold in your head is a design you can verify.
Exam focus · Fail secure is not fail safe

Fail secure protects the asset: on failure, the door locks, access is denied, the transaction is refused. Fail safe protects people: on failure, the door unlocks so occupants can escape. They point in opposite directions and both are correct in their own context. Life safety wins in a fire — always — and the compensating control is a guard, an alarm or a monitored egress, not a locked door.

The four added in 2024

PrincipleWhat it actually requires
Zero Trust / trust but verifyNo implicit trust from network location. Every request is authenticated, authorized and encrypted, evaluated against device state, identity, and context, continuously rather than once at a perimeter. Micro-segmentation and a policy decision point are the structural expressions of it.
Privacy by designPrivacy considered at design time and enforced by default: minimise collection, limit purpose, keep data only as long as needed, make the privacy-protective option the default, and build in subject rights rather than servicing them manually.
Shared responsibilityIn cloud, the provider is responsible of the cloud and the customer in it, and the boundary moves with the service model. Misplacing it is the single most common cloud security failure.
Secure access service edge (SASE)Convergence of network and security functions — SD-WAN, secure web gateway, CASB, zero trust network access, firewall as a service — delivered from a distributed cloud edge close to the user, rather than backhauling traffic to a data centre to be inspected.
The guide continues for 160 pagesKeep reading: unlock the full guide

Not ready to buy? Read it later.

We'll email you a free sample of this guide as a PDF, no purchase needed.

Try 3 sample questions

Pulled straight from the guide's 100-question bank. Tap an answer for instant feedback and the explanation.

From module 3.1 · Secure design principles

  1. 1. A magnetic door lock releases when the building fire alarm activates. Which principle governs this behaviour?

From module 3.2 · Security models

  1. 1. Which rule is the Bell-LaPadula star property?

From module 3.3 · Selecting controls to requirements

  1. 1. What does an Evaluation Assurance Level indicate?

97 more questions like these are waiting inside.

What's inside

  • 45 in-depth topics across 10 modules, mapped to objectives 3.1–3.10
  • 100 exam-style practice questions with instant feedback
  • Full answer key explaining why every distractor is wrong
  • Bell-LaPadula and Biba, with the memory aid that resolves every property question
  • Objective 3.10, new in 2024 and omitted by most study material
  • Complete CISSP acronym & key-term reference
  • 160-page downloadable PDF for offline study and printing
  • Lifetime updates as the exam evolves

The modules, mapped to the objectives

  1. 3.1

    Secure design principles

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

    10 Qs
    Least privilege & need to knowSecure defaults & fail securelyKeep it simple; minimise the TCBZero Trust & trust but verifyPrivacy by designShared responsibility & SASE
  2. 3.2

    Security models

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

    10 Qs
    Bell-LaPadula: no read up, no write downBiba: no read down, no write upClark-Wilson & the access tripleBrewer-Nash (Chinese Wall)Reference monitor & security kernelLattice, state machine & non-interference
  3. 3.3

    Selecting controls to requirements

    Select controls based upon systems security requirements

    10 Qs
    Common Criteria (ISO/IEC 15408)Protection profile vs. security targetTarget of evaluationEAL1–EAL7 and what they measureCertification vs. accreditationRequirements-driven selection
  4. 3.4

    Security capabilities of systems

    Understand security capabilities of Information Systems (IS) (e.g., memory protection, Trusted Platform Module (TPM), encryption/decryption)

    10 Qs
    Process isolation, DEP & ASLRProtection rings & the TCBTPM, PCRs & sealingSecure boot vs. measured bootTEEs & secure enclavesHSMs & key custody
  5. 3.5

    Architecture vulnerabilities

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

    10 Qs
    Client & server-side weaknessesDatabase inference, aggregation & polyinstantiationICS/OT priorities & segmentationContainers, microservices & serverlessIoT & embedded lifetimesVirtualisation & hypervisor escape
  6. 3.6

    Cryptographic solutions

    Select and determine cryptographic solutions

    10 Qs
    Symmetric vs. asymmetric selectionHashing, HMAC & digital signaturesModes of operation & AES-GCMElliptic curve & post-quantumPerfect forward secrecyPKI, CAs, CRL & OCSP
  7. 3.7

    Cryptanalytic attacks

    Understand methods of cryptanalytic attacks

    10 Qs
    Ciphertext-only, known & chosen plaintextFrequency analysis & brute forceSide-channel, timing & fault injectionMan-in-the-middlePass the hashKerberos exploitation & ransomware
  8. 3.8

    Site & facility design principles

    Apply security principles to site and facility design

    10 Qs
    CPTED: surveillance, access control, territorialitySite selection criteriaLayered defensible spaceDeter, delay, detect, respondVisibility & anonymity of facilitiesNatural disaster exposure
  9. 3.9

    Facility security controls

    Design site and facility security controls

    10 Qs
    Wiring closets, data centres, evidence storageFire classes & suppression agentsSprinkler types & pre-actionPower: sag, surge, fault, blackoutUPS & generator strategyHVAC, positive pressure & humidity
  10. 3.10

    Information system lifecycle

    Manage the information system lifecycle

    10 Qs
    Stakeholder needs & requirementsArchitectural designVerification vs. validationTransition & authorizationOperations, drift & sustainmentRetirement & disposal
Chris Rees

About the author

Chris Rees

Professional information technologist with 25+ years in IT and the author of 51 certification training courses, 50+ live on Pluralsight, rated 4.6/5 across more than 2,000 reviews. This guide is that same exam-focused teaching, in a format you can finish.

More about Chris
All 8 CISSP domains

Sitting the whole exam? Get the Complete CISSP Collection.

Every domain of the exam, including this guide, for $129, one time.

See everything inside

Questions, answered

Do I need an account to buy?

No. Checkout is a single Stripe form: email and card, about 30 seconds. We create your access from your checkout email automatically and sign you in the moment payment completes.

Is this up to date with the real CISSP exam?

Yes. The guide is mapped module-by-module to the official ISC2 CISSP objectives (3.1–3.10), and lifetime updates are included, so as the exam evolves your guide does too.

What exactly do I get?

Instant access to the interactive online guide with all 100 practice questions, plus a 160-page PDF you can download, print, and keep forever.

Do I need the other domains too?

This guide covers Domain 3.0 (13% of the exam). To prepare for the whole exam, the Complete CISSP Collection bundles all 8 domains for $129, less than the price of three guides.

What if it isn't for me?

Every purchase comes with a 30-day money-back guarantee. Email us and we'll refund you, no hoops.

Who wrote it?

Chris Rees, a professional information technologist with 25+ years in IT and the author of 51 certification courses published on Pluralsight, rated 4.6/5 across 2,007 ratings.

Be ready for 13% of the exam, for $24.95

Instant access, lifetime updates, and a 30-day money-back guarantee. The only risk is walking into the exam without it.

Get the guide

Share this guide