Collect Jamf Threat Events logs

This document describes how you can collect Jamf Threat Events logs by setting up a Google Security Operations feed and how log fields map to Google SecOps Unified Data Model (UDM) fields. This document also lists the supported Jamf Threat Events version.

For more information, see Data ingestion to Google SecOps .

A typical deployment consists of Jamf Threat Events and the Google SecOps feed configured to send logs to Google SecOps. Each customer deployment can differ and might be more complex.

The deployment contains the following components:

• Jamf Protect: The Jamf Protect platform, configured with Jamf Security Cloud, where you collect network threat logs.

• Google SecOps feed: The Google SecOps feed that fetches logs from Jamf Protect and writes logs to Google SecOps.

• Google SecOps: Google SecOps retains and analyzes the logs from Jamf Protect.

An ingestion label identifies the parser which normalizes raw log data to structured UDM format. The information in this document applies to the parser with the JAMF_THREAT_EVENTS ingestion label.

Before you begin

Ensure you have the following prerequisites:

• A Jamf Protect Telemetry set up
• Jamf Protect version 4.0.0 or later
• All systems in the deployment architecture are configured with the UTC time zone.

Set up feeds from SIEM Settings > Feeds

You can use either Amazon S3 V2 or a webhook to set up an ingestion feed in Google SecOps.

Set up an ingestion feed using Amazon S3 V2

1. Go to SIEM Settings > Feeds.
2. Click Add New Feed.
3. Click the JAMFfeed pack.
4. Locate the Jamf Protect Threat Eventsfeed.
5. Select Amazon S3 V2as the Source Type.

6. Specify the values for the following fields.

   • S3 URI: The bucket URI.
     • s3://your-log-bucket-name/
       • Replace your-log-bucket-name with the actual name of your S3 bucket.
   • Source deletion options: Select the deletion option according to your ingestion preferences.
   • Maximum File Age: Includes files modified in the last number of days. Default is 180 days.
   • Access Key ID: The user's access key with permissions to read from the S3 bucket.
   • Secret Access Key: The user's secret key with permissions to read from the S3 bucket.

   Advanced options

   • Feed Name: A prepopulated value that identifies the feed.
   • Asset Namespace: Namespace associated with the feed .
   • Ingestion Labels: Labels applied to all events from this feed.

7. Click Create Feed.

Set up an ingestion feed using a webhook

1. Go to SIEM Settings > Feeds.
2. Click Add New Feed.
3. Click the JAMFfeed pack.
4. Locate the Jamf Protect Threat Eventsfeed.
5. In the Source Typelist, select Webhook..
6. Specify values for the following fields
   • Split delimiter: The delimiter that is used to separate log lines, such as \n .
   • Asset namespace: The asset namespace .
   • Ingestion labels: The label to be applied to the events from this feed.
7. Click Create Feed.

To configure multiple feeds for different log types within this product family, see Configure feeds by product .

Create an API key for a webhook feed

1. Go to Google Cloud console > Credentials.

   Go to Credentials

2. Click Create credentials, and then select API key.

3. Restrict the API key access to the Google Security Operations API.

Set up Jamf Security Cloud for a webhook feed

1. In the Jamf Security Cloud application, go to Integrations> Data Streams.
2. Click New Configuration.
3. Select Threat Events> Generic HTTP> Continue.
4. In the HTTP Connection Configurationsection, select httpsas the default protocol.
5. Enter your server hostname in the Server Hostname/IPfield, such as us-chronicle.googleapis.com .
6. Enter your server port in the Portfield, such as 443 .
7. Enter your web endpoint in the Endpointfield. (This is the Endpoint Informationfield that you copied from the webhook feed setup. It's already in the required format.)

8. In the Additional headerssection, enter the following settings, where each header is a custom, case-sensitive header that you manually enter:

   • Header name: X-goog-api-keyand click Create option X-goog-api-key
   • Header value insert: API_KEY(The API key to authenticate to Google SecOps.)
   • Header name: X-Webhook-Access-Keyand click Create option X-Webhook-Access-Key
   • Header value insert: SECRET(The secret key that you generated to authenticate the feed.)

9. Click Test Configuration.

10. If successful, click Create Configuration.

For more information about Google SecOps feeds, see Create and manage feeds using the feed management UI . For information about requirements for each feed type, see Feed configuration API .

Supported Jamf Threat Events log formats

The Jamf Threat Events parser supports logs in JSON format.

Supported Jamf Threat Events sample logs

• JSON

   {
    "event": {
      "metadata": {
        "schemaVersion": "1.0",
        "vendor": "Jamf",
        "product": "Threat Events Stream"
      },
      "timestamp": "2023-01-11T13:10:40.410Z",
      "alertId": "debd2e4b-9da1-454e-952d-18a00b42ffce",
      "account": {
        "customerId": "dummycustomerid",
        "parentId": "dummyparentid",
        "name": "Jamf Internal Test Accounts (root) - Jamf - CE Security Team"
      },
      "device": {
        "deviceId": "e9671102-5ccf-4e66-a6b3-b117ba257d5f",
        "os": "UNKNOWN 13.2.1",
        "deviceName": "Mac (13.2.1)",
        "userDeviceName": "darrow",
        "externalId": "0c221ae4-50af-5e39-8275-4424cc87ab8e"
      },
      "eventType": {
        "id": "303",
        "description": "Risky Host/Domain - Malware",
        "name": "ACCESS_BAD_HOST"
      },
      "app": {
        "id": "ru.freeapps.calc",
        "name": "MyFreeCalculator",
        "version": "10.4",
        "sha1": "c3499c2729730a7f807efb8676a92dcb6f8a3f8f",
        "sha256": "50d858e0985ecc7f60418aaf0cc5ab587f42c2570a884095a9e8ccacd0f6545"
      },
      "destination": {
        "name": "dummy.domain.org",
        "ip": "0000:1111:2222:3333:4444:5",
        "port": "80"
      },
      "source": {
        "ip": "198.51.100.1",
        "port": "243"
      },
      "location": "GB",
      "accessPoint": null,
      "accessPointBssid": "23:8f:cf:00:9d:23",
      "severity": 8,
      "user": {
        "email": "test.user@domain.io",
        "name": "Test User"
      },
      "eventUrl": "dummy.domain.com",
      "action": "Blocked"
    }
  } 
  

Field mapping reference

The following table explains how the Google SecOps parser maps Jamf Threat Events logs fields to Google SecOps Unified Data Model (UDM) fields.

Field mapping reference: Event Identifier to Event Type

Field mapping reference: JAMF_THREAT_EVENTS

What's next

• Data ingestion to Google SecOps

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