Question 410
A FortiOS 7.6 team examines: A compliance review requests a list of narrowly scoped TLS decryption exceptions and their business owners. Select TWO complementary choices: the most appropriate corrective action AND the specific evidence confirming success.
Explanation
Correct Answers
The reported FortiOS 7.6 condition is: A compliance review requests a list of narrowly scoped TLS decryption exceptions and their business owners. The targeted administrative response is: Define precise, documented SSL inspection exceptions for legitimate certificate-pinned or privacy-sensitive applications. The relevant failure risk is: Overly broad exclusions can create uninspected channels; blanket interception can break approved confidential services. Validate with: Approved sensitive flows work under narrow exclusions while ordinary eligible web traffic remains inspected.
For the observed situation (A compliance review requests a list of narrowly scoped TLS decryption exceptions and their business owners), the most specific acceptance evidence is: Approved sensitive flows work under narrow exclusions while ordinary eligible web traffic remains inspected. It validates the recommended response: Define precise, documented SSL inspection exceptions for legitimate certificate-pinned or privacy-sensitive applications. This addresses the documented risk: Overly broad exclusions can create uninspected channels; blanket interception can break approved confidential services.
Incorrect Answers
Web-filter authentication and policy mismatch diagnosis (3.2) would demonstrate or implement: Web-filter and traffic events identify which identity, category and policy produced the blocked or allowed result. The case states: A compliance review requests a list of narrowly scoped TLS decryption exceptions and their business owners. The most direct paired action and test is: Define precise, documented SSL inspection exceptions for legitimate certificate-pinned or privacy-sensitive applications.
Antivirus event investigation and quarantine controls (3.4) addresses another technical failure: Disabling antivirus for a broad source population after one false positive weakens protection without evidence. This case instead tests TLS inspection exceptions and sensitive traffic; the choice measures or changes another part of the system.
Flow versus proxy antivirus scan behavior (3.4) would demonstrate or implement: Using an incompatible inspection path can disable desired scan behavior or cause unnecessary disruption to large transfers. The required paired action and test concerns TLS inspection exceptions and sensitive traffic; a passing result for this alternative could leave that requirement unresolved.