-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EA Input] Adding support for Jamf as a provider #40073
Labels
Team:Security-Service Integrations
Security Service Integrations Team
Comments
jamiehynds
added
the
Team:Service-Integrations
Label for the Service Integrations team
label
Jun 11, 2024
6 tasks
narph
added
the
Team:Security-Service Integrations
Security Service Integrations Team
label
Jun 25, 2024
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
narph
removed
the
Team:Service-Integrations
Label for the Service Integrations team
label
Jun 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are about to develop an integration with Jamf Pro (epic here) and in order to support the use cases outlined in the epic, we need the ability to ingest device (typically computer & mobile) metadata, similar to our integrations with EntraID and Okta. Information regarding inventory data collection available here: https://learn.jamf.com/en-US/bundle/jamf-pro-security-overview/page/Data_Collection.html
In order to support the ingest of this data, we need to add Jamf as a supported provider to our Entity Analytics input.
To view the use cases we have in mind, please see the dashboard section of the Jamf Pro epic. Details of the relevant API endpoints can also be found in the Architecture section.
We have access to a Jamf Pro instance and @txhaflaire from Jamf is also available for any technical questions we may have as we work through the Jamf integration. @jaredburgettelastic may also have some thoughts of the device fields we need in order to support our Entity Analytics capabilities too.
The text was updated successfully, but these errors were encountered: