GCRI · Cybersecurity and Digital Resilience
Data and technical methods
The public technical tools of Cybersecurity and Digital Resilience: the models and data behind them, how to reproduce a view and the uncertainty it carries.
The workspace for data and technical methods.
Pipeline
Data and technical methods · Workspace WS-52 · Example interface, not a record
Stages
- Ingest5 sources
- Validateschema · licence
- Transformversioned
- ModelCybersecurity
- Testheld-out
- Releasewith limits
Artefacts
| SIEM alerts | v2.5 | To check | OBSERVED |
| Asset inventory | v4.5 | Open | Published statistics |
| Vulnerability scans | v4.7 | Open | OBSERVED |
| Supplier assessments | v2.3 | Open | ASSESSED |
Compute quota
share used vs alert level
Cybersecurity and Digital Resilience · Pipeline. Pipeline: example names and illustrative values, not a record.
What is published here.
What every cyber tool should state about itself.
Cyber tools serve operators, regulators and insurers assessing systemic exposure. A specialist checks incident definitions, anonymisation and the dependency assumptions in accumulation scenarios. Tools rest on cybersecurity and network science and support the cloud and third parties and critical service cyber topics. Accumulation outputs are scenarios for planning, so they carry the share of affected organisations assumed and the recovery time used.
- Incident definitions used.
- Anonymisation applied.
- Dependency assumptions in accumulation scenarios.
How the process runs.
Process explorer · Process
Data and technical methods: Layers to published map
7 steps·4 stages·1 gate
Process
Data and technical methods: Layers to published map
Layers enter with their rights, are aligned, analysed and checked for uncertainty, then released after public-safe review; a map is a governed spatial claim.
01 Data
- 01Source layers with their rightsDataset · NXS-GRX (canonical data, provenance and risk)Spatial views of The Global Risks Index (NXS-GRX) products sit under the boundary licence gate. Rights classification sets how a layer may be used.
02 Harmonise
- 02Coordinate reference and boundary versionRecord · NXS-EOP (earth observation and digital twins)The area of interest preserves its coordinate reference system, polygon validity and observation support. Boundary versions are kept.
- 03Harmonise units, variables and timeStepUnit metadata, conversion records and transformation logs are required. Alignment is an evidence event, not hidden preprocessing.
03 Analyse and check
- 04Analyse with a recorded processing recipeModel · GIS teamA processing recipe records parameters, calibration, inputs and output lineage. The analysis methods are named in each product's own record.
- 05Spatial uncertainty checkGateSpatial uncertainty is recorded and affects downstream use. A high-uncertainty polygon may suit internal review, not public-safe release.
04 Publish
- 06Spatial metadata bundleRecordThe bundle records boundary type, jurisdiction, geometry version, projection, resolution, source, time window, uncertainty and access class.
- 07Public-safe release of the mapDecisionThe output record names the redactions, uncertainty and public-safe reviewer. A map is a governed spatial claim, never merely a picture.
Spatio-temporal intelligence · Data protocols: semantic, jurisdictional and temporal intelligence · NXS-EOPDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The pages cited are design doctrine.
Working with the tools.
Analysis runs in Foundry for authorised projects. Public pages show released views only, each with its time and space reference and its rights.
Where this page's references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Pages in Data and technical methods.
Questions and answers.
Can I use the data?
Contribute evidence from this page.
Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-GCRISend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Bring a method, a dataset or a question.
Information and enquiries are open today. 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.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.