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, ProcessCommandLineExample, simplified.
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.
01 · Hunt
A new campaign, an advisory or a plain question becomes searches written for Microsoft Defender for Endpoint, run where your data already lives.
02 · Investigate
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.
03 · Check
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.
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, ProcessCommandLineKQL · example, simplified
Each relevant threat ends in a verdict, and every search behind it has a state.
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.
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.
KQL. FourCore writes each search for Microsoft Defender for Endpoint, so hunts run where your data already lives.
No. Hunts only read your data, and any action that would change something waits for approval.
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.
No. It writes the queries, checks the results and follows up on every match, and your hunters decide what happens next.
You pick the threats, we connect read-only, and we review the verdicts together.