What purpose do Data Loss controls serve? (Select all that apply)
The correct answers are A and B. In Zero Trust architecture, Data Loss controls exist to prevent sensitive information from leaving the organization in unauthorized ways. Zscaler's TLS/SSL inspection reference architecture specifically lists Data Loss Prevention (DLP) as a capability that helps prevent sensitive data from leaving the organization. This clearly supports option B, which covers accidental or non-malicious leakage such as unintended sharing, upload mistakes, or improper transfers.
Option A is also correct because data loss controls help detect and stop data theft, including theft carried out by malware or compromised sessions. In Zero Trust, inspection is not limited to who is connecting; it also evaluates what content is moving across the session. That is why encrypted traffic inspection is so important: without it, malicious exfiltration can remain hidden. By contrast, option C describes data integrity and validation functions, which are not the purpose of DLP. Option D refers more to content manipulation or poisoning, which is not the primary function being described by data loss controls in Zscaler's architecture. Therefore, the correct purposes are detecting data theft and preventing accidental leakage.
Identity is a binary decision, not to be revisited. Once a decision is made about who, what, and where, that is final for at least 48 hours.
The correct answer is B. False. Zero Trust architecture does not treat identity and context as a one-time, fixed decision. Zscaler's architecture guidance shows that access is based on ongoing context, including user identity, device posture, location, and other factors that can change over time. For ZIA, policy assignment evaluates the user, device, location, group, and more to determine which policies apply. For ZPA, user access is matched against current conditions such as location, device posture, user group, department, and time of day.
Zscaler documentation also describes reauthentication intervals and session timeout controls, which further shows that identity and authorization are not treated as permanently settled after one decision. In addition, device posture checks can be repeated over time, and a failed posture check can cause a different policy to be applied.
This is fundamental to Zero Trust: trust is continually evaluated, not granted once and assumed valid for an arbitrary period such as 48 hours. Therefore, the statement is false because identity and access context must be revisited as conditions change.
In a Zero Trust architecture, how is the connection to an application provided?
The correct answer is A. Over any network with per-access control. In Zero Trust architecture, access is provided to the specific application, not to the underlying network. This is a foundational design principle in Zscaler's Universal Zero Trust Network Access (ZTNA) guidance. Users can connect from any location and over any network, while policy is enforced per user, per device, per application, and per session. This differs from legacy approaches that first place the user onto the network and then rely on network segmentation or firewall rules to limit access.
Option B is incorrect because establishing a full network-layer connection is characteristic of legacy VPN-based access, which extends network trust and increases lateral movement risk. Option C is also incorrect because Zero Trust is not defined by building a virtual appliance stack in front of applications. Option D includes TLS, which is used in Zscaler architectures, but the key Zero Trust concept being tested is not merely encrypted transport; it is brokered, granular, per-access connectivity without exposing the application to broad network reachability. Therefore, the most accurate answer is A.
Content inspection of encrypted content at scale is widely available on most network-based security platforms, such as firewalls, to deploy.
The correct answer is B. False. In Zero Trust architecture, inspection of encrypted traffic is a major requirement because most internet traffic is now encrypted, and threats frequently hide inside TLS/SSL sessions. However, Zscaler's TLS/SSL inspection reference guidance explains that this type of inspection is not widely available at scale on most traditional network-based security platforms. Conventional security appliances typically experience a major reduction in effective traffic-handling capacity when decryption is enabled, which is one of the main reasons many legacy environments only inspect a limited subset of encrypted traffic.
This limitation is important in Zero Trust because selective inspection creates blind spots. If encrypted traffic is not inspected broadly, malware delivery, command-and-control activity, risky application behavior, and data exfiltration can bypass security controls. Zscaler's architecture is designed to move this function to a cloud-delivered inline security model so inspection can occur more consistently and at scale. Therefore, the statement is false because traditional firewalls and similar appliances have historically struggled to provide encrypted content inspection broadly and efficiently enough for modern Zero Trust needs.
In a Zero Trust architecture, what is required to apply the first levels of control policy decisions?
The correct answer is C. Context and Identity. In Zero Trust architecture, the earliest control decisions cannot be made effectively unless the platform first understands who is making the request and under what conditions that request is happening. That means identity must be verified, and context must be evaluated. Context includes factors such as device posture, location, group membership, application sensitivity, and risk-related conditions. Without those inputs, the architecture cannot determine whether the request should be allowed, restricted, isolated, or blocked.
SSL/TLS inspection is highly important for deeper content-aware controls, but it is not the first requirement for the initial level of control decisions. Local breakout is a traffic-forwarding design choice, not the foundational requirement for policy decision-making. Air-gapping an OT network is a segmentation strategy, but it does not represent the first control layer in Zero Trust. Zero Trust begins with verification and contextual understanding, because policy must be tied to the specific request, not to broad network assumptions. Therefore, the first levels of control policy decisions require context and identity.
Currently there are no comments in this discussion, be the first to comment!