Action Center: Task Types
Overview
There are four types of tasks in the User Risk Action Center. Each comes from a different risk signal and carries a different action.
|
Task type |
Created when |
Action required |
|
Set usage policy |
An app is in use with no explicit usage policy of its own. |
Set a usage policy for the app. |
|
Revoke tokens |
Nudge or Block leaves users holding active OAuth tokens. |
Revoke tokens for the app in question. |
|
Reset passwords |
An identity breach exposed passwords or other credentials. |
Trigger a password reset for affected users, prompting them to set a new password when they next log in. |
|
Review identity breach |
An identity breach affected people in your organization, but exposed no password or credential. |
Notify users, informing them of what happened. |
Set usage policy
Every app in use without an explicit policy of its own generates a Set usage policy task.
- What it shows: Who is using the app, what permissions they granted it, and the security rating of the vendor behind it.
- How it resolves: Click Set usage policy and pick Approve, Tolerate, Nudge or Block.
|
Usage policies |
Outcome |
Follow-up |
|
Approve |
Resolved. The app is sanctioned for business use. |
None. Any open Revoke tokens task for this app is cancelled, because its tokens no longer need revoking. |
|
Tolerate |
Resolved. Accessible, but not endorsed. |
None. Any open Revoke tokens task for this app is cancelled. |
|
Nudge |
Resolved. Users are warned away from the app. |
A Revoke tokens task, if the app has at least one active OAuth token. |
|
Block |
Resolved. Users are prevented from reaching the app. |
A Revoke tokens task, if the app has at least one active OAuth token. |
For what each policy means and what your users experience under it, see User Risk: App Usage Policies.
Revoke tokens
Blocking or nudging an app stops people using it, but doesn’t invalidate the OAuth tokens they’ve already granted. Those tokens stay valid until someone revokes them in the directory; this work is tracked as a Revoke tokens task.
- What it shows: Each user still holding an active token, their team, how old the token is, how many scopes it covers, what those scopes grant, and whether the token has been revoked.
- How it resolves: If you use a Risk Automations workflow to revoke the tokens automatically, the task resolves itself as soon as the workflow finishes. If you revoke the tokens yourself in the directory instead, the next scan will close the task.
Reset passwords
A Reset passwords task is created when there is an identity breach involving your users is and it exposed at least one of passwords, authentication tokens, historical passwords or biometric data.
- What it shows: Which data types were exposed, when the breach happened and when it was disclosed, and each of your users caught in it.
- How it resolves: If you use a Risk Automations workflow to reset affected users’ passwords, the task resolves itself as soon as the workflow finishes. If you reset the passwords yourself in your directory instead, you’ll need to manually close the task with Mark as resolved and an optional note.
Review identity breach
A Review identity breach task is created when an identity breach affects people in your organization but exposes no passwords or credentials. There’s nothing to reset, so the work is telling the affected users what happened and what to watch for.
- What it shows: A description of the breach including when it happened, when it was disclosed, and which of your users were caught in it.
- How it resolves: With a Risk Automations workflow, you can choose who to contact and how, edit the message and send it. Once nobody in the breach is left to notify, the task resolves itself. Without Risk Automations, you’ll need to manually inform your users and then select Mark as resolved.