Which options must you configure in an HTTPS-proxy policy to detect credit card numbers in SSL encrypted HTTP traffic?

To effectively detect credit card numbers in SSL encrypted HTTP traffic, configuring deep inspection of HTTPS content is essential. This capability allows the proxy to decrypt the HTTPS traffic and inspect the data for specific patterns, such as those that match credit card numbers.

Using deep inspection, the WatchGuard Firebox can analyze the content of the traffic after it has been decrypted, applying various security measures to identify sensitive information. This functionality is crucial in environments where financial transactions occur over encrypted channels, ensuring that any sensitive data is monitored and protected.

While other features may enhance the security posture, they do not directly relate to the ability to inspect encrypted content for specific data patterns like credit card numbers. For instance, WebBlocker is primarily for filtering unwanted web content, and Application Control focuses on managing application usage, but neither addresses the specific need for inspecting HTTPS-encrypted data. Data Loss Prevention is designed to prevent data leaks but also does not inherently provide the capability to inspect encrypted traffic without the deep inspection feature. Thus, deep inspection stands out as the necessary configuration to achieve the goal of detecting credit card numbers in SSL encrypted HTTP traffic.