AI agents hunt every new threat inside your IBM QRadar, in AQL. Every match investigated, every empty result checked.
Looking for
Office app starts a script host
Running in IBM QRadar · AQL
SELECT sourceip, "Process Name" FROM events
WHERE "Parent Process Name" IN ('winword.exe', 'excel.exe')
AND "Process Name" IN ('wscript.exe', 'mshta.exe')
LAST 24 HOURSExample, simplified.
FourCore HUNT hunts every new threat that matters to you inside IBM QRadar, 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 IBM QRadar, run where your data already lives.
02 · Investigate
Follow-up searches run in IBM QRadar 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 IBM QRadar can't answer, the verdict says so and names what would close the gap.
Hunts run as AQL searches in your QRadar, so they search the data where it already lives.
Office app starts a script host
SELECT sourceip, "Process Name" FROM events
WHERE "Parent Process Name" IN ('winword.exe', 'excel.exe')
AND "Process Name" IN ('wscript.exe', 'mshta.exe')
LAST 24 HOURSAQL · 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 AQL searches, run them in IBM QRadar, 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 IBM QRadar 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.
AQL. FourCore writes each search for IBM QRadar, 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 IBM QRadar 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.