Skip to content

Is someone already inside?

Threat Hunting
& Discovery

A point in time hunt built around one question: is an attacker already in your environment? We form hypotheses from MITRE ATT&CK and the threats your sector faces, then search endpoint, identity and network data for evidence. You get a clear answer backed by evidence, and an honest account of what we could not see.

How the hunt runs

Assume compromise,
then look.

Hunts are hypothesis driven and mapped to MITRE ATT&CK. We use your existing EDR, SIEM and identity logs, adding collection tools such as Velociraptor where coverage is thin. This is a point in time engagement, not ongoing monitoring, and every finding is confirmed by hand.

Phase 01 · Scope & data

Agree what to hunt and what data we can see.

A hunt plan listing in scope systems, data sources and the visibility gaps, stated up front.

  • Agree scope and the trigger: a tip, an alert, an acquisition, or plain doubt.
  • Inventory EDR, SIEM, identity and network log coverage.
  • Deploy collection where coverage is missing, with your approval.

Phase 02 · Hypotheses

Decide what an intruder would leave behind.

A set of hunt hypotheses, each tied to MITRE ATT&CK techniques and your environment.

  • Build hypotheses from the threats relevant to your sector.
  • Prioritize persistence, credential access and lateral movement.
  • Write queries and Sigma or YARA rules for each hypothesis.

Phase 03 · Hunt

Search the evidence, system by system.

Every hypothesis tested, with what was found or why it came back clean.

  • Run queries across endpoint, identity and cloud logs.
  • Look for unusual admin activity, new persistence and odd outbound traffic.
  • Collect artifacts from suspicious hosts for closer analysis.

Phase 04 · Verify

Separate real intrusion from noise.

Confirmed findings, each with the evidence that supports it, and false positives ruled out.

  • Analyze suspicious artifacts and timelines by hand.
  • Rule out legitimate admin tools and scheduled jobs.
  • Stop and brief your leadership if we confirm active compromise.

Phase 05 · Report

Hand over the answer and what we could not see.

A report with the verdict, the evidence, the detection gaps and new rules your team can keep.

  • State the result plainly: evidence of compromise, or none found within scope.
  • List the visibility gaps that limited the hunt.
  • Hand over the queries and rules we wrote.

Agree what to hunt and what data we can see.

A hunt plan listing in scope systems, data sources and the visibility gaps, stated up front.

  • Agree scope and the trigger: a tip, an alert, an acquisition, or plain doubt.
  • Inventory EDR, SIEM, identity and network log coverage.
  • Deploy collection where coverage is missing, with your approval.

Key benefits

An answer to the question nobody wants to ask.

A real answer, with evidence

Each hypothesis is tested and documented, so the result is a verdict you can defend to the board, an acquirer or an auditor instead of a vague all clear.

Hunts shaped to your threats

Hypotheses come from MITRE ATT&CK and the groups that target your sector, matched to your systems, so the hunt looks where an intruder in your environment would likely hide.

Detections you keep

The queries and Sigma or YARA rules written for the hunt go to your team, so your existing tools can keep looking for the same behavior after the engagement ends.

What you get

What lands on
your desk.

One verdict, the evidence behind it, and the rules to keep looking.

The document

The hunt report

The verdict, each hypothesis with what was tested and found, confirmed findings with evidence, and the visibility gaps that limited the hunt, ranked by what to fix first.

The working file

The detection pack

The hunt queries and Sigma or YARA rules, documented and tuned for your environment, with notes on where each one belongs in your EDR or SIEM.

The conversation

The findings briefing

A session with leadership and your security team on the verdict, what it means for the business, and the next steps if anything was found.

Client case studies

Real engagements.
Documented outcomes.

YHB | CPAs & Consultants testimonial

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."

Cyrus Kapadia
Chief Technology & Information Officer, YHB | CPAs & Consultants

Trusted by industry leaders.

Before the hunt

Questions worth
asking first.

Straight answers from the practitioners who do the work. If yours is not here, ask us directly.

No. A hunt is a point in time search of your environment, and ForgePath does not run a SOC or provide ongoing monitoring. You keep the queries and rules we write, so your own tools and team can keep looking afterward.

We stop and brief your leadership, then agree next steps with you and your counsel. That may mean moving into our Incident Response Leadership service, scoped separately, or handing the finding to a responder you already have.

Access to your EDR, SIEM and identity logs, plus cloud audit logs where relevant. If coverage is thin, we can deploy a collection tool such as Velociraptor with your approval. The report states plainly what we could and could not see.

It means we found no evidence of compromise in the data we could see, using the hypotheses we tested. That is a meaningful result, and the report says exactly where its limits are so nobody reads more into it than it supports.

The hunt reads data; it does not change systems. Any collection agent is deployed with your approval, tried on a small group of hosts first, and removed when the hunt ends.

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.