SaaS Security
Change Risk Score for Discovered SaaS Apps
Table of Contents
Change Risk Score for Discovered SaaS Apps
Learn how to customize the risk score in SaaS Security Inline to match your
organization’s independent risk assessment of the SaaS app’s vulnerabilities.
| Where Can I Use This? | What Do I Need? |
|---|---|
|
Or any of the following licenses that include the SaaS Security Inline license:
|
SaaS Security Inline provides risk scoring to help you assess the security posture and
enterprise readiness of a given SaaS app. The risk score is between 1 (low risk) and 5 (high risk) and is based on compliance
attributes. Some SaaS apps might temporarily have no risk score
because the SaaS apps are pending risk assessment by SaaS Security Inline. You
can’t change the risk score of Discovered SaaS apps for which the risk score is
unknown.
When a given SaaS app in the App Dictionary is a known
industry SaaS app but does not yet have a risk score due to pending risk assessment
by SaaS Security Inline, the risk score indicates NA
for score, Under Research in the legend, and
Application Compliance is under research in
Compliance.
There are two ways to change a risk score for SaaS apps:
- Individual (Manual) Risk Score—Manually change the risk score for individual SaaS apps without changing the underlying calculation method.
- Global (Custom) Risk Score—Adjust the weights for the underlying attributes and allow SaaS Security Inline to recalculate and apply the risk score automatically and uniformly across all SaaS apps.
To identify whether you’ve changed a SaaS app’s risk score from its default
assigned by SaaS Security Inline, simply move your cursor over the risk score
to display Default, Manual, or
Custom.
Change Individual Risk Score
SaaS Security Inline enables you to change the default risk score for any SaaS app.
Although the risk score represents attributes that reflect the security posture
of a given SaaS app, your organization might view a specific SaaS app as having
an overall higher or lower security vulnerability due to supplemental
information discovered in the course of your assessment. If you later reevaluate
the SaaS app’s security posture, you can reset to the default risk score or
revise as necessary.
- Log in to Strata Cloud Manager.Select .Select the SaaS app with the risk score you want to change.Select a new risk score. In the Actions column for the selected SaaS app, click the score meter icon to display the risk score scale. Select a new score (1-5).To restore a SaaS app to its default risk score, click Restore to Default.
Change Global Risk Score
By default, SaaS Security Inline assigns unequal weights to the attributes that underlie each SaaS app’s risk score. Key attributes have a higher impact on a SaaS app’s risk score: the risk score is derived by applying different weights to each attribute and calculating the risk score based on whether the SaaS app meets those compliance and security standards.Although the default weights that SaaS Security Inline assigns reflect a concerted effort to balance risks, organizations perceive risk differently. For this reason, SaaS Security Inline enables you to assign your own weight (formula) to each attribute to reflect the attributes that are more important to your organization. SaaS Security Inline recalculates the risk score for all SaaS apps based on the new weights, then displays the updated risk score for each SaaS app and updated dashboard metrics. This process can take up to 2 minutes to complete. For example, if your organization is a healthcare provider, you might want to assign the HIPPA attribute a heavier weightage.- Log in to Strata Cloud Manager.To configure global risk scoring, select .Assign a weight ( 0-100) to each Compliance attribute for a combined total of 100.Assign a weight ( 0-100) to each Security and Privacy attribute for a combined total of 100.Toggle Use Custom Weights, then SaveTo restore the attributes to their default weights and reset all SaaS apps to their default risks scores accordingly, set the toggle to the off position, then Save.
