Skip to content

fix: prevent credential leakage in security-review evidence snippets #92

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
paulocesarmsf wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: prevent credential leakage in security-review evidence snippets #92

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: 3 additions & 1 deletion plugins/sentry-skills/skills/security-review/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -242,6 +242,8 @@ random.random() for token # FLAG: Security tokens need secrets module

## Output Format

**Evidence and secrets:** When including code snippets as evidence, **never reproduce actual secret values** (passwords, API keys, tokens, private keys). Redact them with placeholders (e.g. `api_key = "sk-***REDACTED***"`, `password = "[REDACTED]"`) so the report does not leak credentials.

```markdown
## Security Review: [File/Component Name]

Expand All @@ -259,7 +261,7 @@ random.random() for token # FLAG: Security tokens need secrets module
- **Impact**: [What an attacker could do]
- **Evidence**:
```python
[Vulnerable code snippet]
[Vulnerable code snippet — redact any secret values; use placeholders]
```
- **Fix**: [How to remediate]

Expand Down