HackerOne provides functionality to allow you to define your program's scope by listing assets that are considered in or out of scope for your program.
HackerOne supports the following types of assets:
||Any valid IPv4 or IPv6 CIDR range.
||Domain of the asset. Wild card (
*) may be used.
|iOS: App Store
||The identifier in the Apple Store to locate your App.
||A standard apple identifier (https://developer.apple.com/testflight/).
Note: If you'll be providing a different version than the one available in the App Store, please detail the invitation process in the instructions.
||A standard apple identifier.
Note: If you'll be providing a different version than the one available in the App Store or Testflight, please detail where they can be located.
|Android Play Store
||The id in Play Store used to locate your application (https://developer.android.com/studio/build/application-id.html).
||A standard APK identifier.
Note: If you'll be providing a different version than the one available in the Play Store, please detail where they can be located.
|Windows: Microsoft Store
||The identifier in the Microsoft Store used to locate your app. It can be either a store ID like '9WZDNCRFHVJL' or an identifier name like 'Microsoft.SDKSamples.ApplicationDataSample'.
||Link to the repository of an open source project.
||Packaged executable on Linux, Windows, or Mac. Open source projects with releases can and should link as a Downloadable executable too.
||Identifiable model number and make. Be sure to explain in the instructions how to locate the model details and what they may look like.
||Any other type of asset that is not contained within the existing taxonomy.
Source Code, Downloadable Executables, and Hardware Identifiers aren't validated. You're free to use this in whatever suits your naming conventions.
You can edit your scopes in your settings under Program Settings > Program > Scope.