CCZT Reviews Questions

Multifactor authentication is a method of validating the identity of an entity by requiring two or more factors, such as something the entity knows (e.g., password, PIN), something the entity has (e.g., token, smart card), or something the entity is (e.g., biometric, behavioral). Multifactor authentication enhances the security of Zero Trust Architecture (ZTA) by reducing the risk of identity compromise and unauthorized access.

References = Certificate of Competence in Zero Trust (CCZT) - Cloud Security Alliance, Zero Trust Training (ZTT) - Module 4: Identity and Access Management

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​​.

Device validation helps establish a trusted connection based on certificate-based keys in a ZT deployment. Device validation is the process of verifying the identity and posture of the devices that request access to the protected resources. Device validation relies on the use of certificates, which are digital credentials that bind the device identity to a public key. Certificates are issued by a trusted authority and can be used to authenticate the device and encrypt the communication. Device validation helps to ensure that only healthy and compliant devices can access the resources, and that the connection is secure and confidential.

References =

• Certificate of Competence in Zero Trust (CCZT) prepkit, page 15, section 2.2.3
• Zero Trust and Windows device health - Windows Security, section “Device health attestation on Windows”
• Devices and zero trust | Google Cloud Blog, section “In a zero trust environment, every device has to earn trust in order to be granted access.”

In a ZTA, the logical combination of both the policy engine (PE) and policy administrator (PA) is called the policy decision point (PDP). The PE is the component that evaluates the policies and the contextual data collected from various sources and generates an access decision. The PA is the component that establishes or terminates the communication between a subject and a resource based on the access decision. The PDP communicates with the policy enforcement point (PEP), which enforces the access decision on the resource.

References =

• Certificate of Competence in Zero Trust (CCZT) prepkit, page 14, section 2.2.2
• Zero Trust Architecture Project - NIST Computer Security Resource Center, slide 9
• What Is a Zero Trust Security Framework? | Votiro, section “The Policy Engine and Policy Administrator”
• Zero Trust Frameworks Architecture Guide - Cisco, page 4, section “Policy Decision Point”