简体中文
EnglishWhat Is Hai on the HackerOne Platform?
Updated
Hai is HackerOne's agentic AI orchestrator. It coordinates AI agents across every stage of the vulnerability lifecycle—discovery, validation, prioritization, and remediation—continuously scoring and validating findings. HackerOne says this reduces prioritization decisions from hours to seconds. Hai is best understood as the coordination layer inside the H1 Platform's Continuous Threat Exposure Management (CTEM) system, not a standalone scanning tool.
Where Hai sits in the H1 Platform
HackerOne describes the H1 Platform as "a single connected system across discovery, validation, prioritization, and remediation, powered by Hai and an elite community of security researchers." That sentence defines Hai's role: it is the AI layer that keeps the other components working as one pipeline.
The platform components Hai works alongside include:
| Component | What it does |
|---|---|
| H1 Bounty | Elite researchers find critical vulnerabilities, including novel attack chains and business logic flaws that automated tools miss |
| H1 Agentic Pentest | AI-driven pentesting that scales with the attack surface |
| H1 Continuous Testing | Always-on agentic testing that finds, validates, and proves exploitable vulnerabilities |
| H1 Validation | Confirms exploitability in your environment, cited at 95% accuracy with a 40% signal improvement |
| H1 Remediation | Source code-informed fix plans delivered to engineering in one click |
| H1 Code | Reviews pull requests, validates exploitability, and delivers context-aware fixes into developer workflows |
| H1 AI Red Teaming | Adversarial testing for AI systems, mapped to OWASP LLM Top 10, MITRE ATLAS, and NIST AI RMF |
Hai's job is to coordinate agents across these stages rather than replace any single one. The human researcher community remains a distinct input—Hai orchestrates AI agents, while bounty researchers supply the ingenuity the platform markets alongside it.
The mechanism: continuous scoring and validation
The core idea behind Hai is that finding vulnerabilities is not the bottleneck—deciding which ones matter is. HackerOne's framing is explicit: "Not every vulnerability matters. Fix the ones that do."
Hai addresses this by scoring and validating findings continuously rather than in batches. Instead of a queue of raw alerts waiting for a human to triage, findings are assessed as they arrive, and exploitability is confirmed before they reach a prioritization decision. The claimed result is that prioritization moves from hours to seconds.
A concrete example of where this matters: a team running continuous testing across several applications may generate a large volume of candidate findings in a week. Without orchestration, an analyst has to manually separate real exploitable issues from noise before engineering can act. With Hai coordinating validation and scoring, the findings that reach engineering are the ones already confirmed as exploitable in the team's own environment—which is the same outcome Shopify reported, citing a 62% acceleration in validation and triage using Hai's agentic AI capabilities.
What Hai is not
- Not a replacement for researchers. HackerOne positions H1 Bounty's elite researchers as finding attack chains and business logic flaws "no automated tool reaches." Hai coordinates agents; it does not eliminate the human community.
- Not a single product you buy separately. Hai is described as the orchestrator inside the H1 Platform. The platform's CTEM positioning—closing the discovery-remediation gap—is the product frame.
- Not a guarantee of zero noise. The 95% validation accuracy and 40% signal improvement figures are HackerOne's own claims; treat them as vendor-reported benchmarks to verify against your environment.
Who should care about Hai
Hai is relevant if your problem is triage volume rather than detection coverage—that is, you already surface more findings than your team can prioritize, and the delay between discovery and remediation is the risk you want to shrink. If your gap is finding vulnerabilities at all, the surrounding components (H1 Bounty, H1 Continuous Testing, H1 Agentic Pentest) are the more direct starting points, with Hai coordinating once those are in place.
For teams evaluating the platform, the practical question to bring to a demo is how Hai's scoring and validation behave against your own codebase and attack surface, since the value proposition rests entirely on prioritization accuracy in your environment.