FourCore HUNT: Splunk threat hunting

AI agents hunt every new threat inside your Splunk, in SPL. Every match investigated, every empty result checked.

Looking for

Office app starts a script host

Running in Splunk · SPL

index=* EventCode=1 ParentImage IN ("*\\winword.exe","*\\excel.exe")
  Image IN ("*\\wscript.exe","*\\mshta.exe")
| stats count by host, Image, ParentImage

Example, simplified.

How a hunt runs in Splunk.

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

  1. 01 · Hunt

    One question, searched in Splunk

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

  2. 02 · Investigate

    Every match followed to its cause

    Follow-up searches run in Splunk 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 Splunk can't answer, the verdict says so and names what would close the gap.

Written for Splunk

Hunts run as SPL searches in your Splunk, so they search the data where it already lives.

Office app starts a script host

index=* EventCode=1 ParentImage IN ("*\\winword.exe","*\\excel.exe")
  Image IN ("*\\wscript.exe","*\\mshta.exe")
| stats count by host, Image, ParentImage

SPL · example, simplified

Built for Splunk.

Fits how your Splunk is set up
Hunts use your own field names and data, so results match what your team already sees.
Answers you can defend
Every verdict lists the searches behind it and what could not be checked, so you can stand behind "not here".

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 Splunk?

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

How do you check Splunk for a new threat or IOCs?

Give FourCore HUNT the report, advisory or indicators. It pulls out the behaviors and indicators, searches Splunk 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 Splunk?

SPL. FourCore writes each search for Splunk, so hunts run where your data already lives.

Does threat hunting change anything in Splunk?

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

What if Splunk is missing the logs a hunt needs?

The verdict says "could not check" for Splunk 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 Splunk.

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