AI agents hunt every new threat inside your Google SecOps, in UDM search. Every match investigated, every empty result checked.
Looking for
Office app starts a script host
Running in Google SecOps · UDM search
metadata.event_type = "PROCESS_LAUNCH" AND principal.process.file.full_path = /(winword|excel)\.exe$/ nocase AND target.process.file.full_path = /(wscript|mshta)\.exe$/ nocase
Example, simplified.
FourCore HUNT hunts every new threat that matters to you inside Google SecOps, 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 Google SecOps, run where your data already lives.
02 · Investigate
Follow-up searches run in Google SecOps 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 Google SecOps can't answer, the verdict says so and names what would close the gap.
Hunts run as UDM search in your Google SecOps instance, so they search the data where it already lives.
Office app starts a script host
metadata.event_type = "PROCESS_LAUNCH" AND principal.process.file.full_path = /(winword|excel)\.exe$/ nocase AND target.process.file.full_path = /(wscript|mshta)\.exe$/ nocase
UDM search · 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 UDM search searches, run them in Google SecOps, 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 Google SecOps 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.
UDM search. FourCore writes each search for Google SecOps, 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 Google SecOps 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.