Question 670
Original unofficial Palo Alto Networks NetSec-Architect scenario: A company discovers that confidential spreadsheets were uploaded to an approved cloud drive yesterday, but its inline proxy can only inspect new transactions. Which test result best demonstrates that the design meets its requirement?
Explanation
Correct Answer
Original fictional security architecture situation: A company discovers that confidential spreadsheets were uploaded to an approved cloud drive yesterday, but its inline proxy can only inspect new transactions. Governing principle: At-rest SaaS exposure exists independently of new data-in-motion transactions. The most defensible design response is: Use an appropriate SaaS API at-rest discovery and remediation workflow alongside inline controls for future uploads. Validation: The historical test file is discovered through API assessment and its access is remediated under policy. Sustained assurance: Reconcile API coverage and inline policy incidents weekly
Incorrect Answers
The proposed design “Test access to the alias follows the same sanctioned versus unsanctioned policy as the main domain.” addresses this related architecture topic: differentiate saas security inline, saas api, sspm and enterprise dlp. The actual security gap is that a company discovers that confidential spreadsheets were uploaded to an approved cloud drive yesterday, but its inline proxy can only inspect new transactions. At-rest SaaS exposure exists independently of new data-in-motion transactions.
“The test unknown SaaS app enters review and cannot receive confidential data before approval.” concerns the separate design topic: design saas application sanctioning and activity-level usage controls. It would not fix the described weakness: a company discovers that confidential spreadsheets were uploaded to an approved cloud drive yesterday, but its inline proxy can only inspect new transactions. At-rest SaaS exposure exists independently of new data-in-motion transactions.
This alternative is linked to the architecture category: design saas application sanctioning and activity-level usage controls. The actual problem is that a company discovers that confidential spreadsheets were uploaded to an approved cloud drive yesterday, but its inline proxy can only inspect new transactions; the controlling distinction is: at-rest SaaS exposure exists independently of new data-in-motion transactions.