Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

We’re all exhausted—both by the problem and by hearing about it. False positives and overwhelming alert volume have long plagued security operations. And despite years of innovation, solutions have remained elusive. Alert volume. Alert fatigue. SOC burnout. This persistent problem puts security teams in a tough position: For CISOs and SOC managers, it’s a lose-lose scenario.

What does it really mean to have a SIEM Without Compromise? For too long, security teams have been stuck in a no-win game—forced to choose between visibility and cost, detection breadth and team capacity, automation, and control. Every decision felt like a trade-off, with real-world consequences: dropped logs, missed alerts, and inconsistent response when it mattered most. With the Spring ’25 release of Graylog Security 6.2, we’re eliminating those compromises.

When Amazon Web Services (AWS) initially launched in 2006, it offered the first compute, storage, and database cloud service that developers could build on. Over time, AWS became a fundamental cloud service provider as organizations started migrating to the cloud. As one of the three primary cloud services providers, AWS remains integral to most businesses.

CVE-2025-24813 is a critical vulnerability (CVSS base score of 9.8) affecting Apache Tomcat, a widely used open-source web server and servlet container. This issue affects Apache Tomcat: In this blog, we’ll simulate an attack and look at the activity within Graylog. Throughout the analysis, and at the conclusion of the post, we’ll provide practical threat-hunting and detection strategies you can implement in your own environments.

Like every industry, the manufacturing sector has embraced digital transformation to improve operations. Digital manufacturing uses technologies like Internet of Things (IoT) devices, data analytics, and cloud computing to improve production processes and gain efficiencies. With businesses increasingly embracing digital transformation, they face the challenge of securing interconnected systems.

In cybersecurity, the adage “what’s old is new” continues to hold true as attackers resurface longstanding techniques or repurpose them with new twists and adaptations. The popularization of Living Off the Land Binaries (LOLBins) — legitimate, Windows-native tools commonly abused for malicious uses — is a great example of this.

Industrial facilities increasingly rely on interconnected systems to improve operations. As they implement these technologies into their legacy environments, they create new cybersecurity risks within previously isolated Industrial Control Systems (ICS) and Supervisory Control and Data Acquisition (SCADA) by connecting them to public internet-facing applications.

Think about how your banking app connects to payment processors or how your healthcare provider’s system shares records securely – APIs have become essential for modern digital interactions, enabling applications to communicate and share data effortlessly. However, this convenience comes at a cost: APIs often handle vast amounts of Personally Identifiable Information (PII), making them prime targets for API data exfiltration.