<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ty Zeno on Medium]]></title>
        <description><![CDATA[Stories by Ty Zeno on Medium]]></description>
        <link>https://medium.com/@tyz_89492?source=rss-2a044bb9278b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ZLTCIyRKxZAYyDdr</url>
            <title>Stories by Ty Zeno on Medium</title>
            <link>https://medium.com/@tyz_89492?source=rss-2a044bb9278b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:51:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tyz_89492/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Most Threat Intelligence Products Are Selling You Content]]></title>
            <link>https://medium.com/@tyz_89492/most-threat-intelligence-products-are-selling-you-content-b38a4b4ec4d5?source=rss-2a044bb9278b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b38a4b4ec4d5</guid>
            <category><![CDATA[intelligence]]></category>
            <category><![CDATA[soc]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[content-marketing]]></category>
            <dc:creator><![CDATA[Ty Zeno]]></dc:creator>
            <pubDate>Thu, 28 May 2026 01:26:38 GMT</pubDate>
            <atom:updated>2026-05-28T03:56:05.408Z</atom:updated>
            <content:encoded><![CDATA[<p>I have been reviewing the TENEX.AI Signal this week. <a href="https://www.linkedin.com/pulse/tenexsignal-05262026-tenex-ai-wq1xe/">https://www.linkedin.com/pulse/tenexsignal-05262026-tenex-ai-wq1xe/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/1*dGZ63Rh1muYCRIHloIpitQ.png" /></figure><p>Real incidents. Solid sourcing. The recommendations section restates what you should have done. Before I explain what that means, let me explain the difference between content, information, and intelligence.</p><p>Content is the road sign that says “accident ahead.” It’s real and you can see it yourself and so it’s now sourced. Information is knowing the accident is at mile marker 47, a jackknifed semi, left two lanes blocked, reported 22 minutes ago. Now you have context. You know what happened and roughly what it looks like. Intelligence is your GPS rerouting you before you hit the backup. It looked at the same accident, then looked at where you are, where you’re going, and what time it is, and told you to take exit 31 right now.</p><p>Back to the Signal brief. In the example I used above, reviewing this product is like sitting in traffic near mile marker 47 while someone tells you that you should have taken exit 31. The recommendations section reads:</p><ul><li>“Audit your third-party dependencies.”</li><li>“Enforce code-signing verification.”</li><li>“Restrict unapproved extensions enterprise-wide.”</li></ul><p>Every one of those recommendations predates the incidents in the product by years and is already a de facto standard. They are not derived from the analysis. They are a justified list. The incidents are used to support recommendations that already existed, not to generate new ones.</p><p>The code-signing recommendation is the clearest failure. Two items, one week apart:</p><p><strong>May 21, 2026:</strong> Fox Tempest, a Cybercrime-as-a-Service operation active since May 2025, weaponized Microsoft’s Artifact Signing infrastructure to sell signed malware enabling Rhysida, Qilin, INC, BlackByte, and Akira ransomware deployments. The threat actor likely used stolen US and Canadian identities to pass identity validation, generating 72-hour certificates.</p><p><strong>May 26, 2026:</strong> Enforce code-signing verification.</p><p>How should I use a company’s policies to enforce code-signing verification and, if I do that correctly, how does that protect me from the threat I was warned about only one week ago? Fox Tempest didn’t use unsigned code from unknown publishers. It used real Microsoft-issued certificates obtained by passing identity verification with fraudulent credentials. A verified signature from an authorized publisher was the trust signal being exploited. A recommendation that doesn’t survive contact with the incident it appears alongside isn’t finished analysis. It’s a checkbox.</p><h3>What Intelligence Looks Like: Fox Tempest</h3><p>Here is what I derive from this one incident.</p><h3>Treat short-validity certificates as a detection signal, not a trust confirmation.</h3><p>Legitimate software vendors do not sign production builds with certificates issued hours before deployment. A 72-hour validity window is operationally normal for a threat actor who needs to rotate before revocation. It is anomalous for an enterprise software release cycle. Your EDR and code-integrity logs almost certainly capture certificate validity windows. Hunt for binaries signed with certificates issued within 96 hours of first execution, particularly from publisher identities not in your approved software inventory.</p><h3>Decouple “signed” from “trusted.”</h3><p>Fox Tempest passed Microsoft’s identity validation. The signature was real. The trust chain was intact. Any control that treats a valid signature as a terminal trust decision needs a second condition: is this publisher identity expected in this environment, and has it appeared before? Signature verification is necessary. It is no longer sufficient.</p><h3>Cross-reference the affiliated ransomware groups.</h3><p>Fox Tempest served Rhysida, Qilin, INC, BlackByte, and Akira. If any of those groups are already in your threat profile, and for most mid-to-large enterprises they should be, exploitation of valid certificates is now a relevant initial access vector for your environment specifically. That changes the priority on reviewing recently signed binaries from unfamiliar publishers and tightens the case for auditing your software acquisition pipeline against identity-validation weaknesses.</p><p>The recommendation “enforce code-signing verification” was already written before Fox Tempest existed. It will still be written after the next campaign exploits the same trust model. That’s the problem.</p><h3>Fox Tempest: Malware-Signing-as-a-Service</h3><p>Primary source is Microsoft’s own security blog and Microsoft On the Issues blog, both published May 19, 2026. The $5,000–$9,000 pricing, 72-hour certificate validity, and signspace[.]cloud domain are confirmed in Microsoft’s complaint and independently corroborated by BleepingComputer, The Record, SecurityWeek, Hacker News, and SC World.</p><p>One clarification on the framing: Artifact Signing (formerly Azure Trusted Signing) is a legitimate developer signing service. Fox Tempest abused it by using stolen or synthetic US/Canadian identities to pass identity verification and obtain legitimate certificates, rather than exploiting a vulnerability in the service itself. This distinction matters for IR and policy discussions.</p><h3>SOC Team Resources</h3><ul><li><strong>Microsoft Threat Intelligence primary analysis: </strong><a href="https://www.microsoft.com/en-us/security/blog/2026/05/19/exposing-fox-tempest-a-malware-signing-service-operation/">https://www.microsoft.com/en-us/security/blog/2026/05/19/exposing-fox-tempest-a-malware-signing-service-operation/</a> — Contains the attack chain from malvertising through signed installer to Oyster backdoor to Rhysida deployment. Confirmed malware families: Oyster/Broomstick, Lumma Stealer, Vidar, Rhysida.</li><li><strong>Microsoft On the Issues (legal/policy): </strong><a href="https://blogs.microsoft.com/on-the-issues/2026/05/19/disrupting-fox-tempest-a-cybercrime-service/">https://blogs.microsoft.com/on-the-issues/2026/05/19/disrupting-fox-tempest-a-cybercrime-service/</a> — Documents the Vanilla Tempest co-conspirator relationship, FBI and Europol partnership, and Microsoft’s observation of Fox Tempest attempting to shift customers to an alternate signing service. The service is disrupted but not eliminated.</li><li><strong>BleepingComputer: </strong><a href="https://www.bleepingcomputer.com/news/security/cybercrime-service-disrupted-for-abusing-microsoft-platform-to-sign-malware/">https://www.bleepingcomputer.com/news/security/cybercrime-service-disrupted-for-abusing-microsoft-platform-to-sign-malware/</a> — Covers certificate revocation scope (1,000+), the VM evolution in February 2026, and specific ransomware group connections.</li><li><strong>The Record: </strong><a href="https://therecord.media/microsoft-disrupts-fox-tempest-malware-signing-service">https://therecord.media/microsoft-disrupts-fox-tempest-malware-signing-service</a> — Additional context on delivery mechanism: malicious Teams, AnyDesk, PuTTY, and Webex installers distributed via legitimately purchased ads.</li><li><strong>Cybersecurity News: </strong><a href="https://cybersecuritynews.com/fox-tempest-abuse-microsoft-artifact-signing/">https://cybersecuritynews.com/fox-tempest-abuse-microsoft-artifact-signing/</a> — Documents Cloudzy-hosted VM infrastructure from February 2026 onward, metadata.json and PowerShell automation scripts, and the Resecurity partnership in the takedown.</li></ul><h3>Confirmed IOCs</h3><ul><li><strong>Seized domain: </strong>signspace[.]cloud (redirects to Microsoft seizure notice)</li><li><strong>Malware families distributed: </strong>Oyster (also known as Broomstick, CleanUpLoader), Lumma Stealer, Vidar</li><li><strong>Ransomware families enabled: </strong>Rhysida, Qilin, INC, BlackByte, Akira</li><li><strong>Ransomware operators confirmed using service: </strong>Vanilla Tempest, Storm-0501, Storm-2561, Storm-0249</li><li><strong>Delivery mechanism: </strong>Trojanized MSTeamsSetup.exe (and AnyDesk, PuTTY, Webex variants) via malvertising</li><li><strong>Certificate type: </strong>Short-lived, 72-hour validity, Microsoft-issued via Artifact Signing</li><li><strong>Certificate volume: </strong>Over 1,000 certificates revoked by Microsoft</li><li><strong>VM infrastructure provider: </strong>Cloudzy (from February 2026 onward)</li><li><strong>Geographic targeting: </strong>US, France, India, China, Brazil, Germany, Japan, UK, Italy, Spain</li></ul><h3>SOC Hunting Priorities</h3><ul><li>In endpoint telemetry, search for execution of MSTeamsSetup.exe, AnyDesk-Setup.exe, PuTTY-Setup.exe, or webex-setup.exe from browser download directories or temp paths where the binary is signed but the signing certificate has a validity period of 72 hours or less. Standard legitimate installers do not use short-lived certificates.</li><li>In email and web proxy logs, search for downloads of installer files from domains that are not the official vendor download pages for Teams (teams.microsoft.com), AnyDesk (anydesk.com), PuTTY (putty.org), or Webex (webex.com). Malvertising redirects users to typosquat or lookalike pages.</li><li>In EDR process trees, search for MSTeamsSetup.exe or similar installer spawning cmd.exe, PowerShell, or wscript.exe as child processes. Legitimate installer behavior does not include spawning shell interpreters as children.</li><li>For Oyster/Broomstick specifically: search for CleanUpLoader artifacts. The backdoor establishes persistent remote access and initiates C2 communications. Network-level hunting should look for persistent low-frequency beaconing to non-Microsoft infrastructure from hosts where Teams was recently installed.</li><li>Search certificate transparency logs or your EDR’s certificate telemetry for code-signing certificates issued within the past 90 days by Microsoft Artifact Signing / Azure Trusted Signing against any binary executed in your environment. Certificates issued to Fox Tempest’s fraudulent identities will have been revoked, but binaries may have already been executed before revocation.</li></ul><h3>IR Team Resources</h3><ul><li><strong>Microsoft Security Blog (primary IR reference): </strong><a href="https://www.microsoft.com/en-us/security/blog/2026/05/19/exposing-fox-tempest-a-malware-signing-service-operation/">https://www.microsoft.com/en-us/security/blog/2026/05/19/exposing-fox-tempest-a-malware-signing-service-operation/</a> — Contains the full attack chain and confirms that Microsoft has revoked all 1,000+ certificates. First step is to determine whether any Fox Tempest-signed binaries executed in your environment before revocation.</li><li><strong>SecurityWeek: </strong><a href="https://www.securityweek.com/microsoft-disrupts-malware-signing-service-run-by-fox-tempest/">https://www.securityweek.com/microsoft-disrupts-malware-signing-service-run-by-fox-tempest/</a> — Confirms ransomware family associations (Rhysida, INC, Qilin, Akira) and sector targeting (healthcare, education, government, financial services).</li><li><strong>Axios: </strong><a href="https://www.axios.com/2026/05/19/microsoft-fox-tempest-law-enforcement-takedown">https://www.axios.com/2026/05/19/microsoft-fox-tempest-law-enforcement-takedown</a> — Geographic targeting footprint. If your organization operates in the US, France, India, China, Brazil, Germany, Japan, UK, Italy, or Spain, you are within the confirmed victim population.</li><li><strong>BleepingComputer: </strong><a href="https://www.bleepingcomputer.com/news/security/cybercrime-service-disrupted-for-abusing-microsoft-platform-to-sign-malware/">https://www.bleepingcomputer.com/news/security/cybercrime-service-disrupted-for-abusing-microsoft-platform-to-sign-malware/</a> — Vanilla Tempest attack chain (malvertising to signed Teams installer to Oyster to Rhysida) provides the most complete playbook for IR teams assessing a potential Rhysida deployment.</li></ul><h3>IR Scope and Sequencing</h3><ol><li><strong>Binary audit: </strong>Search all endpoints for the presence of trojanized installer files and any binaries signed with short-lived Microsoft Artifact Signing certificates issued after May 2025. Certificate revocation has occurred but does not remove already-executed payloads.</li><li><strong>Oyster/Broomstick hunt: </strong>If any suspicious installer execution is found, immediately hunt for Oyster backdoor artifacts. Oyster establishes persistent remote access before ransomware delivery. Containing Oyster before ransomware deployment is the priority.</li><li><strong>Lateral movement assessment: </strong>If Oyster is found, treat the incident as a pre-ransomware intrusion. Vanilla Tempest’s observed timeline from initial access to ransomware deployment is not publicly quantified from this campaign, but the presence of Oyster means the actor has persistent access and the clock is running.</li><li><strong>Certificate revocation verification: </strong>Confirm through your EDR or endpoint management platform that the revoked certificates are being enforced. Windows certificate revocation checking behavior varies by configuration; environments with OCSP stapling disabled or CRL caching may not immediately reflect revocation status.</li></ol><h3>IR Anti-Patterns</h3><ul><li>Treating this as a resolved threat because Microsoft seized signspace[.]cloud. Microsoft’s On the Issues blog explicitly notes they observed Fox Tempest attempting to shift operations to an alternate signing service. The infrastructure is disrupted; the capability is not permanently disabled. Any organization that discovered a Fox Tempest-signed binary in their environment should treat the actor as potentially still active.</li><li>Assuming that certificate revocation means previously signed binaries cannot execute. Revocation prevents new trust evaluation, but already-executed payloads that have established persistence are not affected by certificate revocation. IR scope must extend to hunting for persistence mechanisms, not just blocking future execution.</li></ul><h3>Prior Incident Context</h3><p>Vanilla Tempest was previously targeted by Microsoft in October 2025. Rhysida has a documented prior high-profile impact record: the British Library data theft and Seattle-Tacoma International Airport disruption are attributed operations. The reuse of Rhysida by multiple ransomware-as-a-service operators demonstrates the RaaS model’s capacity to amplify a single ransomware family’s reach across diverse sectors.</p><h3>Business Operations Value</h3><ol><li><strong>Code-signing certificates from trusted authorities are no longer a reliable security signal for enterprise software. </strong>Fox Tempest obtained legitimate Microsoft-issued certificates by fraudulently passing identity verification. The certificates that allowed malware to impersonate Teams and AnyDesk were not forged: they were real certificates issued to fraudulent identities. Any policy that permits execution of signed software without additional verification is operating on a trust model this operation has structurally undermined. Policy implication: user training that instructs employees to verify software is “signed” or “verified” must be updated. The signing status of a binary is insufficient; the download source and delivery path are equally critical controls.</li><li><strong>The $5,000–$9,000 price point industrializes ransomware deployment for unsophisticated operators. </strong>Before services like Fox Tempest, bypassing code-signing controls required either technical sophistication or access to stolen certificates. At $5,000–$9,000 per engagement, this barrier is eliminated for any ransomware affiliate with minimal resources. Microsoft documented this enabling Rhysida, Qilin, INC, BlackByte, and Akira deployments across healthcare, education, government, and financial services. Policy implication: the financial calculus for ransomware attacks against mid-market targets has changed. Organizations that previously assumed they were too small to attract sophisticated threat actors should reassess that assumption.</li><li><strong>The healthcare, education, and government sector targeting pattern reflects deliberate adversary selection for maximum coercive pressure. </strong>Vanilla Tempest specifically targeted schools and hospitals. These sectors face the highest regulatory and operational pressure to pay ransoms because system downtime directly affects patient care and student safety. The targeting is not opportunistic: it reflects structured adversary decision-making that weighs restoration payout against attack difficulty. Policy implication: healthcare and education organizations operating on-premise infrastructure should treat Fox Tempest-associated ransomware families (Rhysida, Qilin, INC, BlackByte, Akira) as active and elevated threats to their environments, not historical incidents affecting other sectors.</li><li><strong>Microsoft’s seizure of Fox Tempest infrastructure does not eliminate the risk. </strong>Microsoft’s own disclosure states that Fox Tempest was observed attempting to redirect customers to a replacement signing service following the takedown. The disruption imposes operational cost and friction; it does not remove the capability from the threat landscape. Policy implication: incident response planning that treats law enforcement takedowns as resolved threats creates dangerous gaps. The capability to sign malware with legitimate certificates existed before Fox Tempest and will exist after it.</li></ol><p><strong>Real intelligence narrows the decision space.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b38a4b4ec4d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Was It So Hard to Find the Truth? The Frustration of Portraying SNAP’s Real Faces]]></title>
            <link>https://medium.com/@tyz_89492/why-was-it-so-hard-to-find-the-truth-the-frustration-of-portraying-snaps-real-faces-a18a702c3bf3?source=rss-2a044bb9278b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a18a702c3bf3</guid>
            <category><![CDATA[demographics]]></category>
            <category><![CDATA[government-shutdown]]></category>
            <category><![CDATA[food-insecurity]]></category>
            <category><![CDATA[stereotypes]]></category>
            <category><![CDATA[journalism-ethics]]></category>
            <dc:creator><![CDATA[Ty Zeno]]></dc:creator>
            <pubDate>Wed, 29 Oct 2025 17:08:54 GMT</pubDate>
            <atom:updated>2025-10-29T17:08:54.357Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0pPt2h0PTHSH7tBxgsqAZw.png" /><figcaption><em>Dragnet</em>, the 1960s police TV show, featuring Sgt. Joe Friday</figcaption></figure><p>I find myself overwhelmed with the problems we keep making. This paradox exploded today when my news feed flashed the headline: “42 million Americans to lose food aid as shutdown hits day 28.” That headline by itself should send warning alarms to everyone in the country.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*s1U_sz5TLCeCTZ_Ymup6_A.jpeg" /><figcaption>Mountaineer Food Bank distribution in West Virginia</figcaption></figure><p>But right under that warning, there’s a photo designed — intentionally or not — to offer false comfort to some readers. It’s an image sourced from NBC News, showing only Black Americans receiving food assistance. Suddenly, the message for millions of viewers is, “Well, it’s not harming me or people like me. It’s only harming them, I guess. I shouldn’t be as upset.” And my frustration explodes again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*2kNizS4sBdbIJiQp2m3VTQ.png" /><figcaption><em>Volunteers distribute bread and groceries at a food pantry as food assistance demand rises during the U.S. government shutdown.<br>Credit: NBC News</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/1*_ZDQ23jNZzOy94NUNnSflQ.png" /><figcaption>States with the highest SNAP use in 2024</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/1*PG2thU7guPS2hdJxrduKnA.png" /><figcaption>Race Breakdown by State</figcaption></figure><p>This is not a subtle issue. That image choice is specifically used to fuel the comfortable lie , the myth that SNAP is “white tax dollars going to Black people.” It’s not just a myth. By using the headline and picture together it’s a misleading information statement designed to lead those who don’t read further to the assumption that food assistance mostly benefits Black Americans. While this is factually and ethically wrong, it becomes the lens through which many, especially in the headline-and-meme-driven audience to conclude, “It’s still okay for the government to be shutdown and for those second-class citizens to go without the basics for survival.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*qF6s5tz9AsKL60MWkeVyFQ.jpeg" /><figcaption>Mountaineer Food Bank distribution in West Virginia</figcaption></figure><p>Finding a photo , one actually reflecting who is most affected by the SNAP crisis was, frankly, infuriating. Why is it so hard? When searching for images of food assistance in America, national outlets and wire services overwhelmingly default to the same lazy, misleading visual trope: photos of Black families or individuals in line at food banks. It’s as if editors, producers, and content managers simply grab whatever stock image is easiest, or even worse , let their biases pick the most “clickable” representation, regardless of the truth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/0*NbZuVTeL7nvVk5lp" /><figcaption>RALEIGH, N.C. (WNCN) 17 News</figcaption></figure><p>Let’s be clear: In West Virginia, Louisiana, and Alabama, the people most affected by SNAP cuts are overwhelmingly white, rural, and working-class. Yet trying to find a news photo, a wire photo — any “mainstream” visual — of this reality is like looking for a needle in a haystack. I had to dig through local Facebook pages and community posts just to find an honest, recent, dignified photo like the one above — real people, real demographics, real need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vIKRqEYT_nNAxCwa.jpg" /><figcaption><a href="https://westvirginiawatch.com/2025/10/24/im-very-scared-snap-benefits-delay-worries-wv-elderly-who-use-it-to-feed-themselves-grandkids/">https://westvirginiawatch.com</a> Copyright: Michael Salerno Photography</figcaption></figure><p>So here’s the question we should all be asking:<br>Why is this so hard? Why is it so easy, so lazy, for the national media to perpetuate the stereotype of “Black poverty” as the face of food assistance, but so difficult to find and use images that accurately represent the states and people most reliant on these programs? This is a problem that faces all Americans, not “others” or “them” or insert term that people use and everyone understands like “welfare queens”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*Qc-Iogkvm6DxuFR7.jpg" /><figcaption>Baldwin County Alabama, Angels food pantry</figcaption></figure><p>And, let’s really get uncomfortable for a second:<br>Where are the images of people in line for food aid wearing “MAGA” hats or Trump apparel? We know from voting data and state demographics that many of the communities hit hardest by SNAP cuts are the same ones that overwhelmingly supported shutting down the very government programs they depend on. The silence or editorial avoidance around this reality is as telling as the choice of images.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*VG4jGFrLWYkzQXlN" /><figcaption><a href="https://www.azquotes.com/">https://www.azquotes.com/</a></figcaption></figure><p>It’s an injustice, not just to the people in need but to everyone who deserves to know the truth about America’s safety net: who it really supports, and what those faces genuinely look like. The truth takes work. Too many people working in industries that should be telling facts aren’t willing to do it. That perpetuates the lie, and we’re all the worse off for it.</p><p>One final thought.</p><p>I spent my fare share of running in formation yelling “Don’t let your shipmate dangle in the dirt!” We don’t all have the same morals and outlooks but this article comes from mine that was instilled in me though the US Navy. Honor. Courage. Commitment. I still believe in my Sailors Creed:</p><p><em>I am a United States Sailor.<br>I will support and defend the Constitution of the United States of America<br>and I will obey the orders of those appointed over me.<br>I represent the fighting spirit of the Navy and those who have gone before me<br>to defend freedom and democracy around the world.<br>I proudly serve my country’s Navy combat team with Honor, Courage, and Commitment.<br>I am committed to excellence and the fair treatment of all.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sOzhJeID_-oMP0O_.jpg" /></figure><p>No shame if you need help. There are great people still helping because it is the right thing to do. <a href="https://www.feedingamerica.org/find-your-local-foodbank">https://www.feedingamerica.org/find-your-local-foodbank</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a18a702c3bf3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Acceleration of Cyber Risk: Criminal Economies, Corporate Dependencies, and Systemic Pressure]]></title>
            <link>https://medium.com/@tyz_89492/the-acceleration-of-cyber-risk-criminal-economies-corporate-dependencies-and-systemic-pressure-963ee94be8c9?source=rss-2a044bb9278b------2</link>
            <guid isPermaLink="false">https://medium.com/p/963ee94be8c9</guid>
            <category><![CDATA[ransomware]]></category>
            <category><![CDATA[cyber-insurance]]></category>
            <category><![CDATA[trends]]></category>
            <category><![CDATA[cyber-risk]]></category>
            <dc:creator><![CDATA[Ty Zeno]]></dc:creator>
            <pubDate>Fri, 22 Aug 2025 20:00:29 GMT</pubDate>
            <atom:updated>2025-10-22T16:48:06.630Z</atom:updated>
            <content:encoded><![CDATA[<p>Cyber risk is not growing in a straight line.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Sdb8YNIRmNWX0VBm" /><figcaption>Verizon DBIR</figcaption></figure><p>Every meaningful dataset points to acceleration — exposure, frequency, and severity all climbing at exponential rates. That trajectory doesn’t just signal a rise in losses; it reflects the expansion of the criminal economy itself. What we are witnessing is the maturation of cybercrime as a service market, where attacks scale like a business model, and where dependencies are exploited in ways that create systemic effects far beyond any single target.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/0*y40ucxd_lAnSDIxj" /><figcaption>2024 Guy Carpenter Global Cyber Industry Insights</figcaption></figure><p>The first trend is the shift in exposure from the US to global markets. Guy Carpenter’s relativity data shows that while US premium growth has been steady, international growth is exploding. This mirrors the global expansion of criminal activity. Cybercriminals do not operate in a US-only context; they follow opportunity. Emerging economies with uneven defenses, fragmented regulations, and less mature insurance oversight are fertile ground. Just as insurers diversify their portfolios, criminal actors diversify their hunting grounds, seeking maximum return with minimal interference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mLNeqZ-JlGzO4Or-" /><figcaption>BlackFog State of Ransomware</figcaption></figure><p>The second trend is ransomware frequency. BlackFog’s data confirms what every operator already knows: ransomware has industrialized. Attacks have tripled since 2020, and the rise is steep. But behind those numbers is an ecosystem — ransomware-as-a-service platforms, initial access brokers, laundering networks — that all profit when the volume of attacks grows. We saw this clearly with Colonial Pipeline. That attack wasn’t just about one pipeline company; it exposed how a single ransomware affiliate, backed by an ecosystem of enablers, could hold a portion of a country’s infrastructure hostage. The disruption extended far beyond the ransom note. It forced federal intervention, triggered fuel shortages, and drew law enforcement attention that reached into the broader criminal supply chain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l6EgYhqlmyVdZwx6" /><figcaption>Verizon DBIR</figcaption></figure><p>The third trend is breach severity. Verizon’s DBIR shows that containment is failing: what once were minor intrusions now routinely escalate into breaches. By 2025, more than half of incidents are expected to end in confirmed compromise. That escalation reflects a criminal market that is not only scaling in frequency but also optimizing for depth. When attackers break in, they monetize every dependency available — regulatory exposure, litigation, supply chain disruption, reputational harm. The <em>Change Healthcare</em> attack is the latest proof. It wasn’t just one company paying a ransom; it was one third of the American population’s healthcare transactions grinding to a halt. That magnitude of impact didn’t just pressure the company; it forced the federal government, regulators, and insurers into the response. Law enforcement pressure moved beyond a single ransomware group and into the broader criminal economy itself.</p><p>When we connect these threads, the picture becomes clearer. Cybercrime is no longer about isolated gangs cashing out Bitcoin wallets. It is an ecosystem that mirrors legitimate markets — services, partnerships, profit incentives — while targeting dependencies that guarantee leverage. Every successful systemic attack rebalances the risk-reward equation for both sides. Criminals probe for weaknesses that maximize profit. Companies and insurers scramble to limit exposure while sustaining operations. Governments step in when the impact crosses into national security or economic stability.</p><p>This is why cyber insurance can no longer model cyber as if it were a traditional line of attritional losses. The trends we see in global exposure, rising ransomware frequency, and escalating breach rates are symptoms of a larger structural reality: cyber insurance should be modeling and underwriting against a functioning, global criminal economy. That economy does not just exploit vulnerabilities; it exploits dependencies. The more interconnected the target, the more powerful the leverage.</p><p>The lesson is direct. If we treat each incident in isolation, we miss the systemic forces at work. Colonial Pipeline, Change Healthcare, and countless less-publicized cases show that the “as-a-service” criminal market is targeting dependencies that ripple through industries, supply chains, and even entire countries. Insurers, regulators, and enterprises must model these risks not just as probabilities, but as predictable outputs of an economy designed to maximize profit while spreading risk across its participants.</p><p>Cyber has reached the point where it behaves like a natural catastrophe — but unlike hurricanes, this storm has a business plan.</p><h3>Defining the term “Cyber Insurance” in This Publication</h3><p>When I use the word <strong>“cyber”</strong> in this publication, I am not trying to make the subject sound exotic or futuristic. The term is often used as a catch-all buzzword for anything involving computers, networks, or technology. Here, I use it in a straightforward sense: <strong>it refers to risks that arise directly from the use of technology on business operations.</strong></p><p>When I use the word <strong>“insurance,”</strong> I mean it in its traditional sense: a contract that shifts or shares responsibility for losses between parties. Nothing more, nothing less. Insurance is about agreeing in advance how to distribute burdens, financial or otherwise, when problems happen, so no single entity bears the entire cost alone.</p><p>And when I use the phrase <strong>“cyber insurance,”</strong> I am talking specifically about insurance products designed to address the risks created by technology use. That includes ransomware, business interruption from outages, data breaches, regulatory fines, and other technology-driven events that can cascade into financial loss.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=963ee94be8c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Legitimate Use, Catastrophic Loss: The Insurance Risk Hiding in Plain Sight]]></title>
            <link>https://medium.com/@tyz_89492/legitimate-use-catastrophic-loss-the-insurance-risk-hiding-in-plain-sight-31af645eb0cd?source=rss-2a044bb9278b------2</link>
            <guid isPermaLink="false">https://medium.com/p/31af645eb0cd</guid>
            <category><![CDATA[cyber-risk]]></category>
            <category><![CDATA[risk-modeling]]></category>
            <category><![CDATA[cyber-insurance]]></category>
            <category><![CDATA[insurance]]></category>
            <category><![CDATA[cloud-security]]></category>
            <dc:creator><![CDATA[Ty Zeno]]></dc:creator>
            <pubDate>Mon, 21 Apr 2025 17:16:54 GMT</pubDate>
            <atom:updated>2025-04-21T17:16:54.069Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vqx9J-d0nnudfCTbfU1v_A.jpeg" /></figure><h4>What if the next catastrophic cyber loss doesn’t come from an exotic exploit — but from the tools we use every day, behaving exactly as designed?</h4><p>That’s the emerging threat shaping today’s cloud risk landscape. Over the past year, ransomware operators have quietly evolved their tactics — not by discovering new vulnerabilities, but by abusing legitimate cloud services like AWS S3. Their goal? To exploit trusted infrastructure, using it exactly as intended, to lock organizations out of their own environments.</p><p>This isn’t theoretical. This is operational. Recent ransomware campaigns show attackers using stolen AWS credentials to encrypt data through Server-Side Encryption with Customer-Provided Keys (SSE-C). There’s no malware. No exfiltration. No alert from endpoint detection and response (EDR). Just native API calls — and business-critical data rendered inaccessible unless a ransom is paid.</p><p>These are zero-visibility campaigns; attacks that leave no forensic fingerprints, no malware signatures, and no alert trail. They bypass traditional controls not by hiding, but by blending in — using cloud-native tools as intended to create loss from within.</p><p>These are not passive events. They are deliberate, adversary-driven campaigns. The criminal economy is shifting toward cloud-native extortion models because they are:</p><ul><li>Low risk — no exploit needed</li><li>High reward — immediate operational impact</li><li>Nearly invisible — legitimate feature usage evades traditional detection</li></ul><h4>Current Activities: Criminal Campaigns Targeting AWS S3</h4><p>In an era where cloud infrastructure forms the backbone of modern enterprise, the threats have adapted to match the moment. What was once the realm of brute-force intrusion has given way to something quieter, more insidious — a form of digital sabotage executed not through exotic exploits, but through the silent manipulation of tools already inside the gates.</p><p>The criminal syndicate known as <em>Codefinger</em> has emerged as an emblem of this transformation. Leveraging <a href="https://www.theregister.com/2025/01/13/ransomware_crew_abuses_compromised_aws/">Amazon Web Services’ Server-Side Encryption with Customer-Provided Keys (SSE-C)</a>, they do not exfiltrate data or trigger alarms. Instead, with <a href="https://hackread.com/mass-ransomware-campaign-s3-buckets-stolen-aws-keys/">stolen AWS credentials</a>, they encrypt a company’s own information using the platform’s legitimate features — locking victims out of their S3 buckets and demanding ransom in exchange for the decryption keys. The victims are not given time to deliberate. They face a seven-day deadline before their data is irrevocably deleted. What makes this method chilling is not its sophistication, but its simplicity. The tools were there all along.</p><p>Meanwhile, in the forgotten corners of the cloud, another danger brews. Researchers have uncovered how attackers exploit <a href="https://labs.watchtowr.com/8-million-requests-later-we-made-the-solarwinds-supply-chain-attack-look-amateur/">abandoned S3 buckets</a> — assets once used and since left untended, yet still referenced by live systems. Like squatters occupying a house left unlocked, adversaries re-register these buckets and weaponize them. What follows is a quiet corruption: <a href="https://www.techtarget.com/searchstorage/tip/Why-Amazon-S3-is-a-ransomware-target-and-how-to-protect-it">poisoned software updates, phishing infrastructure, and supply chain compromises</a> that ripple outward across networks.</p><p>And yet, even vigilance may not be enough when default behaviors betray security. Studies from <a href="https://securityboulevard.com/2025/03/veriti-research-uncovers-malware-exploiting-cloud-services/">Veriti Research</a> reveal that over 40% of enterprise networks maintain default “any/any” access rules to major cloud providers. Malware strains such as <a href="https://hackread.com/hackers-exploit-cloud-misconfigurations-spread-malware/">XWorm and Sliver C2</a> thrive in this permissive environment, establishing command-and-control channels with ease, bypassing perimeter defenses, and moving laterally within networks that never saw them coming.</p><p>Layered atop this is a shift in the very vectors of compromise. According to <a href="https://cybernews.com/security/identity-based-attacks-most-prevalent/">Cisco Talos</a>, 60% of cybersecurity incidents in 2024 stemmed not from technical vulnerabilities, but from identity-based attacks. In this new order, the battle for access is waged not through exploitation of code, but through theft of trust — stolen credentials, leaked keys, and mismanaged identity and access management (IAM) policies. The adversary no longer needs to sneak in through a crack in the wall; they simply walk through the front door, carrying the right credentials.</p><p>These events are not outliers. They are not anomalies. They are the pattern — the campaign — of an adversary learning to operate within the very systems built to keep them out.</p><h4>Veteran Perspective: Cyber Operations Meets Insurance Analytics</h4><p>After decades in national cyber operations and intelligence — and now years modeling cyber insurance risk — I see a troubling convergence: attackers are no longer just breaching systems — they are systematically attacking trust itself. They’re weaponizing the very infrastructure, services, and controls organizations rely on.</p><p>These attacks are strategic — not incidental. The use of AWS’s Server-Side Encryption with Customer-Provided Keys (SSE-C) isn’t a misconfiguration; it’s a functional compromise. The system works as designed, but it assumes only legitimate actors hold the keys. Credential theft shatters that assumption.</p><p>The criminal economy now mirrors FinTech logic. Attackers outsource capabilities, share access, and monetize tooling at scale. These are no longer improvisations — they are productized campaigns, engineered to scale, repeat, and profit.</p><p>To a cyber operator, these aren’t anomalies — they’re campaign signatures: repeatable, tested, and tailored to evade detection. They work. They’re low effort, high reward. And defenders are struggling to see them.</p><p>These developments raise critical questions for insurers and modelers:</p><ul><li>Are you treating these as isolated technical failures — or as systemic collapses of trust?</li><li>Have you mapped how functional dependencies — like reliance on SSE-C — translate into real-world business interruption?</li><li>Most importantly: are your financial models prepared for when trust itself becomes the attack surface?</li></ul><p>These events must be understood not just technically, but as insured cyber events (ICEs) with systemic capital implications.</p><p>The most dangerous attacks no longer breach walls — they pass through gates, with keys we issued, in systems we trusted. That’s not a breach. That’s a failure born of assumption.</p><h4>The Insurance Lens: Why This Becomes an ICE</h4><p><strong>1. This Is an Adversary Campaign<br></strong>This is where cyber risk becomes an insurable loss. What starts as a technical incident — credential theft, re-used buckets, misconfigured cloud access — can become an insured cyber event (ICE) when the consequence reaches the threshold of economic damage, policy language, and client dependency.</p><p>These campaigns do not operate in isolation. They are designed for replication. They scale horizontally across victims and vertically across business functions. From a modeling perspective, this changes the nature of risk: these are not anomalies; they are aggregating patterns.</p><p>So the questions shift:</p><ul><li>Do your models account for events without exploits?</li><li>Are you rating clients based on cloud posture, not just endpoint defense?</li><li>Can you identify shared service dependencies — like AWS S3 — across policyholders?</li></ul><p>The risk is not only technical. It is economical. It is systemic. And it is already operational. For insurance professionals, the call is not to predict the exploit — but to model the effect.</p><p><strong>2. Why It Evades Traditional Modeling<br></strong>There’s no perimeter breach. No exploit. No exfiltration. Many risk models still depend on those flags. The result: a scenario that causes policy-triggering loss but remains underpriced, misclassified, or overlooked in accumulation.</p><p><strong>3. Examples of Financial Exposure:</strong></p><ul><li><strong>Ransomware</strong>: Encrypted S3 buckets = BI, restoration costs, ransom negotiations</li><li><strong>Supply Chain Disruption</strong>: Poisoned updates via hijacked buckets = third-party liability</li><li><strong>Data Breach</strong>: Public S3 exposure = regulatory fines, legal defense, brand harm</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*Dv6awz9_E8Oj1_Jtfi8RDQ.png" /></figure><h4>Strategic Recommendations for Insurers</h4><p>History has shown that crises rarely arrive with new tools; rather, they emerge from old tools used in new and dangerous ways. And so it is with cyber risk. The same features that enable speed, scale, and efficiency in cloud environments have now become the pathways of peril. Insurers must respond — not with fear, but with clarity.</p><p><strong>First</strong>, treat functional abuse not as a one-off, but as a class of peril. The misuse of SSE-C, IAM sprawl, or public bucket inheritance should be modeled with the same gravity as a malware outbreak. These are campaign techniques, not outliers. Their scale and repeatability warrant systemic treatment.</p><p><strong>Second</strong>, integrate real-time cloud posture into risk scoring. The age of relying solely on annual checklists is over. IAM entropy, key leakage, exposed buckets — these are not static metrics. They fluctuate. And underwriting must adapt to track them dynamically.</p><p><strong>Third</strong>, reassess policy language. If a legitimate feature is used maliciously to deny access, is it covered? If an attacker logs in rather than breaks in, does that trigger the same protections? These are not legal hypotheticals — they are claims decisions in waiting.</p><p><strong>Finally</strong>, model the adversary — not just the incident. Move beyond asset-based modeling to campaign-based scenarios. What happens when the same SSE-C abuse technique impacts 100 policyholders across the same cloud region? What does that look like in your portfolio exposure?</p><h4>Call to Action: Modeling What Matters</h4><p>This risk is not speculative. It is active, evolving, and, most importantly, operational. The only question is whether your models can see it. The next billion-dollar cyber loss may not come from a zero-day. It may not involve a nation-state. It may stem from a forgotten S3 bucket, an unused IAM role, or a storage feature functioning exactly as it should — just under someone else’s control.</p><p>Coming from the cyber operations and intelligence community, I’ve seen the cost of shaping data to fit conclusions. In insurance, I now see a similar risk: models built around backward logic — “What number can I defend?” — instead of forward inquiry: “What risk must I truly understand?”</p><p>Too often, we rely on proxies like cost-per-record or endpoint counts — metrics that are easy to explain but fail to capture adversary behavior or the operational structures of risk. These abstractions may satisfy capital markets, but they are detached from the architectures and functions that define real loss. We’re building castles on sand.</p><p>In intelligence, we let the data lead. Threat models are shaped by collection, risk analysis, and mission context — not by retrofitting outcomes to match expected loss ratios. The insurance industry must start with this foundation and build models off of it, replacing marketable figures with operational truths.</p><p>Without this shift, insurers remain reactive — responding to headlines instead of hard data. Blind spots become capital losses. The time to act is now: update your models, scrutinize cloud configurations, and build processes that anticipate, not just react to the future.</p><p>Move from modeling technical breaches to understanding trust collapses. From misconfigurations to campaign techniques. From cyber incidents to insured events. And most importantly — know the difference.</p><h4>Final Thoughts: Operational Fidelity for Economic Risk</h4><p>We need to reframe how we talk about cloud risk in insurance. These aren’t “configuration errors.” They are systemic vulnerabilities tied to how cloud services function — and how adversaries abuse that function.</p><p>I’ve written about this before: the shift from cyber incident to insured cyber event (ICE) is essential. Not all incidents create claims. But many of these new tactics do — and they’re being repeated across industries, across verticals, and across cloud providers.</p><p>By treating these events as insurable, accumulable, and systemic — not just “weird IT problems” — we give ourselves a fighting chance to model and price them properly.</p><p>Let’s stop assuming intent is required for damage to be covered. Sometimes, the most catastrophic losses come not from things going wrong — but from things going exactly as planned.</p><h4>References</h4><p>Amazon Web Services. (n.d.). <em>Protecting data using server-side encryption with customer-provided encryption keys (SSE-C)</em>. AWS Documentation. Retrieved from <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html">https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html</a></p><p>Cisco Talos. (2024, January). <em>Talos Year in Review: 2024 threat landscape summary</em>. Cisco. Retrieved from <a href="https://blog.talosintelligence.com/">https://blog.talosintelligence.com/</a></p><p>Cybernews. (2024, April 12). <em>Huge ransomware campaign targets AWS S3 storage: Attackers have thousands of keys</em>. CyberNews. Retrieved from <a href="https://cybernews.com/security/aws-cloud-storage-bucket-ransomware-attacks/">https://cybernews.com/security/aws-cloud-storage-bucket-ransomware-attacks/</a></p><p>Global Security Magazine. (2024, April 12). <em>Massive ransomware campaign targets AWS S3 storage: Attackers have thousands of keys</em>. Global Security Mag. Retrieved from <a href="https://www.globalsecuritymag.fr/massive-ransomware-campaign-targets-aws-s3-storage-attackers-have-thousands-of.html">https://www.globalsecuritymag.fr/massive-ransomware-campaign-targets-aws-s3-storage-attackers-have-thousands-of.html</a></p><p>Hackread. (2024, April 13). <em>Mass ransomware campaign hits S3 buckets using stolen AWS keys</em>. Hackread. Retrieved from <a href="https://www.hackread.com/mass-ransomware-campaign-s3-buckets-stolen-aws-keys/">https://www.hackread.com/mass-ransomware-campaign-s3-buckets-stolen-aws-keys/</a></p><p>IBM Security. (2023). <em>Cost of a Data Breach Report 2023</em>. IBM. Retrieved from <a href="https://www.ibm.com/reports/data-breach">https://www.ibm.com/reports/data-breach</a></p><p>Veriti Research. (2024, February). <em>Cloud configuration risks and exposure analysis</em>. Veriti Labs. <a href="https://securityboulevard.com/2025/03/veriti-research-uncovers-malware-exploiting-cloud-services/">https://securityboulevard.com/2025/03/veriti-research-uncovers-malware-exploiting-cloud-services/</a></p><p>Microsoft Threat Intelligence. (2023). <em>Digital Defense Report 2023</em>. Microsoft. Retrieved from <a href="https://www.microsoft.com/en-us/security/business/security-intelligence-report">https://www.microsoft.com/en-us/security/business/security-intelligence-report</a></p><p>CrowdStrike. (2024). <em>Global Threat Report 2024</em>. CrowdStrike. Retrieved from <a href="https://www.crowdstrike.com/global-threat-report/">https://www.crowdstrike.com/global-threat-report/</a></p><p>Zeno, T. (2023, November 1). <em>When hackers met actuaries: How cybersecurity reports inform and challenge the evolving cyber insurance model</em>. Medium. Retrieved from <a href="https://medium.com/@tyz_89492/when-hackers-met-actuaries-how-cybersecurity-reports-inform-and-challenge-the-evolving-cyber-ac1386341fd3">https://medium.com/@tyz_89492/when-hackers-met-actuaries-how-cybersecurity-reports-inform-and-challenge-the-evolving-cyber-ac1386341fd3</a></p><p><em>Author: Ty Zeno<br></em>Senior Cyber Threat Researcher | Cyber Operations Veteran | Cyber Insurance Modeler<br><a href="https://medium.com/@tyz_89492/when-hackers-met-actuaries-how-cybersecurity-reports-inform-and-challenge-the-evolving-cyber-ac1386341fd3">Original Thought Leadership: “When Hackers Met Actuaries”</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31af645eb0cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Attack on the Supply Chain: The Blue Yonder Attack]]></title>
            <link>https://medium.com/@tyz_89492/rethinking-cyber-risk-lessons-from-the-blue-yonder-attack-d96ee5aeba62?source=rss-2a044bb9278b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d96ee5aeba62</guid>
            <category><![CDATA[dependencies]]></category>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[critical-thinking]]></category>
            <category><![CDATA[cyber-defense]]></category>
            <category><![CDATA[cyber-insurance]]></category>
            <dc:creator><![CDATA[Ty Zeno]]></dc:creator>
            <pubDate>Tue, 03 Dec 2024 18:57:51 GMT</pubDate>
            <atom:updated>2024-12-10T17:29:57.425Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*okMsc8cTMuSV6mOt105NhA.jpeg" /></figure><p>As a cyber network operations (CNO) professional deeply engaged in the intersection of technology and insurance, I’ve been analyzing the November 2024 ransomware attack on Blue Yonder. This incident underscores the urgent need to rethink how we assess and insure against cyber risks in our interconnected world. I invite my fellow cyber insurance professionals to join this critical conversation and explore actionable solutions.</p><p><strong>Discussion Points for Readers</strong>:</p><ul><li>How can companies balance the efficiency of centralized service providers with the risks of single points of failure?</li><li>What metrics should insurers prioritize when assessing supply chain resilience?</li></ul><h3>Incident Overview and Key Impacts</h3><h4>Attack Details</h4><ul><li><strong>Type</strong>: Ransomware attack targeting Blue Yonder’s managed services hosted environment.</li><li><strong>Threat Actor</strong>: <strong>Termite ransomware group</strong>, linked to the notorious Babuk ransomware.</li><li><strong>Timeline</strong>: Detected on <strong>November 21, 2024</strong>; recovery efforts remain ongoing.</li><li><strong>Data Compromised</strong>: Claims of <strong>680GB</strong> of stolen data, including email lists, insurance documents, and sensitive operational records.</li></ul><h4>Affected Clients and Services</h4><p>Blue Yonder’s critical role in supply chain operations amplified the attack’s impact across multiple sectors:</p><ul><li><strong>Starbucks</strong>: Struggled with payroll and scheduling disruptions affecting over 11,000 stores.</li><li><strong>Morrisons &amp; Sainsbury’s</strong>: Experienced interruptions in warehouse management systems, leading to stock shortages.</li><li><strong>BIC</strong>: Faced limited shipping delays.</li></ul><p>Unverified reports suggest other potential victims, including <strong>Albertsons, Kroger</strong>, and <strong>Procter &amp; Gamble</strong>, highlighting the systemic risks of a single point of failure.</p><h3>Key Analysis and Lessons Learned</h3><h4>1. Systemic Risks in Supply Chain Technology</h4><p>Blue Yonder’s extensive client base — spanning retail, manufacturing, and logistics — demonstrates the systemic risks posed by technology providers in interconnected supply chains. Its <strong>Warehouse Management System (WMS)</strong> and <strong>Workforce Management</strong> solutions, integral to operations, more than likely became chokepoints during the attack.</p><ul><li><strong>Functional Dependency</strong>: Companies’ reliance on Blue Yonder’s cloud-hosted environments underscores the fragility of ecosystems where one vendor’s compromise cascades across multiple industries.</li><li><strong>Single Point of Failure</strong>: The incident exemplifies how a breach in one service provider can impact and possibly cripple entire supply chains.</li></ul><h4>2. Evolving Threat Actor Tactics</h4><p>Termite ransomware’s advanced tactics — such as targeting backup systems and virtual machine environments — reflect the growing trend of cyber adversaries, specifically in the use of ransomware malware. The group’s alleged links to Babuk ransomware group highlight the trend of <strong>rebranding</strong> among threat actors to evade detection and attribution.</p><h4>3. Cross-Border Cascading Effects</h4><p>The attack’s global impact, affecting entities in the <strong>U.S., UK, and France</strong>, underscores the interconnected nature of modern supply chains. Retailers had to implement contingency measures, such as manual inventory management, to mitigate operational disruptions.</p><h4>4. Recovery Complexities</h4><p>Despite leveraging Microsoft Azure’s private cloud and external cybersecurity expertise, Blue Yonder’s ongoing recovery highlights the challenges of restoring operations after a ransomware attack. Extended downtimes and incomplete service restoration exacerbate operational and reputational damage.</p><h3>Implications for Cyber Insurance and Risk Modeling</h3><h4>Quantifying Business Interruption (BI) and Contingent Business Interruption (CBI)</h4><p>The incident highlights the need for insurers to reassess <strong>functional dependencies</strong> and the cascading effects of ransomware attacks:</p><ul><li><strong>Direct BI</strong>: Losses incurred by Blue Yonder due to service disruptions.</li><li><strong>CBI</strong>: Economic losses faced by its customers, such as Starbucks and Morrisons, due to operational outages.</li></ul><h4>Worst-Case Scenario Modeling</h4><p>The attack validates the importance of modeling <strong>worst-case scenarios</strong> where:</p><ul><li>Critical systems like WMS are compromised.</li><li>Extended recovery timelines amplify financial losses.</li><li>Reputation damage leads to customer attrition and regulatory scrutiny.</li></ul><h4>Supply Chain Resilience as a Coverage Metric</h4><p>This incident reinforces the need for insurers to evaluate the resilience of supply chain partners. Metrics such as contingency planning, in place policies signed by the CEO, failover capabilities, and vendor risk assessments could inform underwriting decisions.</p><p>How does your organization currently assess the risk of cascading supply chain disruptions? Are we accounting for these hidden dependencies effectively?</p><h3>Introducing the Functional Dependency Framework</h3><p>In response to incidents like this, I’ve developed the <strong>Functional Dependency Framework</strong> — an approach that examines how technology dependencies intersect with operational criticality and potential attack vectors. This framework focuses on <strong>functional systems</strong> like supply chain management platforms, ERP solutions, or payment processing systems that underpin essential business operations.</p><ul><li>How would you map the functional dependencies across your client portfolio? Could this reveal unexpected risks?</li><li>Companies experienced differing levels of disruption based on their integration depth with Blue Yonder’s platform. Can you identify similar vulnerabilities in your clients’ ecosystems? What proactive measures can reduce these risks?</li><li>How do information gaps, such as specifics of the ransom demand or exact number of customers affected and to what extent, influence your approach to policy writing, pricing, and claims evaluation? How can insurers address uncertainty in underwriting?</li><li>Share your perspectives on the evolving cyber insurance landscape. What methodologies or innovations have you found effective in tackling these challenges?</li><li>What enhancements do you see as critical for the future of cyber insurance? How can we integrate them into current practices?</li></ul><h3>Future Considerations</h3><p>Governments may increase scrutiny of supply chain cybersecurity practices. Regulatory frameworks could mandate stricter reporting requirements and resilience benchmarks for service providers like Blue Yonder.</p><h3>Call to Action: Preparing for Tomorrow’s Threats</h3><p>The Blue Yonder ransomware attack identifies every industries dependent on interconnected technologies. It highlights the urgent need for understanding interconnected technologies, robust technology dependency risk modeling, and cross-industry collaboration to mitigate the systemic risks. By fostering resilience and preparedness, companies can navigate the complexities of modern cyber threats, ensuring business continuity and protecting critical supply chains from future disruptions.</p><p>As we reflect on the lessons of Blue Yonder, let’s collaborate to strengthen our understanding of cyber risks and build a more resilient industry. Share your thoughts, and let’s move this conversation — and our industry — forward together.</p><h3><strong>References</strong></h3><p>The Stack, “Blue Yonder ransomware attack triggers potato shortages,” November 27, 2024, <a href="https://www.thestack.technology/blueyonder-ransomware-attack-triggers-potato-shortages-2/">https://www.thestack.technology/blueyonder-ransomware-attack-triggers-potato-shortages-2/</a><br>Security Magazine, “Supply chain technology provider Blue Yonder faces ransomware attack,” November 26, 2024, <a href="https://www.securitymagazine.com/articles/101213-supply-chain-technology-provider-blue-yonder-faces-ransomware-attack">https://www.securitymagazine.com/articles/101213-supply-chain-technology-provider-blue-yonder-faces-ransomware-attack</a><br>ITPro, “Blue Yonder ransomware attack disrupts grocery, retail, and hospitality firms,” November 26, 2024, <a href="https://www.itpro.com/security/cyber-attacks/blue-yonder-ransomware-attack-disrupts-grocery-retail-and-hospitality-firms">https://www.itpro.com/security/cyber-attacks/blue-yonder-ransomware-attack-disrupts-grocery-retail-and-hospitality-firms</a><br>SecurityWeek, “Starbucks, Grocery Stores Hit by Blue Yonder Ransomware Attack,” November 26, 2024, Starbucks, <a href="https://www.securityweek.com/starbucks-grocery-stores-hit-by-blue-yonder-ransomware-attack/">https://www.securityweek.com/starbucks-grocery-stores-hit-by-blue-yonder-ransomware-attack/</a><br>Cybersecurity Dive, “Blue Yonder moves closer to full recovery following November ransomware attack,” December 2, 2024, <a href="https://www.cybersecuritydive.com/news/blue-yonder-recovery-ransomware/734275/">https://www.cybersecuritydive.com/news/blue-yonder-recovery-ransomware/734275/</a><br>Global Relay, “Systems in UK and US retailers down after Blue Yonder ransomware attack,” November 29, 2024, <a href="https://www.grip.globalrelay.com/systems-in-uk-retailers-down-after-blue-yonder-ransomware-attack">https://www.grip.globalrelay.com/systems-in-uk-retailers-down-after-blue-yonder-ransomware-attack</a><br>Wall Street Journal, “Starbucks, Other Retailers Hit by Ransomware Attack on Tech Provider”, November 25, 2024, <a href="https://www.wsj.com/articles/starbucks-other-retailers-hit-by-ransomware-attack-on-tech-provider-98314528">https://www.wsj.com/articles/starbucks-other-retailers-hit-by-ransomware-attack-on-tech-provider-98314528</a><br>Mastodon, Security Researcher Kevin Beaumount, <a href="https://cyberplace.social/@GossiTheDog/113550481295785096">https://cyberplace.social/@GossiTheDog/113550481295785096</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d96ee5aeba62" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Espionage Threats and Their Impact on the Cyber Insurance Industry]]></title>
            <link>https://medium.com/@tyz_89492/espionage-threats-and-their-impact-on-the-cyber-insurance-industry-ec8254c5f8a4?source=rss-2a044bb9278b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec8254c5f8a4</guid>
            <category><![CDATA[risk-modeling]]></category>
            <category><![CDATA[cyber-insurance]]></category>
            <category><![CDATA[catastropic-cyber-event]]></category>
            <category><![CDATA[cyber-threat]]></category>
            <category><![CDATA[thought-leadership]]></category>
            <dc:creator><![CDATA[Ty Zeno]]></dc:creator>
            <pubDate>Wed, 09 Oct 2024 18:22:06 GMT</pubDate>
            <atom:updated>2024-10-09T18:22:06.333Z</atom:updated>
            <content:encoded><![CDATA[<h3>Understanding the Threat: GoldenJackal</h3><p>Cyber operations will always continue to evolve, however, it is a mistake to assume that <strong>espionage-based motivations</strong> are less impactful than financially motivated attacks like ransomware. The distinction between espionage or financial motives does not diminish the underlying risk. To believe that espionage poses less of a threat to <strong>cyber insurance risk modeling</strong> is a misunderstanding. Any <strong>unauthorized access</strong> — whether financially or espionage-driven — represents a critical risk to the integrity of a system or network. Understanding this distinction is key for insurers who need to assess the full spectrum of <strong>cyber risks</strong>, including those involving <strong>espionage</strong>, which can lead to severe <strong>regulatory, legal, and reputational consequences</strong> for the insured.</p><p>Operating under the radar, GoldenJackal, an advanced persistent threat (APT) group active since 2019, targets <strong>government institutions, diplomatic entities</strong>, and <strong>critical infrastructure sectors</strong> across Europe, South Asia, and the Middle East. Their primary objective is <strong>espionage</strong>, focusing on the theft of sensitive information rather than causing immediate disruptive damage or extortion.</p><h3>A Focus on Air-Gapped Systems</h3><p>One of GoldenJackal’s most significant tactics is its ability to breach <strong>air-gapped systems</strong> — networks that are physically separated from unsecured public networks. Traditionally, these systems are considered some of the most secure due to their isolation. Yet, GoldenJackal has demonstrated that no system is entirely safe from exploitation. Their use of tools and tactics, which can bypass air-gapped security measures, presents unique challenges for cyber insurers.</p><p>For the <strong>cyber insurance market</strong>, this raises a critical question: How do we model and underwrite risks for systems traditionally thought of as secure? While air-gapped systems may seem less vulnerable to conventional network-based attacks, <strong>GoldenJackal’s capabilities show that even these environments are at risk</strong>, creating new considerations for risk modeling and premium calculations.</p><h3>Financial Impacts and Insurance Claims</h3><p>While GoldenJackal’s focus is not financially motivated like many ransomware attacks, the <strong>long-term consequences</strong> of their espionage campaigns can be severe. When sensitive government or diplomatic data is stolen, the fallout includes <strong>regulatory fines</strong>, <strong>reputational damage</strong>, and <strong>legal claims</strong>. These factors are critical for insurers to assess when calculating potential payouts.</p><p>Consider the <strong>Merck NotPetya incident</strong>, a stark reminder of how a cyberattack with an espionage angle can spiral into a <strong>financial catastrophe</strong>. Merck’s claim amounted to <strong>$1.4 billion</strong>, stemming from an attack originally designed as a geopolitical weapon. Though Merck did not have specific cyber insurance, the case highlighted how insurers need to clearly define policy coverage, especially concerning <strong>nation-state actions</strong>.</p><h3>Escalating Threats and Cyber Catastrophe Modeling</h3><p>The <strong>NotPetya attack</strong> serves as an example of how nation-state cyber tools, initially aimed at espionage or sabotage, can escalate into <strong>global-scale events</strong>. What began as an attack targeting Ukraine spread worldwide, causing over <strong>$10 billion in damages</strong>. This event prompted insurers to rethink how they cover <strong>nation-state cyberattacks</strong>, with many now reevaluating their policy language around <strong>war exclusion clauses</strong>. The <strong>Merck case</strong> eventually led to a settlement that reinforced the need for clear definitions of coverage and raised the question of whether the typical war exclusion should apply to cyber incidents without direct military involvement.</p><p>For the insurance industry, <strong>GoldenJackal’s operations</strong> raise similar concerns. While their current focus is on stealthy intelligence gathering, the group’s <strong>sophisticated tools</strong> could be repurposed or evolve, leading to larger-scale disruptions in critical sectors such as energy, defense, and diplomacy. If that happens, insurers may face a wave of claims that will require a <strong>cyber catastrophe model</strong> on par with the worst ransomware outbreaks.</p><h3>The Implications for Insurers</h3><p>Insurers must now consider several factors when underwriting policies for industries vulnerable to <strong>cyber espionage</strong>:</p><ul><li><strong>Air-Gapped Systems</strong>: The assumption that these are secure may no longer hold. Insurers must adjust premiums and risk models accordingly.</li><li><strong>Long-Term Exposure</strong>: Espionage doesn’t cause immediate financial loss, but its <strong>long-term repercussions</strong> — such as regulatory fines, reputational damage, and lawsuits — can be severe.</li><li><strong>Nation-State Attribution</strong>: Clear definitions around <strong>war exclusions</strong> are essential as attacks like NotPetya, or potential future incidents involving GoldenJackal, blur the lines between criminal activity and state-sponsored cyber operations.</li></ul><h3>Looking Ahead: A Cyber Insurance Crossroad</h3><p>The activities of groups like <strong>GoldenJackal</strong> pose complex challenges for the cyber insurance industry. While traditional underwriting focused on ransomware and business interruption, the rise of <strong>sophisticated espionage operations</strong> introduces new variables that insurers must account for. With <strong>nation-state tools</strong> potentially spiraling out of control, as seen with NotPetya, the risks for insurers are higher than ever.</p><p>Insurers need to prepare for a future where cyber espionage can trigger massive <strong>catastrophic losses</strong>, even without the overt destruction typically associated with cyberattacks. <strong>Advanced risk modeling</strong> and clearer policy language around cyber warfare will be crucial for the industry to stay resilient in the face of evolving threats.</p><h3>References:</h3><ul><li>Securelist: “GoldenJackal APT Group”<br>• <a href="https://securelist.com/goldenjackal-apt-group/109677/">https://securelist.com/goldenjackal-apt-group/109677/</a></li><li>ESET: “Mind the air-gap: GoldenJackal gooses government guardrails”<br>• <a href="https://www.welivesecurity.com/en/eset-research/mind-air-gap-goldenjackal-gooses-government-guardrails/">https://www.welivesecurity.com/en/eset-research/mind-air-gap-goldenjackal-gooses-government-guardrails/</a></li><li>The Record: “GoldenJackal hackers target government, diplomatic entities”<br>• <a href="https://therecord.media/goldenjackal-hackers-target-government-diplomatic-entities">https://therecord.media/goldenjackal-hackers-target-government-diplomatic-entities</a></li><li>ESET: “GoldenJackal APT Group, with air-gap-capable tools, targets systems in Europe to steal confidential data”<br>• <a href="https://www.eset.com/int/about/newsroom/press-releases/eset-research-goldenjackal-apt-group/">https://www.eset.com/int/about/newsroom/press-releases/eset-research-goldenjackal-apt-group/</a></li><li>ESET: “Hackers attack government institutions in Europe to steal data”<br>• <a href="https://www.eset.com/ua/about/newsroom/hackers-target-european-institutions-goldenjackal/">https://www.eset.com/ua/about/newsroom/hackers-target-european-institutions-goldenjackal/</a></li><li>SecurityWeek: “Merck Settles NotPetya Insurance Claim”<br>• <a href="https://www.securityweek.com/merck-settles-notpetya-insurance-claim">https://www.securityweek.com/merck-settles-notpetya-insurance-claim</a></li><li>SecurityIntelligence: “How Will the Merck Settlement Affect the Insurance Industry?”<br>• <a href="https://securityintelligence.com/news/merck-notpetya-settlement-insurance-industry/">https://securityintelligence.com/news/merck-notpetya-settlement-insurance-industry/</a></li><li>Insurance Business America: “Merck’s $1.4 billion cyberattack claim”<br>• <a href="https://www.insurancebusinessmag.com/us/news/cyber/mercks-1-4-billion-cyberattack-claim--the-specter-of-notpetya-324674.aspx">https://www.insurancebusinessmag.com/us/news/cyber/mercks-1-4-billion-cyberattack-claim--the-specter-of-notpetya-324674.aspx</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec8254c5f8a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Hackers Met Actuaries: How Cybersecurity Reports Inform and Challenge the Evolving Cyber…]]></title>
            <link>https://medium.com/@tyz_89492/when-hackers-met-actuaries-how-cybersecurity-reports-inform-and-challenge-the-evolving-cyber-ac1386341fd3?source=rss-2a044bb9278b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac1386341fd3</guid>
            <category><![CDATA[cyber-insurance]]></category>
            <category><![CDATA[cyber]]></category>
            <category><![CDATA[cyber-insurance-industry]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber-insurance-market]]></category>
            <dc:creator><![CDATA[Ty Zeno]]></dc:creator>
            <pubDate>Tue, 20 Aug 2024 17:37:41 GMT</pubDate>
            <atom:updated>2024-08-20T17:54:23.264Z</atom:updated>
            <content:encoded><![CDATA[<h3>When Hackers Met Actuaries: How Cybersecurity Reports Inform and Challenge the Evolving Cyber Insurance Market</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/1*09U13JbE4-05gxQ6JakJTg.png" /></figure><p>It’s easy to assume that cybersecurity reports, which highlight threats and the costs of incidents, would naturally align with cyber insurance trends. However, the reality is more complex. While these reports provide valuable insights into digital threats, they don’t always directly correspond to the specific needs of the insurance industry. Cybersecurity encompasses a broad range of issues, while the cyber insurance market is concerned with more focused aspects like risk modeling, policy structures, and market behavior for cyber insured events. The gap between cybersecurity insights and the cyber insurance market is evident in cases like the SolarWinds attack. Despite the massive breach and its significant cybersecurity implications, which affected thousands of organizations, including critical infrastructure, it had little to no immediate impact on the cyber insurance market. This disconnect occurs because not all cybersecurity incidents are ensured cyber events. Even though a breach like SolarWinds raises significant concerns, it doesn’t always result in a measurable financial impact that insurers can respond to. This highlights the gap: not every major cybersecurity event affects the insurance market, even if it poses substantial threats in the digital world. Understanding and addressing this gap is crucial for better aligning cybersecurity practices with effective insurance strategies.</p><h3>The Misalignment Between Cybersecurity Reports and the Insurance Market</h3><p>Cybersecurity reports encompass a wide range of factors and emerging threats, but the cyber insurance market distills this complex information into actionable metrics that drive policy creation, pricing, and risk assessment. This process often leads to a disconnect between the comprehensive insights provided by cybersecurity reports and the specific metrics needed for insurance decision-making.</p><p>According to the 2023 Verizon Data Breach Investigations Report (DBIR), ransomware accounted for approximately 24% of all cyber breaches and in the 2024 Verizon Data Breach Investigations Report (DBIR), ransomware accounted for 23% of all breaches. This significant proportion reflects the widespread prevalence and impact of ransomware attacks across various industries. However, when comparing this statistic to cyber insured events, ransomware attacks represent an even higher percentage of claims, underscoring their greater impact on the cyber insurance market.</p><p>For instance:<br>The <strong>Coalition Cyber Insurance Claims Report (2023)</strong> indicated that ransomware was the top cause of loss for cyber insurance claims, accounting for approximately 40% of claims.</p><ul><li>The <strong>AON Cyber Insurance Market Insights (2023)</strong> highlighted ransomware as a significant driver of claims, with ransomware making up close to 35% of total cyber insurance claims.</li><li>The <strong>Beazley Breach Insights Report (2023)</strong>, from a leading cyber insurer, reported that ransomware accounted for about 30–35% of their cyber insurance claims.</li><li>The <strong>Marsh Global Insurance Market Index (2023)</strong> also emphasized ransomware as a major cause of cyber insurance claims, estimating that ransomware was responsible for approximately 30–40% of claims.</li></ul><p>This comparison reveals that while ransomware makes up a substantial portion of all cyber breaches, it represents an even larger share of cyber insured events. This highlights ransomware’s significant financial impact and the higher likelihood of these incidents leading to insurance claims.</p><h3>Key Factors Influencing the Cyber Insurance Market</h3><p><strong>Risk Modeling</strong></p><p>At the heart of the cyber insurance market is risk modeling. Insurers must assess the likelihood and potential impact of various cyber threats to set premiums and determine coverage limits. The challenge is in translating the chaotic, evolving nature of cyber threats into models that can reliably forecast risk. While cybersecurity reports might highlight emerging threats or sophisticated attacks, the insurance industry focuses on trends that are statistically significant and can be modeled with a degree of predictability.</p><p><strong>Policy Structures</strong></p><p>Cyber insurance policies are not one-size-fits-all; they are tailored to specific industries, company sizes, and risk appetites. This means that while a cybersecurity report might emphasize a particular type of threat, such as ransomware, the impact on the insurance market can vary widely depending on the insured entities. For example, a small business and a multinational corporation may face vastly different risks and consequences from the same type of attack, leading to divergent insurance needs and policy structures.</p><p><strong>Market Behavior</strong></p><p>The behavior of the cyber insurance market is also shaped by factors beyond just the latest cybersecurity reports. Economic conditions, regulatory changes, and high-profile legal cases can influence how insurers approach the market. For instance, a surge in claims from a particular type of cyber incident could lead insurers to adjust their premiums or policy terms, even if the underlying cybersecurity risk hasn’t changed dramatically. Additionally, the market’s reaction to emerging technologies and the evolving regulatory landscape can create shifts that aren’t immediately apparent in cybersecurity data.</p><p><strong>Human and Organizational Factors</strong></p><p>Human behavior and organizational responses play a significant role in the cyber insurance market. Insurers must consider not just the technical aspects of cybersecurity but also how organizations manage and mitigate these risks. This includes assessing the effectiveness of cybersecurity programs, employee training, incident response plans, and overall security culture. While cybersecurity reports may highlight vulnerabilities and threats, the insurance market must evaluate how well organizations are prepared to handle these challenges and how that preparedness influences their risk profile.</p><h3>Ransomware: Still A Growing Crisis</h3><p>Ransomware is a leading threat within the cyber insurance marketplace. There was a 21% increase in leak site victims in 2024, according to <strong>Corvus Insurance’s Q1 Ransomware Report</strong>. Despite significant law enforcement disruptions, ransomware operations have proven resilient, with new groups emerging and adapting to continue their attacks. <strong>Chainalysis</strong> reports that ransomware actors extorted over $459 million in the first half of 2024, with a significant rise in the median ransom payments. The <strong>SOCRadar report</strong> further emphasizes the prevalence of ransomware-as-a-service groups, which, while posing lower risks for the attackers, yield higher rewards. These groups have been responsible for the majority of attacks across various sectors, particularly targeting manufacturing, healthcare, and other critical infrastructure. The <strong>Cybereason Annual Global Study on Ransomware Business Impact</strong> indicates that ransomware re-attacks are common, with 78% of organizations that paid a ransom being re-victimized, often by the same actors.</p><h3>Insured Cyber Events and Market Impact</h3><p>The increasing frequency and severity of ransomware attacks are directly impacting the cyber insurance market. The <strong>2024 Howden Cyber Report</strong> emphasizes that ransomware remains the most costly cyber threat, with an 85% increase in attacks compared to 2022. The report underscores the critical importance of robust risk controls in mitigating the financial impacts of these attacks. In parallel, the <strong>2023 NAIC Cyber Supplement reports</strong> a slowdown in premium growth despite an increase in the complexity and cost of claims. This deceleration reflects the challenges insurers face in balancing the need for comprehensive coverage with the financial risks posed by escalating cyber threats. The <strong>2024 IBM Cost of a Data Breach Report</strong> reinforces these concerns, noting a significant increase in the average cost of a data breach to $4.88 million. The report highlights the importance of AI and automation in reducing breach costs, a critical consideration for insurers when assessing the risk and pricing of policies.</p><p>The U.S. cyber insurance market grew to approximately $9.7 billion in direct written premiums in 2022, reflecting a 47.6% increase. However, the number of policies in force has grown at a slower pace, indicating market stabilization. Insurers have refined their underwriting processes, demanding higher security measures from organizations and introducing stricter policy terms. The issuance of cyber catastrophe bonds since late 2023 indicates strong investor appetite and represents a significant development in the market, suggesting potential growth in this area.</p><p>High-profile attacks on software like MOVEit and organizations like Change Healthcare have highlighted the risks associated with SPoFs (Single Points of Failure), where a single attack can have widespread consequences across multiple industries (MOVEit) or cripple the majority of an industry (Change Healthcare). The number of reported Common Vulnerabilities and Exposures (CVEs) has risen by 30%, reflecting growing software complexity. While only a small percentage of these vulnerabilities have been weaponized, those that are exploited have had significant impacts. The exploitation of zero-day vulnerabilities continues to rise, with 97 zero-day vulnerabilities exploited in 2023, slightly below the record set in 2021. The increased targeting of third-party components and enterprise technologies has posed new challenges.</p><p>The recent ransomware attack on Change Healthcare has become a critical case study, significantly impacting the healthcare sector and the broader cyber insurance market. The attack led to prolonged downtime, affecting pharmacies, hospitals, and insurers unable to process claims. This incident highlights the importance of Contingent Business Interruption (CBI) coverage. Many businesses dependent on Change Healthcare’s services faced severe financial strain, emphasizing the necessity for CBI coverage in cyber insurance policies, particularly for industries heavily reliant on third-party vendors.</p><h3>Sector-Specific Trends and Risks</h3><p>The critical manufacturing sector continues to be the most targeted, with over 280 ransomware incidents recorded in H1 2024, according to the <strong>GRF Semiannual Ransomware Report</strong>. This sector’s vulnerabilities underscore the need for targeted insurance products that address the specific risks associated with operational technology and industrial control systems.</p><p>Healthcare also remains a top target, as noted in multiple reports, including the <strong>Sophos 2024 Threat Report</strong>, which highlights the disproportionate impact of cyber threats on small and medium-sized healthcare providers. The <strong>2024 BlackBerry Global Threat Intelligence Report</strong> also points to significant targeting of critical infrastructure, with government and public sector organizations bearing the brunt of these attacks.</p><p>The Change Healthcare incident underscores the unique vulnerabilities within the healthcare sector, where the dependency on third-party technology providers like Change Healthcare is particularly pronounced. This sector’s reliance on external vendors for essential services such as claims processing and prescription management makes it especially susceptible to widespread disruption when these providers are targeted by cyberattacks.</p><h3>Geopolitical and Regulatory Influences</h3><p>The geopolitical environment is increasingly shaping the cyber threat landscape. The <strong>Orange Cyberdefense Cy-Xplorer Report</strong> discusses the role of state-sponsored actors and the impact of the war in Ukraine on the cyber extortion landscape. The <strong>2024 Verizon Data Breach Investigations Report</strong> further notes the growing influence of third-party breaches and supply chain vulnerabilities, which have seen a 68% increase from the previous year. Regulatory developments, such as the U.S. Cybersecurity Strategy and the EU’s Cyber Resilience Act, are also influencing the cyber insurance market. Emerging partnerships between insurers and tech companies illustrate the industry’s response to these challenges. For example, Prudential’s collaboration with Google Cloud is a prime case of leveraging AI to enhance insurance operations across Asia and Africa. This partnership, including the establishment of an AI Lab, focuses on using AI to transform customer experiences, streamline operations, and expand access to healthcare. Such collaborations demonstrate the potential of AI in reshaping insurance strategies, particularly in regions with unique regulatory landscapes. These regulations aim to enhance security practices and enforce rapid disclosure of incidents, which will likely drive demand for more comprehensive insurance products.</p><h3>Market Maturity and Future Outlook</h3><p>The cyber insurance market is transitioning into a more mature phase, with increased competition and a focus on innovation, as highlighted in the <strong>Howden Cyber Report</strong>. Despite a temporary slowdown in premium growth, the market is expected to continue expanding, driven by innovation in broking, SME engagement, and geographic expansion. As the cyber insurance market continues to mature, insurers are increasingly turning to advanced technologies to stay competitive. P<strong>rudential’s partnership with Google Cloud</strong> highlights the growing trend of integrating AI into insurance operations. The AI Lab established through this partnership aims to accelerate innovation by providing employees with tools to create scalable, AI-driven solutions. This development represents a significant shift toward using AI to not only mitigate risks but also to drive growth and improve efficiency across the insurance sector.</p><p>Moving forward, the integration of advanced technologies, such as AI, and the ongoing refinement of regulatory frameworks will play crucial roles in shaping the future landscape of cybersecurity risk and the cyber insurance market. <strong>Chainalysis Crypto Crime Report</strong> provides additional context by highlighting the surge in ransomware payments and the evolving tactics of cybercriminals, such as the use of stablecoins and advanced laundering techniques. These developments underscore the need for insurers to adapt their risk models to account for the increasing complexity of the threat landscape.</p><p>It is crucial to recognize that the landscape we operate in is not just shaped by technology but by the unpredictable nature of human behavior. To effectively bridge the knowledge gaps that exist, we must go beyond surface-level trends and dive deeper into understanding why these gaps persist. Engage with cybersecurity experts, challenge existing risk models, and continuously educate yourselves on the evolving threat landscape. Only by acknowledging and addressing these complexities can we create resilient insurance strategies that are truly equipped to handle the dynamic and ever-changing nature of cyber risk.</p><p>Sources:<br>1. Chainalysis 2024 Report on Ransomware Payments<br>2. Sophos 2024 Ransomware Report<br>3. Cybereason 2024 Annual Global Study on Ransomware Business Impact<br>4. Qualys 2024 Midyear Threat Landscape Review<br>5. Orange Cyberdefense Cy-Xplorer Report 2024<br>6. Google TAG &amp; Mandiant Report on Zero-Day Exploits 2024<br>7. Howden Cyber Report 2024<br>8. GRF Semiannual Ransomware Report H1 2024<br>9. IBM Cost of a Data Breach Report 2024<br>10. NAIC Cyber Supplement 2023<br>11. Verizon Data Breach Investigations Report 2024<br>12. SOCRadar Ransomware Report 2024<br>13. Corvus Insurance 2024 Q1 Ransomware Report<br>14. BlackBerry Global Threat Intelligence Report 2024<br>15. Chainalysis Crypto Crime Report 2024<br>16. Red Canary Threat Detection Report 2024<br>17. Fortnightly Ransomware Summary (Q1 2024)<br>18. <a href="https://www.insurtechinsights.com/prudential-and-google-cloud-partner-to-transform-insurance-with-ai">Prudential and Google Cloud Partner to Transform Insurance with AI</a><br>19. <a href="https://www.linkedin.com/pulse/cyber-savvy-broker-newsletter-march-2024-coalitioninc-so1sc">Coalitions’ Cyber Savvy Broker Newsletter: March 2024 — Change Healthcare Attack Fallout</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac1386341fd3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[QakBot: The Hidden Cyber Threat Every Insurance Professional Should Know]]></title>
            <link>https://medium.com/@tyz_89492/qakbot-the-hidden-cyber-threat-every-insurance-professional-should-know-10ce3f419b78?source=rss-2a044bb9278b------2</link>
            <guid isPermaLink="false">https://medium.com/p/10ce3f419b78</guid>
            <category><![CDATA[malware]]></category>
            <category><![CDATA[insurance]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[cyber]]></category>
            <category><![CDATA[cyber-insurance]]></category>
            <dc:creator><![CDATA[Ty Zeno]]></dc:creator>
            <pubDate>Tue, 13 Aug 2024 17:02:51 GMT</pubDate>
            <atom:updated>2024-08-13T17:02:51.147Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iQpomiFh6QKWlk1P1MznFw.png" /></figure><p>Cyber insurance professionals often assess risks by looking at surface-level trends in the cyber landscape. However, these trends can miss the full scope of sophisticated threats like QakBot, a highly adaptable malware that has evolved to bypass security measures and cause significant damage. Understanding QakBot and its impact is a prime example of why insurance professionals need to look beyond the basics and dig deeper into the complexities of cyber threats. This article explains why it’s crucial for insurance professionals to be aware of QakBot, how this sophisticated malware operates, and what external indicators can signal a potential compromise — even without direct access to a client’s network. By mastering these concepts, you’ll be better equipped to assess and mitigate the risks posed by this elusive cyber threat.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*tQCD9-exx7Mbei4IozpCVA.png" /><figcaption><em>2024 Sophos Threat Report: Cybercrime on Main Street</em></figcaption></figure><h3>Why Cyber Insurance Professionals Should Care About QakBot Malware: Real World Example</h3><p>In early 2020, QakBot was identified as the initial access broker in an attack that led to the deployment of ProLock ransomware. QakBot infiltrated the network of several organizations, including those in the healthcare, manufacturing, and financial sectors, by stealing credentials and allowing attackers to gain a foothold in the systems. Once QakBot established access, it facilitated the deployment of ProLock ransomware. The attackers encrypted critical files and demanded hefty ransoms in exchange for the decryption keys. One victim of this attack was a healthcare organization that suffered significant operational disruptions due to the encryption of patient records and other essential data.</p><h4>Financial Impact and Cyber Insurance Involvement:</h4><p>The financial impact on the affected organizations was substantial. The healthcare organization, in particular, faced not only the direct costs of the ransom (which was in the six-figure range) but also the costs associated with system downtime, data recovery, and potential regulatory fines due to the exposure of patient data. A cyber insurance company involved in this case covered part of the ransom payment, as well as some of the associated recovery costs. The incident highlighted the growing trend of ransomware attacks facilitated by QakBot and the increasing financial burden on insurers due to these sophisticated multi-stage cyber attacks.</p><p><strong>Grasping the Risk QakBot Poses:</strong></p><p>QakBot is a highly dangerous form of malware due to its capabilities, which allow even less experienced hackers to control devices without the user’s knowledge. For insurance professionals, this means that a QakBot infection can lead to significant financial losses for businesses resulting in substantial claims, making it a critical risk to understand. Despite its long history, it remains a prevalent tool in cybercrime, with developers who continually adapt and enhance it, even in response to law enforcement actions. This persistent threat is particularly concerning for businesses and the insurance industry because of the significant financial losses it can inflict.</p><p>QakBot can steal sensitive information, such as usernames, passwords, and even banking details, which could lead to a breach, an outage, and/or financial fraud — risks that could result in insurance claims. It can also take screenshots and record your online banking details, making it a potent tool for cybercriminals. Once QakBot infiltrates a network, it acts like a digital contagion, spreading rapidly from one device to others connected within the same network. This widespread infection not only exacerbates the damage but also makes containment and remediation efforts more challenging. For insurers, the ability of QakBot to quickly propagate across a network increases the potential scale of an incident, which can lead to higher costs and more complex claims processes.</p><p>But that’s not all. QakBot can hide from most antivirus programs, making it very difficult to detect and remove. Infected devices aren’t just a problem for the organization that owns them — QakBot can turn these devices into part of a botnet, a network of compromised computers controlled by hackers. These botnets can be used to carry out large-scale attacks, send spam, or distribute additional malware. This adds another layer of risk for insurers, as the involvement in botnet activities can lead to legal complications, additional financial losses, and further strain on resources during the claims process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z3_SoCHClMFa7FFbawDcLQ.png" /><figcaption>QakBot’s Modularity: A Cybercriminal’s Toolbox — Attackers can customize and deploy only the “building blocks” they need for each targeted attack, making it a versatile and persistent threat.</figcaption></figure><h3>The Evolution of QakBot</h3><p>QakBot, also known as QBot, is a persistent threat that has evolved over more than a decade, continuously adapting to bypass security measures. This evolution makes it a significant ongoing risk for businesses and an important factor to understand in the cyber insurance industry. QakBot’s continuous evolution not only makes it harder for network defenders to detect but also increases the financial risks for businesses, clients, and their insurers.</p><p>Initially identified by Symantec in 2007 as a banking Trojan, QakBot was designed to steal financial information, like online banking credentials. Over the years, it has added features like keystroke logging, rootkit capabilities (which help it hide from detection), and methods to self-replicate across networks, making it more potent and harder to detect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/629/1*SmuNRbpPQDfQUIe6AAhmhQ.png" /><figcaption>15 Years of Qakbot Development</figcaption></figure><p>QakBot’s evolution didn’t stop there. For instance, it can now inject itself into existing email conversations to appear legitimate, dynamically update itself to avoid detection, and serve as a gateway for even more dangerous attacks, like ransomware. This means that QakBot often serves as a loader for other malicious software, setting the stage for full-blown attacks that can lock down entire computer systems until a ransom is paid. These ransomware attacks are a growing concern for businesses and their insurers, as they can lead to costly disruptions and claims.</p><h3>Key Insights for Insurance Professionals</h3><ol><li><strong>QakBot’s Origin:</strong> QakBot started in 2007 as a tool for stealing financial information, like credentials, and conducting ACH, wire, and credit card fraud. But it has since evolved into a versatile and persistent piece of malware.</li><li><strong>Initial Access Broker:</strong> In recent years, QakBot has emerged as a significant enabler of other cyberattacks. QakBot often serves as an initial access broker, meaning it infiltrates networks and then sells this access to other cybercriminals, who use tools like Cobalt Strike to move laterally within the network and launch further attacks.</li><li><strong>Evasion Techniques:</strong> QakBot’s ability to avoid detection has improved significantly. It now uses advanced techniques to evade malware sandboxes, antivirus software, and other security products.</li><li><strong>Modular Malware:</strong> The malware is modular, meaning it can download and add new functionalities on the fly. This adaptability allows QakBot to continue evolving, making it a persistent threat that is hard to defend against.</li><li><strong>Ongoing Threat:</strong> Despite significant disruption to QakBot in August 2023, the threat group remains active and continues to update their codebase, including support for 64-bit versions of Windows, improved encryption algorithms, and added obfuscation techniques. This shows that QakBot will likely remain a threat for the foreseeable future.</li></ol><h3><strong>Why Understanding QakBot Matters Even for Non-Technical Cyber Insurance Professionals</strong></h3><p>Understanding QakBot is crucial for insurance professionals, even those without a technical background, because it represents a constantly evolving cyber risk that is increasingly difficult to predict and mitigate. The financial impact of a QakBot infection can be significant, particularly when it escalates to more severe attacks like ransomware.</p><p>Despite major efforts to dismantle QakBot in 2023, the malware has continued to evolve. This ongoing threat means that businesses and insurers must remain vigilant. QakBot — and the risks associated with it — are likely to persist for the foreseeable future, making it essential for insurance professionals to stay informed.</p><h3><strong>Understanding How to Detect QakBot</strong></h3><p>Detecting whether an organization has been compromised by QakBot can be exceptionally challenging due to the malware’s sophisticated ability to conceal itself. Even with advanced detection methods within a network, identifying QakBot can be difficult, as it often evades traditional scans and security measures. Techniques such as behavioral analysis or anomaly detection might provide more insights, but even these can sometimes miss QakBot’s subtle signs.</p><p>If you have internal access to a network, there are several indicators that could suggest a possible QakBot infection:</p><ul><li><strong>Unusual Network Activity:</strong> Look for unexpected spikes in network traffic, particularly to unfamiliar external servers, as this could signal QakBot’s presence.</li><li><strong>Strange Behavior on Devices:</strong> Slower performance, unexpected crashes, or other unusual behaviors might indicate that QakBot is at work.</li><li><strong>Unusual Login Activity:</strong> Logins occurring at odd times or from unusual locations could be a result of QakBot using stolen credentials.</li><li><strong>Unexpected Emails:</strong> Suspicious emails, especially those appearing to come from trusted internal sources, may suggest that QakBot is spreading within your organization.</li><li><strong>Antivirus Alerts:</strong> While QakBot is adept at hiding, it’s not foolproof. Occasionally, antivirus or security software might detect unusual files or activities linked to QakBot.</li><li><strong>Botnet Indicators:</strong> If your systems are sending out large amounts of spam or participating in other activities without your knowledge, it could indicate that QakBot is controlling them.</li></ul><p>For cyber insurance professionals, it’s more likely that you’ll only have access to external information, often referred to as “outside-in data.” This lack of direct access makes detecting or making informed assumptions about QakBot infections more challenging. However, external indicators can be crucial early warning signs and should be used when making decisions on insured risk factors. Here are some methods to consider:</p><ul><li><strong>Monitoring Public Indicators of Compromise (IOCs):</strong> Keep an eye on public security reports that list suspicious IP addresses or domains associated with QakBot. If a company is communicating with these, it could indicate an infection.</li><li><strong>Analyzing Email Phishing Campaigns:</strong> By reviewing reports and alerts from threat intelligence services, industry reports, or email security providers, you can identify unusual patterns in phishing emails that may be linked to QakBot.</li><li><strong>Botnet Activity Detection:</strong> Monitoring reputation blacklists, using threat intelligence platforms, or employing botnet monitoring services can help identify if a company’s systems are sending out spam or participating in botnet activities.</li><li><strong>Public Reports and Disclosures:</strong> Stay updated on cybersecurity news and breach notifications, as some companies may publicly disclose compromises involving QakBot.</li></ul><p>While these methods aren’t foolproof, they can provide valuable insights or suspicions that a company might be compromised. Because internal or external detection alone is so challenging, relying on both internal and external indicators and threat intelligence often provides the best insight available. However, for definitive confirmation, incident response professionals with internal access to the company’s systems and data is typically required. Remember, even with internal access, detection is not guaranteed, so the importance companies using multiple layers of detection, both internal and external is critical. Understanding these detection challenges is essential for cyber insurance professionals, as they play a critical role in assessing risks and managing claims processes.</p><p>To further enhance your understanding of QakBot and stay ahead of the curve, explore these in-depth resources. They offer valuable insights and up-to-date information on the latest developments in QakBot’s evolution and its impact on the cyber insurance landscape.</p><ul><li>CISA: Cybersecurity Advisory on QakBot <a href="https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-242a">https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-242a</a></li><li>Zscaler: Tracking 15 Years of QakBot Development <a href="https://www.zscaler.com/blogs/security-research/tracking-15-years-qakbot-development">https://www.zscaler.com/blogs/security-research/tracking-15-years-qakbot-development</a></li><li>SOCRadar: QakBot — One of the Most Observed Malware <a href="https://socradar.io/qakbot-one-of-the-most-observed-malware/">https://socradar.io/qakbot-one-of-the-most-observed-malware/</a></li><li>TechRadar: QakBot Returns with New Malware Tricks <a href="https://www.techradar.com/pro/security/qakbot-returns-devious-new-malware-tricks-victims-by-using-a-fake-adobe-installer">https://www.techradar.com/pro/security/qakbot-returns-devious-new-malware-tricks-victims-by-using-a-fake-adobe-installer</a></li><li>Microsoft: A Closer Look at QakBot’s Latest Building Blocks <a href="https://www.microsoft.com/en-us/security/blog/2021/12/09/a-closer-look-at-qakbots-latest-building-blocks-and-how-to-knock-them-down/">https://www.microsoft.com/en-us/security/blog/2021/12/09/a-closer-look-at-qakbots-latest-building-blocks-and-how-to-knock-them-down/</a></li><li>Sophos 2024 Threat Report <a href="https://news.sophos.com/en-us/2024/03/12/2024-sophos-threat-report/">https://news.sophos.com/en-us/2024/03/12/2024-sophos-threat-report/</a></li><li>ProLock Ransomware teams up with QakBot trojan for network access <a href="https://www.bleepingcomputer.com/news/security/prolock-ransomware-teams-up-with-qakbot-trojan-for-network-access/">https://www.bleepingcomputer.com/news/security/prolock-ransomware-teams-up-with-qakbot-trojan-for-network-access/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10ce3f419b78" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[In a galaxy far, far away, the eternal battle between the Light and Dark sides of the Force mirrors…]]></title>
            <link>https://medium.com/@tyz_89492/in-a-galaxy-far-far-away-the-eternal-battle-between-the-light-and-dark-sides-of-the-force-mirrors-4352d7f22a35?source=rss-2a044bb9278b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4352d7f22a35</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[self-awareness]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[star-wars]]></category>
            <dc:creator><![CDATA[Ty Zeno]]></dc:creator>
            <pubDate>Mon, 29 Jul 2024 15:11:25 GMT</pubDate>
            <atom:updated>2024-07-29T15:11:25.796Z</atom:updated>
            <content:encoded><![CDATA[<p>In a galaxy far, far away, the eternal battle between the Light and Dark sides of the Force mirrors our own daily struggles between good and evil. As I reflect on the world around me, I find myself drawn to the philosophy and moral dilemmas of the Star Wars universe. The Jedi’s quest to align with the will of the Force and resist the temptations of the Dark Side resonates deeply with my own journey to uphold integrity and compassion in a complex world.</p><p>In this morning’s reflection, I will explore my interpretation of the Force as a metaphor for the moral compass guiding us all. I’ll delve into the challenges of staying true to the light, especially when faced with adversity and the seductive allure of easier, darker paths. Through the lens of Star Wars, I seek to understand my role in this vast universe and how I can contribute positively, doing the will of the Force while maintaining my commitment to justice, peace, and empathy. This reflection is not just about the fictional battles of Jedi and Sith, but about our real-world choices and the impact they have on the world and people around us.</p><p>In &quot;Star Wars: Darth Bane: Rule of Two&quot;, Master Valenthyne Farfalla is a Jedi who cautions against the allure of the dark side. One of his notable lines is:</p><p>&quot;This is the danger of the dark side. It can corrupt even the best intentions and lead even the good to do evil.&quot;</p><p>This warning emphasizes the dark side’s capacity to corrupt and the importance of staying vigilant and maintaining one’s moral compass, even when faced with challenging circumstances. Farfalla’s words serve as a reminder that the path to the dark side can start with small compromises and seemingly benign actions.</p><p>As I navigate my daily life, I strive to embody the lessons from the Force in my worldview, conversations, and interactions within both physical and digital realms. By seeking balance and harmony, I aim to accept the things I can not change, change the things I can, and discern the difference between the two. This journey, like that of the Jedi, is ongoing and challenging, but it is one I embrace with a hopeful heart, knowing that even small acts of kindness and understanding can make a profound difference. May the Force be with us all as we walk our unique paths.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4352d7f22a35" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Understanding Cyber Risk: Start with Critical Infrastructure and Key Resources (CIKR) ]]></title>
            <link>https://medium.com/@tyz_89492/understanding-cyber-risk-start-with-critical-infrastructure-and-key-resources-cikr-c9e60dee2b5d?source=rss-2a044bb9278b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9e60dee2b5d</guid>
            <category><![CDATA[digital-asset]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber-risk]]></category>
            <category><![CDATA[philosophy]]></category>
            <dc:creator><![CDATA[Ty Zeno]]></dc:creator>
            <pubDate>Mon, 29 Jul 2024 00:34:22 GMT</pubDate>
            <atom:updated>2025-10-17T14:38:01.266Z</atom:updated>
            <content:encoded><![CDATA[<p>🌐 **Understanding Cyber Risk: Start with Critical Infrastructure and Key Resources (CIKR)** 🌐</p><p>In the complex world of cybersecurity, not all assets are equal. My latest article explores why starting with a CIKR framework is crucial for identifying and protecting the most critical aspects of your business. Drawing inspiration from strategists like Sun Tzu and Musashi, I discuss how to &quot;Know the Enemy,&quot; &quot;Know Yourself,&quot; and choose the right tools to fortify your defenses.</p><h3>Cyber Risk Understanding: Start with Critical Infrastructure and Key Resources (CIKR)</h3><p>One reason why understanding risks, vulnerabilities, and threats in the cyber domain is difficult is because many don’t have a framework to help them identify critical questions that must be answered or understood first. In cybersecurity, as in business, if everything is labeled critical, then nothing truly is. To protect what matters most, leaders must distinguish the essential from the merely important or convenient, focusing resources on what truly impacts business operations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*QPlSDZ6w25Go6gee" /></figure><p>CIKR Framework for YOUR Business Operations and Strategies</p><p>Maintaining the confidentiality, integrity, and availability (CIA) of data, resources, and infrastructure is one of the most challenging tasks for those responsible for these assets. This triad, known universally in cyber and IT sectors, is crucial for securing information and maintaining operational standards. However, the question arises: how can we measure these elements in an environment that is inherently risky and constantly changing? How can we ensure that our cybersecurity measures are adequate to protect our information and infrastructure when our dependency of the functions they provide are not in my control?</p><p>Many organizations fall into the trap of a false sense of security, or they find themselves perpetually playing a game of “whack-a-mole,” responding reactively to threats as they arise. One reason for this is because we start on the wrong foot when thinking about “assessing risks and vulnerabilities” in general. To address these challenges, let’s take a step back and consider our current state through the lens of some of the world’s greatest strategists.</p><p>Sun Tzu, in <em>The Art of War</em>, famously said, “If you know the enemy and know yourself, you need not fear the result of a hundred battles. If you know yourself but not the enemy, for every victory gained you will also suffer a defeat. If you know neither the enemy nor yourself, you will succumb in every battle.” Similarly, Miyamoto Musashi, in <em>The Book of Five Rings</em>, advised against becoming too attached to any particular weapon, emphasizing the need for versatility and adaptability.</p><p>A historical example illustrating the perils of overconfidence comes from Fu Chien, the prince of Ch`in. In 383 A.D., despite commanding a vast army, he underestimated his opponents and suffered a devastating defeat. This overconfidence, born of numerical superiority, mirrors the mindset of some industry leaders today. They invest heavily in cybersecurity tools and personnel, believing that outspending potential attackers ensures safety. However, internal and external threats continue to impact the CIA of their systems, leading to potentially disastrous outcomes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/522/0*GgeU-3U5zfsSRYdz" /></figure><p>To better understand and mitigate these risks, we should revisit the foundational principles laid out by strategists like Tzu and Musashi:</p><p>1. Know the Enemy: Understanding potential threats, whether they come from external hackers, insider threats, or accidental breaches, is crucial. This involves staying updated with threat intelligence and being aware of the tactics, techniques, and procedures (TTPs) used by adversaries.</p><p>2. Know Yourself: This means having a clear understanding of your own infrastructure, including its strengths, vulnerabilities, core business functions, and dependencies. It also involves recognizing the limitations of your current cybersecurity measures and being prepared to adapt as needed.</p><p>3. Know the Weaponry that Suits You: In the context of cybersecurity, this translates to choosing the right tools, technologies, and strategies that align with your specific needs and risk profile. It’s not about having the most expensive or cutting-edge solutions but about having the right ones.</p><p>Many people trying to identify, assess, or quantify cyber risk start with the wrong mindset. They focus on the highest CVSS scores or whether vulnerabilities are being actively exploited in the wild. The real starting point should be a framework similar to that used for Critical Infrastructure and Key Resources (CIKR). The CIKR framework is designed to protect essential services and resources and can be scaled to fit the specific scope or area of concern.</p><p>The CIKR approach involves:</p><p>1. Identifying Critical Assets: Determining what needs protection is the first step. This involves identifying the infrastructure or resources vital to your business operations.</p><p>2. Prioritizing These Assets: Once identified, these assets must be prioritized based on the impact their loss would have on your business.</p><p>3. Determining Necessary Protections and Redundancies: Finally, planning the necessary safeguards and redundancies ensures that core business operations can continue during incidents.</p><p>With these elements in place, organizations can develop a robust strategy for assessing risks, vulnerabilities, and threats. This strategic approach ensures the resilience and security of vital infrastructure and resources, protecting them from a range of threats, including natural disasters, cyberattacks, and terrorism. By focusing on the right metrics and principles, we can better safeguard our assets and ensure long-term security in the ever-evolving cyber domain.</p><p>The insights of strategists like Tzu and Musashi are as relevant today in the cyber domain as they were in ancient times. By thoroughly understanding our adversaries, our own systems, and the tools at our disposal, we can develop more effective defenses against cyber threats. Adopting a structured approach, such as the CIKR framework, allows us to identify, prioritize, and protect our critical assets, ensuring business continuity even in the face of adversity.</p><p>In an era where cyber threats are becoming increasingly sophisticated, it’s not just about responding to incidents but proactively building a resilient infrastructure. This means going beyond surface-level metrics and focusing on what truly matters — maintaining the integrity and availability of our core operations. As we navigate the complexities of the digital landscape, a strategic, informed, and adaptable approach will be our best defense, safeguarding our organizations from the myriad challenges that lie ahead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*H7UTmM0DUteg7cxom49jew.png" /></figure><p>Original post: https://www.linkedin.com/pulse/cyber-risk-understanding-start-critical-key-resources-natal-ty-zeno-u7s7e/</p><p>#CyberSecurity #CriticalInfrastructure #RiskManagement #CIAtriad #CyberResilience #StrategicPlanning #CIKRFramework</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9e60dee2b5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>