Elastic Reports AI Bug Bounty Triage System Agrees with Humans 85% of the Time
Summary
Elastic says its AI pipeline triaged HackerOne vulnerability reports for about $2 each and agreed with human decisions 85% of the time in retrospective testing on 764 reports. It uses isolated ephemeral VMs, adversarial review, and human approval.
Key points
- Elastic says it received more than 1,390 bug bounty reports in the first half of 2026, exceeding its combined totals for 2024 and 2025.
- Retrospective testing on 764 reports with known outcomes showed 85% agreement with human security engineers; calibration used more than 3,300 historical reports.
- The eight-stage analysis pipeline assesses validity, realistic exploitability, product applicability, CVSS, and reproduction feasibility; an independent adversarial review can route disagreements to a human.
- Analysis and reproduction run on separate ephemeral Google Cloud VMs. Reproduction executes researcher-described steps in a sandboxed Docker environment, and VMs terminate after 30 minutes.
- Controls include network isolation, filtered outbound traffic, separated credentials, resource limits, and read-only workspaces.
- Human reviewers make every final decision and approve external actions. Elastic says the system is in production but is still collecting data on production accuracy.
Article Details
- Topic
- Elastic's AI-assisted bug bounty triage system, including its validation process, sandboxed vulnerability reproduction, and security controls.
MITRE ATT&CK
T1059 · Command and Scripting InterpreterThe reproduction phase may execute researcher-described commands inside a sandboxed tester container.T1496 · Resource HijackingThe threat model considers resource abuse, including cryptocurrency mining and costly cloud provisioning.T1499 · Endpoint Denial of ServiceThe article discusses denial-of-service reports involving a crafted request that causes an out-of-memory crash.T1609 · Container Administration CommandThe system uses Docker Compose to provision Elastic Stack containers for reproduction.T1611 · Escape to HostThe threat model considers reproduction steps that attempt to escape the Docker container to the host VM.
Vendors
Anthropicand injected as environment variables only for the phase that needs them. The analysis VM gets the Anthropic API key. The reproduction VM gets the Elastic Cloud key (only if provisioning a cloud environment). NoElasticElastic built an AI-assisted bug bounty triage system to handle a surge of AI-generated HackerOne reports, using multi-stage analysis, adversarial review, and sandboxed reproduction on ephemeral Google Cloud VMs.Google CloudElastic built an AI-assisted bug bounty triage system to handle a surge of AI-generated HackerOne reports, using multi-stage analysis, adversarial review, and sandboxed reproduction on ephemeral Google Cloud VMs.HackerOneElastic built an AI-assisted bug bounty triage system to handle a surge of AI-generated HackerOne reports, using multi-stage analysis, adversarial review, and sandboxed reproduction on ephemeral Google Cloud VMs.
Products
Claude#HackerOneElastic Stack[T1609 ] Container Administration Command – The system explicitly runs Docker Compose and containers to provision reproducible environments (‘provisions an Elastic Stack via Docker Compose’).Elastic WorkflowsElastic Workflows orchestrates the entire flow: triggering on new HackerOne reports synced into Elasticsearch, managing the VM lifecycle, enforcing concurrency limits, posting triage results back to HackerOne asElasticsearch#HackerOneHackerOneElastic built an AI-assisted bug bounty triage system to handle a surge of AI-generated HackerOne reports, using multi-stage analysis, adversarial review, and sandboxed reproduction on ephemeral Google Cloud VMs.