Critical Infrastructure

Threat model by sector: hazards, cyber, governance; cite RS; no exploit guidance.

Assess resilience risks and mitigations; cite RS; propose coordination with host authorities.

Build continuity SOP: escalation, comms, redundancy; include legal/protocol gates.

Evaluate resilience dependencies; propose diversification and governance; cite RS; avoid offensive content.

Design response program with triggers, coordination map, and KPIs; cite RS.

Rank adaptation interventions; include feasibility, impact, safeguards; propose 90-day starter set.

Create procurement integrity shield: transparency, audit, third-party checks, grievance, stop/go triggers.

Stress-test interdependencies and propose containment; include decision triggers.

Map coordination roles and triggers; propose comms discipline and after-action learning; cite RS.

Specify early warning data, thresholds, and action protocols; cite RS; include privacy and legitimacy safeguards.

Define registry fields for assets at aggregated level; include access control and data minimization rules.

Create command charter: roles, escalation, comms, continuity steps; avoid technical exploit instructions.

Identify critical inputs and alternative sourcing; cite RS; propose inventory and coordination policy.

Design governance: steering, reporting, audits, dispute triggers; include integrity safeguards.

Build comms ladder for incidents; include attribution rules, partner sync, rumor control (truthful).

Link climate impacts to stability and infrastructure; cite RS; propose preventive engagement.

Define safeguards, monitoring, grievance mechanisms; include stop/go thresholds.

Build preparedness plan: triggers, coordination, continuity; include comms and duty-of-care steps.

Stress test financing risks; propose hedges and governance; label assumptions.

Define governance for cyber-physical risks: roles, reporting, controls, incident response.

Create vendor risk framework: evaluation criteria, transparency, audit, diversification; avoid targeting.

Propose data architecture: minimization, residency, access control, audit; flag legal review.

Design quarterly exercise plan for continuity: scenarios, evaluation, after-action improvements.

Provide ROI ranges only if RS supports; otherwise output UNKNOWN and specify needed data.

Map compliance obligations and reporting; cite RS; create gating checklist.

Define who coordinates with whom (institution/role), cadence, and comms discipline.

Identify actions robust across scenarios; list those requiring triggers and approvals.

Design integrity controls for emergency procurement; include transparency and audit practices.

Build diplomacy plan for cross-border infrastructure: sequencing, safeguards, language options; cite RS.

Define KPIs, reporting cadence, evidence sources, and governance for learning loops.