Configuring Jamf Protect Connectors
This connector allows Stellar Cyber to ingest logs from Jamf Protect and add the records to the data lake.
Connector Overview: Jamf Protect
Capabilities
-
Collect: Yes
-
Respond: No
-
Native Alerts Mapped: No
-
Runs on: DP
-
Interval: Configurable
Collected Data
Content Type |
Index |
Locating Records |
---|---|---|
Alerts |
Syslog |
Domain
https://<Hostname> where <Hostname> is a variable from the configuration of this connector |
Response Actions
N/A
Third Party Native Alert Integration Details
N/A
Required Credentials
-
Hostname portion of your Jamf Protect console login
-
Client ID and password for API client having at least the Read Only role
Let us know if you find the above overview useful.
Adding a Jamf Protect Connector
To add a Jamf Protect connector:
- Obtain Jamf Protect API credentials
- Add the connector in Stellar Cyber
- Test the connector
- Verify ingestion
Obtaining Jamf Protect API Credentials
Follow guidance on the Jamf documentation site to obtain the credentials for your connector.
-
Access the Jamf | PROTECT Console as an administrative user.
-
Navigate to Administrative > API Clients.
-
Click the button to Create API Client.
-
In the page that displays, enter a Name for the API client.
-
Add one or more Roles to configure permissions for the API client (Read Only is sufficient)
-
Click Save.
-
From the dialog that displays next, copy the API Client Password. Save this value for later use.
The password cannot be retrieved or reset after this dialog is closed. Clicking the button to Copy to Clipboard also closes the dialog. Be sure to take care when saving this value.
-
After the password dialog closes, the new API client configuration and endpoint information displays. Make note of the Client ID and also the hostname portion of the API URL.
Adding the Connector in Stellar Cyber
With the access information handy, you can add a Jamf Protect connector in Stellar Cyber:
-
Log in to Stellar Cyber.
-
Click System | Integration | Connectors. The Connector Overview appears.
-
Click Create. The General tab of the Add Connector screen appears. The information on this tab cannot be changed after you add the connector.
The asterisk (*) indicates a required field.
-
Choose Endpoint Security from the Category drop-down.
-
Choose Jamf Protect from the Type drop-down.
-
For this connector, the supported Function is Collect, which is enabled already.
-
Enter a Name.
This field does not accept multibyte characters.
-
Choose a Tenant Name. This identifies which tenant is allowed to use the connector.
-
Choose the device on which to run the connector.
-
(Optional) When the Function is Collect, you can create Log Filters. For information, see Managing Log Filters.
-
Click Next. The Configuration tab appears.
The asterisk (*) indicates a required field.
-
Enter the Hostname using the information you noted above.
Do not include https in the Hostname field.
Example:
your-organization.protect.jamfcloud.com
-
Enter the Client ID you noted above.
-
Enter the Password for that client.
-
Choose the Interval (min). This is how often the logs are collected.
-
Choose the Content Type. The logs for Alerts are supported.
-
Click Next. The final confirmation tab appears.
-
Click Submit.
To pull data, a connector must be added to a Data Analyzer profile if it is running on the Data Processor.
The new connector is immediately active.
Testing the Connector
When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you entered. (The test validates only the authentication / connectivity; it does not validate data flow).
For connectors running on a sensor, Stellar Cyber recommends that you allow 30-60 seconds for new or modified configuration details to be propagated to the sensor before performing a test.
-
Click System | Integrations | Connectors. The Connector Overview appears.
-
Locate the connector that you added, or modified, or that you want to test.
-
Click Test at the right side of that row. The test runs immediately.
Note that you may run only one test at a time.
Stellar Cyber conducts a basic connectivity test for the connector and reports a success or failure result. A successful test indicates that you entered all of the connector information correctly.
To aid troubleshooting your connector, the dialog remains open until you explicitly close it by using the X button. If the test fails, you can select the button from the same row to review and correct issues.
The connector status is updated every five (5) minutes. A successful test clears the connector status, but if issues persist, the status reverts to failed after a minute.
Repeat the test as needed.
Verifying Ingestion
To verify ingestion:
- Click Investigate | Threat Hunting. The Interflow Search tab appears.
- Change the Indices to Syslog. The table immediately updates to show ingested Interflow records.
- Use the Locating Records values in the above card to query for the ingested data.