Huntress vs. ServiceNow Security Operations

Huntress is great for a managed service provider to provide a better cybersecurity stack to their endpoints/customers. Some smaller clients cannot afford high-priced SOC services but require SOC-level protection. Along with a couple of other layers of security, Huntress provides peace of mind for the MSP that if a threat were to arise, they would be notified with specific instructions for dealing with that threat.

Incentivized

Tight integration across ticketing, CMDB and ServiceNow Security Operations workflows automation module definitely stand out. In addition, the mean time to detection has reduced in my organization leading to a more efficient security operations with less burnout.

Incentivized

• Using the latest industry knowledge of threats that have been ongoing, but not previously known and projecting it back in time against their installed endpoints to identify machines that are vulnerable or breached and when it these events occurred
• Very quiet. If they alert, it is a thing.
• Very good at remediation.
• They communicate extremely well when it matters.
• While there are the most extensive products more often than not they are the first to alert us to a threat.

Incentivized

• Automatically creates a ticket for security incidents.
• Complete root cause Analysis of the problem.
• Ability to provide more knowledge because of threat intelligence.

Incentivized

• Now that they have EDR capability, they need to fully participate in MITRE testing for direct comparison against other EDR products.
• Now that they are going into Managed Antivirus and EDR with isolation capabilities they need to update their SLA comparative to other vendors
• Support for non-Windows OSes for consistency in a network
• It would be nice to seed canary files in custom shares on servers.

Incentivized

• Even though I mentioned that we built incident response playbooks, we found the learning curve to be steep, having drag and drop or something similar to this would be appreciated

Incentivized

We dropped SentinelOne in favor of Huntress because the UI was much more simplistic for the tier 1 techs to maintain. It beats the old web design model of three clicks to where you want to go. It is very intuitive. No one needs training to figure out how to navigate its console.

Incentivized

Seamless integration across modules mentioned in the previous sections along with the ability to automate security workflows are the main reasons.

Incentivized

Firstly from a business model, [VMware] Carbon Black [Cloud Managed Detection] was not outfitted for the MSP where Huntress is very MSP-friendly from an affordably easy point to entry to value for money licensing. Carbon Black TS is not bad in anyway, well, that we found, but Huntress is a new layer of security that fits between the OS and AV layers to provide additional information, monitoring, and detection. With Huntress backing the MSP, [it] sure does help as well.

Instead of integrating Spunk to ServiceNow ticketing and asset tool, I was able to get a native built in integration across ServiceNow modules and this helped a lot.

Incentivized

• We have been able to lower operational costs by shifting to Huntress.
• We've been able to cut costs to our clients by utilizing Huntress over competing products.
• In spite of inflation, we've been able to keep our managed service prices at a steady, below market rate, because of Huntress.

Incentivized

• Positive ROI since most of the security incidents can be closed via a security centre.

Incentivized