Permissions and users · Lesson 14 of 33 · 7 minutes

Sensitive path audit

Find and inspect sensitive configuration paths.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Find ssh paths
Run find /etc -name ssh.
Hint & worked example
Search directory trees by criteria rather than relying on one shallow listing.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
find /etc -name ssh
```
Remember: Quote wildcard patterns so find receives them instead of the shell expanding them first.
2
Inspect ssh config
Run stat /etc/ssh/sshd_config.
Hint & worked example
Inspect a file or directory metadata record, including ownership, permissions, and size.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
stat /etc/ssh/sshd_config
```
Remember: Metadata and file contents answer different questions.
3
Inspect sudoers
Run stat /etc/sudoers.d/learners.
Hint & worked example
Inspect a file or directory metadata record, including ownership, permissions, and size.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
stat /etc/sudoers.d/learners
```
Remember: Metadata and file contents answer different questions.

Understand the pattern

Security review starts with knowing where sensitive files live.

find: Search directory trees by criteria rather than relying on one shallow listing.
Quote wildcard patterns so find receives them instead of the shell expanding them first.
stat: Inspect a file or directory metadata record, including ownership, permissions, and size.
Metadata and file contents answer different questions.

Worked example and expected result

$ find /etc -name ssh

/etc/ssh
/etc/ssh/sshd_config
/etc/systemd/system/ssh.service

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

$ stat /etc/ssh/sshd_config

Path: /etc/ssh/sshd_config
Type: file
Mode: -rw-------
Owner: root
Group: root
Size: 69 bytes

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

$ stat /etc/sudoers.d/learners

Path: /etc/sudoers.d/learners
Type: file
Mode: -r--r-----
Owner: root
Group: root
Size: 86 bytes

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 “Sensitive path audit”, which interpretation is safe?Metadata and file contents answer different questions.A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.

Apply it elsewhere

Before adapting the stat workflow from “Sensitive path audit” to another server, what should you do?Paste the training paths unchanged into production.Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Test file types Try 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

GNU Coreutils manual · GNU Bash manual