Skip to main content
Threatsys

Cyber Forensics & Investigation

Network Forensics

Packet and flow reconstruction that shows exactly what left the network, and when.

Every engagement includes manual validation, a two audience report and free re-testing.

Get a scoped quote+91 96682 00222

What this actually is

Endpoint evidence can be wiped. Network evidence usually cannot, because it was recorded somewhere else while the attack was happening.

We reconstruct sessions from packet captures and flow records to establish what actually left the network. For data breach notification, that distinction between possible access and confirmed exfiltration is the entire question.

Where full packet capture does not exist, flow records and DNS logs still tell a surprising amount.

What we go after

  • Packet capture analysis and session reconstruction
  • NetFlow and connection record analysis
  • DNS query analysis for command and control
  • Encrypted traffic metadata analysis
  • Data exfiltration volume and destination determination
  • Lateral movement mapping across the network
  • Command and control infrastructure attribution

How we run it

  1. 01

    Preserve

    First priority is evidence integrity. We image and hash before anyone starts changing things.

  2. 02

    Contain

    Stop the bleeding without destroying the trail. These two goals fight each other, and experience is what balances them.

  3. 03

    Investigate

    Timeline reconstruction across endpoint, network, cloud and identity, until we can say what happened and when.

  4. 04

    Report

    Findings written to survive scrutiny from a regulator, an insurer or a court.

  5. 05

    Harden

    The root cause fixed, not just the symptom, so the same door is not open next quarter.

What you receive

  • Network activity timeline
  • Exfiltration assessment with volumes and destinations
  • Command and control infrastructure indicators
  • Detection recommendations for the future
  • Report suitable for regulatory notification

Who needs this

Organisations determining the scope of a breach, particularly where notification obligations depend on what actually left.

How long it takes

One to three weeks depending on capture volume.

Standards this satisfies

  • NIST SP 800-86
  • ISO 27035
  • CERT-In
  • DPDP Act

Why it matters

After an incident there are three questions that have to be answered, and none of them can be answered well without preparation: when did it start, what was actually taken, and is the attacker still inside. Regulators, insurers and customers all ask them, and vague answers are treated as bad ones.

The most common problem we meet is that the evidence is already gone. Systems rebuilt, logs rotated, machines rebooted in good faith before anything was preserved. How the first hour is handled decides whether the rest of the investigation is possible.

Choose how you want this delivered

Most of the price difference between quotes comes down to this one choice, and it is rarely explained. Pick one to see what it covers, what it suits and what it costs you.

Terms, contacts and access agreed in advance, with a guaranteed response time. The value is not the discount, it is that the first day is spent responding rather than negotiating a contract while an intruder is still active.

Choose this when

  • Any organisation holding regulated or personal data
  • Boards or insurers asking about incident readiness
  • You want the mobilisation clock to start in minutes, not days

Effort and cost

An annual fee, with unused hours typically usable for proactive work. The cheapest reduction in breach cost available.

Scope it yourself, before you call anyone

Answer a few questions and you get an indicative number, the working behind it and what your answers tell us. It runs in your browser, so nothing you type reaches us.

1/5

Roughly how many personal records do you hold?

What we look for, and keep finding

These are the classes of problem this work exists to surface. Not every engagement finds all of them, but these are the ones that turn up often enough to be worth naming.

  • Evidence destroyed by the response

    The most common problem we meet. Systems rebuilt, logs rotated, machines rebooted before anything was preserved. What could have been established is often gone before we arrive.

  • Incomplete timeline

    Knowing the breach happened but not when it began. Without an accurate first access, scope cannot be bounded and notification obligations cannot be answered honestly.

  • Unclear data exposure

    The question every regulator and customer asks: what was actually taken. Answering it needs artefacts that only exist if logging and retention were adequate beforehand.

  • Chain of custody failures

    Evidence handled in a way that will not survive challenge. If there is any prospect of proceedings, how the first hour was handled decides whether the findings are usable.

  • Persistence left behind

    Recovery declared complete while access remains. We look specifically for the second and third mechanism, because a competent intruder does not rely on one.

Who runs your engagement

Investigators who have given evidence

Investigations are led by people who have produced findings that survived challenge. Our founder advises law enforcement and has trained officers in cyber crime investigation, so the method is one that police and courts recognise.

Questions we get asked

We do not have full packet capture. Can you still help?

Usually. Flow records, firewall logs, proxy logs and DNS queries between them answer most of the important questions, even without payload.

Often scoped alongside

Ready to scope your network forensics?

Thirty minutes with a senior engineer, and you leave with a written scope and indicative effort.

Book a 30-min consultation+91 96682 00222