Watchguard Network Security Practice Test

Which options must be configured in an HTTPS-proxy policy to detect credit card numbers in encrypted HTTP traffic?

1. WebBlocker, Content Inspection

2. Gateway AntiVirus, Data Loss Prevention

3. Content Inspection, Data Loss Prevention

4. Application Control, WebBlocker

The correct answer is: Content Inspection, Data Loss Prevention

To effectively detect credit card numbers in encrypted HTTP traffic using an HTTPS-proxy policy, it's essential to leverage both Content Inspection and Data Loss Prevention features. Content Inspection plays a critical role in examining the content of data packets passing through the proxy, even when that data is encrypted. It allows the system to analyze the payload of HTTPS traffic, which would otherwise be inaccessible. This feature is crucial for identifying patterns or specific data types, such as credit card numbers, that may be present in the encrypted content. Data Loss Prevention (DLP) complements Content Inspection by managing and protecting sensitive information within network traffic. DLP involves establishing rules and policies that govern how sensitive information is handled, monitored, and potentially blocked or alerted upon during transmission. It ensures that any credit card numbers detected by Content Inspection can trigger actions to prevent unauthorized transmission, thus enhancing overall security. While other options include helpful features like WebBlocker and Gateway AntiVirus, they do not specifically target the detection of credit card numbers in encrypted traffic. Application Control focuses more on managing and controlling the use of applications rather than inspecting content for sensitive information.