Permissions and users · Lesson 33 of 33 · 8 minutes

Least privilege bridge

Checkpoint ownership, group assignment, and minimum useful modes.

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
Create the protected note
Run touch lab/least-privilege.txt.
Hint & worked example
Create an empty file when absent, or update timestamps without truncating an existing file.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
touch lab/least-privilege.txt
```
Remember: touch is not a way to empty a file that already has content.
2
Set the intended owner
Run sudo chown learner:learners lab/least-privilege.txt.
Hint & worked example
Change ownership; on a real Linux system changing the file owner normally requires elevated privilege.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
sudo chown learner:learners lab/least-privilege.txt
```
Remember: Ownership and mode bits are separate controls; inspect both.
3
Set the minimum useful mode
Run chmod 640 lab/least-privilege.txt.
Hint & worked example
Change permissions using an octal mode or a symbolic adjustment. Each rwx bit belongs to owner, group, or other.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
chmod 640 lab/least-privilege.txt
```
Remember: Do not use 777 as a blanket fix. Grant the smallest access needed.
4
Verify the final metadata
Run stat lab/least-privilege.txt.
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 lab/least-privilege.txt
```
Remember: Metadata and file contents answer different questions.

Understand the pattern

Applying least privilege to a new operator note helps operators explain what they know before they change anything.

touch: Create an empty file when absent, or update timestamps without truncating an existing file.
touch is not a way to empty a file that already has content.
chown: Change ownership; on a real Linux system changing the file owner normally requires elevated privilege.
Ownership and mode bits are separate controls; inspect both.
chmod: Change permissions using an octal mode or a symbolic adjustment. Each rwx bit belongs to owner, group, or other.
Do not use 777 as a blanket fix. Grant the smallest access needed.
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

$ touch lab/least-privilege.txt

(no output; exit 0)

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

$ sudo chown learner:learners lab/least-privilege.txt

(no output; exit 0)

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

$ chmod 640 lab/least-privilege.txt

(no output; exit 0)

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

$ stat lab/least-privilege.txt

Path: /home/learner/lab/least-privilege.txt
Type: file
Mode: -rw-r-----
Owner: learner
Group: learners
Size: 0 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 “Least privilege bridge”, which interpretation is safe?Ownership and mode bits are separate controls; inspect both.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 chown workflow from “Least privilege bridge” 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.

Review this course 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

01Service account ownershipRelate a web file owner to the identity used by its service.Practice

GNU Coreutils manual · GNU Bash manual