Skip to content
Clairos Learn

Security administration · Lesson 27 of 35 · 8 minutes

Log redaction note

Capture evidence without copying more than needed.

Mastery 0/3Run itExplain itApply it
learner@clairosSimulated Linux lab
learner@clairos:~ $
↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

grep
Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection.

No matches is exit status 1, which is different from a malformed invocation.

tee
Copy a stream both to a file and standard output; -a appends.

tee can overwrite a file even though the output is also visible on screen.

wc
Count input. -l counts newline characters, -w counts whitespace-delimited words, and -c counts bytes.

Text without a final newline may have fewer counted lines than visible rows.

printf
Format data deliberately, including separators and final newlines.

A format string controls output; a newline is data, not an automatic guarantee.

Worked example and expected result
$ grep denied /var/log/auth.log | tee lab/redacted-auth.txt
May 26 08:18:33 clairos-learn sshd[118]: denied password for root
May 26 08:21:44 clairos-learn sshd[141]: denied password for admin

Exit status: 0. The command completed successfully in the training fixture.

$ wc -l lab/redacted-auth.txt
2 lab/redacted-auth.txt

Exit status: 0. The command completed successfully in the training fixture.

$ printf redaction-reviewed > lab/redaction-note.txt
(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Log redaction note”, which interpretation is safe?

Apply it elsewhere

Before adapting the wc workflow from “Log redaction note” to another server, what should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Hardening header reviewTry an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

  1. 01Package security deep reviewConnect package state to recent package logs.Practice
  2. 02Hardening header reviewInspect web security header config and static API blocking.Practice
  3. 03Service exposure noteWrite a short exposure review from listener evidence.Practice