Collect Duo entity context logs

This document explains how to ingest Duo entity context data to Google Security Operations using Amazon S3. The parser transforms the JSON logs into a unified data model (UDM) by first extracting fields from the raw JSON, then mapping those fields to UDM attributes. It handles various data scenarios, including user and asset information, software details, and security labels, ensuring comprehensive representation within the UDM schema.

Before you begin

• Google SecOps instance
• Privileged access to Duo tenant (Admin API application)
• Privileged access to AWS (S3, IAM, Lambda, EventBridge)

Configure Duo Admin API application

1. Sign in to Duo Admin Panel.
2. Go to Applications > Application Catalog.
3. Add Admin API application.
4. Record the following values:
   • Integration key (ikey)
   • Secret key (skey)
   • API hostname (for example, api-XXXXXXXX.duosecurity.com)
5. In Permissions, enable Grant resource – Read (to read users, groups, devices/endpoints).
6. Save the application.

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, duo-context).
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": "AllowPutDuoObjects",
         "Effect": "Allow",
         "Action": "s3:PutObject",
         "Resource": "arn:aws:s3:::duo-context/*"
       }
     ]
   }
   

   • Replace duo-context 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 WriteDuoToS3Role 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	duo_entity_context_to_s3
   Runtime	Python 3.13
   Architecture	x86_64
   Execution role	WriteDuoToS3Role

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

   #!/usr/bin/env python3
   
   import os, json, time, hmac, hashlib, base64, email.utils, urllib.parse
   from urllib.request import Request, urlopen
   import boto3
   
   # Env
   DUO_IKEY = os.environ["DUO_IKEY"]
   DUO_SKEY = os.environ["DUO_SKEY"]
   DUO_API_HOSTNAME = os.environ["DUO_API_HOSTNAME"].strip()
   S3_BUCKET = os.environ["S3_BUCKET"]
   S3_PREFIX = os.environ.get("S3_PREFIX", "duo/context/")
   # Default set can be adjusted via ENV
   RESOURCES = [r.strip() for r in os.environ.get(
       "RESOURCES",
       "users,groups,phones,endpoints,tokens,webauthncredentials,desktop_authenticators"
   ).split(",") if r.strip()]
   # Duo paging: default 100; max 500 for these endpoints
   LIMIT = int(os.environ.get("LIMIT", "500"))
   
   s3 = boto3.client("s3")
   
   def _canon_params(params: dict) -> str:
       """RFC3986 encoding with '~' unescaped, keys sorted lexicographically."""
       if not params:
           return ""
       parts = []
       for k in sorted(params.keys()):
           v = params[k]
           if v is None:
               continue
           ks = urllib.parse.quote(str(k), safe="~")
           vs = urllib.parse.quote(str(v), safe="~")
           parts.append(f"{ks}={vs}")
       return "&".join(parts)
   
   def _sign(method: str, host: str, path: str, params: dict) -> dict:
       """Construct Duo Admin API Authorization + Date headers (HMAC-SHA1)."""
       now = email.utils.formatdate()
       canon = "\n".join([now, method.upper(), host.lower(), path, _canon_params(params)])
       sig = hmac.new(DUO_SKEY.encode("utf-8"), canon.encode("utf-8"), hashlib.sha1).hexdigest()
       auth = base64.b64encode(f"{DUO_IKEY}:{sig}".encode("utf-8")).decode("utf-8")
       return {"Date": now, "Authorization": f"Basic {auth}"}
   
   def _call(method: str, path: str, params: dict) -> dict:
       host = DUO_API_HOSTNAME
       assert host.startswith("api-") and host.endswith(".duosecurity.com"), \
           "DUO_API_HOSTNAME must be e.g. api-XXXXXXXX.duosecurity.com"
       qs = _canon_params(params)
       url = f"https://{host}{path}" + (f"?{qs}" if method.upper() == "GET" and qs else "")
       req = Request(url, method=method.upper())
       for k, v in _sign(method, host, path, params).items():
           req.add_header(k, v)
       with urlopen(req, timeout=60) as r:
           return json.loads(r.read().decode("utf-8"))
   
   def _write_json(obj: dict, when: float, resource: str, page: int) -> str:
       prefix = S3_PREFIX.strip("/") + "/" if S3_PREFIX else ""
       key = f"{prefix}{time.strftime('%Y/%m/%d', time.gmtime(when))}/duo-{resource}-{page:05d}.json"
       s3.put_object(Bucket=S3_BUCKET, Key=key, Body=json.dumps(obj, separators=(",", ":")).encode("utf-8"))
       return key
   
   def _fetch_resource(resource: str) -> dict:
       """Fetch all pages for a list endpoint using limit/offset + metadata.next_offset."""
       path = f"/admin/v1/{resource}"
       offset = 0
       page = 0
       now = time.time()
       total_items = 0
   
       while True:
           params = {"limit": LIMIT, "offset": offset}
           data = _call("GET", path, params)
           _write_json(data, now, resource, page)
           page += 1
   
           resp = data.get("response")
           # most endpoints return a list; if not a list, count as 1 object page
           if isinstance(resp, list):
               total_items += len(resp)
           elif resp is not None:
               total_items += 1
   
           meta = data.get("metadata") or {}
           next_offset = meta.get("next_offset")
           if next_offset is None:
               break
   
           # Duo returns next_offset as int
           try:
               offset = int(next_offset)
           except Exception:
               break
   
       return {"resource": resource, "pages": page, "objects": total_items}
   
   def lambda_handler(event=None, context=None):
       results = []
       for res in RESOURCES:
           results.append(_fetch_resource(res))
       return {"ok": True, "results": results}
   
   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	duo-context
   S3_PREFIX	duo/context/
   DUO_IKEY	DIXYZ...
   DUO_SKEY	****************
   DUO_API_HOSTNAME	api-XXXXXXXX.duosecurity.com
   LIMIT	200
   RESOURCES	users,groups,phones,endpoints,tokens,webauthncredentials

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: duo-entity-context-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 Duo Entity Context data

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, Duo Entity Context).
4. Select Amazon S3 V2 as the Source type.
5. Select Duo Entity context data as the Log type.
6. Click Next.
7. Specify values for the following input parameters:
   • S3 URI: s3://duo-context/duo/context/
   • 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.