Integrations

Works with the stack you already run

Lairhunt reads from the telemetry sources you already collect and acts through the security tools you already own. Nothing needs replacing to start.

NVIDIA

GPU-native from packet to playbook

Pipelines

Morpheus

GPU cybersecurity pipelines for line-rate telemetry analysis.

Data science

RAPIDS

cuDF, cuML and cuGraph for dataframes, models and attack graphs.

Agents

NeMo

The investigation agent, retrieval and guardrails behind Veridex.

Serving

Triton, NIM and TensorRT

Low-latency model serving for detection and reasoning.

Network

BlueField DPU and DOCA

In-path capture and enforcement at line rate.

Edge

Jetson and IGX

The hardware inside Sentix appliances.

Telemetry sources

What Lairhunt reads

SplunkSIEM search and forwarders
Microsoft SentinelSIEM and Log Analytics
ElasticSecurity and log indices
Google ChronicleSecOps data
CrowdStrike FalconEDR telemetry
Microsoft DefenderXDR telemetry
Okta and Entra IDIdentity events
AWS, Azure, Google CloudAudit and flow logs

Response and workflow

Where Lairhunt acts and reports

CrowdStrike, Defender, SentinelOneHost isolation
Okta, Entra IDDisable, reset, revoke sessions
Palo Alto Networks, FortinetBlock flows and domains
Cloud APIsQuarantine workloads
Splunk SOAR, Cortex XSOARPlaybook handoff
ServiceNow, JiraIncident tickets
Slack, Microsoft TeamsIncident alerts
WebhooksAnything else

API

Everything in the console, from the API

List incidents, read their evidence and approve or roll back actions through a REST API. Signed webhooks tell your systems when something changes.

  • REST API with an OpenAPI spec
  • Signed webhooks for incident and action events
  • Scoped API tokens per integration
curl · example
curl https://api.lairhunt.com/v1/incidents?status=open \
  -H "Authorization: Bearer $LAIRHUNT_TOKEN"

# approve the recommended action on one incident
curl -X POST https://api.lairhunt.com/v1/incidents/INC-0412/actions/act_01JD4K7P/approve \
  -H "Authorization: Bearer $LAIRHUNT_TOKEN" \
  -d '{"comment": "Confirmed with IAM on-call"}'

Data formats

What we read and write

DataFormats inFormats out
NetworkNetFlow v5/v9, IPFIX, sFlow, VPC flow logs, Zeek, PCAPScored flow metadata
LogsSyslog, CEF, LEEF, JSON, OCSFOCSF-normalised events
IdentityEntra ID, Okta and Active Directory sign-in and audit logsIdentity timelines
Threat intelSTIX 2.1, TAXII, MISPSTIX 2.1 indicators from incidents
IncidentsNot applicableJSON, PDF, webhook events

Don't see your tool?

Most new sources take a connector and a few days. Tell a hunter what you run.