Watch the explanation. Practice the skill.
Software quality, testing, and safe telemetry
Test your software without copying secrets into logs.
Captions appear here during playback.
Software quality, testing, and safe telemetry
Test your software without copying secrets into logs.
Video playback is unavailable. Read the descriptive transcript below, go directly to practice, or open the video file.
Source-based teaching example · Fictional data · Reviewed 2026-10-03. Microsoft Mark · locally synthesized. On a small screen, use fullscreen for diagram details or read the transcript.
Read the descriptive transcript
0:00 · What you will learn
Test your software without copying secrets into logs.
What appears on screen
Test your software without copying secrets into logs.
0:06 · 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.
What appears on screen
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.
0:20 · One useful term
Allowlist. An explicit list of permitted fields, actions or resources.
What appears on screen
An explicit list of permitted fields, actions or resources.
0:29 · 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.
What appears on screen
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.
0:45 · Your turn to think
Is logging the whole request and redacting it later the same boundary? Pause and decide before continuing.
What appears on screen
Is logging the whole request and redacting it later the same boundary? Pause the video if you need more time.
1:03 · Why this answer works
No. The sensitive content was already captured. Fix the logging entry point and retest every affected path.
What appears on screen
No. The sensitive content was already captured. Fix the logging entry point and retest every affected path.
1:13 · Check 1
Build logs from allowed fields only.
What appears on screen
Build logs from allowed fields only.
1:19 · Check 2
Test several secret formats.
What appears on screen
Test several secret formats.
1:24 · Check 3
Check all paths after a logging change.
What appears on screen
Check all paths after a logging change.
1:29 · 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.
What appears on screen
Open the lesson Try the new case Check and revise The full task and its requirements are in the linked lesson.
Watching explains the example. Complete the lesson practice to check what you can do. Explore all visual lessons →