Evidence handled properly
Digital
Forensics
We preserve and examine digital evidence during an incident or a legal matter, led by the same senior responder who runs the incident. Disk, memory, cloud and email evidence is collected with documented chain of custody, then analyzed to establish what happened, when, and what the attacker touched. Findings are written for counsel to use.
From preservation to findings
Preserve first,
then ask questions.
Work follows NIST SP 800-86 and ISO/IEC 27037 for identifying, collecting and preserving digital evidence. Every item is hashed and logged with chain of custody from collection onward. Engagements can run through counsel to protect privilege, and the analysis answers the questions counsel and leadership need settled.
Phase 01 · Questions & scope
Agree what the investigation needs to answer.
A written set of investigative questions and the evidence sources that can answer them.
- Agree the questions with counsel and leadership.
- Identify relevant systems, accounts, logs and retention limits.
- Issue preservation steps before data ages out or is overwritten.
Phase 02 · Preserve
Capture the evidence before it changes.
Forensic images and exports, hashed and logged with chain of custody.
- Acquire disk images and memory, using write blocking where it applies.
- Export cloud, email and identity logs before retention expires.
- Hash every item and record who handled it and when.
Phase 03 · Examine
Pull the facts out of the evidence.
Artifacts parsed and correlated into a single timeline of attacker and user activity.
- Analyze memory with Volatility and collect disk artifacts with tools such as KAPE.
- Build super timelines with Plaso.
- Review mailbox and cloud audit logs for access and exfiltration.
Phase 04 · Analyze
Answer the questions that were asked.
Findings tied to evidence: how access was gained, what was touched, and what left.
- Establish initial access, persistence and lateral movement.
- Determine what data was accessed or exfiltrated, where the evidence allows.
- Separate confirmed facts from reasonable inference.
Phase 05 · Report
Hand counsel findings they can rely on.
A forensic report with method, evidence references and findings stated to the level the evidence supports.
- Write findings with references to specific evidence items.
- Document the method so another examiner could repeat it.
- Brief counsel and leadership on what the evidence shows.
Agree what the investigation needs to answer.
A written set of investigative questions and the evidence sources that can answer them.
- Agree the questions with counsel and leadership.
- Identify relevant systems, accounts, logs and retention limits.
- Issue preservation steps before data ages out or is overwritten.
Capture the evidence before it changes.
Forensic images and exports, hashed and logged with chain of custody.
- Acquire disk images and memory, using write blocking where it applies.
- Export cloud, email and identity logs before retention expires.
- Hash every item and record who handled it and when.
Pull the facts out of the evidence.
Artifacts parsed and correlated into a single timeline of attacker and user activity.
- Analyze memory with Volatility and collect disk artifacts with tools such as KAPE.
- Build super timelines with Plaso.
- Review mailbox and cloud audit logs for access and exfiltration.
Answer the questions that were asked.
Findings tied to evidence: how access was gained, what was touched, and what left.
- Establish initial access, persistence and lateral movement.
- Determine what data was accessed or exfiltrated, where the evidence allows.
- Separate confirmed facts from reasonable inference.
Hand counsel findings they can rely on.
A forensic report with method, evidence references and findings stated to the level the evidence supports.
- Write findings with references to specific evidence items.
- Document the method so another examiner could repeat it.
- Brief counsel and leadership on what the evidence shows.
Key benefits
Know what happened from evidence, not assumption.
Each item is hashed and logged from collection onward, following NIST SP 800-86 and ISO/IEC 27037, so counsel can show where it came from and who handled it.
Whether data was accessed or taken drives notification duties. Forensic analysis gives counsel evidence to decide from, rather than assuming the worst or hoping for the best.
The senior responder who leads the incident also leads the forensics, so evidence collection follows the response decisions and the findings stay with the person who knows the incident.
What you get
What lands on
your desk.
Written for counsel and leadership, with the evidence trail behind every statement.
The document
The forensic report
The questions investigated, the method, evidence sources, timeline and findings, each tied to specific evidence items and stated no more strongly than the evidence itself supports.
The working file
Evidence register and custody log
Every evidence item with its source, hash, collection method, storage location and full handling history. It is the record counsel needs if the findings are ever challenged.
The conversation
The counsel briefing
A session with counsel and leadership walking through what the evidence shows, what it does not, and what that means for notification, remediation and any legal matter.
Client case studies
Real engagements.
Documented outcomes.
In their words
"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
In their words
"ForgePath has become a trusted security partner for YHB. Beyond helping us comply with FTC Safeguards requirements, they provide the governance, oversight, and guidance we rely on to protect our firm and our clients’ data. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
Trusted by industry leaders.
Forensics questions
Asked by
counsel first.
Straight answers from the practitioners who do the work. If yours is not here, ask us directly.
Often, yes. Engaging forensics through outside counsel can help protect privilege over the findings, though whether it applies is a legal question for your counsel. We work under their direction and follow their instructions on how reports are prepared and shared.
Access to the affected systems or their images, cloud and email admin accounts for log export, and someone who knows the environment. Above all, do not wipe or rebuild affected systems before evidence is preserved unless containment requires it.
Yes. Forensics also supports legal matters, internal investigations and questions such as whether a departing employee took data. The same evidence handling applies, and the scope is set by the questions counsel needs answered.
That depends on our availability at the time, and the scoping call settles it. Until then you can protect evidence yourself: keep affected systems powered on but isolated, and extend log retention. If an attack is in progress, see our Under Attack page.
A senior practitioner, the same responder who leads the incident if there is one. The person who scopes the investigation collects the evidence, does the analysis and writes the report. No junior examiners and no handoffs.
Ready?
Bring us
the problem.
One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.








