Security
Huntress integration
Reads which Huntress agents have stopped checking in. View-only.
Setup steps are for connected customers — sign in to read them.
What we find in Huntress
Agents that have gone quiet (no survey check-in past 7 days) — an overlay on the RMM's fleet, not a second one. OS/hardware facts not yet wired: no confirmed field names beyond organization identity and survey timestamp.
Every finding lands on your Client Upsell board as a named client with a number beside it — not a report you have to read.
What the Huntress connection does
Read — powers Client Upsell
Read your clients' stack
Who is actually protected: endpoints still onboarding, seats never deployed, sites with no filtering policy.
Read-only
We only ever read — we never change anything in Huntress
You make a view-only key using our setup steps. Our connection has no code that can write to Huntress, and your key is encrypted and only used to read.
Huntress integration — common questions
- What does the Huntress integration read?
- Reads which Huntress agents have stopped checking in. View-only.
- What does MSProspector find in Huntress?
- Agents that have gone quiet (no survey check-in past 7 days) — an overlay on the RMM's fleet, not a second one. OS/hardware facts not yet wired: no confirmed field names beyond organization identity and survey timestamp.
- Is the Huntress connection read-only?
- Yes. We only ever read from Huntress — our Huntress connection has no code that can change anything, and an automated check on every change to our code blocks any that could. Please create a view-only key using the setup steps, so the key itself can't make changes either.