Collect Bitwarden Enterprise event logs

This document explains how to ingest Bitwarden Enterprise event logs to Google Security Operations using Amazon S3. The parser transforms raw JSON formatted event logs into a structured format conforming to the Chronicle UDM. It extracts relevant fields like user details, IP addresses, and event types, mapping them to corresponding UDM fields for consistent security analysis.

Before you begin

• Google SecOps instance
• Privileged access to Bitwarden tenant
• Privileged access to AWS (S3, IAM, Lambda, EventBridge)

Get Bitwarden API key and URL

1. In the Bitwarden Admin console.
2. Go to Settings > Organization info > View API key.
3. Copy and save the following details to a secure location:
   • Client ID
   • Client Secret
4. Determine your Bitwarden endpoints (based on region):
   • IDENTITY_URL: https://identity.bitwarden.com/connect/token (EU: https://identity.bitwarden.eu/connect/token)
   • API_BASE: https://api.bitwarden.com (EU: https://api.bitwarden.eu)

Configure AWS S3 bucket and IAM for Google SecOps

1. Create Amazon S3 bucket following this user guide: Creating a bucket
2. Save bucket Name and Region for future reference (for example, bitwarden-events).
3. Create a user following this user guide: Creating an IAM user.
4. Select the created User.
5. Select the Security credentials tab.
6. Click Create Access Key in the Access Keys section.
7. Select Third-party service as the Use case.
8. Click Next.
9. Optional: add a description tag.
10. Click Create access key.
11. Click Download CSV file to save the Access Key and Secret Access Key for later use.
12. Click Done.
13. Select the Permissions tab.
14. Click Add permissions in the Permissions policies section.
15. Select Add permissions.
16. Select Attach policies directly
17. Search for and select the AmazonS3FullAccess policy.
18. Click Next.
19. Click Add permissions.

Configure the IAM policy and role for S3 uploads

1. Go to AWS console > IAM > Policies > Create policy > JSON tab.

2. Enter the following policy:

   {
     "Version": "2012-10-17",
     "Statement": [
       {
         "Sid": "AllowPutBitwardenObjects",
         "Effect": "Allow",
         "Action": "s3:PutObject",
         "Resource": "arn:aws:s3:::bitwarden-events/*"
       },
       {
         "Sid": "AllowGetStateObject",
         "Effect": "Allow",
         "Action": "s3:GetObject",
         "Resource": "arn:aws:s3:::bitwarden-events/bitwarden/events/state.json"
       }
     ]
   }
   
   

   • Replace bitwarden-events if you entered a different bucket name.

3. Click Next > Create policy.

4. Go to IAM > Roles > Create role > AWS service > Lambda.

5. Attach the newly created policy.

6. Name the role WriteBitwardenToS3Role and click Create role.

Create the Lambda function

1. In the AWS Console, go to Lambda > Functions > Create function.
2. Click Author from scratch.

3. Provide the following configuration details:

   Setting	Value
   Name	bitwarden_events_to_s3
   Runtime	Python 3.13
   Architecture	x86_64
   Execution role	WriteBitwardenToS3Role

4. After the function is created, open the Code tab, delete the stub and enter the following code (bitwarden_events_to_s3.py):

   #!/usr/bin/env python3
   
   import os, json, time, urllib.parse
   from urllib.request import Request, urlopen
   from urllib.error import HTTPError, URLError
   import boto3
   
   IDENTITY_URL = os.environ.get("IDENTITY_URL", "https://identity.bitwarden.com/connect/token")
   API_BASE = os.environ.get("API_BASE", "https://api.bitwarden.com").rstrip("/")
   CID = os.environ["BW_CLIENT_ID"]          # organization.ClientId
   CSECRET = os.environ["BW_CLIENT_SECRET"]  # organization.ClientSecret
   BUCKET = os.environ["S3_BUCKET"]
   PREFIX = os.environ.get("S3_PREFIX", "bitwarden/events/").strip("/")
   STATE_KEY = os.environ.get("STATE_KEY", "bitwarden/events/state.json")
   MAX_PAGES = int(os.environ.get("MAX_PAGES", "10"))
   
   HEADERS_FORM = {"Content-Type": "application/x-www-form-urlencoded"}
   HEADERS_JSON = {"Accept": "application/json"}
   
   s3 = boto3.client("s3")
   
   def _read_state():
       try:
           obj = s3.get_object(Bucket=BUCKET, Key=STATE_KEY)
           j = json.loads(obj["Body"].read())
           return j.get("continuationToken")
       except Exception:
           return None
   
   def _write_state(token):
       body = json.dumps({"continuationToken": token}).encode("utf-8")
       s3.put_object(Bucket=BUCKET, Key=STATE_KEY, Body=body, ContentType="application/json")
   
   def _http(req: Request, timeout: int = 60, max_retries: int = 5):
       attempt, backoff = 0, 1.0
       while True:
           try:
               with urlopen(req, timeout=timeout) as r:
                   return json.loads(r.read().decode("utf-8"))
           except HTTPError as e:
               # Retry on 429 and 5xx
               if (e.code == 429 or 500 <= e.code <= 599) and attempt < max_retries:
                   time.sleep(backoff); attempt += 1; backoff *= 2; continue
               raise
           except URLError:
               if attempt < max_retries:
                   time.sleep(backoff); attempt += 1; backoff *= 2; continue
               raise
   
   def _get_token():
       body = urllib.parse.urlencode({
           "grant_type": "client_credentials",
           "scope": "api.organization",
           "client_id": CID,
           "client_secret": CSECRET,
       }).encode("utf-8")
       req = Request(IDENTITY_URL, data=body, method="POST", headers=HEADERS_FORM)
       data = _http(req, timeout=30)
       return data["access_token"], int(data.get("expires_in", 3600))
   
   def _fetch_events(bearer: str, cont: str | None):
       params = {}
       if cont:
           params["continuationToken"] = cont
       qs = ("?" + urllib.parse.urlencode(params)) if params else ""
       url = f"{API_BASE}/public/events{qs}"
       req = Request(url, method="GET", headers={"Authorization": f"Bearer {bearer}", **HEADERS_JSON})
       return _http(req, timeout=60)
   
   def _write_page(obj: dict, run_ts_s: int, page_index: int) -> str:
       # Make filename unique per page to avoid overwrites in the same second
       key = f"{PREFIX}/{time.strftime('%Y/%m/%d/%H%M%S', time.gmtime(run_ts_s))}-page{page_index:05d}-bitwarden-events.json"
       s3.put_object(
           Bucket=BUCKET,
           Key=key,
           Body=json.dumps(obj, separators=(",", ":")).encode("utf-8"),
           ContentType="application/json",
       )
       return key
   
   def lambda_handler(event=None, context=None):
       bearer, _ttl = _get_token()
       cont = _read_state()
       run_ts_s = int(time.time())
   
       pages = 0
       written = 0
       while pages < MAX_PAGES:
           data = _fetch_events(bearer, cont)
           # write page
           _write_page(data, run_ts_s, pages)
           pages += 1
   
           # count entries (official shape: {"object":"list","data":[...], "continuationToken": "..."} )
           entries = []
           if isinstance(data.get("data"), list):
               entries = data["data"]
           elif isinstance(data.get("entries"), list):  # fallback if shape differs
               entries = data["entries"]
           written += len(entries)
   
           # next page token (official: "continuationToken")
           next_cont = data.get("continuationToken")
           if next_cont:
               cont = next_cont
               continue
           break
   
       # Save state only if there are more pages to continue in next run
       _write_state(cont if pages >= MAX_PAGES and cont else None)
       return {"ok": True, "pages": pages, "events_estimate": written, "nextContinuationToken": cont}
   
   if __name__ == "__main__":
       print(lambda_handler())
   
   

5. Go to Configuration > Environment variables > Edit > Add new environment variable.

6. Enter the following environment variables, replacing with your values:

   Key	Example
   S3_BUCKET	bitwarden-events
   S3_PREFIX	bitwarden/events/
   STATE_KEY	bitwarden/events/state.json
   BW_CLIENT_ID	<organization client_id>
   BW_CLIENT_SECRET	<organization client_secret>
   IDENTITY_URL	https://identity.bitwarden.com/connect/token (EU: https://identity.bitwarden.eu/connect/token)
   API_BASE	https://api.bitwarden.com (EU: https://api.bitwarden.eu)
   MAX_PAGES	10

7. After the function is created, stay on its page (or open Lambda > Functions > your-function).

8. Select the Configuration tab.

9. In the General configuration panel click Edit.

10. Change Timeout to 5 minutes (300 seconds) and click Save.

Create an EventBridge schedule

1. Go to Amazon EventBridge > Scheduler > Create schedule.
2. Provide the following configuration details:
   • Recurring schedule: Rate (1 hour).
   • Target: your Lambda function.
   • Name: bitwarden-events-1h.
3. Click Create schedule.

Optional: Create read-only IAM user & keys for Google SecOps

1. In the AWS Console, go to IAM > Users, then click Add users.
2. Provide the following configuration details:
   • User: Enter a unique name (for example, secops-reader)
   • Access type: Select Access key - Programmatic access
   • Click Create user.
3. Attach minimal read policy (custom): Users > select secops-reader > Permissions > Add permissions > Attach policies directly > Create policy

4. In the JSON editor, enter the following policy:

   {
     "Version": "2012-10-17",
     "Statement": [
       {
         "Effect": "Allow",
         "Action": ["s3:GetObject"],
         "Resource": "arn:aws:s3:::<your-bucket>/*"
       },
       {
         "Effect": "Allow",
         "Action": ["s3:ListBucket"],
         "Resource": "arn:aws:s3:::<your-bucket>"
       }
     ]
   }
   

5. Set the name to secops-reader-policy.

6. Go to Create policy > search/select > Next > Add permissions.

7. Go to Security credentials > Access keys > Create access key.

8. Download the CSV (these values are entered into the feed).

Configure a feed in Google SecOps to ingest the Bitwarden Enterprise Event Logs

1. Go to SIEM Settings > Feeds.
2. Click + Add New Feed.
3. In the Feed name field, enter a name for the feed (for example, Bitwarden Events).
4. Select Amazon S3 V2 as the Source type.
5. Select Bitwarden events as the Log type.
6. Click Next.
7. Specify values for the following input parameters:
   • S3 URI: s3://bitwarden-events/bitwarden/events/
   • Source deletion options: Select the deletion option according to your preference.
   • Maximum File Age: Default 180 Days.
   • Access Key ID: User access key with access to the S3 bucket.
   • Secret Access Key: User secret key with access to the S3 bucket.
   • Asset namespace: the asset namespace.
   • Ingestion labels: the label applied to the events from this feed.
8. Click Next.
9. Review your new feed configuration in the Finalize screen, and then click Submit.

UDM Mapping Table

Need more help? Get answers from Community members and Google SecOps professionals.