Security administration · Lesson 5 of 35 · 8 minutes

Firewall baseline

Inspect and update simulated firewall rules with caution.

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
Verbose status
Run ufw status verbose.
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 verbose
```
Remember: Firewall rules should be scoped and reviewed; simulator access is not a production change approval.
2
Allow https
Run ufw allow 443/tcp.
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 allow 443/tcp
```
Remember: Firewall rules should be scoped and reviewed; simulator access is not a production change approval.
3
Deny telnet
Run ufw deny 23/tcp.
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 deny 23/tcp
```
Remember: Firewall rules should be scoped and reviewed; simulator access is not a production change approval.

Understand the pattern

A baseline prevents duplicate or contradictory rules.

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.

Worked example and expected result

$ ufw status verbose

Status: active
Logging: on (simulated)
Default: deny incoming, allow outgoing
- allow 22/tcp
- allow 80/tcp
- allow 443/tcp
- deny 23/tcp

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

$ ufw allow 443/tcp

simulated firewall rule added: allow 443/tcp

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

$ ufw deny 23/tcp

simulated firewall rule added: deny 23/tcp

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 “Firewall baseline”, which interpretation is safe?Firewall rules should be scoped and reviewed; simulator access is not a production change approval.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 ufw workflow from “Firewall baseline” 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: SSH config review 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