Security administration · Lesson 34 of 35 · 8 minutes

Privileged boundary review

Read the simulated sudo boundary and verify the target service action is inspection-only.

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
Read the learner sudo rule
Run sudo cat /etc/sudoers.d/learners.
Hint & worked example
Read one or more files to standard output without editing their contents.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
sudo cat /etc/sudoers.d/learners
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.
2
Use the allowed inspection action
Run sudo systemctl status nginx.
Hint & worked example
Inspect or change a simulated systemd service. Status, active state, and unit configuration reveal different evidence.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
sudo systemctl status nginx
```
Remember: A service can be active while an application endpoint is unhealthy; verify both layers.
3
Read the inspected unit
Run systemctl cat nginx.
Hint & worked example
Inspect or change a simulated systemd service. Status, active state, and unit configuration reveal different evidence.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
systemctl cat nginx
```
Remember: A service can be active while an application endpoint is unhealthy; verify both layers.

Understand the pattern

Recognizing a narrow privileged command boundary helps operators explain what they know before they change anything.

cat: Read one or more files to standard output without editing their contents.
Reading a source file should precede changing it; avoid printing real secrets.
systemctl: Inspect or change a simulated systemd service. Status, active state, and unit configuration reveal different evidence.
A service can be active while an application endpoint is unhealthy; verify both layers.

Worked example and expected result

$ sudo cat /etc/sudoers.d/learners

learner ALL=(root) NOPASSWD: /usr/bin/systemctl status *
# fake readonly training rule

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

$ sudo systemctl status nginx

sudo accepted in simulation only.
nginx.service - simulated nginx
   Loaded: loaded
   Active: active
   Notes: serving the simulated static learn site

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

$ systemctl cat nginx

[Unit]
Description=fake nginx
[Service]
ExecStart=/usr/sbin/nginx -g 'daemon off;'

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 “Privileged boundary review”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.A service can be active while an application endpoint is unhealthy; verify both layers.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Security administration bridge 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