Program Overview
FINRA Response runs a vulnerability disclosure program on HackerOne. The program has 2 in-scope assets and is managed by HackerOne's triage team.
2
In-Scope Assets
100%
Efficiency
In-Scope Assets
| Asset | Type | Max Severity | Eligible |
|---|---|---|---|
| *.finra.org | WILDCARD | Critical | No Bounty |
| https://ews.qa.finra.org/* | WILDCARD | Critical | No Bounty |
Out-of-Scope Assets
- *.fip.finra.org
- https://ews.finra.org/*
Tips for Hacking FINRA Response
- Read the policy — Understand what's in scope, out of scope, and any specific testing restrictions before you start.
- Enumerate the attack surface — Use subdomain enumeration and directory bruteforcing to map all accessible endpoints.
- Focus on high-impact bugs — Look for SQL injection, SSRF, and IDOR vulnerabilities first.
- Test authentication flows — Check for OAuth misconfigurations and CSRF in login/signup flows.
- Write clear reports — Include steps to reproduce, impact assessment, and suggested remediation. Use Burp Suite to capture evidence.
Frequently Asked Questions
How do I start hacking FINRA Response?
Sign up on HackerOne, read the program policy carefully, review the in-scope assets listed above, and start testing. Always stay within scope and follow responsible disclosure guidelines.
Does FINRA Response pay bounties?
No, FINRA Response runs a Vulnerability Disclosure Program (VDP) without monetary rewards. You may receive recognition or swag.
What types of vulnerabilities does FINRA Response accept?
FINRA Response accepts reports for vulnerabilities found in their 2 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.