Software quality, testing, and safe telemetry Test your software without copying secrets into logs. Reviewed: 2026-10-03 Source-based teaching example · Fictional data Narration: Microsoft Mark · locally synthesized 00:00:00.000 — What you will learn Test your software without copying secrets into logs. Visual description: Test your software without copying secrets into logs. 00:00:06.458 — The idea Decide which fields a log may contain. Build the log from those allowed fields. Removing secrets after capturing the full content can already cross the intended boundary. Visual description: Decide which fields a log may contain. Build the log from those allowed fields. Removing secrets after capturing the full content can already cross the intended boundary. 00:00:20.417 — One useful term Allowlist. An explicit list of permitted fields, actions or resources. Visual description: An explicit list of permitted fields, actions or resources. 00:00:29.167 — A worked example A request includes a name, email, secret token and task type. The safe log keeps the request ID, task type, status and elapsed time. Tests check that seeded secrets never appear. Visual description: A request includes a name, email, secret token and task type. The safe log keeps the request ID, task type, status and elapsed time. Tests check that seeded secrets never appear. 00:00:45.708 — Your turn to think Is logging the whole request and redacting it later the same boundary? Pause and decide before continuing. Visual description: Is logging the whole request and redacting it later the same boundary? Pause the video if you need more time. 00:01:03.125 — Why this answer works No. The sensitive content was already captured. Fix the logging entry point and retest every affected path. Visual description: No. The sensitive content was already captured. Fix the logging entry point and retest every affected path. 00:01:13.917 — Check 1 Build logs from allowed fields only. Visual description: Build logs from allowed fields only. 00:01:19.125 — Check 2 Test several secret formats. Visual description: Test several secret formats. 00:01:24.250 — Check 3 Check all paths after a logging change. Visual description: Check all paths after a logging change. 00:01:29.750 — Now try a different case Open the lesson and try its different practice case. Use every check in the full task. Watching alone does not mark the lesson complete. Visual description: Open the lesson Try the new case Check and revise The full task and its requirements are in the linked lesson.