ORBITALWAKE — BEFORE YOU SHARE A HAR FILE
Documentation-based guide. Sources checked 25 October 2026.

Use these prompts while reviewing the actual file you intend to share.
Completing this list does not certify that a file is safe.

[ ] The debugging question and necessary scope are clear.
[ ] The capture is short and relevant to the issue.
[ ] The actual file has been reviewed for sensitive values.
[ ] Edits are documented and useful context is preserved.
[ ] The intended recipient, case, and sharing channel are confirmed.

Review URLs, query values, headers, request bodies, response content,
and application-specific customer or business information.

Before using a viewer or sanitizer, check whether it sends the file to
another service. Confirm that any such destination is authorized for the data.
Keep original and edited copies in an approved location with access limited
to authorized people.

If you are unsure whether information may be shared, ask the data owner
or your security team before attaching the file.

Chrome's sanitized export excludes sensitive information such as
Cookie, Set-Cookie, and Authorization headers. It is not a guarantee
that every value relevant to your application has been removed.

Primary references:
https://developer.chrome.com/docs/devtools/network/reference
https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html
https://docs.cloud.google.com/support/docs/capture-browser-trace

OrbitalWake is an independent security publication.