<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>CipherWatch — Commentary</title><description>Practitioner opinion and analysis on security strategy, threat trends, and industry challenges.</description><link>https://cipherwatch.io/</link><language>en-gb</language><item><title>Air-Gapping Is Not a Security Strategy — Operation Highland Proves It Never Has Been</title><link>https://cipherwatch.io/commentary/2026-06-16-air-gapping-is-not-a-security-strategy/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-16-air-gapping-is-not-a-security-strategy/</guid><description>Velvet Ant&apos;s ten-year persistence inside an air-gapped network is being reported as an extraordinary technical achievement. It isn&apos;t. It is a predictable consequence of substituting physical isolation for security architecture, and the organisations still treating air gaps as a primary control are making the same mistake that left a critical infrastructure network exposed for a decade.</description><pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate><category>air-gap</category><category>network-security</category><category>zero-trust</category><category>apt</category><category>velvet-ant</category><category>security-architecture</category></item><item><title>Your Most Trusted Tool Is Now Your Biggest Blind Spot: The RMM Security Problem</title><link>https://cipherwatch.io/commentary/2026-06-15-rmm-tools-trusted-attack-surface/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-15-rmm-tools-trusted-attack-surface/</guid><description>The SimpleHelp OIDC authentication bypass is the latest in a consistent pattern: remote monitoring and management tools — the software your IT team uses to fix problems — have become one of the primary entry points for sophisticated attackers. The reason is structural, and it won&apos;t be solved by patching one vendor at a time.</description><pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Your Internal Package Mirror Is Not a Supply Chain Defence</title><link>https://cipherwatch.io/commentary/2026-06-14-internal-mirrors-supply-chain-false-comfort/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-14-internal-mirrors-supply-chain-false-comfort/</guid><description>The Miasma supply chain campaign — which compromised publisher credentials to inject malicious code into legitimate packages including the Red Hat npm namespace — exposes a fundamental gap in how most organisations think about dependency security. Internal package mirrors provide real value against several attack classes, but credential compromise of legitimate publishers is not one of them.</description><pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate></item><item><title>The Week That Had Everything: June 2026 and What It Reveals About Enterprise Security Capacity</title><link>https://cipherwatch.io/commentary/2026-06-13-june-2026-biggest-security-week-of-year/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-13-june-2026-biggest-security-week-of-year/</guid><description>The week of 9–13 June 2026 delivered a record Microsoft Patch Tuesday, a CVSS 10.0 Ivanti exploit, a wormable Linux kernel proof-of-concept, Veeam and SAP critical advisories, and an accelerating ransomware worm across 66 countries. It was not a crisis — it was a normal week in 2026. That is the diagnosis.</description><pubDate>Sat, 13 Jun 2026 00:00:00 GMT</pubDate><category>security-operations</category><category>patch-tuesday</category><category>vulnerability-management</category><category>enterprise-security</category><category>ransomware</category><category>incident-response</category><category>security-capacity</category><category>risk-management</category></item><item><title>When Microsoft, SAP, Ivanti, and Palo Alto All Patch Critical Flaws on the Same Day, We Have a Coordination Problem</title><link>https://cipherwatch.io/commentary/2026-06-12-when-every-vendor-patches-at-once/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-12-when-every-vendor-patches-at-once/</guid><description>The week of 9 June 2026 delivered critical security patches from at least four major vendors on the same day, plus a Linux kernel PoC, plus a CISA KEV batch. The security community has created a coordination structure — Patch Tuesday — that has the opposite of its intended effect: it concentrates defender workload in a single week every month while giving attackers 30 predictable days to prepare.</description><pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate><category>patch-tuesday</category><category>vulnerability-management</category><category>coordinated-disclosure</category><category>sap</category><category>ivanti</category><category>microsoft</category><category>risk-management</category><category>enterprise-security</category></item><item><title>Vulnerability Management Is Failing Because the Volume Is Unmanageable. We Need to Admit It.</title><link>https://cipherwatch.io/commentary/2026-06-11-vulnerability-management-volume-crisis/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-11-vulnerability-management-volume-crisis/</guid><description>The June 2026 Patch Tuesday delivered 198 CVEs from one vendor in one day. Security teams also had to process concurrent critical advisories from SAP, Ivanti, Palo Alto, and CISA on the same day. The volume is not a temporary surge — it is the permanent state of software security. The current vulnerability management model is not designed for this scale and the consequences are being measured in ransomware payments.</description><pubDate>Thu, 11 Jun 2026 00:00:00 GMT</pubDate><category>vulnerability-management</category><category>patch-management</category><category>risk-management</category><category>security-operations</category><category>ransomware</category><category>cvss</category><category>enterprise-security</category><category>cisa-kev</category></item><item><title>198 CVEs in One Day. Something Has Gone Wrong With How We Do Patch Management.</title><link>https://cipherwatch.io/commentary/2026-06-09-patch-tuesday-june-2026-decision-fatigue/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-09-patch-tuesday-june-2026-decision-fatigue/</guid><description>Microsoft&apos;s June 2026 Patch Tuesday drops 198 vulnerabilities in a single Tuesday, including six zero-days and three CVSS 9.8 remote code execution flaws. Meanwhile SAP patches 21 flaws on the same day, Cisco issues a critical advisory, and a Linux kernel PoC goes public. The security community has normalised a monthly event so large that no enterprise team can actually process it — and that normalisation is itself the problem.</description><pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate><category>patch-tuesday</category><category>vulnerability-management</category><category>microsoft</category><category>risk-management</category><category>patch-management</category><category>enterprise-security</category><category>cvss</category><category>security-operations</category></item><item><title>VPN Gateways Are Where Ransomware Gets In. CVE-2026-50751 Is Not the Last One.</title><link>https://cipherwatch.io/commentary/2026-06-08-vpn-gateways-ransomware-entry-point-2026/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-08-vpn-gateways-ransomware-entry-point-2026/</guid><description>Check Point CVE-2026-50751 joins a long list of critical authentication bypass and remote code execution vulnerabilities in enterprise VPN gateways that have been exploited in ransomware campaigns. The pattern is consistent enough that it is no longer useful to treat each as a one-off incident — it is a structural category of risk that requires a structural response.</description><pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate><category>check-point</category><category>cve-2026-50751</category><category>vpn</category><category>ransomware</category><category>perimeter-security</category><category>patch-management</category><category>enterprise-risk</category></item><item><title>Why China-Nexus Actors Are Targeting Network Appliances — and Why Your EDR Won&apos;t Tell You</title><link>https://cipherwatch.io/commentary/2026-06-07-china-nexus-appliance-targeting-edr-gap/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-07-china-nexus-appliance-targeting-edr-gap/</guid><description>The BRICKSTORM BSD variant developed by VerdantBamboo is not a technical curiosity. It is evidence of a deliberate strategic investment by China-nexus threat actors in precisely the attack surface that most enterprise security programmes cannot see. Appliance-targeting is not the path of least resistance — it is the path of least detection.</description><pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate><category>china-nexus</category><category>apt</category><category>verdantbamboo</category><category>brickstorm</category><category>network-appliances</category><category>threat-intelligence</category><category>edr-gap</category><category>detection</category></item><item><title>The Smart TV Is a Network Device. Most Enterprises Have Not Noticed.</title><link>https://cipherwatch.io/commentary/2026-06-06-smart-tv-invisible-device-attack-surface/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-06-smart-tv-invisible-device-attack-surface/</guid><description>The revelation that free apps are enrolling Smart TVs as residential proxy exit nodes is not primarily a consumer privacy story. It is a network security story about a class of device that has proliferated across enterprise environments — conference rooms, executive suites, hotel rooms during business travel — without being managed as a network security asset.</description><pubDate>Sat, 06 Jun 2026 00:00:00 GMT</pubDate><category>smart-tv</category><category>iot-security</category><category>network-security</category><category>enterprise-risk</category><category>shadow-infrastructure</category><category>asset-management</category></item><item><title>The Third-Party Plugin Is the Perimeter Now — Magento Today, Your Stack Next</title><link>https://cipherwatch.io/commentary/2026-06-05-third-party-extension-plugin-universal-supply-chain-risk/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-05-third-party-extension-plugin-universal-supply-chain-risk/</guid><description>CVE-2026-45247 in the Mirasvit Magento extension continues a pattern that security teams have been watching for years: the attack surface of any complex platform is not defined by the core platform&apos;s security — it is defined by every third-party component installed on it. This is not a Magento problem. It is an architecture problem that affects every enterprise platform stack.</description><pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate><category>supply-chain</category><category>third-party-plugins</category><category>magento</category><category>extension-security</category><category>architecture</category><category>dependency-risk</category><category>attack-surface</category></item><item><title>CVE-2026-46243 and the Enterprise Linux Kernel Patch Lag Problem</title><link>https://cipherwatch.io/commentary/2026-06-04-linux-kernel-lts-patch-lag-enterprise-risk/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-04-linux-kernel-lts-patch-lag-enterprise-risk/</guid><description>The 19-year latency of CVE-2026-46243 makes headlines. What is less discussed is the operational lag between &apos;patch available&apos; and &apos;patch applied&apos; across enterprise Linux fleets. Distribution advisories are published. Patched kernels hit repositories. And then organisations schedule the reboots — often weeks later. CVE-2026-46243 is not unusual in its severity; it is unusual in making the patch lag visible.</description><pubDate>Thu, 04 Jun 2026 00:00:00 GMT</pubDate><category>linux</category><category>kernel</category><category>patch-management</category><category>cve-2026-46243</category><category>enterprise-security</category><category>vulnerability-management</category><category>security-culture</category></item><item><title>Healthcare Ransomware Is a Structural Problem. The Gentelman Surge Is Not a Surprise.</title><link>https://cipherwatch.io/commentary/2026-06-03-healthcare-ransomware-target-structural-not-cyclical/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-03-healthcare-ransomware-target-structural-not-cyclical/</guid><description>The Gentelman ransomware surge hitting healthcare this week follows a pattern that has repeated with near-mechanical regularity for five years. The security industry has correctly diagnosed the problem: legacy infrastructure, high willingness to pay, broad RMM attack surface, and regulatory environments that prioritise availability over security. The diagnosis is correct. The treatment is not happening fast enough.</description><pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate><category>ransomware</category><category>healthcare</category><category>gentelman</category><category>storm-2697</category><category>rmm</category><category>security-culture</category><category>critical-infrastructure</category></item><item><title>The ITSM Platform Is the Map to Your Infrastructure — and You&apos;ve Left It Unlocked</title><link>https://cipherwatch.io/commentary/2026-06-02-itsm-platforms-credential-goldmine-attack-surface/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-02-itsm-platforms-credential-goldmine-attack-surface/</guid><description>The ServiceNow API breach is the latest confirmation that IT Service Management platforms are among the highest-value targets in the enterprise. They contain everything an attacker needs to plan a targeted intrusion: network topology, patch status, change windows, and credentials. The industry&apos;s classification of these platforms as &apos;IT operations tools&apos; rather than &apos;sensitive data repositories&apos; is a governance error with real consequences.</description><pubDate>Tue, 02 Jun 2026 00:00:00 GMT</pubDate><category>servicenow</category><category>itsm</category><category>attack-surface</category><category>credential-security</category><category>data-governance</category><category>saas-security</category><category>enterprise-risk</category></item><item><title>Oracle&apos;s Quarterly CPU and the Enterprise Java Patching Culture That Makes WebLogic Vulnerabilities Sticky</title><link>https://cipherwatch.io/commentary/2026-06-01-oracle-cpu-enterprise-java-patching-culture/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-06-01-oracle-cpu-enterprise-java-patching-culture/</guid><description>CVE-2024-21182 was patched in January 2024. It reached the CISA KEV in June 2026. The 18-month gap is not unique to this CVE — it reflects how enterprise Java middleware is patched in practice, which is to say: slowly, incompletely, and often only under direct pressure.</description><pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate><category>oracle</category><category>weblogic</category><category>patch-management</category><category>enterprise-java</category><category>cpu-process</category><category>middleware-security</category><category>security-culture</category></item><item><title>When Everything Is Critical, Nothing Is: The CVSS Severity Inflation Problem</title><link>https://cipherwatch.io/commentary/2026-05-31-cvss-severity-inflation-everything-critical/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-31-cvss-severity-inflation-everything-critical/</guid><description>Q2 2026 has produced more CVSS 9.0+ vulnerabilities than most organisations can effectively respond to simultaneously. Part of the problem is the vulnerability itself. Part of the problem is that the CVSS scoring system has drifted toward higher scores over time, reducing the signal value of &apos;critical&apos; as a triage category.</description><pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate><category>cvss</category><category>vulnerability-management</category><category>risk-management</category><category>severity-scoring</category><category>patch-prioritisation</category><category>security-metrics</category></item><item><title>Netlogon Will Be Exploited Again. The Question Is Whether Your Architecture Has Changed Since Zerologon.</title><link>https://cipherwatch.io/commentary/2026-05-29-netlogon-windows-domain-auth-perennial-target/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-29-netlogon-windows-domain-auth-perennial-target/</guid><description>CVE-2026-41089 is the third significant Netlogon vulnerability with active exploitation in six years. Zerologon (CVE-2020-1472) prompted an industry-wide reckoning with domain controller exposure. If your DC network architecture has not materially changed since 2020, the reckoning was incomplete.</description><pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate><category>netlogon</category><category>active-directory</category><category>zerologon</category><category>domain-controller</category><category>network-segmentation</category><category>windows-security</category><category>enterprise-architecture</category></item><item><title>65 Days Unpatched: The Citrix NetScaler Exploitation Pattern Nobody Has Solved</title><link>https://cipherwatch.io/commentary/2026-05-28-citrix-exploitation-unpatched-appliances-patch-gap/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-28-citrix-exploitation-unpatched-appliances-patch-gap/</guid><description>CVE-2026-3055 was patched in March. In late May, Fortinet confirms large-scale exploitation of thousands of unpatched NetScaler appliances. This cycle has repeated with every major Citrix vulnerability for years. The gap between patch availability and patch deployment on network appliances is a structural problem with a known solution that the industry is not implementing.</description><pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate><category>citrix</category><category>netscaler</category><category>patch-management</category><category>network-appliances</category><category>cve-2026-3055</category><category>vulnerability-management</category></item><item><title>Developer Toolchains Are the New Perimeter — and the Industry Has Not Accepted It</title><link>https://cipherwatch.io/commentary/2026-05-27-developer-toolchain-supply-chain-inevitable-target/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-27-developer-toolchain-supply-chain-inevitable-target/</guid><description>Simultaneous CISA KEV additions for three developer toolchain compromises in one campaign makes the case explicitly: the software supply chain attack surface runs through the tools developers use, not just the code they write. The security industry is still catching up.</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate><category>supply-chain</category><category>developer-security</category><category>npm</category><category>vs-code</category><category>security-culture</category><category>threat-modeling</category></item><item><title>Apple&apos;s CVE Transparency Problem Is Also the Industry&apos;s CVE Transparency Problem</title><link>https://cipherwatch.io/commentary/2026-05-26-apple-cve-transparency-vendor-disclosure-norms/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-26-apple-cve-transparency-vendor-disclosure-norms/</guid><description>Apple routinely patches vulnerabilities without disclosing CVE IDs, adding them retroactively weeks later. This is criticised as a transparency failure. But Apple is not uniquely bad at this — it is doing what the industry&apos;s incentive structure rewards.</description><pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate><category>apple</category><category>cve-disclosure</category><category>transparency</category><category>vendor-security</category><category>patch-management</category><category>industry-norms</category></item><item><title>2026&apos;s Linux Kernel LPE Cluster Is Not Bad Luck — It Is a Research Dividend</title><link>https://cipherwatch.io/commentary/2026-05-25-linux-kernel-lpe-cluster-2026-systemic/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-25-linux-kernel-lpe-cluster-2026-systemic/</guid><description>Four significant Linux kernel local privilege escalation vulnerabilities in three months is a pattern worth examining. The kernel is not suddenly getting worse. Security research intensity is increasing, and the backlog of unaudited kernel subsystems is being worked through.</description><pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate><category>linux</category><category>kernel</category><category>privilege-escalation</category><category>vulnerability-research</category><category>security-debt</category><category>qualys</category><category>ptrace</category></item><item><title>UniFi in the Enterprise: When Prosumer Infrastructure Carries Production Risk</title><link>https://cipherwatch.io/commentary/2026-05-24-enterprise-wifi-security-unifi-prosumer-gap/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-24-enterprise-wifi-security-unifi-prosumer-gap/</guid><description>Three CVSS 10.0 vulnerabilities in Ubiquiti UniFi OS this week exposed a gap that has widened quietly over a decade: the growing presence of prosumer-grade networking in environments carrying enterprise data. The security posture of UniFi was not designed for the scrutiny those environments require.</description><pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate><category>ubiquiti</category><category>unifi</category><category>enterprise-security</category><category>network-security</category><category>wifi</category><category>risk-management</category><category>prosumer-infrastructure</category></item><item><title>WordPress Plugin Vulnerabilities Keep Hitting Enterprise Sites That Don&apos;t Know They&apos;re Enterprise Sites</title><link>https://cipherwatch.io/commentary/2026-05-23-wordpress-plugin-enterprise-security-ignored/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-23-wordpress-plugin-enterprise-security-ignored/</guid><description>Four CVSS 8.8 flaws in a 100,000-install WordPress membership plugin. The subscriber-to-admin escalation is technically straightforward. The real problem is not the code — it is that these WordPress deployments exist outside the security governance perimeter of the organisations that run them.</description><pubDate>Sat, 23 May 2026 00:00:00 GMT</pubDate><category>wordpress</category><category>cms-security</category><category>enterprise-governance</category><category>risk-management</category><category>plugin-security</category></item><item><title>Mass Open-Source Cryptography Advisories Are Becoming the New Normal — and the Industry Isn&apos;t Ready</title><link>https://cipherwatch.io/commentary/2026-05-22-mass-open-source-crypto-advisories-industry-unready/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-22-mass-open-source-crypto-advisories-industry-unready/</guid><description>The nine-CVE golang.org/x/crypto advisory follows a pattern that is accelerating: coordinated mass advisories in foundational open-source cryptographic libraries that affect thousands of downstream applications simultaneously. The industry&apos;s response tooling and processes have not kept pace with the advisory volume or the structural complexity of transitive dependency exposure.</description><pubDate>Fri, 22 May 2026 00:00:00 GMT</pubDate><category>open-source</category><category>supply-chain</category><category>cryptography</category><category>golang</category><category>dependency-management</category><category>sca</category><category>vulnerability-management</category></item><item><title>Two PAN-OS GlobalProtect Authentication Bypasses in Three Months Is a Pattern, Not a Coincidence</title><link>https://cipherwatch.io/commentary/2026-05-21-vpn-authentication-bypass-recurring-pattern/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-21-vpn-authentication-bypass-recurring-pattern/</guid><description>CVE-2026-0257, a second actively exploited Palo Alto Networks GlobalProtect authentication bypass in the same three-month window as CVE-2026-0300, is not bad luck. It reflects the structural dynamics of high-value attack surface concentration: when enterprise VPN infrastructure is widely deployed, highly privileged, and technically complex, it attracts sustained, focused research from both legitimate researchers and threat actors.</description><pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate><category>palo-alto</category><category>pan-os</category><category>globalprotect</category><category>vpn</category><category>vulnerability-research</category><category>zero-trust</category><category>security-architecture</category></item><item><title>AI Vector Databases Are the New Attack Surface Nobody Inventoried</title><link>https://cipherwatch.io/commentary/2026-05-20-ai-vector-databases-uninventoried-attack-surface/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-20-ai-vector-databases-uninventoried-attack-surface/</guid><description>ChromaDB CVE-2026-45829 is a specific vulnerability in one product. The underlying problem it exposes is structural: enterprise AI deployments are creating new categories of sensitive data storage that are not subject to the security controls applied to comparable databases. The vulnerability is fixable. The architectural gap is not fixed by a patch.</description><pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate><category>ai-security</category><category>vector-database</category><category>chromadb</category><category>rag-pipeline</category><category>security-architecture</category><category>asset-management</category></item><item><title>End-of-Life Equipment Is Not a Budget Problem — It&apos;s a Security Architecture Decision</title><link>https://cipherwatch.io/commentary/2026-05-19-eolife-equipment-budget-vs-security-architecture/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-19-eolife-equipment-budget-vs-security-architecture/</guid><description>The framing of end-of-life network equipment as a procurement or budget problem is systematically incorrect. EoL equipment with active CVEs is a deliberate security architecture choice to operate known-exploitable infrastructure. Treating it as such changes the conversation, the decision-makers involved, and the urgency applied.</description><pubDate>Tue, 19 May 2026 00:00:00 GMT</pubDate><category>end-of-life</category><category>security-architecture</category><category>risk-management</category><category>vpn</category><category>sonicwall</category><category>asset-management</category></item><item><title>The 90-Day Patch Clock Is a Threat Actor Countdown Timer — We Should Use It That Way</title><link>https://cipherwatch.io/commentary/2026-05-18-90-day-clock-threat-actor-countdown/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-18-90-day-clock-threat-actor-countdown/</guid><description>Pwn2Own&apos;s 90-day coordinated disclosure window is designed to give vendors time to patch. But for enterprise defenders, it is also a confirmed, public notice that specific classes of zero-day vulnerability exist in named products. Most organisations wait for the patch to act. The ones that prepare during the 90-day window have a meaningful advantage.</description><pubDate>Mon, 18 May 2026 00:00:00 GMT</pubDate><category>vulnerability-management</category><category>patch-management</category><category>coordinated-disclosure</category><category>pwn2own</category><category>enterprise-security</category></item><item><title>Hypervisor Escapes Should Change How Enterprise Architects Design Isolation — They Rarely Do</title><link>https://cipherwatch.io/commentary/2026-05-17-hypervisor-escapes-enterprise-isolation-design/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-17-hypervisor-escapes-enterprise-isolation-design/</guid><description>VMware ESXi cross-tenant code execution at Pwn2Own Berlin 2026 demonstrates again that virtualisation is not a security boundary. Yet enterprise architecture continues to treat hypervisor isolation as equivalent to physical isolation. The security implication of this assumption has been known for years and consistently under-acted upon.</description><pubDate>Sun, 17 May 2026 00:00:00 GMT</pubDate><category>virtualisation</category><category>vmware</category><category>esxi</category><category>hypervisor</category><category>architecture</category><category>isolation</category><category>cloud-security</category><category>pwn2own</category></item><item><title>AI at Pwn2Own Is an Admission: These Tools Were Never Secure</title><link>https://cipherwatch.io/commentary/2026-05-16-ai-pwn2own-category-security-admission/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-16-ai-pwn2own-category-security-admission/</guid><description>The addition of an AI products category at Pwn2Own Berlin 2026 — and its immediate success with five exploits across three vendors — is not evidence that AI tools are newly insecure. It is evidence that the security industry has finally started looking. The results are a lagging indicator of what has been deployed in enterprise environments for the past two years.</description><pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate><category>ai-security</category><category>pwn2own</category><category>developer-tools</category><category>sandbox-security</category><category>lm-studio</category><category>codex</category></item><item><title>Exchange Keeps Getting Exploited Because We Still Treat Email Infrastructure as Trusted</title><link>https://cipherwatch.io/commentary/2026-05-15-exchange-email-still-treated-as-trusted-infrastructure/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-15-exchange-email-still-treated-as-trusted-infrastructure/</guid><description>CVE-2026-42897 is the third actively exploited Exchange zero-day in fourteen months. Each time, the analysis focuses on the specific vulnerability. The more useful question is why email infrastructure continues to receive weaker security monitoring and network controls than VPN gateways and web servers, despite processing more untrusted content than any other enterprise system.</description><pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate><category>exchange</category><category>email-security</category><category>zero-day</category><category>threat-modelling</category><category>cve-2026-42897</category></item><item><title>Pwn2Own Proves the Software Is Breakable. Enterprise Patching Pretends It Isn&apos;t.</title><link>https://cipherwatch.io/commentary/2026-05-14-pwn2own-enterprise-patching-response-gap/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-14-pwn2own-enterprise-patching-response-gap/</guid><description>Pwn2Own Berlin Day 1 saw Windows 11 compromised three separate times, Edge&apos;s sandbox escaped, and two hypervisors defeated. Vendors will patch the reported bugs within 90 days. The enterprise response to Pwn2Own results is almost universally: nothing. We treat demonstrated zero-days as vendor problems until they become CVEs, and we treat CVEs as patch management problems until they become incidents.</description><pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate><category>pwn2own</category><category>vulnerability-research</category><category>patch-management</category><category>zero-day</category><category>enterprise-security</category></item><item><title>BitLocker Gives You Compliance, Not Security Against Determined Attackers</title><link>https://cipherwatch.io/commentary/2026-05-13-bitlocker-compliance-not-security-yellowkey/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-13-bitlocker-compliance-not-security-yellowkey/</guid><description>The YellowKey BitLocker bypass demonstrates what practitioners have known for years: BitLocker deployed in its default TPM-only configuration satisfies regulatory checkboxes but does not protect against an adversary with physical access or WinRE trigger capability. The compliance requirement and the security requirement are not the same thing, and conflating them leaves organisations with an expensive false assurance.</description><pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate><category>bitlocker</category><category>encryption</category><category>compliance</category><category>endpoint-security</category><category>full-disk-encryption</category></item><item><title>The &apos;No Zero-Days&apos; Headline Is Teaching Defenders the Wrong Lesson About Patch Tuesday</title><link>https://cipherwatch.io/commentary/2026-05-12-no-zero-days-headline-misleads-patch-tuesday/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-12-no-zero-days-headline-misleads-patch-tuesday/</guid><description>Every month that Microsoft&apos;s Patch Tuesday contains no actively exploited zero-days, security coverage softens and patching urgency drops. This framing optimises for the wrong signal — it measures whether attackers have already acted, not whether they are about to. May&apos;s Patch Tuesday has 120 vulnerabilities including a wormable DNS RCE, but the dominant headline will be the absence of zero-days.</description><pubDate>Tue, 12 May 2026 00:00:00 GMT</pubDate><category>patch-tuesday</category><category>vulnerability-management</category><category>risk-management</category><category>security-operations</category></item><item><title>The Risk Calculus Changed Today</title><link>https://cipherwatch.io/commentary/2026-05-11-ai-developed-exploits-risk-calculus-changed/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-11-ai-developed-exploits-risk-calculus-changed/</guid><description>Google&apos;s confirmation of the first AI-developed zero-day used in live exploitation is not a warning about the future. It is a statement about the present. The security industry&apos;s habit of treating AI-assisted exploitation as a &apos;horizon threat&apos; just ran out of runway.</description><pubDate>Mon, 11 May 2026 00:00:00 GMT</pubDate><category>ai-security</category><category>zero-day</category><category>threat-intelligence</category><category>risk-management</category><category>exploitation</category></item><item><title>Post-Quantum Cryptography: The Decision Is Not Whether to Migrate, It Is When to Start Counting</title><link>https://cipherwatch.io/commentary/2026-05-10-post-quantum-now-vs-later-decision/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-10-post-quantum-now-vs-later-decision/</guid><description>Proton Mail&apos;s post-quantum encryption launch is another data point in an accelerating migration across email, messaging, and enterprise security platforms. The industry debate has shifted from &apos;should we?&apos; to &apos;how urgent is the harvest-now-decrypt-later threat?&apos; For most organisations the answer is more urgent than their current roadmap reflects — because the data being generated today has a longer confidentiality requirement than the planning horizon that informs most security investment decisions.</description><pubDate>Sun, 10 May 2026 00:00:00 GMT</pubDate><category>post-quantum</category><category>cryptography</category><category>pqc</category><category>ml-kem</category><category>migration</category><category>nist</category><category>harvest-now-decrypt-later</category><category>long-term-security</category></item><item><title>AI Platforms Inherited the npm Trust Model and Its Problems Are Arriving on Schedule</title><link>https://cipherwatch.io/commentary/2026-05-09-ai-platform-trust-model-broken-huggingface/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-09-ai-platform-trust-model-broken-huggingface/</guid><description>A fake OpenAI repository reached #1 trending on Hugging Face and delivered an infostealer to 244,000 users. This was predictable. The AI/ML developer ecosystem adopted the open-publishing, community-trust model of package registries without adopting the hard-won security lessons those registries learned over the past decade. The attack surface Hugging Face presents in 2026 looks remarkably like the attack surface npm presented in 2016.</description><pubDate>Sat, 09 May 2026 00:00:00 GMT</pubDate><category>ai-security</category><category>hugging-face</category><category>supply-chain</category><category>trust-model</category><category>developer-security</category><category>platform-security</category></item><item><title>Developer Credentials Are the New Supply Chain Entry Point and the Industry Has Not Caught Up</title><link>https://cipherwatch.io/commentary/2026-05-08-developer-credential-theft-new-supply-chain-vector/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-08-developer-credential-theft-new-supply-chain-vector/</guid><description>QLNX&apos;s Linux RAT specifically harvests npm tokens, PyPI credentials, and cloud provider keys to enable malicious package publishing under the compromised developer&apos;s identity. This is not a new threat — it is a threat that has been escalating systematically for three years while the defensive response has been fragmented. The combination of credential-based package publishing and minimal post-publish scrutiny makes the developer credential the most valuable initial access target in software supply chain attacks.</description><pubDate>Fri, 08 May 2026 00:00:00 GMT</pubDate><category>supply-chain</category><category>developer-security</category><category>npm</category><category>pypi</category><category>credential-theft</category><category>package-registry</category><category>software-development-security</category></item><item><title>The ICS Security Debt Is Now in the Middleware Layer, Not Just the PLCs</title><link>https://cipherwatch.io/commentary/2026-05-07-ics-security-debt-industrial-middleware-platforms/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-07-ics-security-debt-industrial-middleware-platforms/</guid><description>Eclipse BaSyx&apos;s CVSS 10.0 vulnerability is not a story about old OT equipment running Windows XP. It is a story about new, modern, actively maintained open-source ICS infrastructure that was deployed rapidly into Industry 4.0 architectures without the security scrutiny that its network position demands. The security debt in operational technology environments has migrated upward — into the integration and orchestration layer that connects IT and OT.</description><pubDate>Thu, 07 May 2026 00:00:00 GMT</pubDate><category>ics</category><category>ot-security</category><category>industry-4</category><category>asset-administration-shell</category><category>eclipse-basyx</category><category>security-architecture</category><category>middleware</category></item><item><title>Attackers Discovered That Developer Tools Make Better C2 Infrastructure Than Their Own Servers</title><link>https://cipherwatch.io/commentary/2026-05-06-legitimate-developer-tools-attack-infrastructure/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-06-legitimate-developer-tools-attack-infrastructure/</guid><description>KidsProtect&apos;s use of VS Code Remote Tunnels and Discord webhooks for command-and-control is not a stalkerware quirk — it is the latest example of a systematic shift toward legitimate cloud services as attack infrastructure. When defenders cannot block VS Code tunnels without breaking developer workflows, the standard network-layer controls that security architecture depends on stop working.</description><pubDate>Wed, 06 May 2026 00:00:00 GMT</pubDate><category>c2-infrastructure</category><category>developer-tools</category><category>vscode-tunnel</category><category>discord-abuse</category><category>detection-evasion</category><category>network-monitoring</category><category>zero-trust</category></item><item><title>Seven Thousand Ransomware Victims in a Year and We&apos;re Still Surprised Every Time</title><link>https://cipherwatch.io/commentary/2026-05-05-ransomware-seven-thousand-victims-still-surprised/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-05-ransomware-seven-thousand-victims-still-surprised/</guid><description>Fortinet&apos;s 2026 threat landscape report documents 7,831 confirmed ransomware victims last year — nearly five times the 2024 figure. The industry will spend a week discussing what this means. Then a new disclosure will arrive, and the conversation will move on. The problem is not that we lack threat intelligence. The problem is that threat intelligence is not changing behaviour fast enough to matter.</description><pubDate>Tue, 05 May 2026 00:00:00 GMT</pubDate><category>ransomware</category><category>threat-intelligence</category><category>security-programme-design</category><category>risk-management</category><category>manufacturing</category><category>incident-response</category></item><item><title>Managed File Transfer Is a Permanent Attack Surface and You Should Treat It That Way</title><link>https://cipherwatch.io/commentary/2026-05-04-managed-file-transfer-permanent-attack-surface/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-04-managed-file-transfer-permanent-attack-surface/</guid><description>MOVEit&apos;s latest critical vulnerability is not a surprise — it is the latest instalment in an unending series. The industry keeps treating each managed file transfer vulnerability as an exceptional event requiring exceptional response, when the correct model is to treat MFT platforms as inherently hostile internet-facing infrastructure requiring architectural controls that assume compromise is inevitable.</description><pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate><category>managed-file-transfer</category><category>moveit</category><category>attack-surface</category><category>architecture</category><category>zero-trust</category><category>patching</category></item><item><title>Defenders Can&apos;t Block Google. That&apos;s Why Attackers Are Routing Through It.</title><link>https://cipherwatch.io/commentary/2026-05-03-legitimate-cloud-infrastructure-attack-delivery-rail/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-03-legitimate-cloud-infrastructure-attack-delivery-rail/</guid><description>AccountDumpling abuses Google AppSheet to deliver phishing. EtherRAT uses Cloudflare and Ethereum nodes for C2. DEEP#DOOR tunnels over Cloudflare. The pattern is consistent: sophisticated attackers have discovered that the fastest route past enterprise security controls is through infrastructure defenders cannot block. The defence posture that assumes blocking bad infrastructure will stop bad traffic is being systematically rendered obsolete.</description><pubDate>Sun, 03 May 2026 00:00:00 GMT</pubDate><category>cloud-security</category><category>phishing</category><category>c2</category><category>saas-abuse</category><category>detection</category><category>security-architecture</category></item><item><title>The Patch-to-Exploit Window Has Collapsed — cPanel in 48 Hours Is Not an Anomaly, It&apos;s the New Baseline</title><link>https://cipherwatch.io/commentary/2026-05-02-patch-release-to-mass-exploitation-window-collapsed/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-02-patch-release-to-mass-exploitation-window-collapsed/</guid><description>The &apos;Sorry&apos; ransomware group compromised 44,000 cPanel servers within 48 hours of a critical patch release. The industry still plans patch cycles in weeks. These two realities are incompatible, and the gap between them is where organisations keep getting destroyed.</description><pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate><category>patch-management</category><category>vulnerability-management</category><category>ransomware</category><category>cpanel-whm</category><category>remediation-velocity</category></item><item><title>AI Didn&apos;t Make Attackers Smarter — It Removed the Barrier That Was Keeping Them Small</title><link>https://cipherwatch.io/commentary/2026-05-01-ai-augmented-threat-actors-scale-barrier/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-05-01-ai-augmented-threat-actors-scale-barrier/</guid><description>DPRK&apos;s AI-generated npm malware campaign is not remarkable because AI made it more sophisticated. It&apos;s remarkable because AI let a small team produce something that would previously have required many more people to build and maintain. The scale constraint on supply chain attacks has just changed fundamentally.</description><pubDate>Fri, 01 May 2026 00:00:00 GMT</pubDate><category>dprk</category><category>ai-security</category><category>supply-chain</category><category>threat-intelligence</category><category>attacker-economics</category><category>npm</category></item><item><title>Your Security Tools Are the Crown Jewels — Attackers Already Know This</title><link>https://cipherwatch.io/commentary/2026-04-30-security-monitoring-infrastructure-as-attack-target/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-30-security-monitoring-infrastructure-as-attack-target/</guid><description>A remote code execution vulnerability in Wazuh&apos;s SIEM platform is a reminder that security monitoring infrastructure is among the highest-value targets in any enterprise environment. Most security programmes defend it like a server, not like a choke point that controls visibility across the entire estate.</description><pubDate>Thu, 30 Apr 2026 00:00:00 GMT</pubDate><category>siem</category><category>xdr</category><category>wazuh</category><category>security-operations</category><category>monitoring-infrastructure</category><category>defence-in-depth</category></item><item><title>The Model Context Protocol&apos;s Security Debt Is Already Piling Up</title><link>https://cipherwatch.io/commentary/2026-04-29-mcp-security-debt-model-context-protocol/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-29-mcp-security-debt-model-context-protocol/</guid><description>MCP&apos;s rapid enterprise adoption has outpaced its security design. The protocol was built to solve an integration problem, not a security one — and the debt is accumulating faster than the ecosystem can audit it.</description><pubDate>Wed, 29 Apr 2026 00:00:00 GMT</pubDate><category>mcp</category><category>ai-security</category><category>supply-chain</category><category>protocol-security</category><category>llm</category><category>commentary</category></item><item><title>Security Awareness Training Was Built to Spot Bad Phishing — AI Has Made That Irrelevant</title><link>https://cipherwatch.io/commentary/2026-04-28-security-awareness-training-broken-ai-fraud/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-28-security-awareness-training-broken-ai-fraud/</guid><description>The FTC&apos;s $2.1 billion social media fraud figure is not a user education failure. It is evidence that the threat model security awareness training was designed for no longer exists. AI-generated fraud does not produce the observable cues our training teaches users to detect — and the industry needs to acknowledge this before it spends another decade on the wrong solution.</description><pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate><category>security-awareness</category><category>social-engineering</category><category>ai-fraud</category><category>phishing</category><category>user-training</category></item><item><title>Managed Identity Is the New Local Admin — and Most Enterprises Haven&apos;t Noticed</title><link>https://cipherwatch.io/commentary/2026-04-27-managed-identity-new-local-admin/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-27-managed-identity-new-local-admin/</guid><description>CVE-2026-26117 in the Azure Arc agent is not just a patching story. It reveals that managed identity has quietly become the most powerful unguarded credential in enterprise infrastructure. We dismantled local admin accounts and hardcoded passwords over the past decade — and then rebuilt the same concentration of privilege under a different name, with even less monitoring attached.</description><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><category>managed-identity</category><category>privilege-escalation</category><category>cloud-security</category><category>azure-arc</category><category>identity-access-management</category></item><item><title>Lockfiles Don&apos;t Protect You When the Maintainer Is the Threat</title><link>https://cipherwatch.io/commentary/2026-04-26-lockfiles-dont-protect-against-maintainer-compromise/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-26-lockfiles-dont-protect-against-maintainer-compromise/</guid><description>Three npm supply chain attacks in a single week — Axios, @bitwarden/cli, and CanisterSprawl — have been met with the same industry response: update your lockfile. This is wrong. When the original maintainer account is compromised, a new legitimate-signed version is published, and lockfiles pin to whatever is current, the entire model breaks down. The industry is treating a trust infrastructure failure as a dependency hygiene problem.</description><pubDate>Sun, 26 Apr 2026 00:00:00 GMT</pubDate><category>supply-chain</category><category>npm</category><category>developer-security</category><category>trust-model</category><category>package-signing</category></item><item><title>The 13-Hour Problem: Your AI Inference Infrastructure Is Already a Tier-One Target</title><link>https://cipherwatch.io/commentary/2026-04-25-ai-inference-13-hour-exploitation-window/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-25-ai-inference-13-hour-exploitation-window/</guid><description>LMDeploy was exploited 13 hours after its RCE vulnerability was disclosed. Langflow took 20 hours. Marimo lasted days. The pattern is not bad luck — it is the predictable consequence of treating AI inference infrastructure as development tooling while exposing it like a production web server. The window for getting ahead of this has closed.</description><pubDate>Sat, 25 Apr 2026 00:00:00 GMT</pubDate><category>ai-security</category><category>llm-infrastructure</category><category>vulnerability-management</category><category>attack-surface</category><category>exploit-development</category></item><item><title>AI Inference Frameworks Are a First-Class Attack Surface — and Most Enterprises Are Treating Them Like Research Tools</title><link>https://cipherwatch.io/commentary/2026-04-24-ai-inference-frameworks-new-attack-surface/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-24-ai-inference-frameworks-new-attack-surface/</guid><description>Two critical AI inference framework vulnerabilities disclosed this week — one exploited within 13 hours, one scoring CVSS 9.8 — reveal an uncomfortable truth: the AI toolchain has become enterprise infrastructure, but most security programmes are still treating it like a research curiosity. That gap is now being actively exploited.</description><pubDate>Fri, 24 Apr 2026 00:00:00 GMT</pubDate><category>ai-security</category><category>vulnerability-management</category><category>software-development-security</category><category>commentary</category></item><item><title>TeamPCP Has Now Hit Every Developer Distribution Channel. The Pipeline Is the Perimeter.</title><link>https://cipherwatch.io/commentary/2026-04-24-developer-toolchain-supply-chain-every-channel/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-24-developer-toolchain-supply-chain-every-channel/</guid><description>In six weeks, one supply chain threat group has successfully backdoored GitHub Actions, PyPI, npm, Docker Hub, and the VS Code Marketplace. The security industry&apos;s response has been to treat each incident as a separate patching problem. It isn&apos;t. It&apos;s a systematic demonstration that the developer distribution stack has no defence-in-depth, and that the security controls the industry has built — SCA, SBOM, SAST — operate at entirely the wrong layer.</description><pubDate>Fri, 24 Apr 2026 00:00:00 GMT</pubDate><category>supply-chain</category><category>software-security</category><category>developer-security</category><category>devops</category><category>ci-cd</category><category>npm</category><category>docker</category></item><item><title>When Ransomware Deploys via Group Policy, You Were Already Owned</title><link>https://cipherwatch.io/commentary/2026-04-23-gpo-ransomware-means-domain-already-lost/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-23-gpo-ransomware-means-domain-already-lost/</guid><description>The Gentlemen ransomware group&apos;s use of Group Policy Objects to distribute encryption payloads domain-wide is not just a clever tactic — it&apos;s a forensic signal. GPO deployment requires Domain Admin access. The ransomware event you detected was not the attack. It was the end of an attack that was already over.</description><pubDate>Thu, 23 Apr 2026 00:00:00 GMT</pubDate><category>ransomware</category><category>active-directory</category><category>detection</category><category>incident-response</category><category>threat-hunting</category><category>enterprise-security</category></item><item><title>The Hallucination Problem in Your AI Security Tools Is Not Getting Fixed</title><link>https://cipherwatch.io/commentary/2026-04-23-transformer-limits-security-ai-hallucination-ceiling/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-23-transformer-limits-security-ai-hallucination-ceiling/</guid><description>A new paper by Vishal Sikka and Varin Sikka uses settled computational complexity theory to prove that transformer hallucinations and fixed reasoning depth are architectural facts, not engineering failures. For security practitioners building operational dependencies on LLM-based tools, the implication is uncomfortable: the limitations most vendors are implicitly promising to train away cannot be trained away. They are proven.</description><pubDate>Thu, 23 Apr 2026 00:00:00 GMT</pubDate><category>ai-security</category><category>llm</category><category>threat-detection</category><category>security-operations</category><category>risk-management</category></item><item><title>AI Has Learned to Find Bugs Faster Than We Can Fix Them</title><link>https://cipherwatch.io/commentary/2026-04-22-ai-discovers-bugs-faster-than-we-fix-them/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-22-ai-discovers-bugs-faster-than-we-fix-them/</guid><description>Claude Mythos discovering thousands of zero-days confirms what was already theoretically obvious: AI vulnerability research is orders of magnitude faster than human-paced remediation. The industry&apos;s response — private disclosure programmes — is a delay mechanism, not a solution to the structural asymmetry between discovery speed and patch deployment speed.</description><pubDate>Wed, 22 Apr 2026 00:00:00 GMT</pubDate><category>ai-security</category><category>vulnerability-management</category><category>zero-day</category><category>patch-management</category><category>threat-landscape</category><category>risk-governance</category></item><item><title>The Shared Responsibility Model Is a Liability Shield, Not a Security Framework</title><link>https://cipherwatch.io/commentary/2026-04-19-saas-shared-responsibility-is-a-lie/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-19-saas-shared-responsibility-is-a-lie/</guid><description>McGraw Hill&apos;s statement that its Salesforce breach &apos;appears to be part of a broader issue involving a misconfiguration within Salesforce&apos;s environment&apos; exposes what the shared responsibility model actually is: a contractual arrangement that tells you who to blame after a breach, not a security control that prevents one.</description><pubDate>Sun, 19 Apr 2026 00:00:00 GMT</pubDate><category>saas</category><category>shared-responsibility</category><category>cloud-security</category><category>salesforce</category><category>data-breach</category><category>third-party-risk</category><category>commentary</category></item><item><title>Patch Tuesday Is Not a Patching Programme</title><link>https://cipherwatch.io/commentary/2026-04-15-patch-tuesday-is-not-a-patching-programme/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-15-patch-tuesday-is-not-a-patching-programme/</guid><description>Every second Tuesday, the industry runs a collective sprint to triage, test, and deploy hundreds of Microsoft patches before the next cycle begins. We call this a patching programme. It isn&apos;t. It&apos;s a treadmill — and the real security question is whether we&apos;re measuring the right thing.</description><pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate><category>patch-management</category><category>vulnerability-management</category><category>microsoft</category><category>risk-prioritisation</category><category>compliance</category></item><item><title>Security Awareness Training Is Solving the Wrong Problem</title><link>https://cipherwatch.io/commentary/2026-04-15-security-awareness-training-wrong-problem/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-15-security-awareness-training-wrong-problem/</guid><description>We spend billions every year teaching employees not to click malicious links. The same employees work in environments where clicking a malicious link can collapse the company. The problem isn&apos;t the clicking.</description><pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate><category>security-awareness</category><category>human-factors</category><category>secure-design</category><category>phishing</category><category>user-risk</category></item><item><title>TOTP MFA Is Security Theatre and We Need to Admit It</title><link>https://cipherwatch.io/commentary/2026-04-13-totp-mfa-is-security-theatre/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-13-totp-mfa-is-security-theatre/</guid><description>Adversary-in-the-Middle toolkits that defeat time-based one-time passwords are commercially available for under £400. The security industry&apos;s continued recommendation of TOTP as meaningful phishing protection is not a minor technical nuance — it is a significant misrepresentation of what MFA actually protects against in 2026.</description><pubDate>Mon, 13 Apr 2026 00:00:00 GMT</pubDate><category>mfa</category><category>totp</category><category>fido2</category><category>passkeys</category><category>phishing</category><category>aitm</category><category>identity-security</category><category>authentication</category></item><item><title>The CISO Role Is Structurally Broken — and Fixing It Requires Honesty About Why</title><link>https://cipherwatch.io/commentary/2026-04-12-ciso-role-is-broken/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-12-ciso-role-is-broken/</guid><description>The average CISO tenure is 18 to 26 months. We treat this as a talent pipeline problem. It isn&apos;t. It&apos;s a governance problem that the industry has been unwilling to name clearly for fifteen years.</description><pubDate>Sun, 12 Apr 2026 00:00:00 GMT</pubDate><category>ciso</category><category>governance</category><category>risk-management</category><category>leadership</category><category>accountability</category><category>board</category></item><item><title>The Threat Intelligence Report That Nobody Reads</title><link>https://cipherwatch.io/commentary/2026-04-10-threat-intelligence-nobody-reads/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-10-threat-intelligence-nobody-reads/</guid><description>Most organisations have a threat intelligence subscription. Fewer have a threat intelligence programme. The gap between the two is not a budget problem — it is a clarity problem about what intelligence is actually for, and it costs the industry significantly in both money and security posture.</description><pubDate>Fri, 10 Apr 2026 00:00:00 GMT</pubDate><category>threat-intelligence</category><category>security-operations</category><category>soc</category><category>siem</category><category>ioc</category><category>risk-management</category><category>cti</category></item><item><title>Vendor Security Ratings Are a Confidence Trick — And We Keep Buying Them</title><link>https://cipherwatch.io/commentary/2026-04-10-vendor-security-ratings-are-fiction/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-10-vendor-security-ratings-are-fiction/</guid><description>The third-party security ratings industry has built a billion-dollar business on a simple premise: that an outside-in scan of your suppliers&apos; infrastructure tells you something meaningful about their security posture. It doesn&apos;t. And the gap between what these tools imply and what they deliver is creating a false sense of supply chain security in boardrooms everywhere.</description><pubDate>Fri, 10 Apr 2026 00:00:00 GMT</pubDate><category>third-party-risk</category><category>supply-chain</category><category>vendor-risk</category><category>security-ratings</category><category>governance</category><category>due-diligence</category></item><item><title>Ransomware in Healthcare Is a Patient Safety Crisis, Not an IT Problem</title><link>https://cipherwatch.io/commentary/2026-04-09-ransomware-healthcare-patient-safety/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-09-ransomware-healthcare-patient-safety/</guid><description>The ransomware attack on ChipSoft paralysing 80% of Dutch hospitals and the Anubis attack on Signature Healthcare this week are not data breach incidents with clinical inconvenience as a side effect. They are patient safety events. The healthcare sector&apos;s continued treatment of ransomware as a cybersecurity problem rather than a clinical risk is costing lives.</description><pubDate>Thu, 09 Apr 2026 00:00:00 GMT</pubDate><category>ransomware</category><category>healthcare</category><category>security-risk-management</category><category>incident-response</category><category>risk</category><category>critical-infrastructure</category></item><item><title>BYOVD Is a Commodity Technique Now — Your EDR Vendor Knows</title><link>https://cipherwatch.io/commentary/2026-04-07-byovd-edr-is-not-enough/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-07-byovd-edr-is-not-enough/</guid><description>Qilin&apos;s Warlock toolkit, capable of disabling over 300 security tools using Bring Your Own Vulnerable Driver techniques, is not a nation-state capability — it is an affiliate-accessible ransomware tool. EDR is a necessary control. It is not a sufficient one, and the industry&apos;s marketing has outpaced what the technology can actually guarantee.</description><pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate><category>endpoint-security</category><category>edr</category><category>byovd</category><category>ransomware</category><category>security-operations</category><category>detection-engineering</category></item><item><title>Active Directory Keeps Getting Owned Because We Keep Letting It</title><link>https://cipherwatch.io/commentary/2026-04-05-why-active-directory-keeps-getting-owned/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-05-why-active-directory-keeps-getting-owned/</guid><description>A Kerberos authentication bypass and an Active Directory privilege escalation were both patched this week, adding to a multi-year catalogue of critical flaws in Microsoft&apos;s foundational identity infrastructure. The problem is not that Microsoft keeps shipping vulnerabilities — it is that organisations keep deploying Active Directory in configurations that maximise their exposure when those vulnerabilities arrive.</description><pubDate>Sun, 05 Apr 2026 00:00:00 GMT</pubDate><category>identity-access-management</category><category>kerberos</category><category>active-directory</category><category>authentication</category><category>windows</category><category>privilege-escalation</category></item><item><title>Ransomware Has Industrialised — Your Response Strategy Probably Has Not</title><link>https://cipherwatch.io/commentary/2026-04-02-ransomware-industrialised-response-has-not/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-04-02-ransomware-industrialised-response-has-not/</guid><description>Qilin&apos;s 131 confirmed victims in March alone is not a spike — it is what a mature criminal enterprise operating at scale looks like. The ransomware ecosystem has industrialised completely, with dedicated development, HR, and affiliate management functions. Enterprise response strategies built for a different threat model are overdue for review.</description><pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate><category>ransomware</category><category>security-operations</category><category>incident-response</category><category>security-risk-management</category><category>threat-intelligence</category></item><item><title>AI Infrastructure Is Accumulating Security Debt Faster Than Anyone Admits</title><link>https://cipherwatch.io/commentary/2026-03-31-ai-infrastructure-security-debt/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-03-31-ai-infrastructure-security-debt/</guid><description>LangFlow&apos;s actively exploited remote code execution vulnerability and this week&apos;s LiteLLM supply chain attack are not isolated incidents — they are early symptoms of an ecosystem that has scaled faster than its security practices. Organisations deploying AI infrastructure are inheriting technical debt they have not yet been asked to account for.</description><pubDate>Tue, 31 Mar 2026 00:00:00 GMT</pubDate><category>ai-security</category><category>supply-chain</category><category>software-development-security</category><category>open-source</category><category>llm</category><category>risk</category></item><item><title>Your CI/CD Pipeline Is Now a Primary Attack Surface</title><link>https://cipherwatch.io/commentary/2026-03-27-cicd-pipeline-primary-attack-surface/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-03-27-cicd-pipeline-primary-attack-surface/</guid><description>Two supply chain attacks this week — one against a widely-used vulnerability scanner, another poisoning an AI framework via PyPI — targeted the tools developers trust without question. CI/CD pipelines and open-source tooling are not peripheral attack surfaces. They are the path of least resistance into production.</description><pubDate>Fri, 27 Mar 2026 00:00:00 GMT</pubDate><category>supply-chain</category><category>devsecops</category><category>cicd</category><category>software-development-security</category><category>open-source</category><category>sbom</category></item><item><title>The KEV List Is Not a Vulnerability Management Strategy</title><link>https://cipherwatch.io/commentary/2026-03-25-kev-list-not-vulnerability-management/</link><guid isPermaLink="true">https://cipherwatch.io/commentary/2026-03-25-kev-list-not-vulnerability-management/</guid><description>CISA&apos;s Known Exploited Vulnerabilities catalogue has become the de facto patch priority list for thousands of organisations — most of whom had no coherent strategy before it arrived. Treating the KEV list as a vulnerability management programme is a category error that leaves organisations systematically exposed to everything that has not yet been exploited.</description><pubDate>Wed, 25 Mar 2026 00:00:00 GMT</pubDate><category>vulnerability-management</category><category>cisa</category><category>kev</category><category>security-risk-management</category><category>patch-management</category><category>risk</category></item></channel></rss>