What problem does it solve?
Bug-bounty submissions often inadvertently leak cookies, PII, or internal identifiers in evidence such as screenshots, HAR files, and logs. This Skill defines a disciplined hygiene workflow to ensure that all artifacts are sanitized before submission, reducing leakage risk and helping maintain responsible-disclosure standards.
Core Features & Use Cases
- Cookie redaction protocol: masks session cookies, CSRF tokens, Authorization headers, and Set-Cookie values while leaving triager-useful metadata intact.
- HAR sanitization: provides jq-based rules to redact sensitive headers and cookies from HAR files, plus optional victim-PII masking when cross-account data is captured.
- PII masking guidelines: clear rules for redacting names, emails, phones, and other user data while preserving enough data for verification.
- Evidence hygiene workflow: guidance for screenshots, Har captures, and report bodies across Bugcrowd, Immunefi, and similar platforms.
- Use Case: a researcher prepares a sanitized 5-shot PoC ready for submission without exposing credentials.
Quick Start
Review the evidence-hygiene guidelines and apply cookie and PII redaction, HAR sanitization, and reporting hygiene to all bug-bounty submissions.