What is our primary use case?
Huntress Managed SIEM serves as our central log collection and search platform. For a typical example, we ingest FortiGate traffic and correlate it with Windows login events and Linux SSH logs. If a suspicious external IP hits SSH repeatedly, we can see that alongside firewall logs in one place.
Storage and retention are getting tight because Huntress Managed SIEM ingests a lot from FortiGate, reaching 40 to 50 gigabytes per day, and we are watching capacity closely.
We align Huntress Managed SIEM's compliance reports with our organization's existing security frameworks by mapping the SIEM logs, alerts, and monitoring to our security requirements and policies, using Windows auth logs, Linux system logs, and FortiGate firewall logs to support audits and compliance checks. We review reports to spot gaps and provide evidence, ideally aligning with frameworks including ISO 27001 and NIST. Centralized logging helps significantly, but better automated compliance reporting and customizable report templates would make that process even more efficient.
How has it helped my organization?
Huntress Managed SIEM has positively impacted our organization by providing central visibility, faster investigation, and eliminating the need to jump between tools, which has made incident checks smoother, even though capacity management remains necessary.
While we have not calculated the exact time saved since using Huntress Managed SIEM, investigations are definitely faster because logs from FortiGate, Windows, and Linux are available centrally, saving manual effort and accelerating the process of spotting suspicious patterns.
Huntress Managed SIEM has improved our organization's capability to manage hybrid infrastructures by giving centralized visibility across different environments. We can collect and correlate logs from FortiGate firewalls, Windows servers, and Linux systems in one place, making it easier to monitor activity, investigate incidents, and spot suspicious behavior without switching between multiple tools. This definitely helps our operational efficiency and visibility, though managing storage and retention across environments remains a challenge.
We saw actionable detections after deploying Huntress Managed SIEM within that same early phase, where correlations including failed logins and suspicious connections became easier to spot, giving us a solid start in active detection.
What is most valuable?
The best features Huntress Managed SIEM offers are having central visibility, which makes it easier to investigate issues across the firewall, Windows, and Linux together.
Having that central visibility helps with investigations and day-to-day operations by saving time during a suspicious login incident. Instead of jumping between the FortiGate GUI and the Windows server, I can pivot in Huntress Managed SIEM and pull the firewall event and the correlated Windows failed logins in one timeline view. That is much faster than checking their separate consoles.
The alerting and the dashboard in Huntress Managed SIEM help spot patterns early, including repeated failed logins from the same source or unusual after-hours access, which helps us catch issues before they spread.
On day one of using Huntress Managed SIEM, we got central visibility into our infrastructure, being able to collect and monitor FortiGate, Windows, and Linux logs from a single platform, though the visibility depended on correct log source configuration and integration. Overall, the initial visibility was good and gave us a useful starting point for security monitoring and incident investigation.
It is very important to us that Huntress Managed SIEM offers security and compliance solutions without complexity, as we need strong security monitoring and compliance without adding too much operational complexity. Managing multiple log sources including FortiGate, Windows, and Linux, having centralized visibility, a simple dashboard, and predefined alerts lets us focus on threats and incidents instead of managing Huntress Managed SIEM itself, which saves time and reduces manual effort. Simplicity combined with reliable security features is key.
We are still exploring Huntress Managed SIEM's no-alert-tuning feature, which could save time for the operations team and let analysts focus on real security events, but we also value the flexibility to customize alerts based on our environment, especially with the different log sources we handle, including FortiGate, Windows, and Linux.
Huntress Managed SIEM's enhanced correlation and detection coverage helps us identify potential threats earlier. For instance, linking firewall events with Windows logins and Linux SSH activity, where repeated failed logins followed by unusual access stand out more clearly. That cross-log visibility reduces investigation time and moves us closer to proactive threat detection rather than just reacting to an incident.
We have used Huntress Managed SIEM's broader log source integrations feature to facilitate faster ingestion and correlation across our infrastructure, integrating FortiGate logs, Windows event logs, and Linux system logs, which organizes ingestion. For example, we can correlate a suspicious firewall connection with failed Windows logins or unusual Linux SSH activity, speeding up investigations, reducing manual effort, and giving us better visibility across the infrastructure.
What needs improvement?
Huntress Managed SIEM could be improved with better storage scaling options and flexible retention settings, so high ingest will not push us into capacity worries.
Handling the OpenSearch memory pressure and making scaling easier would definitely improve the experience with Huntress Managed SIEM, especially when data volumes spike.
The major improvement needed for Huntress Managed SIEM is storage scaling, especially with our heavy ingest from FortiGate, plus some help managing OpenSearch memory spikes. If retention and capacity were easier to manage, the overall experience would improve significantly.
For how long have I used the solution?
I have been using Huntress Managed SIEM for a few months and have been testing it in our VMware setup through K3s and Podman to collect FortiGate, Windows, and Linux logs.
What do I think about the scalability of the solution?
Overall, Huntress Managed SIEM is stable for our current workload and supports central monitoring. Regarding scalability, it can handle growing log sources and monitoring needs, but with high ingest, such as from FortiGate, storage capacity, retention, and memory management become important constraints. We would like easier scaling and more flexible storage options to handle future growth smoothly.
How are customer service and support?
Our experience with customer support for Huntress Managed SIEM has been generally positive and helpful when we needed configuration help or troubleshooting. Fast response times matter to us, especially with the production environment, and we would appreciate continued improvement in response times and proactive guidance.
Which solution did I use previously and why did I switch?
We previously used a different solution, relying more on separate tools and consoles to review firewall, Windows, and Linux logs. We wanted a more centralized solution to simplify log monitoring, correlation, and security investigations, which is why we moved toward Huntress Managed SIEM. It gives us better visibility in one place and helps reduce the manual effort involved in investigating security events.
How was the initial setup?
Huntress Managed SIEM is deployed on-premises for us on a VMware VM with K3s containers, with the manager backend, log storage, and database as pods, so we keep control of our infrastructure, logs, and security settings.
What was our ROI?
We have seen a return on investment primarily in operational benefits, particularly in investigation time. Earlier, we had to check firewall, Windows, and Linux logs separately, but now we do that centrally, saving manual effort and speeding up spotting suspicious activity. We have not formally measured hours saved or cost reductions, so the ROI is mainly improved visibility and faster investigations with the same team.
What's my experience with pricing, setup cost, and licensing?
Huntress Managed SIEM's flat and straightforward pricing has a beneficial effect on our organization's budgeting and financial planning, as it helps us plan security costs with fewer surprises, making budgeting and financial planning easier. It is also simpler to justify an investment to management, but as our log volume and infrastructure grow, we will still need to review pricing to make sure it stays cost-effective.
Our experience with pricing, setup cost, and licensing for Huntress Managed SIEM has been straightforward. The flat pricing makes budgeting easier to plan, and the initial setup involved integrating our log sources, configuring monitoring, and setting up alerts without major licensing complications. That said, as our log volume and infrastructure grow, it is important to keep checking the overall cost and licensing requirements to make sure it remains affordable.
Which other solutions did I evaluate?
Before choosing Huntress Managed SIEM, we evaluated other options, including separate log monitoring tools and open-source SIEM options such as Wazuh and the ELK stack, with our main goal being centralized collection and correlation without too much manual work. Huntress stood out as an option that could simplify monitoring and investigation.
What other advice do I have?
I would rate Huntress Managed SIEM an 8 out of 10, mainly for the visibility and correlation benefits, with storage pressure keeping it from being higher. I gave it an 8 out of 10 because the visibility and correlation are strong and help speed up investigations, but the storage and retention pressure from heavy log ingestion holds us back. If retention were easier to scale, that score would probably be higher.
Regarding Huntress Managed SIEM's AI capabilities, I think its governance and security features are crucial. The AI features can be useful, especially for spotting suspicious patterns, but I want clear data privacy controls, transparency about how the AI processes and uses log data, role-based access, and audit logs. Explainable alerts help analysts understand why something was flagged, which builds trust in the AI features.
The accuracy and reliability of Huntress Managed SIEM's output seem useful for spotting suspicious activity, but as with any SIEM, false positives can happen, especially with unusual but legitimate logins. We have not formally measured the false positive rate or confirmed missed alerts, and improving alert accuracy, reducing unnecessary notifications, and providing better context in alerts would help analysts quickly distinguish real threats from normal activity.
My advice to others looking into using Huntress Managed SIEM is to understand your security requirements and expected log volume first, and start by integrating key sources including firewall and Windows switches and configuring alerts according to your needs.
Which deployment model are you using for this solution?
On-premises