Collect Proofpoint TAP Threats logs

Supported in:

Google secops SIEM

This document explains how to ingest Proofpoint TAP Threats logs to Google Security Operations using Google Cloud Storage V2.

Proofpoint Targeted Attack Protection (TAP) is an advanced email security platform that detects, analyzes, and blocks threats delivered through email, including malicious attachments and URLs. The TAP SIEM API provides near-real-time data about threat events observed in your environment, including blocked and delivered messages, blocked and permitted clicks, and associated threat metadata such as threat classifications, URLs, attachments, and sender information. These events can be used to detect active email-based attacks, enrich security investigations, and trigger automated response workflows.

Before you begin

Make sure you have the following prerequisites:

A Google SecOps instance
A GCP project with Cloud Storage API enabled
Permissions to create and manage GCS buckets
Permissions to create Cloud Run services, Pub/Sub topics, and Cloud Scheduler jobs
A Proofpoint TAP subscription with access to the Threat Insight Dashboard
TAP API service credentials (Service Principal and Secret) with permissions to access the SIEM API

Generate Proofpoint TAP API service credentials

Sign in to the Proofpoint TAP Threat Insight Dashboard.
Go to Settings > Connected Applications > Service Credentials.
Click Create New Credential.
In the Generated Service Credential dialog, copy and securely store:
- Service Principal: The principal identifier used for API authentication
- Secret: The secret key used for API authentication
Note: The Secret is displayed only once during creation. If lost, you must generate a new credential. Service credentials are required for all TAP API requests and use HTTP Basic Authentication.

Verify API access

Test your credentials before proceeding with the integration:
```
PRINCIPAL="your-service-principal"
SECRET="your-secret"

# Test SIEM API access (fetch last 5 minutes of events)
curl -s "https://tap-api-v2.proofpoint.com/v2/siem/all?format=json&sinceSeconds=300" \
  --user "${PRINCIPAL}:${SECRET}"
```
A successful response returns a JSON object containing messagesBlocked, messagesDelivered, clicksBlocked, and clicksPermitted arrays.
- If you receive a 401 error, verify that your Service Principal and Secret are correct.
- If you receive a 403 error, confirm that your account has TAP API access enabled.

Create a Google Cloud Storage bucket

Go to the Google Cloud Console.
Select your project or create a new one.
In the navigation menu, go to Cloud Storage > Buckets.
Click Create bucket.

Provide the following configuration details:

Setting	Value
Name your bucket	Enter a globally unique name (for example, `proofpoint-tap-threats-logs`)
Location type	Choose based on your needs (Region, Dual-region, Multi-region)
Location	Select the location (for example, `us-central1`)
Storage class	Standard (recommended for frequently accessed logs)
Access control	Uniform (recommended)
Protection tools	Optional: Enable object versioning or retention policy

Click Create.

Create a service account for the Cloud Run function

The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.

Create a service account

In the GCP Console, go to IAM & Admin > Service Accounts.
Click Create Service Account.
Provide the following configuration details:
- Service account name: Enter tap-threats-collector-sa
- Service account description: Enter Service account for Cloud Run function to collect Proofpoint TAP Threats logs
Click Create and Continue.
In the Grant this service account access to project section, add the following roles:
1. Click Select a role.
2. Search for and select Storage Object Admin.
3. Click + Add another role.
4. Search for and select Cloud Run Invoker.
5. Click + Add another role.
6. Search for and select Cloud Functions Invoker.
Click Continue.
Click Done.

These roles are required for:

Storage Object Admin: Write threat event data to GCS bucket and manage state files
Cloud Run Invoker: Allow Pub/Sub to invoke the function
Cloud Functions Invoker: Allow function invocation

Grant IAM permissions on the GCS bucket

Grant the service account write permissions on the GCS bucket:

Go to Cloud Storage > Buckets.
Click your bucket name.
Go to the Permissions tab.
Click Grant access.
Provide the following configuration details:
- Add principals: Enter the service account email (for example, tap-threats-collector-sa@PROJECT_ID.iam.gserviceaccount.com)
- Assign roles: Select Storage Object Admin
Click Save.

Create a Pub/Sub topic

Create a Pub/Sub topic that Cloud Scheduler will publish to and the Cloud Run function will subscribe to.

In the GCP Console, go to Pub/Sub > Topics.
Click Create topic.
Provide the following configuration details:
- Topic ID: Enter tap-threats-collector-trigger
- Leave other settings as default
Click Create.

Create a Cloud Run function to collect threat events

The Cloud Run function will be triggered by Pub/Sub messages from Cloud Scheduler to fetch threat events from the Proofpoint TAP SIEM API and write the results to GCS.

In the GCP Console, go to Cloud Run.
Click Create service.
Select Function (use an inline editor to create a function).
In the Configure section, provide the following configuration details:

Setting Value

Service name tap-threats-collector

Region Select region matching your GCS bucket (for example, us-central1)

Runtime Select Python 3.12 or later
In the Trigger (optional) section:
1. Click + Add trigger.
2. Select Cloud Pub/Sub.
3. In Select a Cloud Pub/Sub topic, choose the topic tap-threats-collector-trigger.
4. Click Save.
In the Authentication section:
1. Select Require authentication.
2. Check Identity and Access Management (IAM).
Note: Pub/Sub will automatically handle authentication when invoking the function.
Scroll down and expand Containers, Networking, Security.
Go to the Security tab:
- Service account: Select the service account tap-threats-collector-sa

Setting	Value
Service name	`tap-threats-collector`
Region	Select region matching your GCS bucket (for example, `us-central1`)
Runtime	Select Python 3.12 or later

Go to the Containers tab:

Click Variables & Secrets.
Click + Add variable for each environment variable:

Variable Name	Example Value	Description
`GCS_BUCKET`	`proofpoint-tap-threats-logs`	GCS bucket name
`GCS_PREFIX`	`tap-threats`	Prefix for log files
`STATE_KEY`	`tap-threats/state.json`	State file path
`TAP_PRINCIPAL`	`your-service-principal`	TAP API Service Principal
`TAP_SECRET`	`your-secret`	TAP API Secret
`LOOKBACK_HOURS`	`1`	Initial lookback period in hours (max 7 days)

Scroll down in the Variables & Secrets section to Requests:
- Request timeout: Enter 540 seconds (9 minutes)
Go to the Settings tab:
- In the Resources section:
  - Memory: Select 512 MiB or higher
  - CPU: Select 1
In the Revision scaling section:
- Minimum number of instances: Enter 0
- Maximum number of instances: Enter 100 (or adjust based on expected load)
Click Create.
Wait for the service to be created (1-2 minutes).
After the service is created, the inline code editor will open automatically.

Add function code

Enter main in the Entry point field.

In the inline code editor, create two files:

First file - main.py:

import functions_framework
from google.cloud import storage
import json
import os
import urllib3
from datetime import datetime, timezone, timedelta
import time
import base64

# Initialize HTTP client with timeouts
http = urllib3.PoolManager(
  timeout=urllib3.Timeout(connect=10.0, read=60.0),
  retries=False,
)

# Initialize Storage client
storage_client = storage.Client()

# Environment variables
GCS_BUCKET = os.environ.get('GCS_BUCKET')
GCS_PREFIX = os.environ.get('GCS_PREFIX', 'tap-threats').strip('/')
STATE_KEY = os.environ.get('STATE_KEY') or f"{GCS_PREFIX}/state.json"
TAP_PRINCIPAL = os.environ.get('TAP_PRINCIPAL')
TAP_SECRET = os.environ.get('TAP_SECRET')
LOOKBACK_HOURS = int(os.environ.get('LOOKBACK_HOURS', '1'))

API_BASE = 'https://tap-api-v2.proofpoint.com'

def get_auth_header():
  """Build HTTP Basic Authentication header."""
  auth_string = f"{TAP_PRINCIPAL}:{TAP_SECRET}"
  auth_bytes = auth_string.encode('utf-8')
  auth_b64 = base64.b64encode(auth_bytes).decode('utf-8')
  return f"Basic {auth_b64}"

@functions_framework.cloud_event
def main(cloud_event):
  """
  Cloud Run function triggered by Pub/Sub to fetch Proofpoint TAP
  SIEM threat events and write to GCS.

  The function queries the TAP SIEM API /v2/siem/all endpoint to
  retrieve blocked and delivered messages, blocked and permitted
  clicks, and associated threat metadata.

  Args:
    cloud_event: CloudEvent object containing Pub/Sub message
  """

  if not all([GCS_BUCKET, TAP_PRINCIPAL, TAP_SECRET]):
    print('Error: Missing required environment variables')
    return

  try:
    bucket = storage_client.bucket(GCS_BUCKET)

    # Load state
    state = load_state(bucket, STATE_KEY)

    # Determine time window
    now = datetime.now(timezone.utc)
    last_time = None

    if isinstance(state, dict) and state.get('last_event_time'):
      try:
        last_time = parse_datetime(state['last_event_time'])
        # Overlap by 2 minutes to catch delayed events
        last_time = last_time - timedelta(minutes=2)
      except Exception as e:
        print(f"Warning: Could not parse last_event_time: {e}")

    if last_time is None:
      last_time = now - timedelta(hours=LOOKBACK_HOURS)

    # TAP SIEM API allows max 1 hour per request and max 7 days lookback
    if (now - last_time) > timedelta(days=7):
      last_time = now - timedelta(days=7)
      print("Warning: Lookback capped to 7 days (TAP API limit)")

    print(f"Fetching threats from {last_time.isoformat()} to {now.isoformat()}")

    # Fetch threat events from the SIEM API
    all_events = fetch_siem_events(last_time, now)

    if not all_events:
      print("No threat events found in the specified time window.")
      save_state(bucket, STATE_KEY, now.isoformat())
      return

    # Write to GCS as NDJSON
    timestamp = now.strftime('%Y%m%d_%H%M%S')
    object_key = f"{GCS_PREFIX}/tap_threats_{timestamp}.ndjson"
    blob = bucket.blob(object_key)

    ndjson = '\n'.join(
      [json.dumps(record, ensure_ascii=False) for record in all_events]
    ) + '\n'
    blob.upload_from_string(ndjson, content_type='application/x-ndjson')

    print(f"Wrote {len(all_events)} records to gs://{GCS_BUCKET}/{object_key}")

    # Update state
    save_state(bucket, STATE_KEY, now.isoformat())

    print(f"Successfully collected {len(all_events)} threat events")

  except Exception as e:
    print(f'Error processing TAP threats: {str(e)}')
    raise

def load_state(bucket, key):
  """Load state from GCS."""
  try:
    blob = bucket.blob(key)
    if blob.exists():
      state_data = blob.download_as_text()
      return json.loads(state_data)
  except Exception as e:
    print(f"Warning: Could not load state: {e}")
  return {}

def save_state(bucket, key, last_event_time_iso):
  """Save the last event timestamp to GCS state file."""
  try:
    state = {'last_event_time': last_event_time_iso}
    blob = bucket.blob(key)
    blob.upload_from_string(
      json.dumps(state, indent=2),
      content_type='application/json'
    )
    print(f"Saved state: last_event_time={last_event_time_iso}")
  except Exception as e:
    print(f"Warning: Could not save state: {e}")

def parse_datetime(value):
  """Parse ISO datetime string to datetime object."""
  if value.endswith('Z'):
    value = value[:-1] + '+00:00'
  return datetime.fromisoformat(value)

def fetch_siem_events(start_time, end_time):
  """
  Fetch threat events from the TAP SIEM API by querying
  in 1-hour intervals within the specified time window.

  Returns individual event records from messagesBlocked,
  messagesDelivered, clicksBlocked, and clicksPermitted arrays,
  each tagged with an _eventType field.

  Args:
    start_time: Start of the time window (datetime)
    end_time: End of the time window (datetime)

  Returns:
    List of event dictionaries
  """
  headers = {
    'Authorization': get_auth_header(),
    'Accept': 'application/json',
    'User-Agent': 'GoogleSecOps-TAPThreatsCollector/1.0',
  }

  all_events = []
  current_start = start_time
  backoff = 1.0

  while current_start < end_time:
    # TAP SIEM API allows max 1 hour per request
    current_end = min(current_start + timedelta(hours=1), end_time)

    interval = (
      f"{current_start.strftime('%Y-%m-%dT%H:%M:%SZ')}"
      f"/{current_end.strftime('%Y-%m-%dT%H:%M:%SZ')}"
    )
    url = f"{API_BASE}/v2/siem/all?format=json&interval={interval}"

    try:
      response = http.request('GET', url, headers=headers)

      if response.status == 429:
        retry_after = int(
          response.headers.get('Retry-After', str(int(backoff)))
        )
        print(f"Rate limited (429). Retrying after {retry_after}s...")
        time.sleep(retry_after)
        backoff = min(backoff * 2, 60.0)
        continue

      backoff = 1.0

      if response.status != 200:
        print(f"SIEM API HTTP Error: {response.status}")
        response_text = response.data.decode('utf-8')
        print(f"Response body: {response_text[:500]}")
        current_start = current_end
        continue

      data = json.loads(response.data.decode('utf-8'))

      # Collect events from all categories with type tagging
      event_types = {
        'messagesBlocked': 'MESSAGE_BLOCKED',
        'messagesDelivered': 'MESSAGE_DELIVERED',
        'clicksBlocked': 'CLICK_BLOCKED',
        'clicksPermitted': 'CLICK_PERMITTED',
      }

      interval_count = 0
      for key, event_type in event_types.items():
        for event in data.get(key, []):
          event['_eventType'] = event_type
          all_events.append(event)
          interval_count += 1

      print(
        f"Interval {interval}: {interval_count} events, "
        f"{len(all_events)} total so far"
      )

    except Exception as e:
      print(f"Error fetching SIEM events: {e}")

    current_start = current_end

  return all_events

Second file - requirements.txt:

functions-framework==3.*
google-cloud-storage==2.*
urllib3>=2.0.0

Click Deploy to save and deploy the function.
Wait for deployment to complete (2-3 minutes).

Note: The function queries the TAP SIEM API /v2/siem/all endpoint to fetch all threat event categories (blocked messages, delivered messages, blocked clicks, and permitted clicks) and writes each event as an individual NDJSON record to GCS. The SIEM API supports a maximum of 1 hour per request and 7 days of lookback. The function automatically splits larger time windows into 1-hour intervals. Each event is tagged with an _eventType field indicating the event category.

Create a Cloud Scheduler job

Cloud Scheduler will publish messages to the Pub/Sub topic at regular intervals, triggering the Cloud Run function.

In the GCP Console, go to Cloud Scheduler.
Click Create Job.

Provide the following configuration details:

Setting	Value
Name	`tap-threats-collector-hourly`
Region	Select same region as Cloud Run function
Frequency	`0 * * * *` (every hour, on the hour)
Timezone	Select timezone (UTC recommended)
Target type	Pub/Sub
Topic	Select the topic `tap-threats-collector-trigger`
Message body	`{}` (empty JSON object)

Click Create.

Schedule frequency options

Choose frequency based on log volume and latency requirements:

Frequency	Cron Expression	Use Case
Every 15 minutes	`/15 * * *`	High-volume environments with many threats
Every hour	`0 * * * *`	Standard (recommended)
Every 6 hours	`0 /6 * *`	Low-volume environments

Test the integration

In the Cloud Scheduler console, find your job.
Click Force run to trigger the job manually.
Wait a few seconds.
Go to Cloud Run > Services.
Click on the function name tap-threats-collector.
Click the Logs tab.

Verify the function executed successfully. Look for:

Fetching threats from YYYY-MM-DDTHH:MM:SS+00:00 to YYYY-MM-DDTHH:MM:SS+00:00
Interval .../...: X events, Y total so far
Wrote Z records to gs://proofpoint-tap-threats-logs/tap-threats/tap_threats_YYYYMMDD_HHMMSS.ndjson
Successfully collected Z threat events

Go to Cloud Storage > Buckets.
Click your bucket name.
Navigate to the prefix folder tap-threats/.
Verify that a new .ndjson file was created with the current timestamp.

If you see errors in the logs:

HTTP 401: Check TAP_PRINCIPAL and TAP_SECRET in environment variables. Verify the Service Principal and Secret are correct.
HTTP 403: Confirm that your TAP account has API access enabled.
HTTP 429: Rate limiting - function will automatically retry with backoff. Consider reducing schedule frequency.
No threat events found: This is normal if no threats were detected in the time window. TAP only reports threats identified by URL Defense or Attachment Defense.
Missing environment variables: Check all required variables are set.

Configure a feed in Google SecOps to ingest Proofpoint TAP Threats logs

Go to SIEM Settings > Feeds.
Click Add New Feed.
Click Configure a single feed.
In the Feed name field, enter a name for the feed (for example, Proofpoint TAP Threats).
Select Google Cloud Storage V2 as the Source type.
Select Proofpoint Tap Threats as the Log type.
Click Get Service Account. A unique service account email will be displayed, for example:
```
chronicle-12345678@chronicle-gcp-prod.iam.gserviceaccount.com
```
Copy this email address for use in the next step.

Note: Each Google SecOps instance has a unique service account. Don't use service accounts from other documentation or examples.
Click Next.
Specify values for the following input parameters:
- Storage bucket URL: Enter the GCS bucket URI with the prefix path:
```
gs://proofpoint-tap-threats-logs/tap-threats/
```
  - Replace:
    - proofpoint-tap-threats-logs: Your GCS bucket name.
    - tap-threats: Optional prefix/folder path where logs are stored (leave empty for root).
Note: Always include the trailing slash (/) at the end of the URI.
- Source deletion option: Select the deletion option according to your preference:
  - Never: Never deletes any files after transfers (recommended for testing).
  - Delete transferred files: Deletes files after successful transfer.
  - Delete transferred files and empty directories: Deletes files and empty directories after successful transfer.
  Note: If you select a deletion option, the service account must have Storage Object Admin role instead of Storage Object Viewer. Update IAM permissions accordingly.
- Maximum File Age: Include files modified in the last number of days (default is 180 days)
- Asset namespace: The asset namespace
- Ingestion labels: The label to be applied to the events from this feed
Click Next.
Review your new feed configuration in the Finalize screen, and then click Submit.

Grant IAM permissions to the Google SecOps service account

The Google SecOps service account needs Storage Object Viewer role on your GCS bucket.

Go to Cloud Storage > Buckets.
Click your bucket name.
Go to the Permissions tab.
Click Grant access.
Provide the following configuration details:
- Add principals: Paste the Google SecOps service account email
- Assign roles: Select Storage Object Viewer
Click Save.

Note: If you plan to use the deletion option "Delete transferred files" or "Delete transferred files and empty directories," grant Storage Object Admin role instead of Storage Object Viewer.

UDM mapping table

Log Field	UDM Mapping	Logic
`detectionType_label`	`additional.fields`	Merged
`geoTargeted_label`	`additional.fields`	Merged
`notable_label`	`additional.fields`	Merged
`verticallyTargeted_label`	`additional.fields`	Merged
`identifiedAt`	`metadata.event_timestamp`	Parsed as `ISO8601`
`has_principal`	`metadata.event_type`	Mapped: `true` → `NETWORK_CONNECTION`, `true` → `STATUS_UPDATE`
`type`	`metadata.product_event_type`	Directly mapped
`id`	`metadata.product_log_id`	Directly mapped
`_associations`	`security_result.associations`	Merged
`_techniques`	`security_result.attack_details.techniques`	Merged
`_category`	`security_result.category`	Merged
`_category_details`	`security_result.category_details`	Merged
`notable`	`security_result.priority`	Mapped: `true` → `HIGH_PRIORITY`
`name`	`security_result.threat_name`	Directly mapped
`status`	`security_result.threat_status`	Mapped: `active` → `ACTIVE`, `cleared` → `CLEARED`
`_verdict_info`	`security_result.verdict_info`	Merged
N/A	`metadata.event_type`	Constant: `NETWORK_CONNECTION`
N/A	`metadata.product_event_type`	Constant: `Proofpoint_Threats_Feed`
N/A	`metadata.product_name`	Constant: `TAP Threats`
N/A	`metadata.vendor_name`	Constant: `Proofpoint`
N/A	`security_result.priority`	Constant: `HIGH_PRIORITY`
N/A	`security_result.threat_status`	Constant: `ACTIVE`

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