Service · Threat hunting
Find what detection missed.
VIntercept’s hunters work with Solomon SOC’s Hunt agent to test hypotheses across kernel telemetry and the tools you already own. Whatever they find becomes a case, and every hunt leaves a new detection behind.
- Credential files read by non-deploy processesrunningfrom: verdict 0412
- Shells spawned by web workloads2 findingsfrom: behavior change
- IMDS calls without a session tokencleanfrom: threat intel
Illustration. Hunt names and results are fictional.
Our approach
Human hunters and agents, in tandem.
Agents cover the breadth; our hunters bring the hypotheses that need judgment.
Hunts that start from evidence
- The Hunt agent proposes hunts from recent verdicts, threat intelligence and changes in behavior
- Our hunters add hypotheses for the gaps automation cannot see
- Hunts run on a schedule or on demand
Telemetry down to the system call
- Process, file and network events from the Solomon eBPF Client on Linux hosts and Kubernetes nodes
- Identity, EDR, cloud and SIEM data from the tools OmniMesh connects
- Threat intelligence lookups from sources such as VirusTotal, GreyNoise and AbuseIPDB
Findings become cases
- Confirmed findings are promoted to cases in Solomon SOC
- Investigate takes them from there, with evidence linked to every claim
- Ask Solomon answers questions about what a hunt found
Every hunt hardens detection
- Detect turns findings into new or tuned rules
- Each rule is backtested against your historical data before it ships
- Coverage mapped to MITRE ATT&CK, with version history and rollback
Hunt method
From intelligence to hardening.
- 01
Gather
Threat intelligence for your sector and stack, plus what recent investigations in your tenant concluded.
- 02
Hypothesize
Testable hypotheses that target the gaps your current rules leave open.
- 03
Hunt
The Hunt agent queries the telemetry while our hunters pivot on what comes back.
- 04
Harden
Findings become cases, and new rules are backtested before they ship.
- per agentic investigation of a finding1
- YARA and Sigma rules in the deterministic layer2
- native connectors to hunt across3
- 1Measured end-to-end Solomon SOC agentic investigations (owner-confirmed, 19 Oct 2026).
- 2YARA and Sigma rules applied in the Platform's deterministic layer (owner-confirmed, 19 Oct 2026).
- 3Connectors in the portal's integrations catalog today; the number updates as the catalog grows.
Solomon platform
What we hunt with
- Agentic investigationSolomon SOCThe Hunt, Investigate and Detect agents, and the cases they share.Explore
- Kernel actsSolomon eBPF ClientKernel telemetry from Linux hosts and Kubernetes nodes.Explore
- Correlate and remediateSolomon OmniMeshIdentity, EDR, cloud, SIEM and threat-intelligence data from your stack.Explore
- AI agents thinkSolomon Agentic AI PlatformStores, normalizes and detects on everything, per tenant.Explore
Find what automation misses.
Schedule a hunt or talk to us about a recurring engagement. A guided pilot is the fastest way to start.