NSK101 · Question #83
You want to see the actual data that caused the policy violation within a DLP Incident view. In this scenario, which profile must be set up?
The correct answer is B. Forensics Profile. DLP Incident View: To see the actual data that caused a policy violation within a DLP incident, detailed logging and data capture are required. Forensics Profile: A Forensics Profile in Netskope is designed to capture and store detailed information about policy violations…
Question
You want to see the actual data that caused the policy violation within a DLP Incident view. In this scenario, which profile must be set up?
Options
- AQuarantine Profile
- BForensics Profile
- CLegal Hold Profile
- Da GDPR DLP Profile
How the community answered
(31 responses)- A6% (2)
- B84% (26)
- C3% (1)
- D6% (2)
Explanation
DLP Incident View: To see the actual data that caused a policy violation within a DLP incident, detailed logging and data capture are required. Forensics Profile: A Forensics Profile in Netskope is designed to capture and store detailed information about policy violations, including the actual data that triggered the incident. It provides a comprehensive view of the incident for investigation and compliance purposes. Navigate to the DLP settings in the Netskope admin console. Configure a Forensics Profile to capture detailed logs and data for policy violations. Ensure that this profile is associated with the relevant DLP policies.
Topics
Community Discussion
No community discussion yet for this question.