A customer worried about unknown attacks is hesitant to enable SSL decryption due to privacy and regulatory issues. How does the platform address the customer's concern?

Question

Options

• AIt overcomes reservations about SSL decrypt by offloading to a higher-capacity firewall to help
• BIt shows how AutoFocus can provide visibility into targeted attacks at the industry sector
• CIt allows a list of websites or URL categories to be defined for exclusion from decryption
• DIt bypasses the need to decrypt SSL traffic by analyzing the file while still encrypted

• A
  8% (3)
• B
  3% (1)
• C
  76% (29)
• D
  13% (5)

Explanation

Option C is correct because enterprise security platforms (like Palo Alto Networks) allow administrators to configure decryption exclusion policies - defining specific websites, domains, or URL categories (e.g., banking, healthcare, HR portals) that are explicitly excluded from SSL/TLS inspection. This directly addresses privacy and regulatory concerns (HIPAA, PCI-DSS, attorney-client privilege) by ensuring sensitive traffic is never decrypted, while still enabling decryption for other traffic to catch unknown threats.

Why the distractors are wrong:

• A is wrong because offloading to a higher-capacity firewall doesn't resolve privacy or regulatory concerns - it just shifts the same decryption problem to another device.
• B is wrong because AutoFocus provides threat intelligence about targeted attacks by industry sector, but it doesn't help with the SSL decryption privacy dilemma.
• D is wrong because fully encrypted traffic analysis without decryption is extremely limited - you cannot inspect file contents, payloads, or detect most malware while the traffic remains encrypted. The platform doesn't bypass the need for decryption in this way.

Memory tip: Think of it as a "decryption whitelist in reverse" - instead of choosing what to decrypt, you build an exclusion list of what not to decrypt, giving compliance teams control over sensitive categories while security teams still gain visibility elsewhere.

No community discussion yet for this question.