non-technical bugbounty tips
Summary
Joseph Thacker's non-technical bug bounty tips: write verbose and clear reports, be assertive but respectful when a valid bug is closed in error, and default to sharing stuck findings with 2-3 peers instead of giving up.
- Published
- Collected
--- id: 1721 title: "non-technical bugbounty tips" source_domain: josephthacker.com source_url: "https://josephthacker.com/hacking/2020/12/26/non-technical-bug-bounty-tips.html" published_at: "2020-12-26T00:00:00Z" tags: ["bug-bounty", "methodology", "tips"] phying_url: "https://phying.com/item/1721" lang: en --- # non-technical bugbounty tips ## Summary Joseph Thacker's non-technical bug bounty tips: write verbose and clear reports, be assertive but respectful when a valid bug is closed in error, and default to sharing stuck findings with 2-3 peers instead of giving up. ## Intelligence Metadata - **Sources:** josephthacker.com - **Published:** 2020-12-26T00:00:00Z - **Original:** https://josephthacker.com/hacking/2020/12/26/non-technical-bug-bounty-tips.html - **Phying News:** https://phying.com/item/1721