Cross-sector · Security & Resilience

Across sectors: security and resilience

What to know now

Each number links to the point's source. Points checked unless the point shows another date.

  • NIST released version 2.0 of its Cybersecurity Framework on February 26, 2024. NIST says it now explicitly aims to help all organizations, beyond critical infrastructure, its original target audience, and adds emphasis on governance and supply chains.1
  • CISA's Known Exploited Vulnerabilities JSON feed, catalog version 2026.11.13 (released 2026-11-13), lists 1,781 vulnerabilities. By our count from that feed, 297 were added in 2026 up to that date and 361 are marked as known to be used in ransomware campaigns.2
  • In its 2025 annual report, the FBI's Internet Crime Complaint Center says it received more than 3,600 ransomware complaints in 2025, with losses over $32 million. The top 10 reported variants most affected critical manufacturing, healthcare and public health, and government facilities.3
  • Executive Order 14409 of June 2, 2026 directed CISA, within 30 days, to release Binding Operational Directives and other guidance, including to help agencies, state and local authorities, and critical infrastructure operators such as rural hospitals, community banks and local utilities get access to cybersecurity tools and services. It also directed Treasury to form an AI cybersecurity clearinghouse, in voluntary collaboration with the AI industry and critical infrastructure operators, to coordinate scanning for, validating and patching software vulnerabilities.4
  • Executive Order 14390 of March 6, 2026 makes it U.S. policy to protect Americans from, and harden financial and digital systems against, cybercrime, fraud and predatory schemes. It ordered an action plan within 120 days that identifies the transnational criminal organizations responsible for scam centers and cybercrime and proposes ways to prevent, disrupt, investigate and dismantle them.5
  • On August 12, 2026, NIST asked for public input on modernizing the National Vulnerability Database as cybersecurity is increasingly shaped by AI and machine-consumable security data. Comments were due October 13, 2026.6

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.

Sources

  1. National Institute of Standards and Technology. NIST releases version 2.0 of landmark Cybersecurity Framework. Checked .
  2. Cybersecurity and Infrastructure Security Agency. Known Exploited Vulnerabilities catalog (JSON feed, catalog version 2026.11.13). Checked .
  3. Federal Bureau of Investigation, Internet Crime Complaint Center. 2025 IC3 Annual Report. Checked .
  4. Office of the Federal Register (Executive Office of the President). Executive Order 14409: Promoting Advanced Artificial Intelligence Innovation and Security. Checked .
  5. Office of the Federal Register (Executive Office of the President). Executive Order 14390: Combating Cybercrime, Fraud, and Predatory Schemes Against American Citizens. Checked .
  6. National Institute of Standards and Technology. Request for Information on Modernizing the National Vulnerability Database in the Age of Artificial Intelligence. Checked .

How we source and check every fact: Editorial standards · Corrections

Last reviewed .

Spotted an error? Tell us and we will check it and correct the page where needed.

Looking Back

  1. Week of September 7, 2026

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

    From September 11, 2026, Europe’s Cyber Resilience Act gave manufacturers 24 hours to warn authorities when attackers exploit a flaw in their products. Customers must be told too, but on no fixed clock, so buyers still need their own way to hear about it.

    • Cross-sector
    • Security & Resilience
    • 13 min read
  2. Week of October 6, 2025

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

    Cl0p’s Oracle E-Business Suite extortion wave worked because the finance system sat with finance, not security. Closing that gap takes three decisions: who can pull the plug in an emergency, what faces the internet, and how much old data the system keeps.

    • Cross-sector
    • Security & Resilience
    • 15 min read
  3. Week of July 22, 2024

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

    KnowBe4 hired a remote engineer who turned out to be a North Korean IT worker. The scheme worked by slipping through four hand-offs owned by different teams. It fails when one verified identity follows the hire from interview to daily work.

    • Cross-sector
    • Security & Resilience
    • 30 min read
  4. Week of June 5, 2023

    Many MOVEit victims never ran MOVEit

    MOVEit reached many organizations through the payroll, pension and contractor firms that ran it for them. Those clients had nothing to patch. What mattered was how fast they found affected vendors, who notified whom, and how much data they had handed over.

    • Cross-sector
    • Security & Resilience
    • 26 min read
  5. Week of February 6, 2023

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

    ESXiArgs used a flaw fixed two years earlier, but the damage came from where it struck. Hit the software that runs all your servers, and one break-in can lock every machine, slip past most security tools and reach the backups too.

    • Cross-sector
    • Security & Resilience
    • 26 min read
  6. Week of August 22, 2022

    LastPass and the first-draft problem in vendor breach notices

    In August 2022, LastPass said thieves had taken source code but no customer data. The attacker’s next move was already under way. The real test for customers was reading that first notice for what it made possible, and being ready to change every password.

    • Cross-sector
    • Security & Resilience
    • 26 min read
  7. Week of October 18, 2021

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

    The October 2021 BlackMatter advisory described an unglamorous attack: intruders walked in with stolen passwords and simply asked the company directory where everything was. How far one login could travel had been decided years earlier, by how access was designed.

    • Cross-sector
    • Security & Resilience
    • 26 min read
  8. Week of July 20, 2020

    The control system map most operators did not have

    On July 23, 2020, the NSA and CISA urged immediate action to protect the systems that run pumps, chillers and power. Their first and hardest request was an accurate map of what was actually connected, something few utilities, hospitals or data center operators had.

    • Cross-sector
    • Security & Resilience
    • 28 min read
  9. Week of April 20, 2020

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

    Zoom 5.0, released in April 2020, fixed real problems in its own product. For banks, hospitals and agencies, the bigger risks lived in two places no vendor could fix for them: how the tool was set up, and what its meetings left behind.

    • Cross-sector
    • Security & Resilience
    • 29 min read
  10. Week of May 13, 2019

    BlueKeep asked organizations to patch on a forecast, before any attack

    Microsoft warned in May 2019 that a Remote Desktop flaw was wormable, though no one had seen it exploited. Acting on that forecast took four things: criteria to judge it, a fast view of exposure, an emergency patch path and mitigations to hold the line.

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

All 11 Looking Back articles in Cross-sector and Security & Resilience

Explainers, checklists and data

  1. Explainer · November 14, 2026

    NIST SP 800-61 Revision 3, incident response as a CSF 2.0 profile, explained

    NIST’s April 2025 revision of SP 800-61 retires the four-phase incident handling cycle, maps incident response to the six CSF 2.0 Functions, rates each outcome High, Medium or Low, and moves the how-to material online.

    • Cross-sector
    • Security & Resilience
    • 6 min read
  2. Explainer · November 14, 2026

    NIST Cybersecurity Framework 2.0, explained: Govern, wider scope, Profiles and Tiers

    CSF 2.0, published on February 26, 2024, adds a sixth Function, Govern, drops the critical-infrastructure title, moves its references online and keeps Profiles and Tiers as the way an organization states where it is and where it wants to be.

    • Cross-sector
    • Security & Resilience
    • 5 min read
  3. Data brief · November 14, 2026

    CISA advisories in 2026: 465 ICS advisories, 140 KEV alerts and 10 cybersecurity advisories

    From January 1 to November 13, 2026, CISA published 465 industrial control system advisories, 140 alerts adding vulnerabilities to its KEV catalog and 10 cybersecurity advisories, 9 of them written with partner agencies. Other alerts fell from 64 to 13.

    • Cross-sector
    • Security & Resilience
    • 2 min read
  4. Checklist · November 14, 2026

    Checklist: the duties around a ransomware payment decision, from sanctions risk to suspicious activity reports and CIRCIA

    Twelve steps for the people who decide whether a ransom is paid: OFAC’s sanctions risk and reporting advice, FinCEN’s suspicious activity report guidance for financial institutions, CIRCIA’s 24-hour payment report once a final rule takes effect, and a state ban on public-entity payments as an example.

    • Cross-sector
    • Security & Resilience
    • 5 min read
  5. Data brief · November 13, 2026

    CISA’s exploited-vulnerability catalog in 2026: more additions, and most now due in three days

    CISA added 297 vulnerabilities to its Known Exploited Vulnerabilities catalog between January 1 and November 13, 2026, more than in the same stretch of any year since 2022. Since BOD 26-04 took effect on June 10, 128 of the 164 additions carry a three-day deadline.

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