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
Response and workflow
Where Lairhunt acts and reports
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 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
| Data | Formats in | Formats out |
|---|---|---|
| Network | NetFlow v5/v9, IPFIX, sFlow, VPC flow logs, Zeek, PCAP | Scored flow metadata |
| Logs | Syslog, CEF, LEEF, JSON, OCSF | OCSF-normalised events |
| Identity | Entra ID, Okta and Active Directory sign-in and audit logs | Identity timelines |
| Threat intel | STIX 2.1, TAXII, MISP | STIX 2.1 indicators from incidents |
| Incidents | Not applicable | JSON, PDF, webhook events |
Don't see your tool?
Most new sources take a connector and a few days. Tell a hunter what you run.