Study guide
4.2 Control Selection, System Security, and Architecture Risk
CISSP Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CISSP Orientation, CAT, and Official Source Control
1.1 Credential Scope, CISSP Mindset, and Search Language 1.2 Exam Outline Effective Date and Eight-Domain Map 1.3 CAT Format, 100-150 Items, and Forward-Only Rules 1.4 Passing Grade, Results, Feedback, and Retake Policy 1.5 Experience, Endorsement, and Associate of ISC2 Path 1.6 Pricing, AMF, CPE, and Maintenance Overview
2 Chapter 2: Security and Risk Management
2.1 Professional Ethics, CIA, and Security Governance 2.2 Policies, Standards, Procedures, Guidelines, and Control Ownership 2.3 Legal, Regulatory, Privacy, and Investigation Context 2.4 Risk Identification, Analysis, Treatment, and Reporting 2.5 Business Continuity, BIA, and Recovery Prioritization 2.6 Personnel Security, Training, Awareness, and Culture 2.7 Threat Modeling, Supply Chain Risk, and Third-Party Governance 2.8 Security and Risk Management Case Lab
3 Chapter 3: Asset Security and Data Lifecycle
3.1 Asset and Data Classification, Ownership, and Roles 3.2 Handling Requirements, Labeling, Privacy, and Cross-Border Data 3.3 Data States and Protection Methods: DLP, DRM, and CASB 3.4 Data Lifecycle, Retention, Remanence, and Destruction 3.5 Secure Provisioning, Inventory, and Asset Management 3.6 Asset Security Case Lab
4 Chapter 4: Security Architecture, Engineering, and Cryptography
4.1 Secure Design Principles and Security Models 4.2 Control Selection, System Security, and Architecture Risk 4.3 Cryptography Foundations: Symmetric, Asymmetric, Hashing, and PKI 4.4 Cryptographic Lifecycle, Key Management, and Attack Patterns 4.5 Cloud, Container, IoT, Edge, and Shared Responsibility Architecture 4.6 Physical Site, Facility, and Environmental Security 4.7 Information System Lifecycle Engineering and Retirement 4.8 Architecture and Engineering Case Lab
5 Chapter 5: Communication, Network Security, and Zero Trust
5.1 Network Architecture, OSI/TCP/IP, and Secure Design 5.2 Secure Protocols, Encryption in Transit, and Channel Protection 5.3 Segmentation, Microsegmentation, SDN, VPC, and Zero Trust 5.4 Wireless, Cellular, Remote Access, and Third-Party Connectivity 5.5 Network Components: NAC, IDS/IPS, Firewalls, and Endpoints 5.6 Monitoring, Observability, Capacity, and Resilient Communications 5.7 Communication and Network Security Case Lab
6 Chapter 6: Identity and Access Management
6.1 Identity Proofing, Authentication, Authorization, and Accountability 6.2 Access Control Models: RBAC, MAC, DAC, ABAC, and Risk-Based Access 6.3 Federation, SSO, MFA, Passwordless, and Session Management 6.4 Provisioning, Deprovisioning, JML, and Access Reviews 6.5 Service Accounts, Non-Human Identities, and Privilege Management 6.6 Physical, Logical, Cloud, and Hybrid Access Boundaries 6.7 IAM Case Lab
7 Chapter 7: Security Assessment, Testing, and Audit Strategy
7.1 Assessment, Test, and Audit Strategy Selection 7.2 Control Testing, Vulnerability Assessment, and Penetration Testing 7.3 Log Review, Code Review, Misuse Cases, and Compliance Checks 7.4 Security Process Data, KPIs, KRIs, and Reporting 7.5 Remediation, Exceptions, Risk Acceptance, and Evidence Quality 7.6 Security Assessment and Testing Case Lab
8 Chapter 8: Security Operations, Incident Response, and Resilience
8.1 Investigations, Evidence, Forensics, and Legal Readiness 8.2 Logging, Monitoring, SOC, and Alert Triage 8.3 Configuration, Change, Patch, and Vulnerability Operations 8.4 Incident Management, Containment, Eradication, and Recovery 8.5 Disaster Recovery, Backup, Availability, and Resilience 8.6 Physical Security Operations and Safety 8.7 Security Operations Case Lab
9 Chapter 9: Software Development Security and DevSecOps
9.1 Secure SDLC Governance and Requirements 9.2 Architecture, Threat Modeling, and Design Review 9.3 Secure Coding, Code Review, and Application Testing 9.4 CI/CD, Source Control, and Environment Separation 9.5 Software Supply Chain, Third-Party Components, and Deployment 9.6 DevSecOps Vulnerability Management and Release Risk 9.7 Software Development Security Case Lab
10 Chapter 10: Integrated CISSP Governance Scenario Labs
10.1 Enterprise Risk Committee Decision Lab 10.2 Cloud Migration Security Architecture Lab 10.3 Ransomware Incident and Business Continuity Lab 10.4 Identity Modernization and Zero Trust Lab 10.5 Third-Party Breach and Contract Governance Lab 10.6 Secure SDLC Transformation Lab 10.7 Full CISSP Manager Simulation
11 Chapter 11: Final Review, Endorsement, CPE, and Test-Day Strategy
11.1 Final 45-Day CISSP Study Plan 11.2 CAT Timing and Forward-Only Decision Workflow 11.3 Mixed-Domain Remediation and Manager Mindset Review 11.4 Test-Day Checklist and Pearson VUE Readiness 11.5 Endorsement, Associate Path, and Work Experience Documentation 11.6 CPE, AMF, and Three-Year Maintenance Plan 11.7 CISSP Final Mixed Review
4.2 Control Selection, System Security, and Architecture Risk
Key Takeaways Explain This Topic AI
Control selection should begin with business impact, threat likelihood, legal obligations, and architecture constraints.
System security capabilities include isolation, trusted paths, secure boot, memory protection, logging, configuration control, and recovery.
Architecture risk often appears in dependencies, inherited trust, management planes, integration patterns, and lifecycle gaps.
The best control set is defensible, measurable, affordable to operate, and tied to explicit residual risk acceptance.
Last updated: May 2026
Selecting Controls for Real Systems
Control selection is not a shopping exercise. It is a risk management decision that connects assets, threats, vulnerabilities, business impact, compliance duties, operating capability, and cost. A CISSP-level architect should be able to explain why a control belongs in the design, what risk remains, and how the control will be maintained.
Start with the mission of the system. A public marketing site, a hospital medication platform, a trading system, and an industrial controller do not need the same control emphasis. Confidentiality, integrity, availability, privacy, safety, and nonrepudiation compete differently in each environment, and the selected controls should reflect that context.
Controls can be administrative, technical, or physical. Administrative controls include policy, standards, training, vendor requirements, risk acceptance, and change management. Technical controls include access enforcement, encryption, endpoint hardening, network segmentation, vulnerability scanning, and logging. Physical controls include locks, guards, barriers, surveillance, fire suppression, and environmental protections.
Controls also have functional types. Preventive controls try to stop an event, detective controls identify events, corrective controls restore desired conditions, deterrent controls discourage behavior, recovery controls restore service, and compensating controls provide alternate risk reduction when the preferred control is not feasible. Mature designs combine these types instead of relying on one layer.
- Risk driver Control question Example control response
- High business impact What must not fail silently? Strong monitoring, alerting, tested recovery
- Privileged access Who can change trust decisions? PAM, approval workflow, session logging
- Sensitive data Where is data exposed or transformed? Encryption, tokenization, DLP, access review
- Legacy dependency What cannot be fixed directly? Segmentation, allow lists, virtual patching
- Third-party connection What trust is inherited? Contract clauses, federation limits, monitoring
System security capabilities are the built-in properties that make controls reliable. Secure boot helps ensure trusted firmware and boot components. Hardware roots of trust, TPMs, measured boot, and attestation can support stronger assurance, especially for endpoints, servers, and cloud workloads that must prove their state before receiving access.
Memory protection, process isolation, address space layout randomization, and execution prevention reduce the impact of coding errors and exploitation attempts. These are not substitutes for secure development, but they provide resilience. Security leaders should ask whether high-value workloads run on platforms with modern hardening enabled and monitored.
Trusted paths matter when users or administrators perform sensitive actions. A login prompt, privilege elevation process, or management console must be distinguishable from an imitation. Phishing-resistant authentication, signed administrative tools, hardened jump hosts, and protected management networks all support the idea that critical commands occur through trustworthy channels.
Reference monitors are conceptual enforcement points that mediate access between subjects and objects. For practical architecture, the key properties are always invoked, tamper resistant, and small enough to verify. Modern examples include kernel access checks, hypervisor controls, identity policy engines, API gateways, and storage access policies.
Architecture risk appears where diagrams become too optimistic. A single identity provider may become a systemic failure point. A shared CI/CD runner may become a path into production. A cloud management account may bypass network segmentation. A logging pipeline may collect sensitive data that creates a new privacy and breach exposure.
Risk also appears in inherited trust. If a SaaS platform, managed service, container image, open source library, certificate authority, DNS provider, or outsourced support team is trusted by the architecture, that trust must be deliberate. Contracts, assurance reports, configuration baselines, monitoring, and exit plans help manage what the organization does not directly control.
Use this architecture risk register pattern during design review:
Item Risk statement Primary control Residual risk owner
Management plane Compromise could bypass application controls MFA, PAM, network restrictions, logging Platform owner
Build pipeline Malicious build could reach production Signed commits, protected branches, artifact signing Engineering leader
Shared database Tenant data could be exposed by query defect Row controls, test coverage, monitoring Product owner
Legacy service Unsupported OS may be exploited Isolation, virtual patching, replacement plan Business sponsor
Good control selection includes verification. A design that says encryption is required should identify approved algorithms, key ownership, rotation expectations, exception handling, and where plaintext exists. A design that says logging is required should specify event types, retention, time synchronization, access controls, alerting rules, and privacy constraints.
Compensating controls deserve careful treatment. They are valid when the primary control is infeasible, but they should be documented with scope, rationale, monitoring, expiration, and approval. A compensating control that becomes permanent without review is often a hidden acceptance of risk.
CISSP judgment favors proportionality. Overcontrolling a low-risk system can waste resources and create shadow IT. Undercontrolling a mission-critical system can create unacceptable loss exposure. The security architect should guide stakeholders toward a balanced design that is defensible to auditors, executives, engineers, and operations teams.