Question 740
Original unofficial Palo Alto Networks NetSec-Architect scenario: A global bank deploys DLP to all locations but the same policy blocks innocuous public documents because it lacks business context. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A global bank deploys DLP to all locations but the same policy blocks innocuous public documents because it lacks business context. Governing principle: DLP effectiveness depends on context and policy actions, not classifier matches alone. The most defensible design response is: Design tiered DLP rules using user role, application activity and data class with documented exceptions. Validation: A synthetic high-sensitivity upload is blocked while an approved public file transfer passes. Sustained assurance: Review false positives and exception owners monthly
Incorrect Answers
This alternative is linked to the architecture category: architect enterprise dlp classifiers, edm, idm, ocr, ml and policy. The actual problem is that a global bank deploys DLP to all locations but the same policy blocks innocuous public documents because it lacks business context; the controlling distinction is: DLP effectiveness depends on context and policy actions, not classifier matches alone.
The suggested “Maintain separate test evidence for threat prevention and DLP.” tests a different architectural concern: differentiate saas security inline, saas api, sspm and enterprise dlp. Here, a global bank deploys DLP to all locations but the same policy blocks innocuous public documents because it lacks business context. DLP effectiveness depends on context and policy actions, not classifier matches alone.
The proposed design “Review sanctioned application group scope during contractor onboarding.” addresses this related architecture topic: design saas application sanctioning and activity-level usage controls. The actual security gap is that a global bank deploys DLP to all locations but the same policy blocks innocuous public documents because it lacks business context. DLP effectiveness depends on context and policy actions, not classifier matches alone.