FourCore HUNT: Google SecOps threat hunting

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.

How a hunt runs in Google SecOps.

FourCore HUNT hunts every new threat that matters to you inside Google SecOps, and brings back a verdict with its searches, evidence and limits.

  1. 01 · Hunt

    One question, searched in Google SecOps

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

  2. 02 · Investigate

    Every match followed to its cause

    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.

  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 Google SecOps can't answer, the verdict says so and names what would close the gap.

Written for Google SecOps

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

Built for Google SecOps.

Detections in context
FourCore Analyst also reads SecOps cases, alerts, detections and rules, so a hunt verdict can say what already fired.

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 Google SecOps?

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.

How do you check Google SecOps for a new threat or IOCs?

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.

Which query language does FourCore use in Google SecOps?

UDM search. FourCore writes each search for Google SecOps, so hunts run where your data already lives.

Does threat hunting change anything in Google SecOps?

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

What if Google SecOps is missing the logs a hunt needs?

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.

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 Google SecOps.

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