Skip to content

Commit 2078cd5

Browse files
bernacodesidoalexjavabraz
authored andcommitted
Update bug bounty program handler, domains and response times
1 parent a915946 commit 2078cd5

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

SECURITY.md

+7-7
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,31 @@
1-
# RSK's Security Process
1+
# 2WP-API Security Process
22

33
We're committed to conduct our security process in a professional and civil manner. Public shaming, under-reporting or misrepresentation of vulnerabilities will not be tolerated.
44

55
## Responsible Disclosure
66

7-
For all security related issues, RSK has to main points of contact. Reach us at <security@iovlabs.org> or refer to our [Bug Bounty Program.](https://www.rsk.co/bounty-program/) **Do not open up a GitHub issue if the bug is a security vulnerability.**
7+
For all security related issues, RootstockLabs has to main points of contact. Reach us at <security@rootstocklabs.com> or refer to our [Bug Bounty Program.](https://www.rootstocklabs.com/bug-bounty-program) **Do not open up a GitHub issue if the bug is a security vulnerability.**
88

99
**Ensure the bug was not already reported** by searching on Github under [Issues](https://github.com/rsksmart/2wp-api/issues).
1010

1111
## Vulnerability Handling
1212

1313
### Response Time
1414

15-
RSK will make a best effort to meet the following response times for reported vulnerabilities:
15+
RootstockLabs will make a best effort to meet the following response times for reported vulnerabilities:
1616

17-
* Time to first response (from report submit) - 24 hours
18-
* Time to triage (from report submit) - 2 business days
17+
* Time to first response (from report submit) - 5 business days
18+
* Time to triage (from report submit) - 7 business days
1919
* Time to bounty (from triage) - 15 business days
2020

2121
We’ll try to keep you informed about our progress throughout the process.
2222

2323
### Disclouse Policy
2424

2525
* Follow HackerOne's [disclosure guidelines](https://www.hackerone.com/disclosure-guidelines).
26-
* Public disclosure of a vulnerability makes it ineligible for a bounty. If the user reports the vulnerability to other security teams (e.g. Ethereum or ETC) but reports to RSK with considerable delay, then RSK may reduce or cancel the bounty.
26+
* Public disclosure of a vulnerability makes it ineligible for a bounty.
2727

28-
For more information check RSK bounty program policy at [HackerOne](https://hackerone.com/iovlabs)
28+
For more information check RootstockLabs bounty program policy at [HackerOne](https://hackerone.com/rootstocklabs)
2929

3030
## Public Keys
3131

0 commit comments

Comments
 (0)