Digital forensics · Incident response · Cyber readiness

WHO WE SERVE / INSURERS & BREACH COUNSEL

Understand the technical position—and its limits.

Incident advice depends on facts that are often incomplete and still developing. We provide scoped forensic investigation and clear reporting to help insurers and breach counsel understand the evidence, direct further technical questions, and advise the affected organization.

HOW A FINDING IS EXPRESSED

Different statements require different support.

01

Observed

What the examined records show.

02

Interpreted

What the evidence supports, with the reasoning explained.

03

Unresolved

What remains unknown or requires another source.

Missing evidence ≠ proof that nothing happened.
Reporting categories, not a numerical confidence score or a claim about an incident.

WHY DFI

Make uncertainty explicit enough to work with.

An organization may be restoring systems while advisers need to understand the incident’s chronology, affected environment, and possible information exposure. We define the investigation questions, preserve agreed sources, and explain the evidentiary basis for the findings. Where a conclusion remains provisional, we identify what would be needed to support or challenge it.

We establish who instructs the work, who receives updates, what approvals apply, and how technical findings will be reported. That keeps the examination aligned with the engagement without confusing technical analysis with legal advice, coverage interpretation, or a guarantee of privilege.

WHERE WE CAN HELP

Focused investigation for a developing incident.

The incident and available records determine the scope. We do not present an attacker’s assertion or a missing log as a confirmed finding.

01

The incident chronology is fragmented

We compare available account, endpoint, network, and response records to establish the supported sequence. We separate observed activity from assumptions and describe where remediation or missing telemetry limits reconstruction.

02

Information exposure is uncertain

We examine available access, transfer, and account evidence within scope, together with relevant system context. We distinguish supported findings from indicators that require corroboration and questions the available data cannot resolve.

03

Multiple technical parties are involved

We coordinate collection and reporting with the organization’s IT team and providers. Defined evidence requests, change context, and update recipients help the parties work from a consistent technical picture.

THE WORK, MADE CONCRETE

Connect the advice question to the evidence needed.

Our work supplies technical findings for the appropriate advisers. Legal, notification, policy, and coverage decisions remain with them.

Connect the advice question to the evidence needed.
Investigation questionEvidence we may examineReporting distinction
What activity can be established?Available device, identity, mailbox, cloud, and relevant network records.Observed events versus interpretation; known chronology versus unobserved periods.
Which systems or accounts are implicated?Relevant alerts, configuration, available logs, and the organization’s system context.Confirmed involvement versus systems requiring further examination.
What is known about information access or movement?Available access and transfer indicators, relevant files, and corroborating records.Supported exposure findings versus indicators or unresolved uncertainty.
What affected the investigation?Collection details, retention, permissions, containment actions and remediation history.Evidence available at examination versus limitations on retrospective conclusions.

COLLABORATION, WITH BOUNDARIES

Keep instruction, analysis, and advice distinct.

Instructing counsel / insurer

Confirms instruction and reporting arrangements, scope approvals, and the questions relevant to its professional role.

DFI

Conducts the agreed technical investigation, reports the basis and limits of findings, and identifies outstanding evidence questions.

Organization & technical providers

Confirm authorized access, supply system context and available records, and execute operational response actions within their responsibilities.

We agree the scope, authority, access, reporting, and responsibilities before the work proceeds.

WHAT YOU RECEIVE

A technical record that supports informed advice.

We agree deliverables before work begins. The appropriate format depends on your purpose, the available evidence, and the engagement.

01

A scoped investigation plan

Questions, sources, collection priorities, reporting recipients, and approval arrangements.

02

A developing factual picture

Agreed updates showing established findings, provisional interpretations, and outstanding requests.

03

An evidence-linked report

The examined sources, relevant chronology, methods, conclusions, and material limits.

04

Technical consultation

A discussion of the findings and further questions within the engagement, without substituting for legal or insurance advice.

A USEFUL FIRST CONVERSATION

Establish the scope and reporting relationship early.

For an active incident, contact DFI through incident help. We will discuss the instructions, available evidence, and appropriate engagement route before work begins.

Discuss an incident

Helpful information to have ready

  • Confirm the instructing party, affected organization, and reporting recipients.
  • Outline the incident, relevant dates, known changes, and questions requiring an answer.
  • Identify the IT/provider contacts and available evidence sources.
  • Explain approval requirements and any existing insurer or response arrangements.

Keep credentials and sensitive evidence out of the initial inquiry. We will agree a secure intake route if the matter proceeds.

Technical background & further reading

These independent references provide general background. They do not endorse DFI or define the scope of an engagement.