Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

The final part of CYJAX's rail cybersecurity series sets out a practical, five-step roadmap for building a rail-specific threat intelligence capability, covering regulation, coverage, and where to start regardless of maturity.

Rate this post Last Updated on July 22, 2026 by Narendra Sahoo Most compliance teams have filed the EU Cyber Resilience Act under “2027” — the date the regulation becomes fully applicable. That’s the wrong filing date. From 11 September 2026, manufacturers must already report actively exploited vulnerabilities and severe incidents affecting products with digital elements, more than a year before the rest of the regulation takes effect.

Every time a cyber breach breaks headlines, leadership teams pose the same urgent question: Does this affect us? But a third-party risk team is likely already asking: Was one of our vendors, suppliers, partners, or other third parties involved? And increasingly: What if it was not our direct vendor, but one of theirs?

Every tool in the enterprise security stack was designed to answer a specific question about a specific threat model.

Cybercrime used to have a ‘"tell." It was the digital equivalent of a villain stroking their cat - clunky grammar, misspelt links and suspicious attachments that screamed ‘phishing’. But the arrival of AI has changed everything. Typos have been replaced by perfect prose. Generic lures have evolved into highly personalized attacks that mimic your internal language and align with your project timelines.

TL;DR While improving our AI Pentest, we ran a whitebox assessment on NodeBB, a forum software powered by NodeJS. The result? Eight high-severity vulnerabilities that would all be exploitable on default instances of NodeBB. This includes Cross-Site Scripting (XSS), two of which require interaction with a custom Federation server that the AI agent had to set up itself. Another affects practically every input on NodeBB due to a template injection.

Oracle's July 2026 Critical Patch Update (CPU) is nearly three times larger than any release in the company's history. To understand it, we parsed all 23 of Oracle's quarterly advisories going back to 2021, matched them against the official CVE record, and compared Oracle against eight other major vendors. We set out to answer three questions: How much of this is genuinely new? Does it really reflect AI-accelerated patching? And how unusual is it?

Consider a few tasks that take place across every business, every day.