What problem does it solve?
Evidence-capture and PoC-redaction discipline for bug-bounty submissions: cookie redaction protocol (which fields to mask, Preview annotation / Burp panel hiding / DevTools workflow), PII black-bar discipline (what to mask in other-user data — names, emails, phones, faces — vs what is safe to leave — usernames, trace IDs, request bodies), HAR file sanitization (jq filters for Cookie/Set-Cookie/Authorization headers), Burp Repeater/Intruder screenshot hygiene (hide request body, show only Results table for rate-limit attacks), Chrome DevTools Console PoC patterns (credentials include so cookies are not echoed, labeled console.log), screenshot capture order, filename conventions, post-submission rotation hygiene. Use BEFORE any PoC screenshot, BEFORE attaching a HAR, or whenever preparing evidence with session cookies or other-user PII. Pairs with bugcrowd-reporting and report-writing.
Core Features & Use Cases
- Cookie redaction protocol and PII masking to prevent leakage of sensitive data in artifacts.
- HAR sanitization and structured evidence preparation using jq-driven transforms.
- Screenshot hygiene and evidence-handling guidance for bug-bounty submissions.
- DevTools, Burp, and Repeater best practices to minimize accidental exposure while preserving triage utility.
- End-to-end workflow guidance pairing with report-writing and bugcrowd-reporting.
Quick Start
Before capturing any PoC screenshot or HAR, apply the evidence-hygiene checklist to redact sensitive data.
