Collect Jamf Protect logs

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

For more information, see Data ingestion to Google Security Operations.

A typical deployment consists of Jamf Protect and the Google Security Operations feed configured to send logs to Google Security Operations. Each customer deployment can differ and might be more complex.

The deployment contains the following components:

• Jamf Protect. The Jamf Protect platform from which you collect logs.

• Google Security Operations feed. The Google Security Operations feed that fetches logs from Jamf Protect and writes logs to Google Security Operations.

• Google Security Operations. Google Security Operations 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_PROTECT ingestion label.

Before you begin

• Ensure that you are using Jamf Protect version 4.0.0 or later.
• Ensure that all systems in the deployment architecture are configured with the UTC time zone.

Configure a feed in Google Security Operations to ingest Jamf Protect logs

You can use either Amazon S3 or a webhook to set up an ingestion feed in Google Security Operations, but we recommend using Amazon S3.

Set up an ingestion feed using Amazon S3

1. From the Google Security Operations menu, select Settings, and then click Feeds.
2. Click Add New.
3. Select Amazon S3 as the Source Type.
4. To create a feed for Jamf Protect, select Jamf Protect Alerts as the Log Type.
5. Click Next.
6. Save the feed and then Submit.
7. Copy the Feed ID from the feed name to use in Jamf Protect.

Set up an ingestion feed using a webhook

1. From the Google Security Operations menu, select Settings, and then click Feeds.
2. Click Add new.
3. In the Feed name field, enter a name for the feed.
4. In the Source Type list, select Webhook.
5. To create a feed for Jamf Protect, select Jamf Protect Alerts as the Log Type.
6. Click Next.
7. Optional: Specify values for the following input parameters:
   • 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.
8. Click Next.
9. Review your new feed configuration in the Finalize screen, and then click Submit.
10. Click Generate Secret Key to generate a secret key to authenticate this feed.
11. Copy and store the secret key as you cannot view this secret again. You can generate a new secret key again, but regeneration of the secret key makes the previous secret key obsolete.
12. From the Details tab, copy the feed endpoint URL from the Endpoint Information field. You need to specify this endpoint URL in Jamf Protect Alerts application.
13. Click Done.
14. Specify the endpoint URL in Jamf Protect.

For more information about Google Security Operations feeds, see Google Security Operations feeds documentation. For information about requirements for each feed type, see Feed configuration by type.

If you encounter issues when you create feeds, contact Google Security Operations support.

Supported Jamf Protect log types

The following table lists the log types that the Jamf Protect parser supports:

Event Type	Display name
GPClickEvent	Synthetic Click Events
GPDownloadEvent	Download Events
GPFSEvent	File System Events
GPGatekeeperEvent	Gatekeeper Events
GPKeylogRegisterEvent	Keylogger Events
GPMRTEvent	Monitor Events
GPPreventedExecutionEvent	Custom Prevent List Events
GPProcessEvent	Process Events
GPThreatMatchExecEvent	Threat Prevention Events
GPUSBEvent	USB Events
GPUnifiedLogEvent	Unified Log Events
Auth-mount	Device Controls Events

Field mapping reference

This section explains how the Google Security Operations parser maps Jamf Protect fields to Google Security Operations Unified Data Model (UDM) fields.

Field mapping reference: Event Identifier to Event Type

The following table lists the JAMF_PROTECT log types and their corresponding UDM event types.

Field mapping reference: JAMF_PROTECT

The following table lists the log fields of the JAMF_PROTECT log type and their corresponding UDM fields.

What's next

• Data ingestion to Google Security Operations