FourCore HUNT: Microsoft Defender for Endpoint threat hunting

AI agents hunt every new threat inside your Microsoft Defender for Endpoint, in KQL. Every match investigated, every empty result checked.

Looking for

Office app starts a script host

Running in Microsoft Defender for Endpoint · KQL

DeviceProcessEvents
| where InitiatingProcessFileName in~ ("winword.exe", "excel.exe")
| where FileName in~ ("wscript.exe", "mshta.exe")
| project Timestamp, DeviceName, FileName, ProcessCommandLine

Example, simplified.

How a hunt runs in Microsoft Defender for Endpoint.

FourCore HUNT hunts every new threat that matters to you inside Microsoft Defender for Endpoint, and brings back a verdict with its searches, evidence and limits.

  1. 01 · Hunt

    One question, searched in Microsoft Defender for Endpoint

    A new campaign, an advisory or a plain question becomes searches written for Microsoft Defender for Endpoint, run where your data already lives.

  2. 02 · Investigate

    Every match followed to its cause

    Follow-up searches run in Microsoft Defender for Endpoint until each match is traced to normal software, admin activity, your own FourCore ATTACK tests, or nothing known.

  3. 03 · Check

    An empty result is checked before it counts

    Before "not seen", FourCore checks the logs, fields and retention behind each search. If Microsoft Defender for Endpoint can't answer, the verdict says so and names what would close the gap.

Written for Microsoft Defender for Endpoint

Hunts run as KQL advanced hunting queries in Microsoft Defender, so they search the data where it already lives.

Office app starts a script host

DeviceProcessEvents
| where InitiatingProcessFileName in~ ("winword.exe", "excel.exe")
| where FileName in~ ("wscript.exe", "mshta.exe")
| project Timestamp, DeviceName, FileName, ProcessCommandLine

KQL · example, simplified

Built for Microsoft Defender for Endpoint.

Nothing new to deploy
Hunts run in the Microsoft Defender you already have, so every new threat gets checked without another agent or data copy.

What you get back.

Each relevant threat ends in a verdict, and every search behind it has a state.

Not seen
The searches could see the data, and nothing matched.
Could not check
The data needed wasn't there. HUNT says so instead of calling it clean.
Seen, explained
It matched, and HUNT traced it to normal activity.
Suspicious
It matched and has no normal explanation yet. A person should look.
Incident
Evidence of the threat. Your team is emailed.

Questions

How do you hunt threats in Microsoft Defender for Endpoint?

With FourCore HUNT, AI agents turn a new threat, an advisory or a plain question into KQL searches, run them in Microsoft Defender for Endpoint, follow every match to its cause and report a verdict with its evidence.

How do you check Microsoft Defender for Endpoint for a new threat or IOCs?

Give FourCore HUNT the report, advisory or indicators. It pulls out the behaviors and indicators, searches Microsoft Defender for Endpoint for each one and tells you whether the threat was seen, with the searches behind the answer. Threats that matter to you can also be hunted on a schedule.

Which query language does FourCore use in Microsoft Defender for Endpoint?

KQL. FourCore writes each search for Microsoft Defender for Endpoint, so hunts run where your data already lives.

Does threat hunting change anything in Microsoft Defender for Endpoint?

No. Hunts only read your data, and any action that would change something waits for approval.

What if Microsoft Defender for Endpoint is missing the logs a hunt needs?

The verdict says "could not check" for Microsoft Defender for Endpoint and names the logging change that would close the gap. A blind spot is never reported as clean.

Does it replace our threat hunters?

No. It writes the queries, checks the results and follows up on every match, and your hunters decide what happens next.

See HUNT on your Microsoft Defender for Endpoint.

You pick the threats, we connect read-only, and we review the verdicts together.