Insights · Looking Back

Security & Resilience

The Looking Back articles seen through security & resilience, across every sector, in order.

61 articles

January 2020

  1. Week of 13 January 2020

    Why a Windows crypto patch was an asset inventory test

    CISA gave agencies ten business days to patch a Windows cryptographic flaw, on the day Windows 7 support ended. Applying the fix was the easy step. Knowing which systems needed it, who owned them and how to prove it was the hard one.

    • Government
    • Security & Resilience
    • 5 min read

February 2020

  1. Week of 10 February 2020

    What the Equifax indictment changed for banks, and what it did not

    The Justice Department charged four Chinese military officers over the 2017 Equifax breach. For banks, the indictment settled who did it and changed nothing that mattered operationally: the data stayed exposed, the entry point stayed ordinary and accountability stayed with the data holder.

    • Financial Services
    • Security & Resilience
    • 5 min read

April 2020

  1. Week of 20 April 2020

    Zoom 5.0 fixed the vendor layer; configuration and records stayed yours

    Zoom’s April 2020 release improved encryption and tightened defaults after weeks of scrutiny. For banks, health systems and agencies, most compliance risk sat in two layers no vendor release could fix: how the platform was configured, and what meeting content had to be kept.

    • Cross-sector
    • Security & Resilience
    • 5 min read

May 2020

  1. Week of 4 May 2020

    Password spraying against research labs: an old attack on a new target

    The May 5, 2020, CISA and NCSC advisory warned that state-backed groups were spraying passwords at health and research organizations to reach COVID-19 research. The defenses were familiar; applying them across academic medicine’s split identities, data stores and remote access was the hard part.

    • Healthcare
    • Security & Resilience
    • 5 min read

June 2020

  1. Week of 22 June 2020

    BlueLeaks: one small web host, hundreds of agencies’ files

    BlueLeaks exposed years of law enforcement and fusion center documents through the compromise of one web development firm. Each agency had judged a small contract; nobody had judged the shared platform, its accumulated archive or its sprawling user base.

    • Government
    • Security & Resilience
    • 5 min read

July 2020

  1. Week of 20 July 2020

    The control system map most operators did not have

    The NSA and CISA alert of July 23, 2020, urged immediate action to protect control systems. Its first and hardest request was an accurate map of what was actually connected, which municipal utilities, hospitals and data center operators rarely had.

    • Cross-sector
    • Security & Resilience
    • 5 min read

September 2020

  1. Week of 7 September 2020

    When a hospital diverts, the whole region absorbs the attack

    The Düsseldorf ransomware attack is remembered for a disputed death. Its lasting lesson for health systems is regional: cyber diversion moves clinical risk onto ambulances and neighboring hospitals that rarely plan for it, and rarely measure it.

    • Healthcare
    • Security & Resilience
    • 5 min read

December 2020

  1. Week of 14 December 2020

    SolarWinds and the three assumptions behind every update policy

    The Orion compromise broke three things agencies took for granted: that a signed update is a safe update, that monitoring tools are low-risk plumbing, and that federal sensors would catch a national-scale intrusion. Only the second was quick to fix.

    • Government
    • Security & Resilience
    • 5 min read

January 2021

  1. Week of 4 January 2021

    Credit for security practice, payable only in arrears

    A short HITECH amendment signed on January 5, 2021 told HHS to weigh recognized security practices when penalizing breaches. The credit requires a year of practice already in place, so it can only be earned before an incident, with evidence produced by daily operations.

    • Healthcare
    • Security & Resilience
    • 5 min read
  2. Week of 11 January 2021

    Before the 36-hour clock: deciding which bank incidents count

    The banking agencies’ proposed notification rule looked like a deadline. The harder work sat upstream of it: a named judgment about what counts as material disruption, and vendor notices that reach the people making that judgment in time.

    • Financial Services
    • Security & Resilience
    • 5 min read

February 2021

  1. Week of 8 February 2021

    Oldsmar’s disputed hack, undisputed weaknesses

    Nobody could later prove whether an outsider or an employee changed Oldsmar’s chemical setting. That uncertainty was itself the finding: small utilities need evidence that can tell the two apart, safeguards that work whoever acts, and public statements that survive revision.

    • Government
    • Security & Resilience
    • 5 min read

March 2021

  1. Week of 1 March 2021

    ProxyLogon: the patch was the easy part

    The March 2021 Exchange Server zero-days looked like a patching race. For public agencies, the damage was decided by three gaps a patch could not close: knowing what faced the internet, hunting for intruders afterward, and owning the decision to retire the platform.

    • Government
    • Security & Resilience
    • 5 min read
  2. Week of 15 March 2021

    Why business email compromise belongs to the payments team

    The FBI’s 2020 crime report again put business email compromise at the top of its loss table. For banks and credit unions, the controls that decide those losses sit at three points in payment operations, and the inbox is only the first.

    • Financial Services
    • Security & Resilience
    • 5 min read

April 2021

  1. Week of 26 April 2021

    Backups could not answer the D.C. police data leak

    The Babuk group’s theft of Washington, D.C. police files in April 2021 showed agencies that extortion now ran on disclosure. Planning had to start from which data would hurt whom if published: the workforce, the mission, or the public.

    • Government
    • Security & Resilience
    • 5 min read

May 2021

  1. Week of 17 May 2021

    Ireland’s HSE attack was decided in the eight weeks before encryption

    The Conti attack on Ireland’s Health Service Executive is remembered for its national scale. Its later independent review showed the outcome was set during nearly eight weeks of undetected access, across three stages: entry, dwell and response.

    • Healthcare
    • Security & Resilience
    • 5 min read

July 2021

  1. Week of 26 July 2021

    What a voluntary control systems memo could not give small water utilities

    The July 2021 national security memorandum promised cybersecurity goals for infrastructure control systems. Voluntary goals presume an owner, a budget line and a reason to act. Most small public water systems had none, and local officials, not federal agencies, were positioned to supply them.

    • Government
    • Security & Resilience
    • 5 min read

October 2021

  1. Week of 18 October 2021

    BlackMatter’s reach was set by the directory, not the malware

    The October 2021 BlackMatter advisory described attackers arriving with stolen credentials and using Active Directory to find everything worth encrypting. How far one credential could travel was decided by identity design made years earlier.

    • Cross-sector
    • Security & Resilience
    • 5 min read

January 2022

  1. Week of 17 January 2022

    No key to buy: WhisperGate and the agency recovery plan

    WhisperGate looked like ransomware but destroyed data with no way back. For US public agencies, it exposed continuity plans that quietly counted on payment as a last resort, and recovery times nobody had measured from total loss.

    • Government
    • Security & Resilience
    • 5 min read

March 2022

  1. Week of 21 March 2022

    A support engineer two contracts away: Okta, Lapsus$ and the hospital front door

    The March 2022 Okta disclosure showed that a subcontractor’s support engineer sat inside every customer’s trust boundary. For health systems running clinical access through one identity provider, the exposure was the two months before customers knew, and the logs they did not hold.

    • Healthcare
    • Security & Resilience
    • 5 min read

April 2022

  1. Week of 4 April 2022

    Cyclops Blink turned forgotten firewalls into someone else’s infrastructure

    The April 2022 court-authorized takedown of the Cyclops Blink botnet showed small firewalls serving Russian military intelligence as relays, often without their owners noticing. For public agencies, an unmanaged edge device is a liability to others before it is a breach of their own.

    • Government
    • Security & Resilience
    • 5 min read
  2. Week of 18 April 2022

    TraderTraitor aimed fake job offers at the engineers who hold the keys

    An April 2022 federal advisory described North Korean operators courting crypto-firm engineers with fake recruiting and trojanized apps. For any financial firm, a job approach reaches the people with the most access through a channel security rarely watches, so controls must assume one will succeed.

    • Financial Services
    • Security & Resilience
    • 5 min read

July 2022

  1. Week of 4 July 2022

    Rogers: the bank outage that started at someone else’s carrier

    When one Canadian carrier failed for most of a day, debit payments failed nationwide, including for banks that never bought a Rogers circuit. Telecom dependency hides in three places a bank’s dual-carrier policy does not reach: shared payment utilities, thinly connected channels, and customers’ phones.

    • Financial Services
    • Security & Resilience
    • 5 min read

August 2022

  1. Week of 22 August 2022

    LastPass and the first-draft problem in vendor breach notices

    LastPass’s August 2022 notice reported stolen source code and safe customer data. The attacker’s next stage was already under way. Customers needed to read the notice for what it enabled, know what their vaults exposed, and be ready to rotate.

    • Cross-sector
    • Security & Resilience
    • 5 min read

September 2022

  1. Week of 5 September 2022

    When a service portal is the target, the outage is the message

    Iran’s attack on Albania’s e-government services aimed at public embarrassment, not ransom. When disruption is the goal, agencies have to defend a minimum visible service, contest the attacker’s story, and know who decides on attribution.

    • Government
    • Security & Resilience
    • 5 min read

October 2022

  1. Week of 31 October 2022

    How hospitals spent the OpenSSL week waiting for ‘not affected’

    A week’s warning of a critical OpenSSL flaw should have made the answer easy. For health systems, it depended on suppliers saying their products were not affected, and few could get that statement quickly, in usable form, or at all.

    • Healthcare
    • Security & Resilience
    • 5 min read

November 2022

  1. Week of 14 November 2022

    What Hive’s victims gained by calling the FBI early

    When federal agencies warned health care about Hive ransomware, the FBI had secretly held the group’s decryption keys for months. Victims who reported got them. Health systems should settle when to call, what to share and how reporting fits other clocks.

    • Healthcare
    • Security & Resilience
    • 5 min read

January 2023

  1. Week of 23 January 2023

    Hive’s takedown removed a supplier, not the ransomware market

    The FBI’s disruption of Hive spared many victims, hospitals among them, from paying. It removed one ransomware brand. The affiliates, techniques and hospital weaknesses that made the attacks work were untouched, and those needed different responses.

    • Healthcare
    • Security & Resilience
    • 5 min read
  2. Week of 30 January 2023

    ION’s outage exposed a vendor no board had on its critical list

    The ransomware attack on ION’s cleared derivatives software showed that sector-wide disruption often starts at specialized post-trade vendors that many firms share and few rank as critical. Finding them, grading them and rehearsing life without them are three separate jobs.

    • Financial Services
    • Security & Resilience
    • 5 min read

February 2023

  1. Week of 6 February 2023

    One console, every server: what ESXiArgs exposed about the hypervisor

    ESXiArgs exploited a flaw patched two years earlier, but its damage came from where it struck. At the virtualization layer, one compromise encrypts every server, sits below most security tooling, and can take the backups with it.

    • Cross-sector
    • Security & Resilience
    • 5 min read

May 2023

  1. Week of 22 May 2023

    Volt Typhoon left little to scan for, so agencies had to know their own normal

    The May 2023 disclosures described a state actor inside US infrastructure using built-in tools and hijacked routers, not malware. Agencies and utilities had to know normal administrator behavior, own their network edge, and plan to run without a trustworthy network.

    • Government
    • Security & Resilience
    • 5 min read

June 2023

  1. Week of 5 June 2023

    Most MOVEit victims never ran MOVEit

    MOVEit reached thousands of organizations through payroll, pension and contractor firms that ran the software for them. Those clients had nothing to patch. Their exposure turned on finding affected vendors fast, settling who notified whom, and how much data they had sent.

    • Cross-sector
    • Security & Resilience
    • 5 min read

September 2023

  1. Week of 4 September 2023

    Storm-0558’s key escaped through a crash dump, a path every agency development team also has

    Microsoft’s September 2023 post-mortem described a signing key that left production in diagnostic data, tokens accepted beyond their scope, and a key that lived for years. Agencies that build their own applications carry all three risks in their own code and contracts.

    • Government
    • Security & Resilience
    • 5 min read
  2. Week of 11 September 2023

    For banks, the MGM and Caesars intrusions were about the few accounts that run the identity platform

    The September 2023 casino attacks used help desk calls to reach identity administrators. For banks, the priority was a small set of control-plane accounts: how they are recovered, who is allowed to recover them, and how a takeover of the identity platform would be spotted.

    • Financial Services
    • Security & Resilience
    • 5 min read

October 2023

  1. Week of 23 October 2023

    How a troubleshooting file handed over an administrator’s session in the Okta breach

    Attackers in Okta’s support system replayed session tokens from files customers had uploaded. For health systems, which send vendors logs and screenshots daily, each support artifact’s exposure depends on what it contains, what it is under HIPAA, and how long it stays usable.

    • Healthcare
    • Security & Resilience
    • 5 min read

November 2023

  1. Week of 6 November 2023

    Three seats at ICBC’s ransomware attack, and the plan each one needed

    When LockBit hit ICBC’s U.S. broker-dealer in November 2023, Treasury trades still had to settle. Every market participant could have been in any of three seats, and each seat needed a different plan written before the day.

    • Financial Services
    • Security & Resilience
    • 5 min read

December 2023

  1. Week of 18 December 2023

    When the FBI offers a decryptor: what ALPHV’s takedown asked of public agencies

    The December 2023 ALPHV disruption gave hundreds of victims a free decryption tool. Accepting that help well required three things agencies rarely plan for: confirming the offer is real, using the tool without making recovery worse, and keeping legal duties on their own clock.

    • Government
    • Security & Resilience
    • 5 min read

January 2024

  1. Week of 8 January 2024

    Why the SEC’s hijacked account was most valuable the day before a decision

    The false bitcoin ETF post from the SEC’s X account came one day before the actual approval, when markets were primed to believe it. Agencies whose announcements move markets or behavior should secure official accounts as privileged credentials, by the calendar, and for the audience.

    • Government
    • Security & Resilience
    • 5 min read

February 2024

  1. Week of 12 February 2024

    Convincing faces, unauthenticated seats: the Hong Kong deepfake was a meeting-identity failure

    The deepfaked video call that moved about US$25 million beat a meeting, not a payment system. Most firms let staff treat a face on screen as identity. Banks need controls at the invitation, inside the meeting, and at the handoff to money.

    • Financial Services
    • Security & Resilience
    • 5 min read
  2. Week of 19 February 2024

    How Change Healthcare’s customers decided whether to pull the plug, and when to plug back in

    When ransomware hit the largest US claims clearinghouse, every connected provider faced the same call. Cutting the connection was quick. Knowing what to cut, and what proof to demand before reconnecting, depended on preparation few had done.

    • Healthcare
    • Security & Resilience
    • 5 min read

March 2024

  1. Week of 18 March 2024

    The governors’ water letter handed one problem to three state secretaries

    The March 2024 White House and EPA letter invited each state’s environmental, health and homeland security secretaries. That list was the finding: water cybersecurity in a state sits with a regulator, a funder and a responder, and few governors had named anyone to join them.

    • Government
    • Security & Resilience
    • 5 min read

April 2024

  1. Week of 29 April 2024

    Why Change Healthcare’s missing MFA was a deal-integration failure

    UnitedHealth’s testimony traced the Change Healthcare attack to a remote-access portal without MFA, about sixteen months after the acquisition closed. Health care buyers should treat inherited internet-facing access as a closing condition, an interim-period control set and a board-level exception list.

    • Healthcare
    • Security & Resilience
    • 5 min read

July 2024

  1. Week of 22 July 2024

    Why North Korea’s fake remote hires succeed in the gaps between HR, IT and security

    KnowBe4’s account of hiring a North Korean IT worker showed a scheme built to pass four hand-offs, each owned by a different team. Controls work when one identity is carried from interview to offer, onboarding, device and daily work.

    • Cross-sector
    • Security & Resilience
    • 5 min read

October 2024

  1. Week of 14 October 2024

    NYDFS wrote no AI rule, and made AI risk part of what the CEO certifies

    New York’s October 2024 letter on AI and cybersecurity added no requirements. Because Part 500 already demands an annual compliance certification signed by the CEO and CISO, it turned four AI risks into evidence those signers must be able to produce.

    • Financial Services
    • Security & Resilience
    • 5 min read

December 2024

  1. Week of 23 December 2024

    The HIPAA Security Rule proposal’s hardest line was a 72-hour restore

    HHS’s proposed overhaul turned flexible safeguards into specific requirements. Sorted by difficulty, most were controls hospitals already had or evidence they could build. Recovery within 72 hours was different: it needed clinical sequencing, tested capacity and money few systems had budgeted.

    • Healthcare
    • Security & Resilience
    • 5 min read
  2. Week of 30 December 2024

    Treasury’s breach ran through a remote-support key the agency never held

    Attackers reached Treasury workstations with a stolen key that secured a vendor’s cloud remote support service. Remote support is privileged access by another name, and governing it takes four controls along the path from vendor to endpoint, most of which agencies only partly had.

    • Government
    • Security & Resilience
    • 5 min read

February 2025

  1. Week of 3 February 2025

    In the Treasury payment access dispute, “read-only” was a claim until the records proved it

    Setting the politics aside, the fight over new access to Treasury’s payment systems played out in sworn filings about who had which permissions. It showed that privileged access governance rests on four separate controls, and that each must be provable, not just stated.

    • Government
    • Security & Resilience
    • 5 min read
  2. Week of 17 February 2025

    Bybit’s signers approved what their screens showed, which was not what they signed

    The largest crypto theft on record defeated multi-signature approval without breaking it, by altering the interface the signers trusted. Banks approving payments through software face the same risk at four points: how the interface is built, what approvers see, how payments are verified, and recovery.

    • Financial Services
    • Security & Resilience
    • 5 min read

March 2025

  1. Week of 10 March 2025

    Medusa showed that a clinic’s remote-support software is its ransomware attack surface

    The March 2025 Medusa advisory read like a catalog of the remote-access and management products hospitals and clinics depend on. Defending against it means governing those tools at three points: entry, movement and evasion.

    • Healthcare
    • Security & Resilience
    • 5 min read

April 2025

  1. Week of 7 April 2025

    Supervisory correspondence: a bank’s most candid file, held in a system it cannot assess

    The OCC’s email breach showed that a bank’s frankest account of its own weaknesses sits with a regulator it cannot audit or replace. Banks still control what they write, how it travels, and how they respond to a breach.

    • Financial Services
    • Security & Resilience
    • 5 min read

June 2025

  1. Week of 16 June 2025

    Why Scattered Spider’s turn to insurers should have set a deadline for the rest of finance

    When a group that works one industry at a time reached U.S. insurers in June 2025, threat intelligence turned into a date. Institutions needed a pre-agreed surge mode: a named trigger, tighter help-desk rules for weeks, and containment planned around compromised identity.

    • Financial Services
    • Security & Resilience
    • 5 min read
  2. Week of 23 June 2025

    One alert, three threats: how local agencies should have read the June 2025 Iran warning

    After U.S. strikes on Iran, federal warnings described one heightened threat. For cities, counties and utilities it was three: hacktivist noise, opportunistic attacks on exposed control systems, and patient state operations. Each has a different owner, timescale and fix.

    • Government
    • Security & Resilience
    • 5 min read

September 2025

  1. Week of 22 September 2025

    Persistence below the patch: what ED 25-03 asked agencies to prove about their firewalls

    CISA’s Emergency Directive 25-03 described attackers who altered Cisco firewall boot firmware to survive reboots and upgrades. The burden shifted from applying a fix to proving that each device could be trusted, and that the fix was the right one.

    • Government
    • Security & Resilience
    • 5 min read

October 2025

  1. Week of 6 October 2025

    Cl0p’s Oracle campaign: an attack on the systems security teams did not run

    The Oracle E-Business Suite extortion wave succeeded because ERP sits with finance, not security. Closing the gap means settling emergency authority, shrinking what faces the internet and cutting what the application retains.

    • Cross-sector
    • Security & Resilience
    • 5 min read

March 2026

  1. Week of 2 March 2026

    Iran’s war tested banks’ decision rights more than their defenses

    The cyber warnings after the strikes on Iran named old techniques banks knew how to stop. The harder test was deciding, amid market stress and thin federal support, what to fix first, who could break a change freeze, and what to demand of providers.

    • Financial Services
    • Security & Resilience
    • 5 min read
  2. Week of 9 March 2026

    Stryker’s wipe made a supplier’s admin console a hospital supply risk

    The attack on Stryker reportedly used the company’s own device-management tools to erase systems, with no ransom and no patient data at stake. It reached hospitals through orders and shipments, which most vendor risk reviews never examine.

    • Healthcare
    • Security & Resilience
    • 5 min read

April 2026

  1. Week of 6 April 2026

    When AI made flaws cheap to find, banks’ patch queues set the pace

    Few banks had access to the model officials warned them about. For most, faster AI-driven discovery would arrive as a surge of fixes from vendors and open-source maintainers, so the constraint was how fast they could absorb patches.

    • Financial Services
    • Security & Resilience
    • 5 min read
  2. Week of 27 April 2026

    Lower quantum estimates moved signatures up the post-quantum queue

    Spring 2026 research cut estimates of what it would take to break elliptic-curve cryptography. For agencies, that mattered less for encryption than for authentication, where certificates, smart cards and firmware keys take longest to replace.

    • Government
    • Security & Resilience
    • 5 min read

May 2026

  1. Week of 18 May 2026

    Searching by balance: how bribed bank insiders choose their targets

    Bank insider cases prosecuted in 2026 show bribed employees selling three things: the search that finds valuable customers, the screens that expose them, and the overrides that open doors. Each can be controlled without first catching the insider.

    • Financial Services
    • Security & Resilience
    • 5 min read

June 2026

  1. Week of 8 June 2026

    Why World Cup cyber risk sat in the city services residents use every day

    Stadiums had federal, state and venue security teams. The exposure host-city agencies owned was in the services around them: resident and visitor channels, transit and traffic systems, 911 and dispatch, and vendors shared across jurisdictions.

    • Government
    • Security & Resilience
    • 5 min read

August 2026

  1. Week of 31 August 2026

    Bank cyber gaps now arrive as observations the board never has to see

    The OCC and FDIC limited matters requiring attention to material financial harm, a year after the FFIEC retired its common cyber assessment. Many cyber weaknesses will now reach banks as informal observations, so banks must set their own escalation rules.

    • Financial Services
    • Security & Resilience
    • 5 min read

September 2026

  1. Week of 7 September 2026

    Europe’s 24-hour vulnerability clock reports to regulators first and customers second

    From September 11, 2026, the Cyber Resilience Act required manufacturers to warn EU authorities of exploited flaws within 24 hours. Customers were owed notice too, but on no fixed clock, so buyers still need their own intake.

    • Cross-sector
    • Security & Resilience
    • 5 min read