Parity Polkadot Release Infrastructure : Program info

IN-SCOPE

• Parity releases pipeline: any bugs which could be used to enable an attacker to inject malicious code into our distributed binaries, or be used to halt Parity’s release process or add malicious/unintended functions to the released binaries.
• Production infrastructure: publicly-available infrastructure Parity runs for production-grade networks (in contrast to testnets), especially parts which are critical for network’s well-being or safety of funds. Please note that this does not include our publicly available web pages that are static.

Please note that where the scope of this policy includes third-party code this should not be taken as an indication that we are legally or otherwise responsible for that code, its security, quality or your rights in respect of that code.

OUT OF SCOPE

Most other things are not in scope, though. Specifically:

• Static websites, until you can find a way to compromise the data on the website for all of the visitors.
• Bugs which have already been submitted by another user or are already known to the Parity team or have already been publicly disclosed.
• Bugs in third-party tools and services we’re using (but we would be glad to connect you with the security team of the corresponding project).
• Parity Technologies’ development team, Parity Technology employees and any other person employed or providing services in any way to the company, directly or indirectly, are not eligible for rewards. Social engineering attacks are also here.
• Anything that contravenes the spirit or letter of this Program.

Responsible investigation and reporting includes, but isn't limited to, the following:

• Use your best effort not to access, modify, delete, or store user data or Parity’s data.
• Don’t defraud, harm, or violate the privacy of Parity Technologies Ltd or its users during your research; you should make a good faith effort to not interrupt or degrade our services.
• Don't target our physical security measures, or attempt to use social engineering, etc.
• Keep the details of any suspected bug confidential.
• Please don’t make repeat submissions of low quality, rejected or automated vulnerability reports. In general, please investigate and report bugs in a way that makes a reasonable, good faith effort not to be disruptive or harmful to us or our users. Otherwise your actions might be interpreted as an attack rather than an effort to be helpful.
• Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
• Make every effort not to damage or restrict the availability of products, services, or infrastructure
• Avoid compromising any personal data, interruption, or degradation of any service
• Don’t access or modify other user data, localize all tests to your accounts
• Perform testing only within the scope
• Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
• Don’t spam forms or account creation flows using automated scanners
• In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
• Don’t break any law and stay in the defined scope
• Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
• In case that your finding is valid you might be asked for extra KYC verification to proceed with payments

• Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
• No vulnerability disclosure, including partial is allowed for the moment.
• Please do NOT publish/discuss bugs

We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability
• Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
• You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
• You must not be a former or current employee of us or one of its contractor.
• ONLY USE YOUR HackenProof ADDRESS (in case of violation, no bounty can be awarded)
• Provide detailed but to-the point reproduction steps