11 posts tagged with "Security Operations"

Alert fatigue is not only a queue problem. It is a story problem.

When a SOC is flooded with notifications, analysts often open one case at a time. Each case may be correct on its own. What is missing is the wider picture: which cases belong to the same attacker activity, the same account, or the same technique path. That gap is why teams can reduce noise and still feel like they are chasing fragments.

We wrote earlier about how 40,000 alerts can become fewer than 10 cases a day, and why alert fatigue is a business problem, not only a SOC inconvenience. SIEM+ 1.1.0 adds the next layer: campaigns that connect related cases so you can move from a single alert to the whole attack story.

Around mid-October 2026, Fortinet PSIRT published a cluster of product security advisories across FortiOS, FortiSIEM, FortiSandbox, FortiManager, FortiAnalyzer, FortiMail, and related products. One widely noted item in that wave was FG-IR-26-181 / CVE-2026-106174: an improper locking issue in FortiOS that can let an unauthenticated network attacker deny service to the HTTPS management GUI on affected 8.0.0 and 7.6.4–7.6.6 builds.

For security teams that already run a SIEM, the interesting part is not any single CVE. It is what happens to the queue when a major vendor drops a dense advisory set in a short window.

What Japan's October cyber wave shows, and five questions leadership should be able to answer this week.

In early October 2026, a run of data leaks caused by unauthorised access drew an unusually direct response from the Japanese government. On 8 October, the government convened an inter-ministerial meeting. Toshiharu Furukawa, Japan's Minister for Digital Transformation, who also oversees cybersecurity, said companies would be asked to fix system vulnerabilities, strengthen authentication and prevent the misuse of leaked information, and that these measures should extend to outsourced contractors.

The next day, the Cabinet Secretariat's National Cybersecurity Office (NCO) published an official notice, 「不正アクセスによる漏えい等の事案を踏まえた対応について」 (roughly, Response to incidents of leaks caused by unauthorised access; the notice is published in Japanese only). It confirms multiple cases in which attackers broke into the systems of organisations holding large volumes of personal data and stole it. The NCO names three routes: exploited web-system vulnerabilities, compromise through the supply chain, and weak data management. At a meeting of the Liberal Democratic Party's National Cybersecurity Strategy Headquarters on 9 October, its head Masaaki Taira said cybersecurity had entered a new phase and that the country now faced "a state of emergency, a contingency" (非常事態、有事). The LDP published its account of the meeting on 14 October. That is a political warning, not a legal declaration. It came just over a week after key provisions of Japan's Active Cyber Defence legislation took effect on 1 October.

We're announcing that SIEM+ now has full, native support for Microsoft Sentinel, joining our existing integrations with Devo, Splunk, and QRadar. If your organization runs Sentinel as its SIEM, you can now add SIEM+'s alert consolidation and AI-powered triage on top of it without changing anything about your existing Sentinel deployment.

Alert fatigue isn't a SOC inconvenience. It's an enterprise risk.​

When security leaders talk about alert fatigue, the conversation usually stays inside the SOC: analysts burning out, dashboards full of red, MTTR creeping up quarter over quarter. That framing isn't wrong — it's just too small.

At the enterprise level — in financial services, pharma, semiconductor, and large-scale manufacturing — alert fatigue isn't an operational nuisance. It's a business risk that shows up on the balance sheet, in audit findings, and in board-level conversations about resilience.