Bug bounty program
FT
ForeScout Technologies
Most upvoted reports2
| Report | Weakness | Disclosed | Bounty | Votes |
|---|---|---|---|---|
| DOM XSS at www.forescout.com in Microsoft Edge and IE BrowserAnalysed#704266 | Cross-site Scripting | 2020-04-07 | – | 98 |
| HTML Injection & Content Spoofing#668422 | No weakness recorded | – | $250 | 63 |
Subdomains636
| Name | Scope | First seen |
|---|---|---|
| auth1x.lab.forescout.comauth | Not in the scope | 2026-11-14 |
| www.auth1x.lab.forescout.comauth | Not in the scope | 2026-11-14 |
| login.app.cloud.forescout.comauth | Not in the scope | 2026-11-14 |
| login.dev.cloud.forescout.comauth, dev | Not in the scope | 2026-11-14 |
| login.stg.cloud.forescout.comauth, staging | Not in the scope | 2026-11-14 |
| login.demo.cloud.forescout.comauth, test | Not in the scope | 2026-11-14 |
17 names are covered by the program's own scope; 0 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.
A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-15.