Study guide
4.5 Cloud, Container, IoT, Edge, and Shared Responsibility Architecture
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.5 Cloud, Container, IoT, Edge, and Shared Responsibility Architecture
Key Takeaways Explain This Topic AI
Shared responsibility must be translated into concrete control ownership for each service model and provider capability.
Cloud architecture risk often concentrates in identity, management planes, storage exposure, network paths, logging gaps, and automation permissions.
Containers and orchestrators require image provenance, runtime isolation, secret management, admission control, and cluster governance.
IoT and edge systems expand physical exposure, update challenges, safety impact, constrained resources, and long lifecycle risk.
Last updated: May 2026
Architecture When Infrastructure Is Distributed
Cloud, container, IoT, and edge architectures change who operates components, but they do not remove accountability for risk. The organization still owns data classification, access decisions, legal obligations, vendor governance, incident response expectations, and residual risk. A shared platform can be secure only when responsibilities are explicit.
Shared responsibility depends on the service model. In infrastructure as a service, the provider manages facilities, hardware, and core virtualization while the customer usually manages operating systems, applications, identities, data, and many network controls. In platform as a service, the provider manages more of the runtime. In software as a service, the customer still manages data use, identities, configuration, monitoring, and contractual risk.
Do not rely on generic shared responsibility diagrams alone. Translate them into a control responsibility matrix for the actual services in use. Storage encryption, backup retention, key ownership, logging, vulnerability management, endpoint access, administrator roles, data residency, and incident notification may vary by service and contract.
- Area Provider may handle Customer usually still owns
- Physical facility Data center access, power, cooling Due diligence and provider assurance review
- Identity Platform IAM features Role design, MFA, federation, access review
- Data Storage services and encryption options Classification, key choices, retention, sharing
- Network Backbone and service endpoints Segmentation, exposure, routing, private access
- Logging Log generation features Collection, alerting, retention, investigation use
- Resilience Regional services and availability zones Architecture, recovery objectives, testing
Cloud architecture risk often starts with identity. Overprivileged roles, long-lived access keys, broad service principals, weak federation settings, and unmanaged break-glass accounts can defeat otherwise strong controls. Cloud security architecture should favor least privilege, short-lived credentials, conditional access, separation of duties, and monitoring of administrative actions.
The management plane is a critical trust boundary. It can create networks, disable security controls, read snapshots, change keys, and alter logging. Treat it like production infrastructure, not a convenience console. Require strong authentication, privileged access governance, change control, alerting, and restrictions on where administrative actions can originate.
Storage exposure is another common failure mode. Public object storage, overly broad bucket policies, permissive snapshots, unmanaged sharing links, and weak data lifecycle rules can expose sensitive information. Encryption helps, but access policy, inventory, data classification, monitoring, and deletion rules determine whether storage is truly governed.
Containers introduce a different set of assumptions. A container image packages application dependencies, but it is not a full security boundary by itself. Host kernel sharing, privileged containers, mounted secrets, weak runtime profiles, and vulnerable base images can increase risk. Container security requires controls from build through runtime.
A container control baseline should include trusted base images, image scanning, signed images, minimal packages, non-root execution, read-only filesystems where practical, network policies, secrets outside images, admission control, runtime monitoring, and controlled access to the orchestrator API. The orchestrator is a high-value management plane and deserves strong protection.
Kubernetes and similar platforms require governance. Namespaces do not automatically create hard multitenancy. Role-based access, admission policies, pod security settings, network policy, secret management, audit logging, and cluster upgrade practices determine whether workload isolation is credible. For highly sensitive workloads, dedicated clusters or stronger isolation may be justified.
IoT and edge environments add physical and lifecycle concerns. Devices may be deployed in public, industrial, clinical, retail, or remote locations where attackers can touch hardware. They may have constrained CPU, memory, storage, and battery capacity, limiting traditional endpoint controls. They may also remain in service for years after vendors stop providing updates.
For IoT, secure architecture includes device identity, secure boot, signed firmware, update mechanisms, encrypted communication, least privilege service accounts, network segmentation, telemetry monitoring, and decommissioning procedures. Safety impact matters. A compromised sensor is different from a compromised actuator that can affect people, equipment, or critical operations.
Edge computing pushes processing closer to data sources. This can reduce latency and bandwidth, but it distributes sensitive computation across many sites. Architects should consider local data minimization, tamper resistance, offline behavior, central policy management, secure synchronization, and procedures for lost or replaced devices.
Use this shared responsibility review workflow:
Inventory the service, data, identities, regions, integrations, and administrators.
Map each control to provider, customer, or shared ownership.
Identify inherited trust, management plane privileges, and default configurations.
Define logging, monitoring, incident notification, and evidence retention.
Test misconfiguration, credential loss, service outage, and recovery scenarios.
Record residual risks, exceptions, and business owners.
The managerial goal is clarity. Cloud and edge failures often happen when everyone assumes someone else owns the control. A defensible architecture states who configures it, who monitors it, who pays for it, who approves exceptions, and who acts when it fails.