Cybersecurity and Digital Resilience
The Global Centre for Risk and Innovation (GCRI)
Maps of Cybersecurity and Digital Resilience are published here once their data rights are cleared and they have been reviewed. Each shows its time and space reference, its sources and its uncertainty.
Cybersecurity and Digital Resilience released maps are reviewed map views of cyber and digital resilience, published once their data rights are cleared, each with its coordinate reference, date, sources and uncertainty. Layers draw on sources such as NIST Cybersecurity Framework 2.0. A map shows released, rights-cleared evidence, not a live feed or an official warning.
Fig.A programme from scoping to the owner's decision. Design, not a record.
For released maps, in GCRI's spatial-intelligence reading, the map opens on night lights, true-colour imagery and population density with night lights tonight from NASA GIBS, framed on World; every other NASA layer, live feed and forecast waits in the layer list.
The interactive map needs JavaScript; the layer list and sources are below.
Layers 3
Connected activity, for this page
Keyboard, with the map focused
Hold Ctrl or ⌘ and scroll to zoom
Latest available
NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth
Loading the latest NASA imagery.
Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.
For released maps, in GCRI's spatial-intelligence reading, the map opens on night lights, true-colour imagery and population density with night lights tonight from NASA GIBS, framed on World; every other NASA layer, live feed and forecast waits in the layer list.Satellite and model products as NASA publishes them, each with its own date; indicators, not assessments of any place; claim ceiling INTEGRATED.
Layers and dates
| Indicator | Unit | Cadence | Evidence label | Topic |
|---|---|---|---|---|
| Assets inventoried | percent of estimated assets | quarterly | Declared | Cyber risk management |
| Critical vulnerabilities past remediation target | count | weekly | Observed | Cyber risk management |
| Accounts with multi-factor authentication | percent of accounts | monthly | Observed | Cyber risk management |
| Known exploited vulnerabilities present | count | weekly | Observed | Cyber risk management |
| Board reporting on cyber risk | frequency per year | annual | Declared | Cyber risk management |
| Estimated loss range for top scenarios | currency range | per assessment | Estimated | Cyber risk management |
| Incidents reported by critical sectors | count by sector | annual | Official | Critical service cyber |
| Internet-exposed industrial control devices | count | monthly | Observed | Critical service cyber |
| Operators with tested manual fallback | percent of operators | per assessment | Reported | Critical service cyber |
| Service outage hours caused by cyber incidents | hours | per incident | Observed | Critical service cyber |
| Security advisories for industrial control systems | count | monthly | Official | Critical service cyber |
| IT and OT network segmentation | percent of sites segmented | per assessment | Declared | Critical service cyber |
| Critical services hosted with a single provider | count | per inventory | Declared | Cloud and third parties |
| Third parties with privileged access | count | quarterly | Observed | Cloud and third parties |
| Cloud misconfiguration findings | count by severity | weekly | Observed | Cloud and third parties |
| Contracts with incident notification and exit terms | percent of critical contracts | annual | Reported | Cloud and third parties |
| Provider outages affecting services | count and hours | annual | Observed | Cloud and third parties |
| Market share of top cloud providers | percent of market | annual | Estimated | Cloud and third parties |
| Accounts using phishing-resistant authentication | percent of accounts | monthly | Observed | Identity and data security |
| Privileged accounts | count | monthly | Observed | Identity and data security |
| Personal data breaches notified to regulators | count | annual | Official | Identity and data security |
| Records exposed in breaches | count | per breach | Reported | Identity and data security |
| Sensitive data encrypted at rest | percent of data stores | per assessment | Declared | Identity and data security |
| Credential exposure in breach datasets | count of organizational accounts | monthly | Observed | Identity and data security |
| Coordinated inauthentic networks removed | count of networks | quarterly | Reported | Information operations |
| Documented foreign information manipulation incidents | count | annual | Reported | Information operations |
| Reach of identified operations | estimated audience | per case | Estimated | Information operations |
| Synthetic media incidents in elections | count | per election | Reported | Information operations |
| Researcher data access under platform rules | count of approved requests | annual | Declared | Information operations |
| Content moderation actions | count by policy | per reporting period | Declared | Information operations |
| Median dwell time | days from intrusion to detection | annual | Estimated | Incident response recovery |
| Mean time to restore critical services | hours | per incident | Observed | Incident response recovery |
| Backups tested for restoration | percent of critical systems | quarterly | Observed | Incident response recovery |
| Immutable or offline backups | percent of critical data | per assessment | Declared | Incident response recovery |
| Incidents reported to national authorities | count by type | annual | Official | Incident response recovery |
| Incident response exercises held | count | annual | Reported | Incident response recovery |
| Products shipped with a software bill of materials | percent of products | per assessment | Declared | Supply chain security |
| Open-source dependencies with known vulnerabilities | count | weekly | Observed | Supply chain security |
| Builds with verifiable provenance | percent of builds | monthly | Observed | Supply chain security |
| Malicious packages reported in registries | count | monthly | Reported | Supply chain security |
| Critical projects with security practices in place | score on a stated checklist | per assessment | Estimated | Supply chain security |
| Time to remediate a critical component vulnerability | days | per event | Observed | Supply chain security |
| Systems with cryptographic inventory | percent of critical systems | per assessment | Declared | Post quantum migration |
| Connections using post-quantum or hybrid key exchange | percent of connections | monthly | Observed | Post quantum migration |
| Products supporting standard post-quantum algorithms | count | per assessment | Declared | Post quantum migration |
| Data with long confidentiality requirements | count of data classes | per assessment | Declared | Post quantum migration |
| Migration milestones met | percent of planned milestones | annual | Reported | Post quantum migration |
| Expert estimates of cryptographically relevant quantum computer timing | probability by period | annual | Estimated | Post quantum migration |
Analysis runs in Nexus Foundry; reviewed releases are listed here.
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| Coordinate reference system | The definition that ties coordinates to locations on Earth, catalogued with EPSG codes. |
| Modifiable areal unit problem | The change in statistical results that comes from how areas are drawn and aggregated. |
| Zonal statistics | Statistics of raster values summarised within boundaries such as districts. |
| Public-safe release | A recorded decision on the detail at which a layer may be published without exposing sensitive sites or people. |
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.