Security administration · Lesson 1 of 35 · 12 minutes

Security admin

Practice security habits: identity, logs, firewall rules, and simulated sudo.

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
Check identity
Run whoami and id.
Hint & worked example
Print the effective user name. Inspect user identity and group membership.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
whoami
id
```
Remember: An elevated command can run with a different effective identity from the normal shell. A file group is useful only when the acting user belongs to it or has an applicable override.
2
Inspect firewall
Run ufw status.
Hint & worked example
Inspect or adjust the training firewall rule list. No real firewall changes occur.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ufw status
```
Remember: Firewall rules should be scoped and reviewed; simulator access is not a production change approval.
3
Try simulated sudo
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.

Understand the pattern

Security work starts by confirming who you are and what you can affect.

whoami: Print the effective user name.
An elevated command can run with a different effective identity from the normal shell.
id: Inspect user identity and group membership.
A file group is useful only when the acting user belongs to it or has an applicable override.
ufw: Inspect or adjust the training firewall rule list. No real firewall changes occur.
Firewall rules should be scoped and reviewed; simulator access is not a production change approval.
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

$ whoami

learner

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

$ id

uid=1000(learner) gid=1000(learners) groups=1000(learners),27(sudo-readonly)

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

$ ufw status

Status: active
- allow 22/tcp
- allow 80/tcp
- allow 443/tcp
- deny 23/tcp

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.

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 “Security admin”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.Firewall rules should be scoped and reviewed; simulator access is not a production change approval.A command appearing in history proves it completed successfully.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: SSH hardening 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