DPO Radio

Incident and Continuity Workflows

Overview Image

Why It Matters

A response team needs to know which facts are established, which duties are in scope and who can act. Continuity teams need the same discipline when setting recovery targets and testing a restore.

A response plan and a restore test answer different questions. Let the response lead examine notification duties while the service owner checks dependencies, tolerances and recovery evidence.

The result shows which checks are incomplete and which decisions belong to a person. Review the sources and use the controls on the run to apply the supported proposals you accept.

How It Works

Triage and review notification duties

Compare incident facts with the recorded severity scale and platform deadlines, then identify who needs to be told for review.

Review what happened

Separate documented root cause from contributing conditions and return questions where the evidence stops.

Draft a response plan and tabletop

Prepare Word drafts for review using the incident and relevant operational context.

Prepare a business impact analysis

Draft individual values for review and use recorded dependencies and the platform's derived maximum tolerable downtime.

Plan and review a restore test

Prepare the test and review the measured outcome. ComplianceOne computes the recorded test result from its inputs.

The Difference

Graphic Image

Without Incident and Continuity Workflows

Graphic Image

With Forseti Incident and Continuity Workflows

IconSeverity, notification duties and clocks are maintained in separate working notes.
IconTriage and review notification duties.
IconA broad cause can hide process, control or ownership issues.
IconReview what happened.
IconExercise materials must be assembled separately from the response plan.
IconDraft a response plan and tabletop.
IconRecovery targets can be discussed without the dependency or impact timeline that supports them.
IconPrepare a business impact analysis.
IconReviewers must reconstruct why an exercise passed or failed.
IconPlan and review a restore test.

Built for Reviewable Compliance Work

Build For Image

See the recorded clock used in an incident review.

Build For Image

Inspect what the restore test measured before discussing its outcome.

Build For Image

Take the response plan and tabletop draft into a team review.

Background Image

See Incident and Continuity Workflows in Action

See the recorded clock used in an incident review.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Next Steps

Icon Image

Start a pilot

Start a pilot using an incident, business impact analysis or restore test.

Icon Image

Talk to us

Talk to us about how incident and continuity workflows fits your team's work.

Frequently Asked Questions

The incident workflow checks deadlines recorded in ComplianceOne. An authorised person resolves missing facts and handles any notification.

The restore-test record computes its result. Forseti can help prepare and review the test and point out gaps in its evidence.

The response-plan and tabletop workflows prepare Word drafts for the incident team to review.

The practitioner run closes with Not checked, Decisions for you, Questions and Re-check when. Review the findings and source references before applying a proposal.

Incident and Continuity Workflows are part of the Practitioner Series on Standard and Enterprise. Access depends on the record type, the user's permissions and any installed framework the workflow needs.