Study guide
6.6 Physical, Logical, Cloud, and Hybrid Access Boundaries
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
6.6 Physical, Logical, Cloud, and Hybrid Access Boundaries
Key Takeaways Explain This Topic AI
Access boundaries exist across buildings, devices, networks, applications, cloud platforms, data stores, and administrative planes.
Physical and logical controls should reinforce each other because a weakness in one layer can defeat strong controls in another.
Cloud and hybrid IAM require clear ownership of identity providers, tenants, roles, trust policies, and third-party access.
Boundary decisions should use least privilege, segmentation, monitoring, and business risk rather than assuming a trusted internal zone.
Last updated: May 2026
Boundaries Are Layered
Access boundaries define where one trust zone ends and another begins. In older designs, the boundary was often described as inside versus outside the network. Modern environments are more complex. Users work remotely, applications run in SaaS and cloud platforms, devices move between networks, partners connect through APIs, and administrators manage resources through web consoles. IAM must treat boundaries as layered and dynamic.
Physical access is still part of IAM. Badges, guards, mantraps, visitor logs, cameras, locks, cages, and secure areas control who can reach facilities and equipment. A person who can enter a data center may bypass logical controls by attaching devices, removing drives, resetting hardware, or accessing consoles. Physical access should follow least privilege just like application access. Not every employee needs a data center badge.
Logical access controls entry to systems, applications, data, network segments, and administrative functions. It includes directories, groups, roles, ACLs, policy engines, certificates, VPNs, device compliance, and application permissions. Logical access should not assume that physical presence or network location equals trust. A laptop on the corporate network can still be compromised, and an employee in an office may still lack a business need for sensitive data.
Cloud access boundaries include tenants, accounts, subscriptions, projects, organizations, virtual networks, security groups, identity roles, resource policies, key management systems, and management planes. The cloud control plane is especially sensitive because it can create systems, change networks, read storage, modify logging, and grant permissions. Administrative cloud access should use strong MFA, separate privileged accounts, least privilege roles, and monitoring.
Hybrid identity connects on-premises directories, cloud identity providers, SaaS applications, endpoint management, and sometimes partner systems. Synchronization can improve usability, but it can also replicate mistakes. A weak on-premises administrator account may become a path into cloud resources. A disabled account may remain active if synchronization fails. A group with legacy broad membership may map to powerful SaaS access.
- Boundary layer Example control IAM concern
- Physical facility Badge, visitor escort, server cage Who can reach equipment and secure areas
- Endpoint Device compliance, certificate, EDR status Whether the device should be trusted for access
- Network Segmentation, VPN, firewall, NAC Which paths are allowed between zones
- Application Roles, entitlements, policy decisions Which functions and data are permitted
- Cloud control plane IAM roles, tenant admin, resource policy Who can administer infrastructure and identity
- Data Classification, encryption, DLP, object ACL Who can view, change, export, or delete data
Zero trust ideas fit this environment because they challenge implicit trust. The practical goal is not a slogan. It is to verify identity and device state, grant least privilege, segment access, assume breach, and continuously monitor. A user on an internal network should not automatically reach every application. A workload in a cloud subnet should not automatically read every storage bucket. A partner API should not automatically inherit employee access.
Network segmentation and IAM work together. Segmentation limits paths, while IAM limits subjects and actions. If a user has permission to administer a database but can connect from any device and any network, the boundary is weak. If a network allows traffic to a database but IAM denies the user, the database remains protected. Defense in depth means these controls support each other rather than relying on one layer.
Physical and logical processes should be coordinated during lifecycle events. When a worker leaves, account disablement is not enough if badges, keys, visitor privileges, remote access devices, and hardware tokens remain active. When a data center technician changes duties, physical access should be reviewed along with system access. When a cloud administrator changes role, console access, API keys, break-glass access, and physical token assignments may all need changes.
Third-party and partner access is a boundary challenge. Vendors may need remote access to support systems, APIs may connect business processes, and contractors may work inside collaboration spaces. These relationships should have sponsors, contracts, access scopes, expiration dates, monitoring, and termination procedures. A vendor account with broad access and no expiration violates both least privilege and lifecycle governance.
Boundary exceptions should be visible. If a legacy system cannot support MFA, document the risk, limit network paths, restrict accounts, monitor use, and set a remediation date. If an emergency access path bypasses normal controls, alert on it and review it. If a cloud workload needs cross-account access, constrain the trust policy and log assumption events. Exception handling is not approval to forget the risk.
Boundary Design Questions
What asset, function, or data is being protected at this boundary?
Which identities, devices, workloads, and partners need access for a defined purpose?
What control proves identity, authorizes action, and records use?
What limits movement if an identity, endpoint, token, or network path is compromised?
How are access changes synchronized when people, roles, systems, or vendors change?
Which logs show boundary crossing, denied attempts, privilege use, and policy changes?
The managerial decision is to align boundary strength with business risk. Public marketing content needs different treatment than regulated records, payment systems, source code, or administrative consoles. The strongest designs avoid assuming a single trusted zone and instead combine physical control, identity assurance, device trust, network limits, application authorization, and monitoring into a coherent access strategy.