The core tenet of Zero Trust is that no entity-internal or external-should be trusted by default. Every request for access must be authenticated, authorized, and encrypted based on granular access policies and continuous validation of identity, device health, location, and behavior.
ZT eliminates reliance on traditional network perimeter models (which B and A describe), focusing instead on microsegmentation and dynamic policy enforcement to prevent lateral movement within a network.
This approach is detailed in Domain 7: Infrastructure Security of the CCSK guidance. It emphasizes identity-aware access control, continuous monitoring, and contextual risk assessment as foundational elements of a secure Zero Trust framework.
Reference:
CSA Security Guidance v4.0 - Domain 7: Infrastructure Security

The shared security responsibility model in cloud environments clarifies that CSPs and CSCs both have roles, with specific responsibilities varying based on the service model (IaaS, PaaS, SaaS). In IaaS, CSCs handle more security, while CSPs manage most security in SaaS. Reference: [CCSK Study Guide, Domain 1 - Cloud Security Scope and Responsibilities][16source].

In a cloud environment, orchestration automates the provisioning and management of various cloud resources, including virtual machines (VMs), networking, storage, and other infrastructure components. Cloud orchestration involves the use of software to coordinate and automate tasks that would otherwise require manual intervention, improving efficiency, scalability, and consistency across the environment.
Monitoring application performance is typically handled by monitoring tools, not orchestration. Manual configuration of security policies is something that can be automated through policy management but is not the focus of orchestration. Installation of operating systems is part of provisioning resources, but orchestration primarily focuses on automating the overall management of infrastructure and services, not just the installation of operating systems.

Load balancing is a key resilience strategy in both traditional and cloud environments. It evenly distributes network or application traffic across multiple servers to ensure no single server becomes a point of failure or overloaded, thereby improving system availability, performance, and fault tolerance.
In cloud infrastructure, load balancers may work at various OSI layers (Layer 4 or Layer 7) and are often integrated into cloud platforms as managed services (e.g., AWS Elastic Load Balancer or Azure Load Balancer). They play a critical role in mitigating risks like traffic spikes, system failure, or regional outages.
This technique is described in Domain 7: Infrastructure Security of the CCSK guidance, which highlights tools like load balancing, redundant systems, and failover mechanisms to support cloud resilience and availability.
Reference:
CSA Security Guidance v4.0 - Domain 7: Infrastructure Security