How can an engineer use risk score customization in SaaS Security Inline to limit the use of unsanctioned SaaS applications by employees within a Security policy?

Question

Options

• ALower the risk score of sanctioned applications and increase the risk score for unsanctioned
• BIncrease the risk score for all SaaS applications to automatically block unwanted applications.
• CBuild an application filter using unsanctioned SaaS as the category.
• DBuild an application filter using unsanctioned SaaS as the characteristic.

• A
  76% (26)
• B
  3% (1)
• C
  6% (2)
• D
  15% (5)

Explanation

SaaS Security Inline allows engineers to customize the risk scores assigned to different SaaS applications based on various factors. By manipulating these risk scores, you can influence how these applications are treated within Security policies. To limit the use of unsanctioned SaaS applications: Lower the risk score of sanctioned applications: This makes them less likely to trigger policies designed to restrict high-risk activities. Increase the risk score of unsanctioned applications: This elevates their perceived risk, making them more likely to be caught by Security policies configured to block or limit access based on risk score thresholds. Then, you would create Security policies that take action (e.g., block access, restrict features) based on these adjusted risk scores. For example, a policy could be configured to block access to any SaaS application with a risk score above a certain threshold, which would primarily target the unsanctioned applications with their inflated scores.

No community discussion yet for this question.