What must you configure for an HTTPS-proxy policy to detect known viruses in HTTP traffic that is encrypted with TLS?

For an HTTPS-proxy policy to effectively detect known viruses in HTTP traffic that is encrypted with TLS, enabling Content Inspection is essential. Content Inspection allows the firewall to inspect the payload of the HTTPS traffic. This process involves decrypting the data temporarily, scanning it for threats such as viruses, and then re-encrypting it for secure transmission to the intended recipient.

When Content Inspection is enabled, the firewall can analyze the traffic for malicious content, ensuring that threats are detected and mitigated before they can reach end-users. Without this feature, the security appliance would not be able to see the encrypted content, rendering it unable to effectively scan for viruses and other malicious payloads that may be hidden within the encrypted traffic.

Other options, while relevant in a broader security context, do not specifically address the requirement for scanning encrypted HTTPS traffic. For instance, enabling the Intrusion Prevention Service focuses on preventing attacks based on known patterns rather than inspecting the content of encrypted traffic. Adjusting TLS Profile settings pertains to compliance with security protocols rather than malware detection. Enabling Gateway AntiVirus provides scanning for known viruses but also relies on the ability to view the traffic, which is achieved through Content Inspection. Thus, enabling Content Inspection is the vital step needed to successfully detect known viruses