Write a report

Bug bounty AI policies

All four major bug bounty platforms allow AI, and all four punish reports nobody verified. Each rule below is quoted from the platform's own page and linked.

Updated November 18, 2026By bugbountyai

HackerOne

Encouraged

permits and encourages the responsible use of AI tools throughout the research workflow
  • AI for recon, discovery and reports
  • Validate every finding yourself
  • Fully autonomous hackbots
  • Disclosure of AI use required
Read the HackerOne rule

Code of Conduct. Updated for AI in May 2026.

Bugcrowd

Allowed

manually review and validate any vulnerability report you've created with the help of GenAI tools
  • GenAI to help write reports
  • Review every report by hand
  • Confidential data in AI tools
  • Disclosure of AI use required
Read the Bugcrowd rule

Code of Conduct. Modified December 1, 2025.

Intigriti

Encouraged

permitted and encouraged when used responsibly as part of a hacker's workflow
  • AI across your workflow
  • Disclose when and how you used AI
  • Verify the bug yourself
  • Unverified or fabricated reports
Read the Intigriti rule

Community Code of Conduct. Dated March 9, 2026.

YesWeHack

Controlled

maintain control over tools, scanners, payloads, and LLM results
  • LLMs under your control
  • Manual verification of findings
  • Reports from AI hypotheses
  • Disclosure of AI use required
Read the YesWeHack rule

Platform code of conduct. Dated March 16, 2026.

The full table

Every cell comes from the quotes on each platform's page.

HackerOneBugcrowdIntigritiYesWeHack
AI useEncouragedAllowedEncouragedControlled
Disclose AI useNot requiredNot requiredRequired, saying when and howNot required
Verify every finding by handRequiredRequiredRequiredRequired
Confidential data in AI toolsNo rule on outside AI tools; you stay responsible for their outputOnly if no confidential information reaches the toolUnapproved tools may not process reproduction informationGeneral rule to keep report data confidential
Fully automated reportsHackbots must not run fully autonomouslyAutomated or unverified output is not a valid submissionUnverified AI output may be closed without responseYou must keep control over LLM results
Penalty for AI slopFinal warning, then a 12-month ban, then a permanent banRejection, a 30-day suspension, and a cap of 6 reports a week under 50% accuracyClosed without response, slower validation, possible removalSeverity 7 of 7, the top of the scale; spam reports cost 3x credits
Program rules on topYesYesYesYes
The rule, quoted"HackerOne permits and encourages the responsible use of AI tools throughout the research workflow, including for learning, reconnaissance, vulnerability discovery, proof-of-concept development, and report quality improvement.""You manually review and validate any vulnerability report you've created with the help of GenAI tools before submitting it.""The use of AI tools is permitted and encouraged when used responsibly as part of a hacker's workflow.""Limit testing volume to what is reasonable and maintain control over tools, scanners, payloads, and LLM results."
SourceHackerOne Code of ConductUpdated for AI in May 2026Bugcrowd Code of ConductModified December 1, 2025Intigriti Community Code of ConductDated March 9, 2026YesWeHack Platform code of conductDated March 16, 2026

A check means the rule says yes, a cross means no, a dash means partly. Read November 18, 2026.

Programs with their own AI rule

A program policy can add rules on top of the platform's.

ProgramIts rule, quotedAlso
curl"If you asked an AI tool to find problems in curl, you must make sure to reveal this fact in your report."Bans users who submit made-up reports.
Django"Disclose which AI tools were used and specify what they were used for"Closes unverified AI reports without response.
Apple Security Bounty"Avoid lengthy descriptions generated by AI tools."May pause your reports for 180 days after repeated unvalidated AI findings.