docs: clarify security scope
This commit is contained in:
10
SECURITY.md
10
SECURITY.md
@@ -7,6 +7,16 @@ If you believe you've found a security issue in OpenClaw, please report it priva
|
|||||||
- Email: `steipete@gmail.com`
|
- Email: `steipete@gmail.com`
|
||||||
- What to include: reproduction steps, impact assessment, and (if possible) a minimal PoC.
|
- What to include: reproduction steps, impact assessment, and (if possible) a minimal PoC.
|
||||||
|
|
||||||
|
## Bug Bounties
|
||||||
|
|
||||||
|
OpenClaw is a labor of love. There is no bug bounty program and no budget for paid reports. Please still disclose responsibly so we can fix issues quickly.
|
||||||
|
The best way to help the project right now is by sending PRs.
|
||||||
|
|
||||||
|
## Out of Scope
|
||||||
|
|
||||||
|
- Public Internet Exposure
|
||||||
|
- Using OpenClaw in ways that the docs recommend not to
|
||||||
|
|
||||||
## Operational Guidance
|
## Operational Guidance
|
||||||
|
|
||||||
For threat model + hardening guidance (including `openclaw security audit --deep` and `--fix`), see:
|
For threat model + hardening guidance (including `openclaw security audit --deep` and `--fix`), see:
|
||||||
|
|||||||
Reference in New Issue
Block a user