Skip to contentAbout Fig Group

Incident Management

Structured incident workflows with evidence capture and regulatory notification tracking.

The challenge

Does this sound familiar?

Incidents are logged in Slack, email, or spreadsheets. Evidence disappears. Regulatory notification deadlines are missed. Post-incident reports never capture the full timeline.

How Fig helps

Incident Management with Fig

Structured Workflows

Every incident follows a defined response playbook with step-by-step checklists, approval gates, and automated escalations. Nothing is forgotten.

Evidence Capture

All incident actions, communications, system logs, and decisions recorded in a shared investigation workspace. MSPs and clients collaborate from the same evidence timeline. Automatic evidence packs for regulatory review and law enforcement.

Fig Incident Management platform view
Core Capability

Fig manages the full incident lifecycle natively, including automatic severity classification, 72-hour GDPR breach notification clocks, escalation workflows, post-incident review automation, and repeat incident detection.

Notification Tracking

Regulatory notification timelines calculated automatically based on incident classification and jurisdiction. Reminders trigger with required disclosure content pre-filled.

Post-Incident Learning

Automated timeline generation, root cause tracking, and remediation recommendations. Findings linked back to preventative controls. Includes tabletop exercise planning and execution for NIS2 and DORA compliance.

Audit-ready workflow

How Incident Management becomes evidence

Incident Management should not be treated as a standalone tool surface. In Fig it is part of a governed workflow: a signal is captured, an owner is assigned, a control or risk is updated, and evidence is retained so the organisation can prove what happened later.

Lifecycle

Where it sits in the operating model

The Respond phase is where this capability sits in the wider Fig operating model. Incidents are logged in Slack, email, or spreadsheets. Evidence disappears. Regulatory notification deadlines are missed. Post-incident reports never capture the full timeline. Fig turns that problem into a repeatable lifecycle so MSPs, risk teams, and auditors are not relying on static spreadsheets or ad hoc screenshots when a buyer asks for proof.

Evidence captured

What auditors and buyers see

For incident management, useful evidence normally includes the triggering record, the affected asset or supplier, the control requirement, the assigned owner, the decision made, the timestamp, and the outcome. That evidence is mapped back to frameworks such as Cyber Essentials, ISO 27001, NIS2, DORA, GDPR, CMMC, and internal policy requirements where relevant.

Implementation checks

Four steps to roll this out

  • 01Define who owns incident management and what events should trigger review.
  • 02Connect the relevant source systems so evidence is collected continuously.
  • 03Map outputs to the frameworks and policies that matter to the organisation.
  • 04Review exceptions, accepted risks, and overdue actions before audit or renewal.

Useful references

Independent sources buyers and auditors recognise

The exact evidence required still depends on your scope, risk profile, sector, and framework obligations.

Built for you

Who uses this?

MSPs & MSSPs

Client incident response workflows standardised and white-labelled. Multi-client incident dashboard and portfolio breach trending.

Learn more

Security & risk teams

Centralised incident coordination across teams with built-in regulatory notification checklists. Board-ready incident summaries generated automatically.

Learn more

Compliance & audit

Complete incident lifecycle evidence for regulatory obligations under GDPR, NIS2, and DORA. Notification compliance and response timelines auditable.

Learn more

Common questions

Frequently asked questions

How do incidents get into Fig?

Incidents can be reported via an in-app form, email integration, Slack commands, or automated detection rules. Severity is assigned on intake and can be adjusted as investigation evolves.

Does this handle GDPR notification deadlines?

Yes. Fig calculates UK GDPR and ePrivacy Regulations notification deadlines based on incident classification. It auto-populates regulatory notification templates and tracks disclosure status.

Can we customise incident response playbooks?

Yes. Fig provides template playbooks for common incident types (ransomware, data breach, phishing) that you can customise with your own escalation paths, notification lists, and evidence requirements.

Can our clients see their own incident timelines?

Yes. MSPs can grant clients read access to their incident workspace. Clients see the investigation timeline, actions taken, and resolution status without being able to modify evidence or internal notes.

What if we already use a ticketing system for incidents?

Fig integrates with ConnectWise, Autotask, ServiceNow, Jira, and other ticketing platforms. Incidents can be created from tickets and synced bidirectionally, so your team does not need to work in two places.

Does Fig support whistleblowing reports?

Yes. Fig includes anonymous case reporting for whistleblowing, increasingly required under the EU Whistleblower Directive. Cases are managed through structured workflows with full confidentiality protections.

Next step

See Incident Management in action.

Book a walkthrough tailored to your frameworks and tooling.