Articles › Security

Third-party involvement in breaches doubled from 15% to 30% in a single year — the largest single-year shift ever recorded by the Verizon 2025 Data Breach Investigations Report. A supply chain compromise now costs an average of $4.91 million and takes 267 days to identify and contain, the longest lifecycle of any breach vector IBM […]

Every field in a security log that an attacker can influence is a field an attacker can write to. A hostname. A username. A DNS query. An HTTP User-Agent string. A process command line. None of that is new — it’s why security logs have always been treated as evidence, not trusted input.

Most SOC content explains architecture. This one walks through an actual incident, alert by alert, on a production stack running for a mid-sized enterprise client — Wazuh for detection, DFIR-IRIS for case management, and a custom FastAPI integrator holding the two together. No SaaS licenses. No cloud SIEM bill. Every component either open-source or built […]

Most security teams I talk to have reasonable IT hygiene: EDR on endpoints, a SIEM ingesting Windows event logs, maybe a WAF in front of the web apps. Then I ask them what’s running on the factory floor and the answer is usually some variation of "Siemens S7s, a Mitsubishi SCADA, and honestly we’re not […]

Most companies don’t discover their identity problem until after the breach. A departing employee’s account stays active in three systems because nobody updated the offboarding checklist. A contractor gets access to the finance portal because they needed "temporary" access six months ago and the ticket was never closed. A phishing attack succeeds not because your […]

Most engineering organisations share the same unspoken vulnerability: identity is everyone’s problem and no one’s responsibility. Here is how CTOs and engineering managers are fixing it — and what they gain in the process.

If your SOC analysts are processing hundreds of alerts per day and still feel like they’re falling behind, you’re not alone. Alert fatigue — the state where analysts become desensitized to security alerts because there are simply too many of them — is the defining operational problem of security teams in 2026.

If your security team is evaluating SIEM options, you will hit the same fork in the road everyone hits: pay six figures for Splunk or Sentinel, or run Wazuh for the cost of the infrastructure.

Every week, another headline: a hospital hit by ransomware, a manufacturer’s production data exfiltrated, a government agency’s email system compromised. The attacks are not slowing down. But most organizations in Southeast Asia still have no systematic way to detect, investigate, or respond to them.

IP cameras. PLCs. HVAC controllers. Access panels. Smart meters. The modern enterprise is full of connected devices that were never designed with security in mind — and most organizations have no idea what those devices are doing on the network.

Your best Tier 1 analyst just gave notice. She’s been with you 18 months. She didn’t quit because of the hours. She didn’t quit because of the pay. She quit because for 18 months she has triaged the same five false-positive alerts, in the same five tools that don’t talk to each other, against the […]

Every vendor with a security product has bolted "AI" onto the marketing page in the last eighteen months. Most of it is rebranded ML classification: anomaly detection that already existed, dressed in 2024 clothes. Where it gets genuinely interesting — and where most teams fail — is when you actually wire a tool-using LLM agent […]

A behind-the-scenes look at how we built a production SOC for a mid-sized enterprise using Wazuh, DFIR-IRIS, and a custom Python middleware — what worked, what broke, and the engineering decisions that actually mattered.

When your AI system goes live, it doesn’t just gain capabilities — it gains an attack surface that didn’t exist before. Most enterprises have invested years hardening their applications, networks, and endpoints. But the AI layer introduces a fundamentally different category of vulnerability that traditional security tools were never designed to handle.

Introduction Drones are no longer solo actors. Modern mission profiles — search and rescue, precision agriculture, infrastructure inspection, defense — increasingly rely on swarms: coordinated groups of UAVs that divide tasks, share situational awareness, and collectively achieve what no single drone can.

War does not stay on the battlefield. Since Russia’s full-scale invasion of Ukraine in 2022, one of the most consistent targets has not been a military base or a weapons depot — it has been the power grid. Substations, gas pipelines, thermal plants, and transmission lines have been hit repeatedly by missiles, drones, and cyberattacks […]

Your SOC is getting buried alive. The average enterprise security operations center receives 4,484 alerts per day from 28 or more tools. An analyst spends 70 minutes investigating a single alert — and 56 minutes pass before anyone even looks at it. According to Devo’s 2024 SOC Performance Report, 53% of those alerts are false […]

A three-week, commit-by-commit account of building a production Security Operations Center using Wazuh 4.x, IRIS-web, and a custom FastAPI integrator — the detection rules, the alert pipelines, the IOC enrichment, and the infrastructure bugs no one puts in their architecture diagrams.

Why most small security programs fail before they start "We need a SOC." It’s a sentence that gets said in every organization that has just experienced a breach, failed an audit, or hired a CISO for the first time. What usually follows is a commercial SIEM vendor pitch, a six-figure quote, and a 12-month deployment […]

A clear, beginner-friendly guide to how Wazuh decoders and rules work together — what fields are, where they come from, when you need a decoder, and how logs become alerts. Tags: Wazuh · OSSEC · SIEM · Blue Team · Detection Engineering Level: Beginner → Intermediate | Read time: 15 min If you’ve ever looked […]