Notification timelines and response commitments are defined in your agreement. This page describes the process and the information to include, not the contractual service levels.
Reporting an incident
If you suspect a security incident affecting your deployment, report it to your Hilt representative or account team.1
Contain on your side if needed
Because the platform runs in your account, you hold the immediate response controls. You can quarantine an affected host to sever its network access while preserving forensic telemetry (see Collectors), and you can revoke Hilt access through your cloud IAM controls.
2
Report to Hilt
Contact your Hilt representative with the deployment identifier, the time window, the hosts or components involved, and what you observed. Findings and the audit log in your dashboard help establish the timeline.
3
Investigate together
Hilt investigates platform-side aspects under your approval workflow. Because telemetry stays in your account, evidence does not need to leave your environment for analysis.
Severity
Incidents are assessed jointly to set priority. A typical framing:
The exact tier definitions, notification timelines, and response targets that apply to your deployment are set out in your agreement.
What Hilt provides
- Notification of incidents affecting the platform, per your agreement.
- Investigation of platform-side components, conducted under your approval workflow.
- Remediation through the versioned release and update process (see Security operations).
Reporting a vulnerability
To report a vulnerability in Hilt’s software (collectors, dashboard, or platform components), contact your Hilt representative or account team. Include:- The affected component and version (collector release tags follow
vMAJOR.MINOR.PATCH) - A description of the issue and its impact
- Steps to reproduce, and any proof-of-concept detail