Skip to main content

Audit log and sessions

An auditor asks who changed that role in March. Or you are in the middle of an incident and want to know whether a key was refused overnight. Both questions need a record nobody could have tidied up afterwards.

That is the audit log. It records changes to members, groups, roles, keys, security and settings, and every request that was refused. Entries cannot be edited or deleted.

Read the audit log​

You need audit:read, which Administrator, Security admin and Auditor hold.

  1. Open Settings › Security, then Audit log.
  2. Search by action, person or target.
  3. Filter by Outcome to see ok or denied, or by Actor to separate users, service accounts and API keys.

Each entry shows who acted, what they did, the target and the outcome, along with a request id.

Export it​

You need audit:export. Choose Export CSV and Dwaar downloads a CSV of the entries that match your search and outcome filter.

Start with the refusals​

Filter to denied first. A burst of refused requests from one service account usually means a pipeline lost a permission, and it may mean something is probing. Either way, you want to know before anyone reports it.

The request id connects this log to what a caller saw, because every API error carries one too. See Troubleshooting.

Sign-ins and sessions​

Settings › Security, under Sign-in & sessions, shows active sessions and recent sign-ins. You see your own, and users with the right access see everyone's in the tenant.

To revoke a session, choose Revoke. That device is signed out immediately and must sign in again. You cannot revoke the session you are using. Sign out instead.

Authentication settings​

You need security:update.

SettingWhat it does
Session timeoutIdle sessions are signed out after this long: 1, 4 or 12 hours, or 1 or 7 days. The default is 1 day.
Require two-factor authenticationRecords your requirement.
Enforce SSORecords your requirement.
Important

Treat Require two-factor authentication and Enforce SSO as records of intent for now. The console stores them, but enforcement belongs to the identity provider and is not connected yet. Confirm your sign-in rules with Dwaar before you tell an auditor these controls are in force.

Try this next​

Export the last month of the log and search it for your own name. Check that every change you remember is there. Then filter the console to denied, and look for anything you cannot explain.