Zero Trust (ZT) security architectureis amodern cloud security approachthat operates on the principle of
"Never Trust, Always Verify."
Primary Benefits of Zero Trust in Cloud:
* Minimizes Attack Surface
* Traditional security modelsassume trust within an internal network.
* Zero Trust eliminates implicit trustand enforcescontinuous verification of user identities.
* Reduces the risk ofdata breaches, insider threats, and lateral movement attacks.
* Strong Authentication & Access Controls
* Multi-Factor Authentication (MFA) & Just-in-Time (JIT) accessare mandatory inZero Trust models.
* Usescontext-based access policies (device, location, behavior analytics)to enforceadaptive security.
* Micro-Segmentation & Least Privilege Access
* Restricts access to only necessary applications, minimizing lateral movement in cloud environments.
* Micro-segmentation isolates workloads, reducing the impact of breaches.
* Cloud-Native Zero Trust Integration
* Cloud providers(AWS, Azure, Google Cloud)offerZero Trust Network Access (ZTNA) solutions.
* Cloud Security Posture Management (CSPM)continuously scans cloud environments for security compliance.
This aligns with:
* CCSK v5 - Security Guidance v4.0, Domain 12 (Identity, Entitlement, and Access Management)
* Zero Trust Cloud Security Architecture (CSA Zero Trust Working Group).

The CCSK v5.0 Study Guide defines cloud computing based on the NIST SP 800-145 definition, which outlines five essential characteristics: on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. Two key capabilities that underpin these characteristics areabstractionand resource pooling.
* Abstractionrefers to the virtualization layer that hides the underlying physical infrastructure, allowing users to interact with resources (e.g., compute, storage, networking) without needing to manage the hardware directly.
* Resource poolingenables the provider's computing resources to be pooled to serve multiple consumers using a multi-tenant model, with resources dynamically assigned and reassigned based on demand.
From theCCSK v5.0 Study Guide, Domain 1 (Cloud Computing Concepts and Architectures), Section
1.2:
"Cloud computing relies on abstraction to simplify the user experience and resource pooling to efficiently allocate resources across multiple tenants. Resource pooling is a defining characteristic, where the provider's computing resources are pooled to serve multiple consumers, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand." Option B correctly identifiesabstraction and resource poolingas the two key capabilities.
* Option A (Abstraction and orchestration) is incorrect because orchestration, while important for automation, is not a defining characteristic of cloud computing.
* Option C (Multi-tenancy and isolation) is incorrect because, while multi-tenancy is a feature of resource pooling, isolation is a security mechanism, not a core capability of cloud computing.
* Option D (Virtualization and multi-tenancy) is incorrect because virtualization is a technology that enables abstraction, but multi-tenancy alone is not sufficient to define cloud computing.
References:
CCSK v5.0 Study Guide, Domain 1, Section 1.2: Cloud Computing Definitions and Characteristics.
NIST SP 800-145: The NIST Definition of Cloud Computing.

Network segmentation isolates sections of the network, limiting the spread of a breach and containing it to a specific segment. Reference: [Security Guidance v5, Domain 7 - Infrastructure & Networking]

Consulting with stakeholders is crucial for ensuring that the cloud security strategy aligns with the overall business objectives and needs. Stakeholders - such as business leaders, IT teams, legal, and compliance officers - bring unique perspectives on what the cloud strategy needs to accomplish, from security to compliance, scalability, and performance. By involving stakeholders, organizations can ensure that the security strategy supports business goals, addresses various concerns, and is comprehensive.
Simplifying the cloud platform selection process is a potential benefit but not the primary reason for consulting stakeholders. Selecting the right cloud platform is part of the broader strategy. Reducing the overall cost of cloud services is not necessarily the outcome of involving stakeholders, although cost considerations may be part of the discussion. Ensuring compliance with technical standards only is too narrow; stakeholders help ensure compliance with both technical and business requirements.