Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Cloud Security Alliance

Vulnerability disclosure program on security.txt cloudsecurityalliance.org

Accepting reports security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
9
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Pays cash
No We are a non-profit organization and do not provide monetary rewards for vulnerability reports.
Hall of fame
No We do not maintain a separate acknowledgments page.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

9 assets you may test, 4 excluded.

Source code 5

  • https://github.com/CloudSecurityAlliance/
  • https://github.com/CloudSecurityAlliance-Chatbots
  • https://github.com/CloudSecurityAlliance-DataSets
  • https://github.com/modelcontextprotocol-security/
  • https://github.com/RiskRubric/

Domains 4

  • cloudsecurityalliance.org
  • csachapter.io
  • star.watch
  • webfinger.io
Out of scope (4)
  • cloudsecurityalliance.auth0.com
  • Any "best practices" for SPF/DKIM/DMARC/BIMI/TLS/HTTP HEADERS/MTA-STS
  • Any wordpress.com related items like "disabling xmlrpc.php"
  • cloudsecurityalliance.auth0.com/*

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Cloud Security Alliance's policy. "We" in these lines means the program, not this site.

While testing

  • These are hosted on third-party platforms — please report any vulnerabilities in those services directly to the respective platform provider.
  • Report vulnerabilities through the Security tab of the affected repository.
  • Please note that software that is pre version 1.0.0 is not eligible for CVE coverage as per our CSA Product Security policy.

Not accepted

  • General model behavioral observations without a specific security impact are not in scope.
  • Any "best practices" for SPF/DKIM/DMARC/BIMI/TLS/HTTP HEADERS/MTA-STS
  • Any wordpress.com related items like "disabling xmlrpc.php"

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 12 Nov 2026. Last checked 2 hours ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.