对比：HAR 脱敏器 vs 日志脱敏工具
决策框架：Choose the right redaction workflow for browser network captures, application logs, headers, cookies, and incident snippets.
使用场景：Use this comparison before sharing evidence in an issue, ticket, vendor portal, or chat thread.
决策因素
| 因素 | Byteflow | 另一种选择 | 实践说明 |
|---|---|---|---|
| Input shape（决策因素） | Byteflow 本地流程：HAR 脱敏器 parses browser capture structure and redacts sensitive network fields defensively. | 另一种选择：日志脱敏工具 scans text for common secrets, PII patterns, tokens, and identifiers. | 实践说明：Use the parser that understands your evidence format. |
| Redaction scope（决策因素） | Byteflow 本地流程：HAR workflows can target headers, cookies, query strings, request bodies, and response bodies. | 另一种选择：Log workflows can target bearer tokens, keys, emails, IPs, paths, and repeated secret-like strings. | 实践说明：Structured captures and free text fail in different ways. |
| Review step（决策因素） | Byteflow 本地流程：Export only after comparing sanitized output and confirming that URLs and bodies are safe to share. | 另一种选择：Diff scrubbed logs against the original so expected context remains while secrets are removed. | 实践说明：Automated redaction is a first pass, not a legal or security approval. |
实践判断：Use HAR 脱敏器 for browser evidence
实践判断：Choose the HAR workflow when the source is a browser export or network troubleshooting capture with request and response metadata.
实践判断：Use 日志脱敏工具 for text evidence
实践判断：Choose the log workflow when the source is application output, shell logs, stack traces, CI logs, or pasted incident notes.
此工作流中的工具
直接打开聚焦工具。这些链接使用与搜索和 sitemap 生成相同的 registry 数据。
信任检查
隐私边界：HAR files and logs commonly contain credentials, cookies, account IDs, full URLs, and private request or response bodies. Keep sanitization local and review before export.
隐私与信任中心常见问题
常见问题：Can I sanitize a HAR file with a plain text scrubber?
回答：You can catch some patterns, but a HAR-aware sanitizer is safer because it understands headers, cookies, URLs, and body fields.
常见问题：Is sanitized output automatically safe to post publicly?
回答：No. Review the result, check domain-specific identifiers, and share the smallest useful excerpt.