Question 520
An emergency change is proposed for: A company permits trusted SaaS traffic but receives malware in downloaded archives that bypass the current allowed policy's inspection. Which caution is most important for this specific change?
Explanation
Correct Answer
The most relevant caution is that allowing SaaS traffic should not be mistaken for authorizing every payload carried by the application. The case concerns a company permits trusted SaaS traffic but receives malware in downloaded archives that bypass the current allowed policy's inspection. The safer path is to check antivirus profile settings, file types, SSL inspection eligibility, and security profile application and then, after verification, to enable the supported antivirus scanning profile on eligible allowed sessions with appropriate TLS inspection. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
A broad category action should not be assumed to satisfy every application-specific exception. The check concerns a broad category action should not be assumed to satisfy every application-specific exception, not confirming that allowing SaaS traffic should not be mistaken for authorizing every payload carried by the application.
Observing a DLP detection in a log is not the same as enforcing an upload block. This assesses observing a DLP detection in a log is not the same as enforcing an upload block; it does not determine the reported condition—a company permits trusted SaaS traffic but receives malware in downloaded archives that bypass the current allowed policy's inspection.
A broad SSL inspection bypass undermines content controls that need decrypted payload visibility. The case-specific requirement is confirming that allowing SaaS traffic should not be mistaken for authorizing every payload carried by the application, which that option does not establish.