Learn how to identify and remediate risky apps on SaaS
SaaS Security Inline provides tools to help
you identify risky SaaS applications and users, including analytics,
risk scores, and reports. After you identify your organization’s
risks, you have the following solutions to increase your security
submit SaaS security policy rule recommendations to address the
risks. However, before you do so, consider some guidelines.
your list of users that are using discovered SaaS apps, not all
of those uses are risky. You’ll need to observe the users in the
context of the risky SaaS apps and overall application usage (MB).
For example, if you find 100 users using WeTransfer but only a few
people are uploading large amounts of data, those users are likely
risky users and require more scrutiny.
Filter on SaaS
apps with a risk score of 8,9, or 10.
Do one of the following:
Click on the individual SaaS apps.
Click on the number of users for the SaaS apps.
Sort the column by
Identify Risky SaaS Applications
A risk score in SaaS Security
Inline enables you to make decisions about security posture of a
given app. The risk score is between 1 (low risk) and 10 (high risk)
and is based on compliance attributes.
Key attributes have a higher impact on the score: the score is assigned
by applying different weights to each compliance attribute and calculating
the score based on whether the application meets those compliance
bar graph, click on
link to display those SaaS applications
with the highest risk.
score for each
SaaS application in the
High Risk — Very likely to be a risk
Med Risk — Moderate risk
Low Risk — Very unlikely to be a risk
Expand the Application Detail for
the SaaS application to assess the risk characteristics (compliance
attributes) that contribute to this risk score.