In continuing our series on building a bounty brief, we've already covered
creating a scope
, and also touched briefly on focus areas. Now that you have the foundation of what you want researchers to be testing, it's now time to turn your attention to what you
want them to be testing - which is just as, if not more important, as clearly stating what you do want to be tested. We do this by explicitly noting and drawing the researcher's attention to our
Why is it so important? Simply put, it's a matter of respecting researchers' time and effort. If we take a moment to look at this from a researcher's point of view, every issue that we clearly exclude on the bounty brief is something they won't/don't need waste their time testing for and/or reporting. A brief that doesn't contain explicit exclusions runs the risk of receiving issues that the program owner may not care for - resulting in wasting the time and resources of both the researcher and the program owner.
To clearly document these exclusions, we've identified five of the most common categories to consider for exclusions when building your program: low impact issues, intended functionality, known issues, accepted risks, and issues resulting from pivoting.