Applies to: Microsoft Cloud App Security
To view alerts:
In the Microsoft Cloud App Security portal, click on Alerts.
After you look at an alert, if it's not interesting, you can Dismiss it. You can enter a comment to explain why you dismissed the alert and you can Send feedback to the Cloud App Security team. This feedback is reviewed by our security research team to constantly improve the alerting mechanism.
If you investigate the alert and mitigate the risk, you can then Resolve the alert. The alert will no longer show up in the alerts table. If you started investigating an issue but you want to make sure you remember to continue, you can Mark as unread. You can also Adjust the policy that matched the alert in order to imrpove future alert matches. Resolving an alert also gives you the option to enter a comment and Send feedback to the Cloud App Security team.
The following alerts types will be displayed.
|New location||ALERT_GEOLOCATION_NEW_COUNTRY||A new location was detected since the scan began (up to 6 months). This only shows up once for each country for your entire organization.|
|New admin user||ALERT_ADMIN_USER||A new admin was detected for a specific app – this can be someone who is an admin in one application and is now an admin for another application. This alert relates to the specific admin type, so it will show up each time the type of admin changes. If a user lost admin privileges and then got them again, this alert will be displayed.|
|Inactive account||ALERT_ZOMBIE_USER||If a user is inactive for 60 days per application – for example, if someone is active in Box but hasn't touched G Suite for 60 days, the user will be considered inactive in G Suite. A tag is added to these users so you can search for inactive accounts.|
|Unexpected admin location||ALERT_NEW_ADMIN_LOCATION||A new location was detected for administrators since the scan began (up to 6 months). This only shows up once for each country for any admin across your organization.|
|Compromised account||ALERT_COMPROMISED_ACCOUNT||If there was a breach in an application, and the list of breached accounts is published, Cloud App Security downloads the list and compares it to your list of users - including internal users, external users and personal accounts.|
|Suspicious activity alert||ALERT_SUSPICIOUS_ACTIVITY||Suspicious activities are scored according to how suspicious the anomalous activity is (Is there an inactive account involved? Is it from a new location?) These criteria are all calculated together to provide a risk score based on the following risk factors:
User is administrator
Strictly remote user
Entire session is failed logins
Numerous failed login
IP/ISP/country/user-agent for user/tenant
IP/ISP/country/user-agent used only by (admin) user
First (admin) user activity in a while
First time this particular administrative activity is performed in a while
This particular administrative activity is not common / was never performed before
This IP had only failed logins in the past
|Suspicious cloud use alert||ALERT_DISCOVERY_ANOMALY_DETECTION||Cloud Discovery anomaly detection checks the pattern of regular behavior and looks for users or apps that are used in an unusual way.|
|Activity policy violation||ALERT_CABINET_EVENT_MATCH_AUDIT||This alert lets you know when a policy match was detected.|
|File policy violation||ALERT_CABINET_EVENT_MATCH_FILE||This alert lets you know when a policy match was detected.|
|Proxy policy violation||ALERT_CABINET_INLINE_EVENT_MATCH||This alert lets you know when a policy match was detected.|
|Field policy violation||ALERT_CABINET_EVENT_MATCH_OBJECT||This alert lets you know when a policy match was detected.|
|New service discovered||ALERT_CABINET_DISCOVERY_NEW_SERVICE||A new app was discovered.|
|Use of personal account||ALERT_PERSONAL_USER_SAGE||Based on file shares and user names, the detection engine searches for personal accounts.|