Question 460
After correcting this architecture issue: A company approves one file-sharing SaaS platform but security blocks all applications in that SaaS category. Which ongoing control belongs in the runbook?
Explanation
Correct Answer
Review allowed app inventory and rule exceptions every quarter. This lowers the risk linked to: SaaS category labels are broader than individual sanction decisions. Verification should show: The approved collaboration service works for permitted files; another file-sharing app is denied.
Incorrect Answers
Audit partner download exceptions and revoke access at contract end. This safeguard addresses another situation: A partner must view an approved contract in a SaaS portal but must not redistribute downloaded copies. It is less directly relevant than the control for: SaaS category labels are broader than individual sanction decisions.
Review discovery reports and new SaaS categorization changes. This safeguard addresses another situation: A newly discovered generative-AI SaaS service is uncategorized but company policy prohibits sending proprietary code there. It is less directly relevant than the control for: SaaS category labels are broader than individual sanction decisions.
Periodically measure precision and recall on redacted representative documents. This safeguard addresses another situation: Sensitive intellectual property has no stable strings and appears as varied narrative descriptions. It is less directly relevant than the control for: SaaS category labels are broader than individual sanction decisions.