Malware Protection inside HTTPS connections is performed using which parts of the Zero Trust Exchange?

Malware hidden inside HTTPS can only be evaluated after the encrypted session is inspected. ZIA's proxy architecture uses TLS Inspection to decrypt the flow, then malware protection engines compare content, signatures, and reputation indicators against known risks before the session is re-encrypted or blocked. Option C (TLS Inspection decrypting traffic to compare signatures for known risks) is correct because TLS inspection is the enabling layer for malware scanning inside encrypted web traffic.

Why the other options are incorrect:

A. Deception creating decoy files for malware to discover: Deception uses decoys, fake credentials, lures, and traps to expose intruders who are exploring the environment.

B. Application Segmentation of users to specific private applications: An Application Segment defines private app reachability by FQDN/IP, ports, and related settings.

D. Data Loss Protection comparing saved filenames for known risks: Comparing saved filenames is weak and easy to evade. Malware scanning inside HTTPS requires TLS inspection so the file content can actually be evaluated.