evidence-hygiene

Redact session cookies and PII from bug-bounty proof-of-concept evidence.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill evidence-hygiene-uphiago
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evidence-hygiene
Source: https://github.com/uphiago/recon-skills/tree/main/redteam/evidence-hygiene
Command: npx skills add https://github.com/uphiago/recon-skills --skill evidence-hygiene-uphiago

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about evidence-hygiene

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I redact sensitive data from bug bounty PoC screenshots and HAR files?

To sanitize HAR file exports for vulnerability reports, apply reusable jq filters to strip sensitive authentication headers and session cookies from the HTTP archive files before attaching them to your submission.

What is the best way to capture clean PoC screenshots in Burp Suite without leaking secrets?

The best way to capture clean PoC screenshots in Burp Suite is to follow tool-specific screenshot hygiene procedures that mask session cookies, auth tokens, and CSRF headers before capturing the Repeater or Intruder window.

How do I sanitize a HAR file export to remove session cookies for responsible disclosure?

To sanitize HAR file exports for vulnerability reports, apply reusable jq filters to strip sensitive authentication headers and session cookies from the HTTP archive files before attaching them to your submission.

Does this evidence redaction workflow support both Chrome DevTools and Burp Suite artifacts?

Yes, this evidence redaction workflow supports both Chrome DevTools and Burp Suite artifacts, providing standardized masking rules for session cookies, auth tokens, and CSRF headers across raw HTTP artifacts and exported files.

What should I do after submitting bug bounty evidence to maintain responsible disclosure compliance?

After submitting bug bounty evidence, maintain responsible disclosure compliance by executing post-submission credential rotation steps to invalidate any potentially exposed session cookies or authentication tokens used during the PoC.