What problem does it solve?
This Skill eliminates the risk of accidental sensitive data leakage in bug-bounty proof-of-concept evidence, which can lead to account compromise, privacy violations, or invalidated submissions if session cookies, user PII, or internal metadata are exposed.
Core Features & Use Cases
- Cookie Redaction Protocol: Standardized masking rules for session cookies, auth tokens, and CSRF headers across DevTools, Burp Suite, and raw HTTP artifacts.
- PII Masking Discipline: Clear guidelines for redacting other-user personal information (names, emails, phone numbers) while preserving triager-useful metadata like trace IDs and endpoint details.
- HAR File Sanitization: Reusable jq filters to strip sensitive headers and cookies from exported HTTP archive files before attachment.
- Tool-Specific Screenshot Hygiene: Step-by-step guidance for capturing clean PoC screenshots in Burp Repeater/Intruder and Chrome DevTools without leaking secrets.
- Standardized Workflow: 5-step PoC capture pattern, filename conventions, and post-submission credential rotation steps to ensure consistent, professional evidence packages.
- Use Case: When submitting an IDOR bug bounty report, use this Skill to redact the victim's PII from response screenshots, sanitize exported HAR files to remove your session cookies, and follow the 5-step PoC pattern to clearly demonstrate the vulnerability without exposing sensitive data.
Quick Start
Use the evidence-hygiene skill to redact session cookies and PII from your bug-bounty PoC screenshots and sanitize exported HAR files before attaching them to a submission.