Collect Slack audit logs

Supported in:

Google secops SIEM

Note: This feature is covered by Pre-GA Offerings Terms of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the Google SecOps Technical Support Service guidelines and the Google SecOps Service Specific Terms.

This document explains how to ingest Slack Audit Logs to Google Security Operations using either Google Cloud Run functions or Amazon S3 with AWS Lambda.

Before you begin

Make sure you have the following prerequisites:

• A Google SecOps instance
• Slack Enterprise Grid plan with Organization Owner or Admin access
• Privileged access to either:
  • Google Cloud (for Option 1: Cloud Run functions and Cloud Scheduler)
  • AWS (for Option 2: S3, IAM, Lambda, EventBridge)

Note: The Slack Audit Logs API is only available for Enterprise Grid organizations. Standard Slack workspaces cannot access this API.

Collect Slack Audit Logs prerequisites (App ID, OAuth Token, Organization ID)

The Slack Audit Logs API requires a User OAuth Token with the auditlogs:read scope. This token must be obtained by installing an app at the Enterprise Grid organization level, not at the workspace level.

Create Slack app for Audit Logs

1. Sign in to the Slack Admin Console with an Enterprise Grid Organization Owner or Admin account.
2. Go to https://api.slack.com/apps and click Create New App > From scratch.
3. Provide the following configuration details:
   • App Name: Enter a descriptive name (for example, Google SecOps Audit Integration).
   • Pick a workspace to develop your app in: Select your Development Slack Workspace (any workspace in the organization).
4. Click Create App.

Configure OAuth scopes

1. Navigate to OAuth & Permissions in the left sidebar.
2. Go to the Scopes section.
3. Under User Token Scopes (NOT Bot Token Scopes), click Add an OAuth Scope.
4. Add the scope: auditlogs:read.

Note: If you encounter installation issues in later steps, you may need to add a basic bot scope (such as users:read) to enable organization-level installation.

Enable public distribution

1. Navigate to Manage Distribution in the left sidebar.
2. Under Share Your App with Other Workspaces, ensure all four sections have green checkmarks:
   • Remove Hard Coded Information
   • Activate Public Distribution
   • Set a Redirect URL
   • Add an OAuth Scope
3. Click Activate Public Distribution.

Note: Public Distribution is required for organization-level apps.

Install app to Enterprise Grid organization

1. Navigate to OAuth & Permissions in the left sidebar.
2. Click Install to Organization (NOT "Install to Workspace").

CRITICAL: Check the drop-down in the upper right of the installation screen to verify you are installing to the Enterprise organization, not an individual workspace.

1. Review the permissions requested and click Allow.
2. After authorization completes, you will be redirected back to the OAuth & Permissions page.

Retrieve credentials

1. Under OAuth Tokens for Your Workspace, locate the User OAuth Token.

2. Copy and securely save the token that starts with xoxp- (for example, xoxp-1234567890-0987654321-1234567890-abc123def456).

   Important: This is your SLACK_ADMIN_TOKEN for the Lambda function or Cloud Run function. Store it securely.

3. Note your Organization ID:

   • Go to the Slack Admin Console.
   • Navigate to Settings & Permissions > Organization settings.
   • Copy the Organization ID.

Option 1: Configure Slack Audit Logs export using Google Cloud Run functions

This option uses Google Cloud Run functions and Cloud Scheduler to collect Slack Audit Logs and ingest them directly into Google SecOps.

Setting up the directory

1. Create a new directory on your local machine for the Cloud Run function deployment.
2. Download the following files from the Chronicle ingestion-scripts GitHub repository:
   • From the slack folder, download:
     • .env.yml
     • main.py
     • requirements.txt
   • From the root of the repository, download the entire common directory with all its files:
     • common/__init__.py
     • common/auth.py
     • common/env_constants.py
     • common/ingest.py
     • common/status.py
     • common/utils.py
3. Place all downloaded files into your deployment directory.

• Your directory structure should look like this:

  deployment_directory/
  ├─common/
  │ ├─__init__.py
  │ ├─auth.py
  │ ├─env_constants.py
  │ ├─ingest.py
  │ ├─status.py
  │ └─utils.py
  ├─.env.yml
  ├─main.py
  └─requirements.txt
  

Create secrets in Google Secret Manager

1. In the Google Cloud Console, go to Security > Secret Manager.
2. Click Create Secret.
3. Provide the following configuration details for the Chronicle service account:
   • Name: Enter chronicle-service-account.
   • Secret value: Paste the contents of your Google SecOps ingestion authentication JSON file.
4. Click Create secret.
5. Copy the secret resource name in the format: projects/<PROJECT_ID>/secrets/chronicle-service-account/versions/latest.
6. Click Create Secret again to create a second secret.
7. Provide the following configuration details for the Slack token:
   • Name: Enter slack-admin-token.
   • Secret value: Paste your Slack User OAuth Token (starting with xoxp-).
8. Click Create secret.
9. Copy the secret resource name in the format: projects/<PROJECT_ID>/secrets/slack-admin-token/versions/latest.

Setting the required runtime environment variables

1. Open the .env.yml file in your deployment directory.

2. Configure the environment variables with your values:

   CHRONICLE_CUSTOMER_ID: "<your-chronicle-customer-id>"
   CHRONICLE_REGION: us
   CHRONICLE_SERVICE_ACCOUNT: "projects/<PROJECT_ID>/secrets/chronicle-service-account/versions/latest"
   CHRONICLE_NAMESPACE: ""
   POLL_INTERVAL: "5"
   SLACK_ADMIN_TOKEN: "projects/<PROJECT_ID>/secrets/slack-admin-token/versions/latest"
   

   • Replace the following:
     • <your-chronicle-customer-id>: Your Google SecOps customer ID.
     • <PROJECT_ID>: Your Google Cloud project ID.
     • CHRONICLE_REGION: Set to your Google SecOps region. Valid values: us, asia-northeast1, asia-south1, asia-southeast1, australia-southeast1, europe, europe-west2, europe-west3, europe-west6, europe-west9, europe-west12, me-central1, me-central2, me-west1, northamerica-northeast2, southamerica-east1.
     • POLL_INTERVAL: Frequency interval (in minutes) at which the function executes. This duration must be the same as the Cloud Scheduler job interval.

3. Save the .env.yml file.

Deploying the Cloud Run function

1. Open a terminal or Cloud Shell in the Google Cloud console.

2. Navigate to your deployment directory:

   cd /path/to/deployment_directory
   

3. Execute the following command to deploy the Cloud Run function:

   gcloud functions deploy slack-audit-to-chronicle \
     --entry-point main \
     --trigger-http \
     --runtime python39 \
     --env-vars-file .env.yml \
     --timeout 300s \
     --memory 512MB \
     --service-account <SERVICE_ACCOUNT_EMAIL>
   

   • Replace <SERVICE_ACCOUNT_EMAIL> with the email address of the service account you want your Cloud Run function to use.

     Note: The service account running your Cloud Run function must have the Cloud Functions Invoker (roles/cloudfunctions.invoker) and Secret Manager Secret Accessor (roles/secretmanager.secretAccessor) roles.

4. Wait for the deployment to complete.

5. Once deployed, note the function URL from the output.

Set up Cloud Scheduler

1. In the Google Cloud Console, go to Cloud Scheduler > Create job.
2. Provide the following configuration details:
   • Name: Enter slack-audit-scheduler.
   • Region: Select the same region where you deployed the Cloud Run function.
   • Frequency: Enter */5 * * * * (runs every 5 minutes, matching the POLL_INTERVAL value).
   • Timezone: Select UTC.
   • Target type: Select HTTP.
   • URL: Enter the Cloud Run function URL from the deployment output.
   • HTTP method: Select POST.
   • Auth header: Select Add OIDC token.
   • Service account: Select the same service account used for the CCloud Run function.
3. Click Create.

Option 2: Configure Slack Audit Logs export using AWS S3

This option uses AWS Lambda to collect Slack Audit Logs and store them in S3, then configures a Google SecOps feed to ingest the logs.

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, slack-audit-logs).
3. Select the Security credentials tab.
4. Click Create Access Key in the Access Keys section.
5. Select Third-party service as the Use case.
6. Click Next.
7. Optional: Add a description tag.
8. Click Create access key.
9. Click Download CSV file for save the Access Key and Secret Access Key for later use.
10. Click Done.
11. Select the Permissions tab.
12. Click Add permissions in the Permissions policies section .
13. Select Add permissions.
14. Select Attach policies directly.
15. Search for and select the AmazonS3FullAccess policy.
16. Click Next.
17. Click Add permissions.

Configure the IAM policy and role for S3 uploads

1. In the AWS console, go to IAM > Policies > Create policy > JSON tab.

2. Copy and paste the following policy.

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

   • Replace slack-audit-logs if you entered a different bucket name.

3. Click Next.

4. Enter the policy name SlackAuditS3Policy.

5. Click Create policy.

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

7. Attach the newly created policy SlackAuditS3Policy.

8. Name the role SlackAuditToS3Role 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	slack_audit_to_s3
   Runtime	Python 3.13
   Architecture	x86_64
   Execution role	SlackAuditToS3Role

4. Click Create function.

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

   #!/usr/bin/env python3
   # Lambda: Pull Slack Audit Logs (Enterprise Grid) to S3 (no transform)
   
   import os, json, time, urllib.parse
   from urllib.request import Request, urlopen
   from urllib.error import HTTPError, URLError
   import boto3
   
   BASE_URL = "https://api.slack.com/audit/v1/logs"
   
   TOKEN        = os.environ["SLACK_AUDIT_TOKEN"]  # org-level user token with auditlogs:read
   BUCKET       = os.environ["S3_BUCKET"]
   PREFIX       = os.environ.get("S3_PREFIX", "slack/audit/")
   STATE_KEY    = os.environ.get("STATE_KEY", "slack/audit/state.json")
   LIMIT        = int(os.environ.get("LIMIT", "200"))             # Slack recommends <= 200
   MAX_PAGES    = int(os.environ.get("MAX_PAGES", "20"))
   LOOKBACK_SEC = int(os.environ.get("LOOKBACK_SECONDS", "3600")) # First-run window
   HTTP_TIMEOUT = int(os.environ.get("HTTP_TIMEOUT", "60"))
   HTTP_RETRIES = int(os.environ.get("HTTP_RETRIES", "3"))
   RETRY_AFTER_DEFAULT = int(os.environ.get("RETRY_AFTER_DEFAULT", "2"))
   # Optional server-side filters (comma-separated "action" values), empty means no filter
   ACTIONS      = os.environ.get("ACTIONS", "").strip()
   
   s3 = boto3.client("s3")
   
   def _get_state() -> dict:
       try:
           obj = s3.get_object(Bucket=BUCKET, Key=STATE_KEY)
           st = json.loads(obj["Body"].read() or b"{}")
           return {"cursor": st.get("cursor")}
       except Exception:
           return {"cursor": None}
   
   def _put_state(state: dict) -> None:
       body = json.dumps(state, separators=(",", ":")).encode("utf-8")
       s3.put_object(Bucket=BUCKET, Key=STATE_KEY, Body=body, ContentType="application/json")
   
   def _http_get(params: dict) -> dict:
       qs  = urllib.parse.urlencode(params, doseq=True)
       url = f"{BASE_URL}?{qs}" if qs else BASE_URL
       req = Request(url, method="GET")
       req.add_header("Authorization", f"Bearer {TOKEN}")
       req.add_header("Accept", "application/json")
   
       attempt = 0
       while True:
           try:
               with urlopen(req, timeout=HTTP_TIMEOUT) as r:
                   return json.loads(r.read().decode("utf-8"))
           except HTTPError as e:
               # Respect Retry-After on 429/5xx
               if e.code in (429, 500, 502, 503, 504) and attempt < HTTP_RETRIES:
                   retry_after = 0
                   try:
                       retry_after = int(e.headers.get("Retry-After", RETRY_AFTER_DEFAULT))
                   except Exception:
                       retry_after = RETRY_AFTER_DEFAULT
                   time.sleep(max(1, retry_after))
                   attempt += 1
                   continue
               # Re-raise other HTTP errors
               raise
           except URLError:
               if attempt < HTTP_RETRIES:
                   time.sleep(RETRY_AFTER_DEFAULT)
                   attempt += 1
                   continue
               raise
   
   def _write_page(payload: dict, page_idx: int) -> str:
       ts  = time.strftime("%Y/%m/%d/%H%M%S", time.gmtime())
       key = f"{PREFIX}{ts}-slack-audit-p{page_idx:05d}.json"
       body = json.dumps(payload, separators=(",", ":")).encode("utf-8")
       s3.put_object(Bucket=BUCKET, Key=key, Body=body, ContentType="application/json")
       return key
   
   def lambda_handler(event=None, context=None):
       state  = _get_state()
       cursor = state.get("cursor")
   
       params = {"limit": LIMIT}
       if ACTIONS:
           params["action"] = [a.strip() for a in ACTIONS.split(",") if a.strip()]
       if cursor:
           params["cursor"] = cursor
       else:
           # First run (or reset): fetch a recent window by time
           params["oldest"] = int(time.time()) - LOOKBACK_SEC
   
       pages = 0
       total = 0
       last_cursor = None
   
       while pages < MAX_PAGES:
           data = _http_get(params)
           _write_page(data, pages)
   
           entries = data.get("entries") or []
           total += len(entries)
   
           # Cursor for next page
           meta = data.get("response_metadata") or {}
           next_cursor = meta.get("next_cursor") or data.get("next_cursor")
           if next_cursor:
               params = {"limit": LIMIT, "cursor": next_cursor}
               if ACTIONS:
                   params["action"] = [a.strip() for a in ACTIONS.split(",") if a.strip()]
               last_cursor = next_cursor
               pages += 1
               continue
           break
   
       if last_cursor:
           _put_state({"cursor": last_cursor})
   
       return {"ok": True, "pages": pages + (1 if total or last_cursor else 0), "entries": total, "cursor": last_cursor}
   
   if __name__ == "__main__":
       print(lambda_handler())
   

6. Go to Configuration > Environment variables > Edit > Add environment variable.

7. Enter the following environment variables, replacing with your values.

   Key	Example value
   S3_BUCKET	slack-audit-logs
   S3_PREFIX	slack/audit/
   STATE_KEY	slack/audit/state.json
   SLACK_AUDIT_TOKEN	xoxp-*** (org-level user token with auditlogs:read)
   LIMIT	200
   MAX_PAGES	20
   LOOKBACK_SECONDS	3600
   HTTP_TIMEOUT	60
   HTTP_RETRIES	3
   RETRY_AFTER_DEFAULT	2
   ACTIONS	(optional, CSV) user_login,app_installed

8. Click Save.

9. Select the Configuration tab.

10. In the General configuration panel click Edit.

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

    Note: Timeout is a hard upper limit, meaning if the function is still running when the timer hits 5 minutes, AWS Lambda will terminate it. Any shorter execution just finishes normally; you are billed only for the actual run time.

Create an EventBridge schedule

1. Go to Amazon EventBridge > Scheduler > Create schedule.
2. Provide the following configuration details:
   • Name: Enter slack-audit-1h.
   • Recurring schedule: Select Rate-based schedule.
   • Rate expression: Enter 1 hours.
   • Flexible time window: Select Off.
3. Click Next.
4. Select Target:
   • Target API: Select AWS Lambda Invoke.
   • Lambda function: Select slack_audit_to_s3.
5. Click Next.
6. Click Next (skip optional settings).
7. Review and click Create schedule.

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

1. Go to AWS Console > IAM > Users > Add users.
2. Click Add users.
3. Provide the following configuration details:
   • User: Enter secops-reader.
   • Access type: Select Access key – Programmatic access.
4. Click Create user.
5. Attach minimal read policy (custom): Users > secops-reader > Permissions > Add permissions > Attach policies directly > Create policy.

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

   {
     "Version": "2012-10-17",
     "Statement": [
       {
         "Effect": "Allow",
         "Action": ["s3:GetObject"],
         "Resource": "arn:aws:s3:::slack-audit-logs/*"
       },
       {
         "Effect": "Allow",
         "Action": ["s3:ListBucket"],
         "Resource": "arn:aws:s3:::slack-audit-logs"
       }
     ]
   }
   

7. Click Next.

8. Enter the policy name secops-reader-policy.

9. Click Create policy.

10. Return to the user creation page, refresh the policy list, and select secops-reader-policy.

11. Click Next.

12. Click Create user.

13. Select the created user secops-reader.

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

15. Select Third-party service.

16. Click Next.

17. Click Create access key.

18. Click Download .csv file to save the credentials.

Configure a feed in Google SecOps to ingest Slack Audit Logs

1. Go to SIEM Settings > Feeds.
2. Click Add new.
3. In the Feed name field, enter a name for the feed (for example, Slack Audit Logs).
4. Select Amazon S3 V2 as the Source type.
5. Select Slack Audit as the Log type.
6. Click Next.
7. Specify values for the following input parameters:
   • S3 URI: s3://slack-audit-logs/slack/audit/
   • Source deletion options: Select deletion option according to your preference.
   • Maximum File Age: Include files modified in the last number of days. Default is 180 days.
   • Access Key ID: User access key with access to the S3 bucket (from secops-reader).
   • Secret Access Key: User secret key with access to the S3 bucket (from secops-reader).
   • 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

Log Field	UDM Mapping	Logic
action	metadata.product_event_type	Directly mapped from the action field in the raw log.
actor.type	principal.labels.value	Directly mapped from the actor.type field, with the key actor.type added.
actor.user.email	principal.user.email_addresses	Directly mapped from the actor.user.email field.
actor.user.id	principal.user.product_object_id	Directly mapped from the actor.user.id field.
actor.user.id	principal.user.userid	Directly mapped from the actor.user.id field.
actor.user.name	principal.user.user_display_name	Directly mapped from the actor.user.name field.
actor.user.team	principal.user.group_identifiers	Directly mapped from the actor.user.team field.
context.ip_address	principal.ip	Directly mapped from the context.ip_address field.
context.location.domain	about.resource.attribute.labels.value	Directly mapped from the context.location.domain field, with the key context.location.domain added.
context.location.id	about.resource.id	Directly mapped from the context.location.id field.
context.location.name	about.resource.name	Directly mapped from the context.location.name field.
context.location.name	about.resource.attribute.labels.value	Directly mapped from the context.location.name field, with the key context.location.name added.
context.location.type	about.resource.resource_subtype	Directly mapped from the context.location.type field.
context.session_id	network.session_id	Directly mapped from the context.session_id field.
context.ua	network.http.user_agent	Directly mapped from the context.ua field.
context.ua	network.http.parsed_user_agent	Parsed user agent information derived from the context.ua field using the parseduseragent filter.
country	principal.location.country_or_region	Directly mapped from the country field.
date_create	metadata.event_timestamp.seconds	The epoch timestamp from the date_create field is converted to a timestamp object.
details.inviter.email	target.user.email_addresses	Directly mapped from the details.inviter.email field.
details.inviter.id	target.user.product_object_id	Directly mapped from the details.inviter.id field.
details.inviter.name	target.user.user_display_name	Directly mapped from the details.inviter.name field.
details.inviter.team	target.user.group_identifiers	Directly mapped from the details.inviter.team field.
details.reason	security_result.description	Directly mapped from the details.reason field, or if it's an array, concatenated with commas.
details.type	about.resource.attribute.labels.value	Directly mapped from the details.type field, with the key details.type added.
details.type	security_result.summary	Directly mapped from the details.type field.
entity.app.id	target.resource.id	Directly mapped from the entity.app.id field.
entity.app.name	target.resource.name	Directly mapped from the entity.app.name field.
entity.channel.id	target.resource.id	Directly mapped from the entity.channel.id field.
entity.channel.name	target.resource.name	Directly mapped from the entity.channel.name field.
entity.channel.privacy	target.resource.attribute.labels.value	Directly mapped from the entity.channel.privacy field, with the key entity.channel.privacy added.
entity.file.filetype	target.resource.attribute.labels.value	Directly mapped from the entity.file.filetype field, with the key entity.file.filetype added.
entity.file.id	target.resource.id	Directly mapped from the entity.file.id field.
entity.file.name	target.resource.name	Directly mapped from the entity.file.name field.
entity.file.title	target.resource.attribute.labels.value	Directly mapped from the entity.file.title field, with the key entity.file.title added.
entity.huddle.date_end	about.resource.attribute.labels.value	Directly mapped from the entity.huddle.date_end field, with the key entity.huddle.date_end added.
entity.huddle.date_start	about.resource.attribute.labels.value	Directly mapped from the entity.huddle.date_start field, with the key entity.huddle.date_start added.
entity.huddle.id	about.resource.attribute.labels.value	Directly mapped from the entity.huddle.id field, with the key entity.huddle.id added.
entity.huddle.participants.0	about.resource.attribute.labels.value	Directly mapped from the entity.huddle.participants.0 field, with the key entity.huddle.participants.0 added.
entity.huddle.participants.1	about.resource.attribute.labels.value	Directly mapped from the entity.huddle.participants.1 field, with the key entity.huddle.participants.1 added.
entity.type	target.resource.resource_subtype	Directly mapped from the entity.type field.
entity.user.email	target.user.email_addresses	Directly mapped from the entity.user.email field.
entity.user.id	target.user.product_object_id	Directly mapped from the entity.user.id field.
entity.user.name	target.user.user_display_name	Directly mapped from the entity.user.name field.
entity.user.team	target.user.group_identifiers	Directly mapped from the entity.user.team field.
entity.workflow.id	target.resource.id	Directly mapped from the entity.workflow.id field.
entity.workflow.name	target.resource.name	Directly mapped from the entity.workflow.name field.
id	metadata.product_log_id	Directly mapped from the id field.
ip	principal.ip	Directly mapped from the ip field. Determined by logic based on the action field. Defaults to USER_COMMUNICATION, but changes to other values like USER_CREATION, USER_LOGIN, USER_LOGOUT, USER_RESOURCE_ACCESS, USER_RESOURCE_UPDATE_PERMISSIONS, or USER_CHANGE_PERMISSIONS based on the value of action. Hardcoded to "SLACK_AUDIT". Set to "Enterprise Grid" if date_create exists, otherwise set to "Audit Logs" if user_id exists. Hardcoded to "Slack". Hardcoded to "REMOTE". Set to "SSO" if action contains "user_login" or "user_logout". Otherwise, set to "MACHINE". Not mapped in the provided examples. Defaults to "ALLOW", but set to "BLOCK" if action is "user_login_failed". Set to "Slack" if date_create exists, otherwise set to "SLACK" if user_id exists.
user_agent	network.http.user_agent	Directly mapped from the user_agent field.
user_id	principal.user.product_object_id	Directly mapped from the user_id field.
username	principal.user.product_object_id	Directly mapped from the username field.

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