Boss Challenge 4: Security Audit & Permissions Lockdown
Concept & Overview
AUDIT FAILURE: An internal compliance scanner raised a critical security finding: /etc/vault.conf containing sensitive credentials was deployed with permissive 777 permissions and is owned by learner instead of root.
Remediate the vulnerability immediately by changing the owner of /etc/vault.conf to root:root and locking down permissions to strict 600 (read/write for owner only).
Inspect the file with ls -l before and after running your remediation.
/etc/vault.conf to root:root and change its permissions to 600.Command Syntax Reference
| Command / Syntax | Description |
|---|---|
sudo chown root:root /etc/vault.conf | Change owner and group to root |
sudo chmod 600 /etc/vault.conf | Restrict permissions to owner read/write |
ls -l /etc/vault.conf | Inspect file permissions and ownership |
Verification Objectives
These conditions will be automatically verified when you run commands inside the interactive terminal simulator:
- ○Ensure /etc/vault.conf is owned by root
- ○Set permissions of /etc/vault.conf to 600
Ready to complete Quest 40?
Test your skills live in the browser terminal with an emulated Linux filesystem, real-time command evaluation, and instant step-by-step hints.