Skip to content

GCRI · Foundations

Live operations: how Nexus Universe runs during its week of controlled exercises

The week of controlled exercises is where an annual programme is most exposed. This page explains who directs, controls and evaluates Nexus Universe, how an exercise is stopped, and what the week must leave on record.

As of
21 October 2026
خوانش
11 minutes
شواهد
18 sources, cited in order
NEXUS TWIN · WF-1 · NETWORKSEED 9ac5c144GCRI-MAIN.POST.1076738xyzSCHEMATIC · NETWORKST-01 · 0.303 0.393ST-02 · 0.054 0.309
WF-1 · network Schematic wireframe twin (network, decision under uncertainty). An illustration, not data.

روش‌ها و شواهد

شواهد
18 sources, cited in order and listed under References
ارقام
6 figures
Data availability
Every chart's data is published as a table on this page.
دروازه
G4
authorises live operation once controllers, evaluators, safety holds and stop-work authority exist1
کنترل‌ها
6
controls designed into every exercise3
مسیرها
10
tracks of Action Week, one led by GRA4
وضعیت
R0
no edition is on record and no exercise is running6

01What live operations means in the programme

What live operations means in the programme

Live operations is the way the Nexus Consortium runs the one week of controlled exercises of Nexus Universe, its annual programme: who directs, who controls, who evaluates, how an exercise is stopped and what it must leave on record. The Nexus Consortium is the public-good programme through which The Global Centre for Risk and Innovation (GCRI), The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) help countries examine interconnected risk with shared methods.

It is a discipline, not an organisation, and GCRI sets out its technical side on therisk.global. GRF stewards the exercises, and the technical office of GCRI runs control and evidence capture on the temporary edition Core 3,2. Exercises test whether roles, information and decisions hold together under degraded conditions; plans that look complete fail at the joins, where a warning reaches the wrong desk or nobody is sure they may take a decision 3.

Live operations is bounded on every side. It is not an emergency service or incident command, and in immediate danger people contact their local emergency services 3. A scenario is labelled as a scenario, and an exercise finding describes how an arrangement performed under stated assumptions; it is never a forecast, a warning or a pass mark 3.

02Why the live window is where trust is won or lost

Why the live window is where trust is won or lost

Planning can be reviewed and a build can be tested, but the week in which many systems, teams and institutions are active together is where a programme is most exposed. A dashboard can show a result before its limits are understood, a simulated message can be mistaken for a real one, and an observer’s presence can be read as approval. Each of those failures is a failure of operation, not of design.

Established exercise practice answers them with structure. The World Health Organization’s Simulation Exercise Manual of 2017 is a practical guide to planning, conducting and evaluating exercises, and the United States Homeland Security Exercise and Evaluation Program, revised in February 2020, records strengths, areas for improvement, capability performance and corrective actions in an after-action report and improvement plan 7,8. The NATO Cooperative Cyber Defence Centre of Excellence has run Locked Shields, a live-fire cyber defence exercise, every year since 2010; its 2026 edition brought together 4,000 participants from 41 nations 9.

Nexus Universe adopts the same separation and adds the records that let the week be checked afterwards. The programme’s exercise design cites HSEEP for objectives, the WHO manual for exercise types, ISO 22398:2013 for scenario and inject design and the WHO after-action review guidance of 2019 for the after-action report 3.

03Direction, control and evaluation are kept apart

Direction, control and evaluation are kept apart

GRF holds four decisions within its instruments: the annual mandate, mission admission, the gate decisions G0 to G7 and what is published 2. As in national exercise programmes, the director who admits participants is kept apart from controllers and evaluators, and a person with a declared conflict does not decide or sign the gate or admission it concerns 2. The gates are set out in the programme’s decision rights. Every gate decision is recorded with its reasons and can be challenged through GRF corrections and concerns 2.

GCRI’s Universe technical office supports exercise controllers and independent evaluators, runs the Core and captures run, decision and observation records sealed for review; it has no governance role 10. Independent evaluators test objectives and observable performance, not attendance, and a reviewer with a declared conflict never signs the acceptance concerned 3. Participants take part with authority to act in the scenario, so that decisions reflect real roles 3.

Finance and insurance readiness is a planned track that GRA is designed to run, with diligence questions and protection gaps, never an approval or a transaction, through its Universe finance-readiness programme 5,2. National structures keep their agenda authority and may decline participation or data sharing at any point, and decisions and execution outside the exercise remain with the relevant government, operator or licensed institution 2.

Fig. 01Direction, control and evaluation are kept apart

Direction, control and evaluation are kept apart Matrix of six roles in the live week, exercise direction by GRF, control by the GCRI technical office, independent evaluation, participants, the GRA finance track and the competent authority, each with what it holds and what it never does. دربرداردNever doesStrong linkPartial link
As set out by GRF, GCRI and GRA on 21 October 2026. No edition is on record.2,3,10,5,11Sources: GRF, programme governance and exercises and learning; GCRI, technical office; GRA, Universe finance-readiness. As of 21 October 2026.
Figure 1 in words

Exercise direction, GRF: holds the annual mandate, mission admission, gate decisions G0 to G7 and publication; never runs the technical environment or judges its own results. Control, GCRI technical office: scenario events list, controllers, simulation cells, the Core and evidence capture; never admits missions or holds a governance role. Evaluation, independent evaluators: observations against stated objectives; never signs an acceptance on which a declared conflict exists. Participants: decisions in real roles and may call a safety hold; never send simulated warnings to live audiences. Finance track (planned), GRA: diligence questions and protection gaps in track 7; never approves, lends, underwrites or transacts. Competent authority, outside the programme: decides and acts under its own rules; is not bound by an exercise finding.

04Six controls designed into every exercise

Six controls designed into every exercise

Every exercise is designed with six controls 3. Control: a scenario events list with exercise controllers and simulation cells, so every inject is planned and traceable. Evaluation: independent evaluators against objectives. Safety: time control, safety holds and an explicit real-world emergency override. Containment: simulated warnings never reach live audiences, and real infrastructure is never an unapproved target. Record: dissent and adverse findings preserved in the after-action record. Learning: improvement items returned to the next annual agenda, each with an owner 3.

Exercise types are chosen for the objectives and stepped up only when the earlier type has been passed: tabletop, then functional, then full-scale 3. Scenarios use a master scenario events list of timed injects, including late, wrong or contradictory information and at least one inject that crosses a jurisdiction or a sector boundary, because that is where real systems fail 3. Public-safety exercises carry clear simulation marking and stop-work controls; the programme is not an emergency-dispatch service 12.

Fig. 02Six controls designed into every exercise

Six controls designed into every exercise Grid of six cards naming the controls designed into every exercise: control through a scenario events list, independent evaluation, safety with holds any participant may call (highlighted), containment of simulated warnings, a record that keeps dissent, and learning with an owner for each item. طراحیStrong linkPartial link
The six controls GRF designs into every Nexus Universe exercise.3Sources: GRF, Nexus Universe exercises and learning. As of 21 October 2026.
Figure 2 in words

Control one, control: a scenario events list with controllers and simulation cells so every inject is planned and traceable. Control two, evaluation: independent evaluators test objectives and observable performance, not attendance. Control three, safety, highlighted: time control, safety holds and an explicit real-world emergency override, and any participant may call a hold. Control four, containment: simulated warnings never reach live audiences and real infrastructure is never an unapproved target. Control five, record: dissent and adverse findings are preserved in the after-action record. Control six, learning: improvement items return to the next annual agenda, each with an owner.

05The week itself

The week itself

Action Week runs in ten tracks: scientific methods and data; sovereign compute and network integration; sector and country missions; frontier technology evaluation; public-authority learning; leadership and policy deliberation; finance and insurance readiness; academy and workforce; rights-holder and public-interest challenge; and public evidence and communication 4. As the programme year sets out, during the week the Foundry pillar runs simulations and benchmarks and monitors the exercise picture, the Standards pillar monitors conformance and logs deviations, Reports observes without reporting anything simulated as observed impact, and Risk Academy assesses performance against stated objectives 4.

The six domain response teams under the National Working Groups, the working groups of each National Nexus, take part in exercises; they support preparedness, observation, verification, mapping, exercises, evidence and learning, and they are not emergency services, incident command or privileged network-access teams 13,4. Access throughout is decided per request under NXS-NSF (trust, authorization and assurance), which binds each grant to a mandate and invalidates dependent decisions when a grant is revoked 14.

Fig. 05Ten tracks in one week of controlled exercise

Ten tracks in one week of controlled exercise The ten Action Week tracks, from scientific methods and data to public evidence and communication, with track 7, finance and insurance readiness, highlighted, beside a comparator: Locked Shields brought together 4,000 participants from 41 nations in 2026. 10Action Week tracks4,000Locked Shields participants, 202641Locked Shields nations, 2026
The Locked Shields figures are shown for the scale of established exercise practice, not as programme figures.4,5,9,13Sources: Nexus programme spine; GRA; NATO CCDCOE. As of 21 October 2026.
Figure 5 in words

Ten numbered tracks in two columns: 1 scientific methods and data; 2 sovereign compute and network integration; 3 sector and country missions; 4 frontier technology evaluation; 5 public-authority learning; 6 leadership and policy deliberation; 7 finance and insurance readiness, highlighted; 8 academy and workforce; 9 rights-holder and public-interest challenge; 10 public evidence and communication. A side panel describes Locked Shields, the live-fire cyber defence exercise of the NATO CCDCOE held annually since 2010, with 4,000 participants from 41 nations in 2026.

06How a live exercise is stopped

How a live exercise is stopped

Every exercise can be stopped, and every stop is recorded. Controllers and evaluators log runs, decisions and observations, and the Standards pillar logs deviations from the composed profiles 3,4. Any participant may call a safety hold, which stops the exercise and is recorded 3. The stop-work authority required before gate G4 halts the activity it governs, and a real emergency overrides the exercise entirely 1,3.

A failed test is a finding, not an embarrassment to be removed 3. Simulated loss or performance is not observed impact, and an exercise result is not a forecast, a rating or an approval 3. Security matters during the week go through a separate security disclosure route, and safeguarding concerns through a restricted route that is never handled in public forums, both listed on corrections and concerns 15.

Fig. 04Every live exercise can be stopped

Every live exercise can be stopped Four rising steps of intervention in a live exercise: observe and log, a safety hold any participant may call (highlighted), stop work under the authority required at G4, and a real-world override in which local emergency services act, not the programme.
A safety hold or a stop is a finding, recorded and reviewed in the after-action record.3,1,4Sources: GRF, exercises and learning and annual operating cycle; the programme year. As of 21 October 2026.
Figure 4 in words

Step one, observe and log: controllers and evaluators record runs, decisions and observations, and the Standards pillar logs deviations. Step two, safety hold, highlighted: any participant may call one; the exercise stops and the hold is recorded. Step three, stop work: the stop-work authority required at gate G4 halts the activity it governs. Step four, real-world override: a real emergency ends the exercise and local emergency services act, not the programme. A note: a safety hold or a stop is a finding, not an embarrassment to be removed.

07From G4 to sealed evidence

From G4 to sealed evidence

Each stage around the week has an entry condition and an exit record, and a failed condition stops the work it governs 1. The month of build ends with a Core Build Report that shows measured readiness and known defects, accepted at G3. Entry to the week requires qualified environments, controllers, evaluators, a scenario plan and stop-work authority; gate G4 authorises controlled live operation; the exit is run, decision and observation records, limitations and improvement items 1.

The planned one-day stand-down needs an approved closeout plan, retention decisions and accountable operators. It stops new work, checkpoints authorised jobs, revokes temporary access, releases temporary capacity and seals transferable evidence, and its exit is a stand-down receipt, a preserved evidence manifest and named open exceptions 1. It becomes a programme commitment only when the annual programme records its purpose, clock, scope and exceptions 1. Media are then purged or retained under approved, validated rules, with no promise of deletion within a day 16.

An immediate structured debrief, the hot wash, captures observations while they are fresh; the after-action review then agrees findings against objectives, including failures and dissent, and names improvement items with owners 3. Results are released only after scientific and editorial review at gate G6, as evidence and outcomes explains, and restricted results stay restricted 3,11.

Fig. 03From build acceptance to publication

From build acceptance to publication Timeline from gate G3, build accepted, through G4, live operation authorised (highlighted), Action Week, the proposed one-day stand-down, G5 evidence sealed and the after-action review, to G6 publication, with the record each step produces. UNDEFINEDG3UNDEFINEDG4UNDEFINEDهفتهٔ اقدامUNDEFINEDپایان آماده‌باشUNDEFINEDG5UNDEFINEDمرور پس از اقدامUNDEFINEDG6
Each stage has an entry condition and an exit record; a failed condition stops the work it governs.1,3,4Sources: GRF, annual operating cycle and exercises and learning; the programme year. As of 21 October 2026.
Figure 3 in words

Seven steps along a line. G3, build accepted: Core Build Report with measured readiness and known defects. G4, live operation authorised, highlighted: controllers, evaluators, safety holds and stop-work authority in place. Week, Action Week: controlled exercises in ten tracks with run, decision and observation records. Day, stand-down: stop new work, checkpoint jobs, revoke access, seal evidence, proposed. G5, evidence sealed: stand-down receipt and preserved evidence manifest. Q3, after-action review: findings against objectives, dissent kept, owners for each improvement. G6, publication: results released after scientific and editorial review.

08What the week is designed to record

What the week is designed to record

The measure of a live week is not attendance or the number of systems connected; the programme never shows attendance figures, participant counts or impact claims without a source and date 11. It is the completeness of the records: run, decision and observation records, the after-action record, the stand-down receipt, the evidence manifest and the exceptions register 1,11. Each result states its scenario assumptions and limits, and failures, adverse findings and dissent are published rather than dropped 11.

Participants see the after-action record; public results are released only after review and publication authorisation 3. National results are published only as agreed for each mission 11. Because no edition is on record, there are no live-operations records to report here, and none is shown; the claims and readiness register and programme status give the current state 11,6.

09Frameworks live operations is read against

Frameworks live operations is read against

The design cites established practice as reference, not as conformance. Incident handling during the week is read against NIST SP 800-61 Revision 3, published in April 2025 as a Community Profile of the NIST Cybersecurity Framework 2.0, whose six Core Functions, Govern, Identify, Protect, Detect, Respond and Recover, give a common vocabulary for the controls in Figure 6 17,18.

Fig. 06Live operations read against an established framework

Live operations read against an established framework Comparison of the six NIST CSF 2.0 Core Functions, govern, identify, protect, detect, respond and recover, each beside where live operations designs it, from gate G4 authorisation to stand-down, closeout and the after-action review.
A reading aid that maps the CSF 2.0 Core Functions to the programme’s design; not a conformance claim.18,1,3,16,14,4,15Sources: NIST CSWP 29 (2024); GRF; GCRI; NXS-NSF; the programme year. As of 21 October 2026.
Figure 6 in words

Six rows. Govern, strategy and policy established and monitored, beside gate G4 authorising live operation with every gate recorded with reasons. Identify, current risks and assets understood, beside qualified environments and resource states. Protect, safeguards used, beside per-request access under NXS-NSF and containment of simulated messages. Detect, possible attacks found and analysed, beside conformance monitoring and logged deviations. Respond, action on a detected incident, beside safety holds, stop-work authority and the security report route. Recover, assets and operations restored, beside stand-down, closeout, the exception register and the after-action review.

سالابزارWhat it contributes
2017WHO Simulation Exercise ManualExercise types and the planning, conduct and evaluation of exercises 7,3
2020FEMA HSEEP doctrine (February 2020 revision)Objectives first; after-action report and improvement plan 8,3
2024NIST Cybersecurity Framework 2.0Six Core Functions as a shared vocabulary 18
2025NIST SP 800-61 Rev. 3Incident response as a CSF 2.0 Community Profile 17
Since 2010Locked Shields (NATO CCDCOE)Annual live exercise; 4,000 participants from 41 nations in 2026 9
Instruments that shape the design of live operations, with their status as of 21 October 2026. Naming an instrument records a reference, not conformance.

10What is changing

What is changing

  • Incident response as a profile. NIST’s 2025 revision folds incident response into the CSF 2.0 functions, so exercise controls and operational security can share one vocabulary 17,18.
  • Cross-boundary injects. Requiring at least one inject that crosses a jurisdiction or a sector boundary tests the joins where real plans fail 3.
  • Exercises at scale. Live exercises can run at scale: Locked Shields, held every year since 2010, brought together 4,000 participants from 41 nations in 2026 9.
  • Finance in the room. The planned finance track would use injects such as a parametric trigger being crossed to test lender and household response, without any transaction 5.

11Three faces of the live week

Three faces of the live week

GCRI runs control, the Core and evidence capture, and leads scientific review of what the week produced 10,11. GRF directs: it authorises the week at G4, records every gate with reasons and decides what is published, as its annual operating cycle sets out 1,2. GRA is designed to bring finance and insurance institutions into the week through track 7, a planned track, with exercise injects such as a parametric trigger being crossed, so that they can see what a mission means for them without any transaction taking place 5.

What this page does not claim: no Nexus Universe edition is on record and no exercise is running; the programme is at service level R0. Nexus Universe is not an emergency service, incident command or a dispatch service, and its domain response teams are not emergency services. An exercise result is not a forecast, a warning, a rating or an approval. GCRI does not regulate or certify, GRF does not regulate, finance or procure, and GRA does not lend, underwrite, rate or invest. Naming an agency or framework is not a claim of partnership, conformance or endorsement.

پرسش‌ها

پرسش‌ها و پاسخ‌ها

Are Nexus Universe exercises running now?

No. Exercises run only once an edition is authorised, and no edition is on record yet. Enquiries receive a reference through the Nexus Universe gateway at GRF or through the enquiry route on therisk.global.

Can an exercise run on our live systems?

Not without approval. Exercises are controlled: simulated messages are marked and kept from live audiences, real infrastructure is never an unapproved target, and a safety hold or a real emergency can stop the exercise at any time.

Who decides whether the live week goes ahead?

GRF records gate G4, controlled live operation authorised, once controllers, evaluators, safety holds and stop-work authority are in place. The GCRI technical office qualifies the technical build but does not admit missions or take governance decisions.

Is Nexus Universe an emergency response service?

No. It is an exercise and learning programme, not an emergency service or incident command, and its domain response teams are not emergency services. In immediate danger, contact your local emergency services.

Who sees the results of an exercise?

Participants see the after-action record. Public results are released only after scientific and editorial review and publication authorisation at gate G6, national results only as agreed for each mission, and restricted results stay restricted.

شرایط

واژه‌نامه

Live operations
The direction, control, evaluation, stopping and recording of the week of controlled exercises of Nexus Universe.
Safety hold
A stop that any participant may call; the exercise halts and the hold is recorded.
Scenario events list
The planned, timed list of injects through which controllers run an exercise, so that every inject is traceable.
Hot wash
An immediate structured debrief while observations are fresh, before the after-action review.
Gate G4
The recorded decision that authorises controlled live operation.

Reuse and cite

Text CC BY 4.0. Cite the page with its date; data tables are linked under each figure.

منابع

منابع

18 sources, numbered in the order they are first cited
  1. The Global Risks Forum (2026-10). Nexus Universe: annual operating cycle. globalriskforum.com. Accessed 2026-10-21.
  2. The Global Risks Forum (2026-10). Programme governance (Nexus Universe). globalriskforum.com. Accessed 2026-10-21.
  3. The Global Risks Forum (2026-10). Nexus Universe: exercises and learning. globalriskforum.com. Accessed 2026-10-21.
  4. Nexus documentation (docs.therisk.global) (2026-10). The programme year. docs.therisk.global. Accessed 2026-10-21.
  5. The Global Risks Alliance (2026-10). Universe finance-readiness programme. globalriskalliance.com. Accessed 2026-10-21.
  6. The Global Centre for Risk and Innovation (2026-10). Claims and readiness register. therisk.global. Accessed 2026-10-21.
  7. World Health Organization (2017-02-01). WHO Simulation Exercise Manual (WHO/WHE/CPI/2017.10). www.who.int. Accessed 2026-10-21.
  8. U.S. Federal Emergency Management Agency (FEMA) (2020-02). Homeland Security Exercise and Evaluation Program (HSEEP). www.fema.gov. Accessed 2026-10-21.
  9. NATO Cooperative Cyber Defence Centre of Excellence (CCDCOE) (2026). Locked Shields. ccdcoe.org. Accessed 2026-10-21.
  10. The Global Centre for Risk and Innovation (2026-10). Nexus Universe technical office. therisk.global. Accessed 2026-10-21.
  11. The Global Risks Forum (2026-10). Nexus Universe: evidence and outcomes. globalriskforum.com. Accessed 2026-10-21.
  12. Nexus documentation (docs.therisk.global) (2026-10). Status and service levels (offering O05, Multi-Hazard and Anticipatory-Action Preparedness). docs.therisk.global. Accessed 2026-10-21.
  13. Nexus documentation (docs.therisk.global) (2026-10). National Working Groups (NWG) and the six CERTs. docs.therisk.global. Accessed 2026-10-21.
  14. Nexus documentation (docs.therisk.global) (2026-10). NXS-NSF: trust, authorization, mandate, policy and assurance. docs.therisk.global. Accessed 2026-10-21.
  15. The Global Centre for Risk and Innovation (2026-10). Corrections and concerns. therisk.global. Accessed 2026-10-21.
  16. The Global Centre for Risk and Innovation (2026-10). Network and Core. therisk.global. Accessed 2026-10-21.
  17. U.S. National Institute of Standards and Technology (NIST) (2025-04-03). SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile. csrc.nist.gov. Accessed 2026-10-21.
  18. U.S. National Institute of Standards and Technology (NIST) (2024-02-26). The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29. nvlpubs.nist.gov. Accessed 2026-10-21.

سابقه

Editorial record

Facts and programme states are given as of 21 October 2026. This page is reviewed at least every 180 days and whenever a programme state, a service level or a cited figure changes. It replaces an earlier version of the same post, which described a separate "GCRI Live Operations" function with its own rooms, telemetry layers and protocol labs on platforms under retired names; no such function is on record, and live operations is described here as the programme’s gates, roles and controls set it out.

Published by the GCRI editorial desk under the scientific and editorial integrity policy. To report an error or request a correction, use the corrections and concerns route; every accepted correction is recorded as a new version, never a silent edit.

Cite this article

GCRI editorial desk (2026, June 8). Live operations: how Nexus Universe runs its exercise week. The Global Centre for Risk and Innovation. https://therisk.global/live-operations-how-nexus-universe-runs-during-the-annual-technical-cycle/

Republish

Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and The Global Centre for Risk and Innovation, link to the original and note any change. Figures, maps and twins made by the institutions carry the same licence; third-party data keeps its own credit line.

Attribution to paste
<p>Live operations: how Nexus Universe runs during its week of controlled exercises — GCRI editorial desk, The Global Centre for Risk and Innovation. First published 8 June 2026 at <a href="https://therisk.global/live-operations-how-nexus-universe-runs-during-the-annual-technical-cycle/">https://therisk.global/live-operations-how-nexus-universe-runs-during-the-annual-technical-cycle/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>

موضوع‌ها

Related across the Consortium

سهم

EmailLinkedInBlueskyMastodon