Skip to content

Cybersecurity

Threat in Cybersecurity & Technology Failure, arrives with intent

A cyber hazard that halts government services, ransomware, a breach, a flood of traffic or a plain system fault, until dispatch, records and payments are restored.

Includes: Ransomware, Data Breach or Data Loss, Denial-of-Service, Critical Software or System Failure

  • Ransomware. An intent-driven cyber threat that encrypts systems and halts government services until they are restored or ransomed.
  • Data Breach or Data Loss. A cyber threat that exposes residents' and employees' personal data, with legal, financial and trust consequences.
  • Denial-of-Service. A cyber threat that floods public-facing systems with traffic, taking websites and online services offline.
  • Critical Software or System Failure. A non-malicious technology hazard: a software or hardware fault that takes down dispatch, records or payment systems without warning.
See a sample briefBook a walkthroughAll 31 hazards →

Sample brief

The first page of a Cybersecurity brief: likelihood, impact and readiness on your own scale, with each figure sourced.

Evidence brief for Cedar Ridge County (example)

September 14, 2026

Cybersecurity

Threat in Cybersecurity & Technology Failure, on the established threats & hazards list

Impact
5432112345

Likelihood

Likelihood
2

Unlikely — Possible but infrequent — roughly once in 50 to 100 years (1–2% chance in any year).

Impact
3

Moderate — Notable effects — injuries possible, damage in multiple areas, essential services disrupted for days.

Readiness
3

Moderate — The organization has a generally established capability to manage this threat or hazard, but identifiable gaps remain. The organization could likely perform many required actions, though effectiveness may vary depending on conditions, staffing, resources, or complexity.

  • 2source documents
  • 58verified mentions
  • —federal declarations
  • —NRI risk score
Worked example: Cedar Ridge County is fictional. The scores illustrate the format and are nobody's decision. Open a full sample brief →

The national record

FEMA’s National Risk Index doesn’t model Cybersecurity. Your team fills it with local evidence, and Hazzard shows the gap rather than a zero.

How it maps

The same hazard in the vocabularies your plan and FEMA already use.

FEMA National Risk Index
Not covered
FEMA declaration incident type
Not covered
NOAA Storm Events type
Not covered
Hazzard category
Cybersecurity & Technology Failure, infrastructure and technologyincludes Ransomware, Data Breach or Data Loss, Denial-of-Service, Critical Software or System Failure

The national record

What the federal data says about Cybersecurity: nothing yet

No federal dataset scores Cybersecurity or files declarations under it. That's common for threats and emerging hazards, and it's why a brief for Cybersecurity is built from your own plans, exercises and records. Hazzard shows the gap instead of inventing a number.

In your plan

What a Cybersecurity profile needs, and where each part comes from

A local hazard mitigation plan profiles each hazard the same way (44 CFR 201.6). Here is how Hazzard fills each part for Cybersecurity.

  1. Location

    44 CFR 201.6(c)(2)(i)

    Your documents

    No national layer maps Cybersecurity. We draw the geographic extent from your plans, studies and annexes, cited to the page.

  2. Extent

    44 CFR 201.6(c)(2)(i)

    Your documents

    The magnitude your plans use for Cybersecurity (a scale, a depth, an acreage, a duration), read from your documents and cited, so the profile states the strength you plan for.

  3. Previous occurrences

    44 CFR 201.6(c)(2)(i)

    Your documents

    FEMA files no declaration type for Cybersecurity. The history comes from your after-action reports, incident records and plans.

  4. Probability of future events

    44 CFR 201.6(c)(2)(i)

    Your team decides

    No national dataset gives a frequency for Cybersecurity. Your team scores likelihood on your scale from the evidence we organize.

  5. Vulnerability and impacts

    44 CFR 201.6(c)(2)(ii)

    Your documents

    The Census population profile and HHS emPOWER counts for context; the consequences themselves come from your plans and exercises.

  6. The assessment itself

    Your team decides

    Likelihood, impact and readiness for Cybersecurity are drafted with every source attached, and a person on your team accepts each one. Hazzard never records a score on its own.

How we can help

How we’d help you prepare for Cybersecurity

  1. 1

    We start from what you own

    Your continuity plan, incident-response material and exercise reports, read so each statement about Cybersecurity points to its source.

  2. 2

    We mark the gap

    No national dataset scores cyber risk for your county. The brief says so, and your team's evidence carries the score.

  3. 3

    You leave with a cited brief

    Likelihood, impact and readiness for Cybersecurity on your own scale, with each figure tied to its source. It is ready for your planning team or council.

Preparing for Cybersecurity

Bring Cybersecurity into the hazard plan with evidence behind it.

Cyber incidents sit on most threat lists, usually as a single paragraph. We assess them like the rest of the plan: scored, cited and assigned an owner. We reply within one business day.

Book a walkthrough

Takes about two minutes. A person reads each request.

Or start by marking your area on the map