Skip to main content

Huntress Integration Agent Sync

Integrations

The new Huntress integration allows syncing of agents, but it assumes all agents will the same asset type in Hudu. We currently distinguish between user endpoint and servers. Is it possible to allow more elaborate mapping?

2 comments

Log in to comment and vote

Comments2

  • Sapphire Geyser

    •

    Oct 27

    We also saw this, along with it duplicating all our assets and identities. I have a support case open at the moment for more detail around the matching behaviour/logic and will have another look today, but when you integrate Halo/Ninja and then Huntress, it falls over pretty quick. You almost have to have a separate layout just for Huntress identities which makes it kinda pointless, as you really want the cards to overlay on the same identity.

    • Sapphire Geyser

      •

      Oct 27

      “For users, the integration matches Huntress identities by asset name, within the matched company and the layout selected for Huntress identities. It uses the Huntress username, or the email address if there is no username. The email address is saved on the new card, but it is not currently used to find an existing person. This means a person asset named “First Last” will not be matched, and a second asset named after the email address is created. Deleting those duplicates does not change this, so a later sync will create them again.”

      I’m about to dig into this, but it currently reads like it doesn’t do any matching? Or if it does, it’s matching on the name of the hudu asset to == the email address, which is not how any of our other systems would store an identity, email would be a field on the person layout, but not the name itself, that would be the persons name. But in Huntress identities are the username/email address.