Log Redaction

Log redaction removes or replaces sensitive values before a record reaches a destination. Field deletion can remove an authorization token stored under a known key; text rules can replace recognized values inside messages. These rules cover different locations and cannot substitute for one another.

Apply the policy to nested fields, stack traces, parse failures, and every output branch. An input disk spool may already hold the original before a filter runs. Prefer avoiding sensitive logging at the source, and control access and retention wherever originals remain. Collector redaction does not erase copies already written elsewhere.

A test finding no sample tokens shows that the tested patterns were handled, not that all sensitive data is absent. An email replacement also removes distinctions between people; it is not stable pseudonymization. Keep useful event identity and diagnostic context without assuming redaction proves anonymity or preserves every analytical use.

Reference: Log and telemetry collection lab.