Question 700
Original unofficial Palo Alto Networks NetSec-Architect scenario: A company sanctions a file-sharing service for employees but not for contractors, yet its security rules permit the domain to everyone. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A company sanctions a file-sharing service for employees but not for contractors, yet its security rules permit the domain to everyone. Governing principle: Vendor sanction approval can be user-group-specific rather than organization-wide. The most defensible design response is: Apply identity-aware sanctioned SaaS access rules with distinct contractor restrictions. Validation: An employee can use the approved tenant while a contractor test identity cannot upload documents. Sustained assurance: Review sanctioned application group scope during contractor onboarding
Incorrect Answers
“Retest tenant restrictions as the SaaS provider changes login behavior.” concerns the separate design topic: design saas application sanctioning and activity-level usage controls. It would not fix the described weakness: a company sanctions a file-sharing service for employees but not for contractors, yet its security rules permit the domain to everyone. Vendor sanction approval can be user-group-specific rather than organization-wide.
This alternative is linked to the architecture category: differentiate saas security inline, saas api, sspm and enterprise dlp. The actual problem is that a company sanctions a file-sharing service for employees but not for contractors, yet its security rules permit the domain to everyone; the controlling distinction is: vendor sanction approval can be user-group-specific rather than organization-wide.
The suggested “Reassess classifier accuracy for new data types and language variants.” tests a different architectural concern: architect enterprise dlp classifiers, edm, idm, ocr, ml and policy. Here, a company sanctions a file-sharing service for employees but not for contractors, yet its security rules permit the domain to everyone. Vendor sanction approval can be user-group-specific rather than organization-wide.