Study guide
10.2 Cloud Migration Security Architecture Lab
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
10.2 Cloud Migration Security Architecture Lab
Key Takeaways Explain This Topic AI
Cloud migration governance starts with shared responsibility, asset classification, regulatory scope, and architecture risk.
Security architecture should integrate identity, network segmentation, encryption, logging, resilience, and change control.
A lift-and-shift plan can preserve insecure assumptions from the data center unless architecture review challenges them.
Management should require measurable guardrails before production migration, not rely on post-migration cleanup.
Last updated: May 2026
Migration Scenario: Fast Cloud Adoption Under Regulatory Pressure
A financial services firm wants to move a customer analytics platform from an aging data center to a public cloud provider. The business wants elastic capacity before the holiday season. Legal notes that the platform processes customer identifiers and transaction history. Engineering proposes a fast lift-and-shift using virtual machines, flat network connectivity, and existing administrator accounts. The board asks whether the cloud provider is now responsible for security.
The CISSP response begins with shared responsibility. The provider secures many facilities, hardware, and managed service layers, but the customer remains accountable for its data, identities, configurations, access decisions, logging choices, and governance. The exact split depends on service model. Infrastructure services leave more operating system and network configuration duties with the customer. Managed platform and software services shift some technical work to the provider but do not remove accountability for data protection and access governance.
The first architecture decision is classification and scope. The platform stores sensitive customer data, so the migration must identify data owners, regulatory obligations, retention rules, encryption requirements, cross-border restrictions, backup requirements, and logging needs. If data is not classified before migration, teams may copy it into unsuitable storage, analytics, or test environments. Cloud speed can magnify poor data governance.
The second decision is identity. Cloud consoles, pipelines, workloads, service accounts, administrators, and support roles need least privilege. Existing data center administrator groups should not be copied blindly into broad cloud roles. The organization should use federation, MFA for privileged access, conditional access, just-in-time elevation, separate administrative accounts, and review of cloud IAM policies. Non-human identities need ownership, rotation, and monitoring.
The third decision is network architecture. A flat virtual network that mirrors the old data center may expose management ports, databases, and internal services to unnecessary paths. Better design uses segmentation, private subnets, controlled ingress and egress, security groups, network access control lists where appropriate, private endpoints, routing review, and monitored connectivity to the remaining data center. Micro-segmentation can limit lateral movement, but it must be operationally manageable.
The fourth decision is encryption and key management. Encrypting data at rest is often easy to enable, but the management question is who controls the keys, where keys are stored, how rotation occurs, who can use keys, and how key access is logged. Customer-managed keys may improve control for sensitive workloads, but they add operational responsibility. If keys are lost or access is misconfigured, availability and confidentiality can both suffer.
Architecture area Decision question Manager-level control evidence
Shared responsibility Which controls remain with the firm? Responsibility matrix by service model and system component
Data protection What data is moving and what rules apply? Classification record, retention decision, encryption and DLP plan
IAM Who can administer, deploy, or read data? Role design, MFA enforcement, access review, break-glass procedure
Network Which paths are allowed? Segmentation diagram, ingress and egress rules, connectivity test
Operations Can the system be monitored and recovered? Logging plan, alert runbooks, backup test, incident integration
Logging and monitoring should be designed before production use. Cloud control plane logs, identity logs, storage access logs, network flow logs, application logs, and key usage logs should flow to a monitored environment with retention aligned to investigation and compliance needs. Logs should be protected from alteration by the same administrators being monitored. Alerts should map to runbooks so the security operations team can respond.
Resilience must also be deliberate. Cloud does not automatically make an application highly available. The team must choose regions, availability zones, backup design, recovery point objectives, recovery time objectives, dependency mapping, and failover testing. A single-region deployment may still be appropriate for cost or compliance reasons, but the decision should be explicit. Critical services should have tested recovery procedures, not assumptions based on provider marketing.
Change control changes in cloud because infrastructure can be created through templates, pipelines, and APIs. That is an opportunity. Security guardrails can be embedded in policy-as-code, baseline templates, image standards, configuration scanning, and automated approval gates. It is also a risk because a single pipeline permission can change many resources quickly. Deployment roles should be separated from approval roles, and emergency changes should be logged and reviewed.
Vendor and contract governance remain important. The firm should review provider certifications, data processing terms, support access, breach notification terms, audit rights, subcontractors, data location, service level commitments, and exit assistance. Certifications do not prove the customer's configuration is secure. They are input evidence for third-party risk management and compliance mapping.
Cloud Migration Readiness Checklist
Define the service model and shared responsibility matrix for each major component.
Classify data, approve regions, and document regulatory and retention requirements.
Replace broad administrator inheritance with least privilege cloud roles and MFA.
Design segmentation, private access paths, controlled egress, and monitored management access.
Implement encryption, key ownership, key access logging, and backup protection.
Route cloud logs to security monitoring before production cutover.
Test recovery, incident response, access revocation, and rollback procedures.
Require architecture approval before handling production data.
A CISSP-level cloud decision is not anti-cloud or pro-cloud. It asks whether the new architecture meets business objectives with controls that are understood, owned, tested, and monitored. Migration speed is valuable, but speed without guardrails creates invisible risk. The security leader should help the business move quickly through reusable patterns, not uncontrolled exceptions.