Skip to content

docs: make bounty forfeiture forward-looking, and fix the level 2 trigger #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aljo242 merged 3 commits into from
Oct 2, 2026
Merged

docs: make bounty forfeiture forward-looking, and fix the level 2 trigger #22

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0c5fab8
docs: make bounty forfeiture forward-looking, and fix the level 2 tri…
aljo242 Oct 1, 2026
6429e32
docs: let severity escalate a first instance to suspension, not only …
aljo242 Oct 2, 2026
3f934dd
docs: say the earned-bounty rule once, for all three levels
aljo242 Oct 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 13 additions & 12 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -236,24 +236,25 @@ conflict.

**1. Warning.** A first instance of publishing ahead of the disclosure date
results in a written warning from the security response team, recorded for the
purpose of judging later instances. Where the reporter was eligible for a
bounty, the report also becomes ineligible.
purpose of judging later instances.

**2. Suspension.** A repeat instance, or publishing something an attacker can
act on immediately, makes the report ineligible and removes the reporter from
any private notification or pre-disclosure list for 3 months. We continue to
accept and act on their vulnerability reports during that period, but those
reports are not eligible for a bounty.
**2. Suspension.** A repeat instance removes the reporter from any private
notification or pre-disclosure list for 3 months. We continue to accept and act
Comment on lines +241 to +242

@greptile-apps greptile-apps Bot Oct 1, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 First-instance suspension is unclear. Level 2 now names only a repeat instance as its trigger, while the policy below says severity can determine the level even for a first instance. That leaves the response team and reporters without a clear rule for a serious first disclosure that warrants suspension but not a permanent block. Please clarify whether severity can trigger a first-instance suspension.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

on their vulnerability reports during that period, but those reports are not
eligible for a bounty.

**3. Permanent block.** A pattern of improper disclosure, or publishing with
intent to cause harm, results in a permanent block from the Cosmos organization
and from any pre-disclosure list. The report is ineligible for a bounty. We
still receive security reports from them, because closing that channel would put
users at risk, but they take no further part in the project.
and from any pre-disclosure list, and no further reports from them are eligible
for a bounty. We still receive security reports from them, because closing that
channel would put users at risk, but they take no further part in the project.

At every level, a bounty already earned on the report that prompted the action
is still paid. What changes is eligibility going forward.

Severity determines the level rather than the number of prior instances, so a
sufficiently serious first instance may result in a permanent block without
prior steps.
sufficiently serious first instance may result in a suspension or a permanent
block without prior steps.

The security response team decides these actions. To appeal one, write to
[conduct@cosmos.network](mailto:conduct@cosmos.network), which is independent of
Expand Down
Loading