Event Logs

What are event logs?

Event logs are timestamped records of events that occur within your Teams or Enterprise organization. Event logs are accessible to admins and owners from the Manage tab of your organization vault:

Event Logs
Event Logs

Events logs are exportable, accessible from the /events endpoint of the Bitwarden Public API, and are retained indefinitely. Most events capture actions taken in various Bitwarden clients, which push event data to the server every 60 seconds, so you may observe small delays in the reporting of recent events.

Events

Event logs record over 50 different types of events. The event logs screen captures a Timestamp for the event, client app information including application type and IP (accessed by hovering over the globe icon), the User connected to the event, and an Event description.

note

Each Event is associated with type code (1000, 1001, etc.) that identifies the action captured by the event. Type codes are used by the Bitwarden Public API to identify the action documented by an event.

All Event types are listed below, with their corresponding type codes:

User events

  • Logged In. (1000)

  • Changed account password. (1001)

  • Enabled/updated two-step login. (1002)

  • Disabled two-step login. (1003)

  • Recovered account from two-step login. (1004)

  • Login attempted failed with incorrect password. (1005)

  • Login attempt failed with incorrect two-step login. (1006)

  • User exported their individual vault items. (1007)

  • User updated a password issued through Admin Password Reset. (1008)

  • User migrated their decryption key with Key Connector. (1009)

Item events

  • Created item item-identifier. (1100)

  • Edited item item-identifier. (1101)

  • Permanently Deleted item item-identifier. (1102)

  • Created attachment for item item-identifier. (1103)

  • Deleted attachment for item item-identifier. (1104)

  • Shared item item-identifier. (1105)

  • Edited collections for item item-identifier (1106)

  • Viewed item item-identifier. (1107)

  • Viewed password for item item-identifier. (1108)

  • Viewed hidden field for item item-identifier. (1109)

  • Viewed security code for item item-identifier. (1110)

  • Copied password for item item-identifier. (1111)

  • Copied hidden field for item item-identifier. (1112)

  • Copied security code for item item-identifier. (1113)

  • Auto-filled item item-identifier. (1114)

  • Sent item item-identifier to trash. (1115)

  • Restored item item-identifier. (1116)

  • Viewed Card Number for item item-identifier. (1117)

Collection events

  • Created collection collection-identifier. (1300)

  • Edited collection collection-identifier. (1301)

  • Deleted collection collection-identifier. (1302)

Group events

  • Created group group-identifier. (1400)

  • Edited group group-identifier. (1401)

  • Deleted group group-identifier. (1402)

Organization events

  • Invited user user-identifier. (1500)

  • Confirmed user user-identifier. (1501)

  • Edited user user-identifier. (1502)

  • Removed user user-identifier. (1503)

  • Edited groups for user user-identifier. (1504)

  • Unlinked SSO. (1505)

  • user-identifier enrolled in Master Password Reset. (1506)

  • user-identifier withdrew from Master Password Reset. (1507)

  • Master Password was reset for user-identifier. (1508)

  • Reset SSO link for user user-identifier. (1509)

  • user-identifier logged in using SSO for the first time. (1510)

  • Revoked organization access for user-identifier (1511)

  • Restores organization access for user-identifier (1512)

  • Edited organization settings. (1600)

  • Purged organization vault. (1601)

  • Exported organization vault. (1602)

  • Organization Vault access by a managing Provider. (1603)

  • Organization enabled SSO. (1604)

  • Organization disabled SSO. (1605)

  • Organization enabled Key Connector. (1606)

  • Organization disabled Key Connector. (1607)

  • Families Sponsorships synced. (1608)

  • Updated a Policy. (1700)

Provider events

When any of the above events is executed by a member of an administering provider, the User column will record the name of the provider. Additionally, a provider-specific event will record whenever a member of an administering provider accesses your organization vault:

Provider Access Event
Provider Access Event

Export events

Exporting event logs will create a .csv of all events within the specified date range:

Export Event Logs
Export Event Logs

For example:

message,appIcon,appName,userId,userName,userEmail,date,ip,type
Logged in.,fa-globe,Web Vault - Chrome,1234abcd-56de-78ef-91gh-abcdef123456,Alice,alice@bitwarden.com,2021-06-14T14:22:23.331751Z,111.11.111.111,User_LoggedIn
Invited user zyxw9876.,fa-globe,Unknown,1234abcd-56de-78ef-91gh-abcdef123456,Alice,alice@bitwarden.com,2021-06-14T14:14:44.7566667Z,111.11.111.111,OrganizationUser_Invited
Edited organization settings.,fa-globe,Web Vault - Chrome,9876dcba-65ed-87fe-19hg-654321fedcba,Bob,bob@bitwarden.com,2021-06-07T17:57:08.1866667Z,222.22.222.222,Organization_Updated

API responses

Accessing event logs from the /events endpoint of the Bitwarden Public API will return a JSON response such as the following:

{
  "object": "list",
  "data": [
    {
      "object": "event",
      "type": 1000,
      "itemId": "string",
      "collectionId": "string",
      "groupId": "string",
      "policyId": "string",
      "memberId": "string",
      "actingUserId": "string",
      "date": "2020-11-04T15:01:21.698Z",
      "device": 0,
      "ipAddress": "xxx.xx.xxx.x"
    }
  ],
  "continuationToken": "string"
}

SIEM and external systems integrations

When exporting data from Bitwarden into other systems, a combination of data from the exports, API and CLI may be used to gather data. For example, using Bitwarden RESTful APIs to gather data around the structure of the organization:

  • GET /public/members returns the members, ids, and assigned groupids

  • GET /public/groups returns all the groups, ids, assigned collections, and their permissions

  • GET /public/collections returns all collections, and their assigned groups

Once you have the unique id for each member, group, and collection, you can now use the CLI tool to gather information using the CLI command bw-list retrieve the following items in JSON format:

  • Org members

  • Items

  • Collections

  • Groups

After gathering this data, you can join rows on their unique ids to build a reference to all parts of your Bitwarden organization. For more information on using the Bitwarden CLI, see the Bitwarden command-line tool (CLI).


言語
© 2022 Bitwarden, Inc.
利用規約プライバシーポリシーサイトマップ