Select the workflows that protect revenue and customer trust. Map their systems, identities, software inputs, suppliers and recovery owners. Agree the tolerable interruption and data loss for each workflow.
Deliverable: a dependency map tied to business outcomes, with an accountable owner for each critical path.
Choose “Not sure” when evidence is missing. Please keep passwords, customer information and incident details out of this tool.
Based on the Cyberpolycrisis articles by Nicholas Roberts. The articles examine shared dependencies across concurrent events; they do not establish a single coordinated campaign.
Each applicable control has equal weight: established and tested = 100, partly in place = 50, missing or untested = 0, and not sure = 0 pending verification. The mean is rounded to a whole number. AI controls are excluded when you report no AI use.
The planning bands are 0–49 “Stabilize”, 50–79 “Close gaps”, and 80–100 “Close remaining gaps” or “Validate and maintain” when none remain. These are editorial priorities, not validated risk thresholds. A current incident concern overrides the band. A high average can still contain a consequential individual gap.
This is a self-reported checklist. It does not measure the probability of a breach, scan your systems or certify your security.
Connections reflect thematic overlap in the published network analysis. Highlighted connections mean your answers show gaps in both areas. They do not demonstrate a live attack path, causal link or measured likelihood. Line thickness is illustrative.
The shortlist matches your business needs to documented capabilities. Shopify can own commerce records; Palantir can support governed operational workflows; Databricks can govern analytics and AI data; Cloudflare can protect access and applications and host suitable workloads.
“Safe haven” means a better-controlled operating model, not a guarantee from a vendor. Documentation alone does not establish a comparative security track record. Before buying, review current assurance reports, relevant incident disclosures, contract terms, data location, implementation cost and exit options.
Vendor controls depend on product, plan and configuration. Your team remains responsible for access, integrations, data and recovery.
Scoring runs in your browser. Saving progress is optional and uses this browser’s local storage. Anyone with access to the browser profile could read saved answers. Your completed review is sent to the chatbot only when you explicitly select “Include my completed review with the next question.”
Chat sends your message and recent conversation to Cloudflare Workers AI. This app keeps the conversation in page memory and does not save transcripts to a database. “New chat” clears that local conversation; it cannot recall data already sent. Hosting and AI providers process requests under their own terms. Do not share passwords, API keys, customer data or confidential incident details.
If you choose “Email me a follow-up,” we store your email address, consent version and request timestamps privately in Cloudflare for Nicholas Roberts to respond. Your chat and assessment aren’t included in this request, and the email address isn’t sent to the AI. This is a personal follow-up request, not a newsletter subscription. You can ask Nicholas to remove your request through his LinkedIn profile.
Downloads stay on your device. The contact button opens a generic email draft and does not include your answers. Hosting providers still process ordinary web requests; do not put assessment information in URLs.
Methodology 1.0. Capability documentation reviewed October 2026. Review current vendor terms and controls before making a decision.
