Skip to content

docs: add SECURITY.md disclosure policy and link from README #912

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

Open
messiawrq-design wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add SECURITY.md disclosure policy and link from README #912

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -203,3 +203,7 @@ We welcome contributions from developers of all skill levels! Please see our [CO
## 📄 License

This project is licensed under the ISC License. See the `LICENSE` file for details..

## 🔒 Security

Please refer to our [Security Policy](SECURITY.md) for information on supported versions, out-of-scope targets, and how to responsibly disclose a vulnerability.
41 changes: 41 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
# Security Policy

## Supported Versions

Currently, the following versions are actively maintained and receive security updates:

| Version | Supported |
| ------- | ------------------ |
| `main` | :white_check_mark: |
| Latest Tag | :white_check_mark: |
| Older Versions | :x: |

## Reporting a Vulnerability

We take security seriously. If you discover a vulnerability in RemitLend's contracts, backend, or frontend, please report it privately. **Do not create a public GitHub issue.**

### Contact Information
Please send your vulnerability reports directly to the maintainers or via our secure communication channels. If no direct security email is listed, you can reach out as a fallback via the contributor Telegram: [https://t.me/+DOylgFv1jyJlNzM0](https://t.me/+DOylgFv1jyJlNzM0) and request a secure channel for disclosure.

### Scope

**In-Scope:**
* Soroban Smart Contracts (`/contracts`)
* Backend API / Services (`/backend`)
* Frontend Client (`/frontend`)

**Out-of-Scope:**
* Third-party services, APIs, and dependencies.
* Issues requiring physical access to a user's device.
* Denial of Service (DoS) attacks.
* Phishing or social engineering.

### Disclosure Policy and SLA
* We will acknowledge receipt of your vulnerability report within **5 business days**.
* We ask for a **90-day responsible disclosure window** before any public disclosure is made by researchers.
* We will keep you updated on the progress of the fix and remediation.

### Bounties
At this time, we do not run a formal, paid bug bounty program. However, high-impact vulnerability reports may be recognized and rewarded on a discretionary basis, depending on the severity of the bug and the quality of the report.

_Note: GPG Key encryption for reports is currently unsupported but may be added in the future._