The Jamf Protect Add-on for Splunk supports the following:
Important
The base event type must be updated before enabling this Add On.
See Splunk Integration with Jamf Protect to learn more how to configure Jamf Protect to send events to Splunk.
Due to differences in the json schema of Jamf Protect Alerts and Jamf Protect Telemetry, individual HTTP Event Collectors (HECs) must be created. The Jamf Protect Add-on expects initial source types of:
jamf:protect:alertsjamf:protect:telemetry:v2jamf:protect:telemetryjamf:protect:webExisting Data
For compatibility with existing Splunk objects such as source types, field names, and similar you may need to make a search time rename for the Jamf Splunk object. To do this, follow these steps:
Jamf Protect Alerts
jamf:protect:alertsJamf Protect Telemetry
jamf:protect:telemetryJamf Security Cloud
jamf:protect:webCopy the top line from the text chunk in [ ] you want to modify from default/props.conf to local/props.conf and set the appropriate original source type.
Example:
###
[EXISTING-SOURCETYPE]
rename = jamf:protect:alerts
This will not change your data, it will only allow you to use the search time extractions from this app with your existing source type. Please make sure that your new data is using the source types of jamf:protect:alerts or jamf:protect:telemetry, depending on your Jamf Protect deployment, for best compatibility with the add-on.
For jamf_protect and jamf_protect_web, the base event types must be updated, so the correct index value is set. This is not necessary for the Telemetry event types. Follow these steps:
Splunk Cloud
index="CORRECTINDEX" sourcetype="jamf:protect:alerts"index="CORRECTINDEX" sourcetype="jamf:protect:web"Splunk Enterprise
Copy the setting below from default/eventtypes.conf to local/eventtypes.conf. Replace index=* with the index your jamf:protect data is in.
Example:
[jamf_protect]
search = index=CORRECTINDEX sourcetype="jamf:protect:alerts"
[jamf_protect_web]
search = index=CORRECTINDEX sourcetype="jamf:protect:web"
Important
The indexes must also be updated within the Telemetry Lookup Workflow Action before it can be used.
audit_token enhancementse_usernameexec_pathmount event enhancementsaudit_token enhancementsgatekeeper_user_override eventBug Fixes
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps from Splunk, our partners and our community. Find an app for most any data source and user need, or simply create your own with help from our developer portal.