Skip to main content

Review refused requests and sign-ins

A run of wrong passwords, someone trying a page they have no access to, an API key that keeps being turned away: each is worth a look in a weekly security check, or after someone reports a strange sign-in prompt. Audit's Activity tab keeps every refused request and every refused sign-in, with the reason and the address it came from. To follow one person instead, see Review what a person did.

Who can do this: you need a role that may view audit activity, as org admins can, and your organization's plan must include Audit. Without it, Activity shows Not on your plan: org admins get a See plans link, everyone else reads Ask an admin to change the plan.

Not on your plan: your plan doesn't include audit, with a See plans link

Refused requests​

  1. Select Audit in the sidebar. It opens on the Activity tab, newest action first.
  2. Pick the period you are checking in From and To, such as the last seven days. Times are shown in your own time zone, named under the filters.
  3. In the Search or filter activity box, type 4 and pick Client error (4xx). The list keeps only the requests Jaah refused, and a note says Result filters match web requests only. Views, pipeline events and system records are hidden.
  4. Narrow to one kind if the list is long: replace the chip with 401 Unauthorized (not signed in, or a credential that was not accepted) or 403 Forbidden (signed in, but not allowed). Select × on a chip to remove it.
  5. Read the rows. A refused change reads as what was tried and the code, such as Create task — refused 403. An action taken with an API key shows Key and the key's name before its owner, so a key that keeps being refused stands out.
  6. Select a row to open it in a pane beside the list. The Event tab shows When, the Actor and the Result; for a refused change, also the Browser and the Address the request came from.

Refused sign-ins​

  1. Remove the Result chip: a refused sign-in's own record has no result code, so the filter hides it.
  2. Choose All, so the list shows every action, not only changes.
  3. Look for rows marked Sign-in refused. Each says why, such as Sign-in refused: wrong password, wrong code, too many attempts or address not on the IP allowlist, and names the sign-in method when it was not a password, such as (Google).
  4. Check who it was for. A refusal for an address with no account names no one: it shows Unattributed, dimmed. Many of these in a row from one address are someone guessing; several for one of your people may mean their password is known to someone else.
  5. Select the row and read its Event tab, with the Address and Browser when they were recorded, to see where the attempt came from.
  6. To act on it, tighten who may sign in under Settings' Sign-in or IP allowlist sections: see Settings.

To share what you found, copy the page's address: the filters, and an open event, are part of it.