Free public control tool

Cyber risk scenario worksheet

Frame one plausible cyber-loss scenario, its assumptions, ownership, and next decision.

Use this worksheet to make a risk discussion specific enough to review. It does not calculate loss from live data or replace a risk model.

Template / checklist for operators. Not legal advice. Not a certification.

Use when

A risk has been raised, but the business impact, assumptions, or decision owner are still unclear.

Output

A reviewable scenario record with assumptions, evidence requests, and a named next action.

Operator checklist

Work through the prompts and retain the evidence references.

Section 1

Scenario definition

Describe one event in operational terms before estimating impact.

  1. 1

    Name the scenario and affected business service.

    Evidence to retain: Service owner and short scenario statement

  2. 2

    State the initiating event and likely failure path.

    Evidence to retain: Incident pattern, threat report, or tabletop notes

  3. 3

    Identify the assets, data, third parties, and business processes in scope.

    Evidence to retain: System inventory and dependency map

Section 2

Impact and assumptions

Record assumptions so reviewers can challenge them later.

  1. 1

    List operational, financial, legal, and customer impacts separately.

    Evidence to retain: Impact assumptions and relevant stakeholders

  2. 2

    Document the time horizon, recovery assumptions, and material uncertainty.

    Evidence to retain: Recovery objectives, contracts, or prior incident data

  3. 3

    Record the decision this scenario informs and the decision date.

    Evidence to retain: Risk committee, executive, or control-owner decision

Section 3

Response readiness

Turn the scenario into owned work, not a static narrative.

  1. 1

    Identify preventive, detective, response, and recovery controls to examine.

    Evidence to retain: Control descriptions and evidence locations

  2. 2

    Assign an owner for each material evidence gap.

    Evidence to retain: Named owner and target date

  3. 3

    Define the next review trigger: change, test, incident, or scheduled review.

    Evidence to retain: Review cadence or event trigger

Want a second set of eyes on the workflow?

Bring one completed worksheet or checklist. Ironframe can help map the handoffs, evidence, ownership, and remediation steps into a workable operating process.