evidence-hygiene

Redact session cookies, PII, and metadata from bug-bounty PoC artifacts.

3|1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/EntroVyx/hermes-agent-offsec --skill evidence-hygiene-entrovyx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evidence-hygiene
Source: https://github.com/EntroVyx/hermes-agent-offsec/tree/main/skills/offsec/redteam/evidence-hygiene
Command: npx skills add https://github.com/EntroVyx/hermes-agent-offsec --skill evidence-hygiene-entrovyx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the accidental leakage of sensitive session cookies, PII, and internal trace data during the bug-bounty submission process, ensuring your evidence is professional and secure.

Core Features & Use Cases

  • Cookie Redaction Protocol: Standardized methods to mask session tokens and authorization headers in screenshots and HAR files.
  • PII Black-Bar Discipline: Guidelines for redacting sensitive user data while maintaining the integrity of the vulnerability proof.
  • HAR Sanitization: Automated jq-based filtering to strip sensitive headers from network traffic logs before submission.

Quick Start

Use the evidence-hygiene skill to sanitize the captured evidence for my current bug-bounty report.

Frequently Asked Questions about evidence-hygiene

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

FAQPage Schema
How do I redact session cookies and PII from bug-bounty evidence before reporting?

HAR sanitization strips sensitive headers from network traffic logs using automated jq-based filtering to remove session cookies, authorization tokens, and internal trace data before submission to security platforms for responsible disclosure.

What is the best way to sanitize PoC artifacts for responsible disclosure compliance?

Sanitizing PoC artifacts for responsible disclosure compliance involves applying strict redaction protocols to cross-account data, authentication tokens, and internal metadata across screenshots, HAR files, and terminal transcripts to ensure professional, secure submissions.

Does evidence-hygiene support automated redaction of sensitive headers in network traffic logs?

Evidence-hygiene supports automated HAR sanitization using jq-based filtering to strip sensitive headers from network traffic logs, ensuring cross-account data and authentication tokens are removed before bug-bounty submission.

Can I use this redaction framework for terminal transcripts and screenshots, or is it only for HAR files?

This redaction framework applies to terminal transcripts and screenshots alongside HAR files, providing PII black-bar discipline and cookie redaction protocols to mask sensitive session tokens and user data across multiple artifact formats.

When should I not use automated sanitization for bug-bounty report evidence?

Automated HAR sanitization should be supplemented with manual PII black-bar discipline when screenshots or terminal transcripts contain complex cross-account data, ensuring the vulnerability proof integrity remains intact while removing sensitive authentication tokens.