CCZT Questions and Answers

ZTA is based on the principle of never trusting any user or device by default, regardless of their location or ownership. ZTA policies can use various methods to verify the identity and context of third-party users and devices, such as tokens, certificates, multifactor authentication, device posture assessment, etc. ZTA policies can also enforce granular and dynamic access policies that grant the minimum necessary privileges to third-party users and devices for accessing specific resources, while hiding all other assets from their view. This reduces the attack surface and prevents unauthorized access and lateral movement within the network.

SDP mitigates the risk of broken access control by mandating micro-segmentation and implementing least privilege. Micro-segmentation divides the network into smaller, isolated segments that can prevent unauthorized access and contain lateral movement. Least privilege grants the minimum necessary access to users and devices for specific resources, while hiding all other assets from their view. This reduces the attack surface and prevents attackers from exploiting weak or misconfigured access controls

One of the core principles of Zero Trust (ZT) is to “never trust, always verify” every request for access to a resource, regardless of where it originates or what resource it accesses1. This means that ZT does not rely on implicit trust based on network perimeters, device types, or user roles, but rather on explicit verification based on multiple data points, such as user identity, device health, location, service, data classification, and anomalies1.

References =

• Zero Trust Architecture | NIST
• Zero Trust Model - Modern Security Architecture | Microsoft Security
• How To Implement Zero Trust: 5-steps Approach & its challenges - Fortinet

Business continuity and disaster recovery are the activities of the ZT implementation preparation phase that ensure the resiliency of the organization’s operations in the event of disruption. Business continuity refers to the process of maintaining or restoring the essential functions of the organization during and after a crisis, such as a natural disaster, a cyberattack, or a pandemic. Disaster recovery refers to the process of recovering the IT systems, data, and infrastructure that support the business continuity. ZT implementation requires planning and testing the business continuity and disaster recovery strategies and procedures, as well as aligning them with the ZT policies and controls.

References =

• Zero Trust Planning - Cloud Security Alliance, section “Monitor & Measure”
• Zero Trust architecture: a paradigm shift in cybersecurity - PwC, section “Continuous monitoring and improvement”
• Zero Trust Implementation, section “Outline Zero Trust Architecture (ZTA) implementation steps”

During the gap analysis phase of Zero Trust (ZT) planning, risk appetite is typically defined when determining the target state. This step involves setting the desired security goals and objectives, taking into account the organization's tolerance for risk. Defining the risk appetite helps in aligning the ZT initiatives with the organization's broader risk management strategy, ensuring that the security measures are both effective and aligned with business objectives​​.

The rule-based security policies configured on the Policy Decision Point (PDP) are designed to define rules that specify how information can flow within an organization's network. These rules are integral to implementing the principle of least privilege and ensuring that data is accessed only by authorized entities under strict conditions. By controlling information flow, the PDP helps in mitigating the risk of data breaches and unauthorized access, reinforcing the Zero Trust model's emphasis on stringent access control and continuous verification of trust.

ZTA models in terms of access decisions are based on the principle of “never trust, always verify”, which means that each access request is handled just-in-time by the policy decision points. The policy decision points are the components in a ZTA that evaluate the policies and the contextual data collected from various sources, such as the user identity, the device posture, the network location, the resource attributes, and the environmental factors, and then generate an access decision. The access decision is communicated to the policy enforcement points, which enforce the decision on the resource. This way, ZTA models apply a consistent access model throughout the environment for all assets, regardless of their location, type, or ownership.

References =

• Certificate of Competence in Zero Trust (CCZT) prepkit, page 14, section 2.2.2
• What Is Zero Trust Architecture (ZTA)? - F5, section “Policy Engine”
• Zero trust security model - Wikipedia, section “What Is Zero Trust Architecture?”
• Zero Trust Maturity Model | CISA, section “Zero trust security model”

ZTA uses micro-segmentation to divide the network into smaller, isolated segments that can prevent unauthorized access and contain lateral movement. ZTA also uses encryption to protect data in transit and at rest from eavesdropping and tampering.

In a Zero Trust Architecture, the Policy Decision Point (PDP) is the primary entity responsible for crafting and maintaining policies, especially those that enforce the principle of least privilege for network access. The PDP evaluates all relevant information about an access request—including the identity of the requester, the context of the request, and the requested resource—and makes a decision on whether to grant or deny access based on predefined policies. This process ensures that access rights are strictly aligned with the necessity of the role and the minimum access required to perform a function, thereby adhering to the principle of least privilege​​.

In a ZTA, policies should be created in the control plane, which is the logical component that defines and manages the policies for accessing resources. The control plane consists of policy entities, such as policy administrators, policy engines, and policy decision points, that are responsible for crafting, maintaining, evaluating, and enforcing the policies1. The control plane interacts with the data plane, which is the logical component that handles the data transmission and processing, and the network, which is the physical or virtual component that provides the connectivity and transport for the data plane1. The endpoint is the device or system that requests or provides access to a resource1.

References =

• Zero Trust Architecture | NIST

A common activity in the scope, priority, and business case steps of ZT planning is to determine the organization’s current state. This involves assessing the existing security posture, architecture, policies, processes, and capabilities of the organization, as well as identifying the key stakeholders, business drivers, and goals for the ZT initiative. Determining the current state helps to establish a baseline, identify gaps and risks, and define the scope and priority of the ZT transformation.

References =

• Zero Trust Planning - Cloud Security Alliance, section “Scope, Priority, & Business Case”
• The Zero Trust Journey: 4 Phases of Implementation - SEI Blog, section “First Phase: Prepare”

Micro-segmentation is a vital ZTA component that enhances network security and simplifies management by creating boundaries between resources in the same network zone. Micro-segmentation divides the network into smaller segments or zones based on the attributes and context of the resources, such as data sensitivity, application functionality, user roles, etc. Micro-segmentation helps to isolate and protect the resources from unauthorized access and lateral movement of attackers within the same network zone.

References = Certificate of Competence in Zero Trust (CCZT) - Cloud Security Alliance, Zero Trust Training (ZTT) - Module 6: Micro-segmentation

The ZT tenet of assume breach is based on the notion that malicious actors reside inside and outside the network, and that any user, device, or service can be compromised at any time. Therefore, ZT requires continuous verification and validation of all entities and transactions, and does not rely on implicit trust or perimeter-based defenses