Question 680
Original unofficial Palo Alto Networks NetSec-Architect scenario: A SaaS administrator enables a risky organization-wide setting in a cloud collaboration product, but no file-specific incident is triggered. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A SaaS administrator enables a risky organization-wide setting in a cloud collaboration product, but no file-specific incident is triggered. Governing principle: SaaS tenant posture includes control-plane settings beyond individual transferred files. The most defensible design response is: Add a SaaS Security Posture Management assessment for tenant configuration, privilege and posture risks. Validation: A purposely misconfigured test setting appears in the SSPM findings with owner and remediation guidance. Sustained assurance: Review configuration drift and privileged SaaS roles regularly
Incorrect Answers
“Reconcile API coverage and inline policy incidents weekly.” concerns the separate design topic: differentiate saas security inline, saas api, sspm and enterprise dlp. It would not fix the described weakness: a SaaS administrator enables a risky organization-wide setting in a cloud collaboration product, but no file-specific incident is triggered. SaaS tenant posture includes control-plane settings beyond individual transferred files.
The suggested “Review SaaS sync policies after endpoint classification changes.” tests a different architectural concern: design saas application sanctioning and activity-level usage controls. Here, a SaaS administrator enables a risky organization-wide setting in a cloud collaboration product, but no file-specific incident is triggered. SaaS tenant posture includes control-plane settings beyond individual transferred files.
The proposed design “Test high-risk SaaS actions after platform feature updates.” addresses this related architecture topic: design saas application sanctioning and activity-level usage controls. The actual security gap is that a SaaS administrator enables a risky organization-wide setting in a cloud collaboration product, but no file-specific incident is triggered. SaaS tenant posture includes control-plane settings beyond individual transferred files.