← sources

Quick opinions on Huntress: 3 hours in

source: reddit (reddit:sysadmin)published 2026-09-30 00:27ingested 2026-10-01 02:43

retained text

I spent part of today setting up Huntress (MDR only).  We are putting it only on servers.  After about 3 hours with it, here are my very preliminary opinions:

1. The web interface is simple and easy.  It's a whole lot easier than both Defender and CrowdStrike in my opinion.  Things are some in some weird places, but on the whole, it's intuitive.

2. It has recommendations on Defender settings, which can be helpful in some environments.  But I will say that, for moderately mature environments adhering to frameworks like CIS Benchmarks, it's going to be unhelpful and actually in conflict with some of the settings required by those compliance requirements.

3. The enterprise app Huntress creates in Entra requires a shit ton of permissions, so you better trust Huntress.

4. The way SAML/SSO works is slightly ass, in my opinion:

\--You have to invite users.  You can't just assign access in Entra and have Huntress create the user account on first logon.  And no SCIM.

\--Users must have email accounts to accept the invitation.  This sucks because none of our privileged/admin accounts (i.e., like the ones that can logon to Huntress) have email accounts -- by design.  So we had to temporarily license these accounts.

\--As far as I can see, once you enforce SSO, you can't have a break-glass account without SSO.  So if SAML breaks, you have to contact Huntress support.  I think this is not ideal.  They should let you specify a single non-SSO account for emergency purposes.

\--Once you logon via SSO, you *still* have to complete Huntress-local MFA if you have MFA enabled.  It's a little weird.  The whole point of SSO is that the IdP is ensuring all that has already been done.

document fetched 2026-10-01 00:41 · canonical https://reddit.com/r/sysadmin/comments/1wtqt5w/quick_opinions_on_huntress_3_hours_in