Skip to content

Improve security reporting guidelines in SECURITY.md #4823

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
lukem-ts wants to merge 1 commit into
base: main
Choose a base branch
from
+12 −1
Open

Improve security reporting guidelines in SECURITY.md #4823

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
13 changes: 12 additions & 1 deletion SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,15 @@
Please report security issues to security@trufflesec.com and include `trufflehog` in the subject line. If your vulnerability involves SSRF or outbound requests, please see our policy for that specific class of vulnerability below.
Please report security issues to security@trufflesec.com and include `trufflehog` in the subject line.

## Reporting Guidelines

Truffle Security values the work of independent security researchers. To help us triage and remediate issues efficiently, please include the following in your report:

- **Summary** - brief description of the issue.
- **Proof of Concept** - steps to reproduce, including any relevant code references.
- **Impact** - the realistic impact this has on TruffleHog users.
- **Suggested Fix** (optional) - any recommendations on how to fix the issue.

If your vulnerability involves SSRF or outbound requests, please see our policy for that specific class of vulnerability below.

## Blind SSRF & Outbound Request Policy
Truffle Security treats blind SSRF (the ability to induce outbound requests without data retrieval) as a hardening opportunity rather than a vulnerability. We do not issue CVEs or formal advisories for reports showing outbound interactions unless they demonstrate a tangible security risk to users.
Expand Down
Loading