Skip to content

Commit b6f4222

Browse files
rnbguygreg-szabo
andauthored
chore: add SECURITY.md (#1328)
* add SECURITY.md Signed-off-by: Rano | Ranadeep <[email protected]> * update SECURITY.md Signed-off-by: Rano | Ranadeep <[email protected]> * apply suggestions from code review Co-authored-by: Greg Szabo <[email protected]> Signed-off-by: Rano | Ranadeep <[email protected]> * fmt Signed-off-by: Rano | Ranadeep <[email protected]> * original interchain text * rm mention of bounty --------- Signed-off-by: Rano | Ranadeep <[email protected]> Signed-off-by: Rano | Ranadeep <[email protected]> Co-authored-by: Greg Szabo <[email protected]>
1 parent 81625d6 commit b6f4222

File tree

1 file changed

+40
-0
lines changed

1 file changed

+40
-0
lines changed

SECURITY.md

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
# Security Policy
2+
3+
## Reporting a Security Vulnerability
4+
5+
If you believe you have found a security vulnerability in the Interchain Stack,
6+
you can report it to our primary vulnerability disclosure channel, the
7+
[Cosmos HackerOne program][hackerone-bug].
8+
9+
> [!NOTE]
10+
> The `ibc-rs` is **NOT** part of the rewards program. Any issues reported for
11+
> `ibc-rs` are not eligible for bounty rewards.
12+
13+
If you prefer to report an issue via email, you may send a bug report to
14+
[email protected] with the issue details, reproduction, impact, and other
15+
information. Please submit only one unique email thread per vulnerability.
16+
17+
<!-- Any issues reported via email are ineligible for bounty rewards. -->
18+
19+
Artifacts from an email report are saved at the time the email is triaged.
20+
Please note: our team cannot monitor dynamic content (e.g. a Google Docs link
21+
that is edited after receipt) throughout the lifecycle of a report. If you would
22+
like to share additional information or modify previous information, please
23+
include it in an additional reply as an additional attachment.
24+
25+
Please **DO NOT** file a public issue in this repository to report a security
26+
vulnerability.
27+
28+
## Coordinated Vulnerability Disclosure Policy and Safe Harbor
29+
30+
For the most up-to-date version of the policies that govern vulnerability
31+
disclosure, please consult the [HackerOne program page][hackerone-policy].
32+
33+
The policy hosted on HackerOne is the official Coordinated Vulnerability
34+
Disclosure policy and Safe Harbor for the Interchain Stack, and the teams and
35+
infrastructure it supports, and it supersedes previous security policies that
36+
have been used in the past by individual teams and projects with targets in
37+
scope of the program.
38+
39+
[hackerone-bug]: https://hackerone.com/cosmos?type=team
40+
[hackerone-policy]: https://hackerone.com/cosmos?type=team&view_policy=true

0 commit comments

Comments
 (0)