Trust and security
A security tool you can audit
Lairhunt reads your most sensitive telemetry and can act on your network. So it is built to keep data in your control, keep people in charge of actions, and record everything it does.
Principles
How we build it
Evidence
Claims link to data
Every incident statement links to the events behind it. Nothing is asserted without evidence.
Uncertainty
Confidence is shown
Incidents carry calibrated confidence. Low confidence is flagged, not hidden.
Control
People set the limits
Automation runs only inside guardrails your team writes and versions.
Reversibility
Every action can be undone
Containment records prior state and supports one-click rollback.
Isolation
Your data stays yours
Telemetry and models are isolated per tenant. Sharing is opt-in and anonymised.
Scope
Know the limits
We state what Lairhunt monitors and, as clearly, what it doesn't.
Method
How an incident earns its confidence
Score
Huntra scores events against your tenant's baselines.
Corroborate
Veridex looks for independent evidence across other sources.
Calibrate
Severity and confidence are calibrated against analyst verdicts.
Decide
Guardrails decide whether a person or Quellix takes the next step.
Standards context
Built to support the frameworks you work to
Lairhunt produces evidence and records that help with these frameworks. Lairhunt is not an auditor or certification body, and using it does not make you compliant.
| Framework | Scope | How Lairhunt helps |
|---|---|---|
| MITRE ATT&CK | Adversary techniques | Every detection and incident is mapped to techniques; coverage is reported |
| NIST CSF 2.0 | Cybersecurity risk management | Evidence for the Detect and Respond functions |
| SOC 2 | Service organisation controls | Monitoring and incident-response records for your own audit |
| ISO/IEC 27001 | Information security management | Logging, monitoring and incident-management evidence |
| NIS2 | EU network and information security | Incident timelines that support reporting deadlines |
| DORA | EU financial-sector operational resilience | ICT incident detection, classification and records |
| HIPAA Security Rule | US health data | Audit-control and security-incident records |
| PCI DSS v4.0 | Payment card data | Log review and incident-response evidence |
| IEC 62443 | Industrial automation security | Monitoring evidence for OT networks through Sentix |
Audit trail
Every action is on the record
Each containment action records the incident, evidence, guardrail version, blast-radius check, who approved it and how to roll it back. Records are signed and exportable.
- Signed, tamper-evident action records
- Immutable storage with configurable retention
- Exports as JSON and PDF for auditors
{
"action_id": "act_01JD4K7P",
"incident": "INC-0412",
"action": "isolate_host",
"target": "hr-fs-02",
"mode": "approve",
"approved_by": "soc-lead@example.com",
"blast_radius": { "interactive_users": 0, "services": 1 },
"guardrails_version": 3,
"evidence": ["evt_9f2c…", "evt_41aa…"],
"rollback": "available",
"signature": "ed25519:3b7d…"
}Security
Protecting your telemetry
Isolation
Per-tenant compute and storage
Each customer's telemetry, baselines and incidents are isolated.
Encryption
In transit and at rest
TLS 1.3 in transit, AES-256 at rest, customer-managed keys available.
Access
SSO and roles
SAML SSO, SCIM provisioning and role-based access with full access logs.
Confidential computing
Protected processing
Planned support for NVIDIA H100 confidential computing for sensitive tenants.
Residency
Choose your region
Data stays in the region you choose, or on your own hardware.
Assurance
Independent audits
SOC 2 Type II and ISO/IEC 27001 audits are planned for our first year of operation. We hold neither today.
Questions
About trust and security
Is Lairhunt certified?
Not yet. SOC 2 Type II and ISO/IEC 27001 audits are planned for our first year of operation. We will publish reports to customers under NDA when they exist.
Can Lairhunt staff see our telemetry?
Only with your permission, for a stated support task, and every access is logged in your audit trail. On-prem deployments give us no access at all.
How do you secure the integrations that take action?
Response integrations use the narrowest API scopes each vendor offers, credentials are stored encrypted per tenant, and every call is logged.
How do we report a vulnerability?
Email security@lairhunt.com. We acknowledge reports within two business days.
Bring your security team
We'll walk through data handling, guardrails and the audit trail with them.