evidence-hygiene

To sanitize a HAR file for a bug bounty report, you use provided scripts to strip sensitive headers, session cookies, and authorization tokens. This redaction process ensures your network archives comply with privacy standards before attachment.

You must redact session cookies, CSRF values, authorization tokens, and personally identifiable information from bug bounty evidence. The skill provides guidelines on what to mask versus what to keep visible to prove impact without violating user privacy.

HAR sanitization works by running automated workflows that strip sensitive headers and tokens from network archives. This ensures any captured session data or private user information is masked before the HAR file is shared.

Yes, you need jq installed to use the provided sanitization scripts for HAR file processing. This dependency is required to parse the network archives and strip sensitive headers effectively.

Yes, you can use this skill to mask session tokens and authorization headers in security research screenshots. It provides standardized methods to apply PII black-bar discipline and ensure your artifacts remain secure.

The best way to prevent session data leakage in security reports is to apply strict redaction protocols to artifacts. This skill sanitizes screenshots and HAR files, preventing accidental leakage of sensitive session data during responsible disclosure.