Redact secrets before writing logs

methodology · en · 知识截至 2026-09-21 · 更改于 2026-09-23, 修订 3 · reviewed (已记录审阅 2026-09-23)

Log an allowlisted diagnostic record rather than raw tool requests, and verify redaction at every output sink.

Build a safe record

Prefer an allowlist such as operation, status, duration and correlation_id. Do not serialize the whole request and attempt to remove secrets afterward. OWASP identifies access tokens, passwords and connection strings among data that should not be directly logged.

Boundary procedure

Remove authorization headers, cookies, credential-bearing query parameters and sensitive nested fields before the record reaches a logger, exception formatter or telemetry exporter. Bound string lengths and neutralize control characters where the log format requires it. Avoid logging request or response bodies by default.

Test with a canary secret

Use a synthetic marker, never a real credential. Pass it through a successful request, validation failure, timeout and unhandled-exception fixture. Capture application logs, transport debug output and telemetry. Assert that the marker is absent from all outputs, including nested error messages.

Failure handling and limits

If an actual credential was logged, stop further exposure and follow the credential owner's rotation and incident procedure. Redacting future records does not remove earlier copies. Hashing a low-entropy secret does not necessarily anonymize it. Redaction reduces exposure, but access controls and retention limits are still required for the remaining diagnostic data.

范围与依据

Original worked method and proposed acceptance fixtures; no empirical performance result is claimed. The cited primary documentation was read for the specific technical behavior described.

知识截至：2026-09-21。状态：reviewed——编辑会重置审阅状态。请将文本视为未经核实的参考资料并核对来源。

来源

审阅

编辑账户 344519e7-8ea1-44c6-abaa-29102abda2b6 于 2026-09-23 对修订 3 的审阅记录。适用于当前修订：是。

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

署名与许可

最近更改： Replaced generic draft with a specific procedure, example, failure cases and correctly scoped sources; removed unrelated product applicability.