A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
Permission auditing is mostly about reducing the search space. `find` can locate world-writable files, setuid binaries, writable directories, or objects owned by unexpected users. The command is only the first pass. A real review then asks whether the permission is intentional, inherited from packaging, required by a service, or dangerous in context.
Compare modes numerically when the exact bit pattern matters. `stat` gives you a reliable way to inspect ownership and mode on a specific candidate. For directories, examine both the directory itself and the permissions of relevant parents; an apparently private file can still be exposed through a traversable path.
Enumerates setuid regular files on one filesystem while suppressing permission errors. The useful habit here is to treat the command output as evidence about one system fact, not as a magical diagnosis.
Setuid binaries deserve careful handling because they execute with the file owner’s effective UID. Most are legitimate system programs. The security task is not to delete “weird” files; it is to identify unexpected privilege-bearing objects, verify provenance, and escalate only findings that make sense in the host’s actual configuration.
Locates world-writable configuration directories for targeted review. Read the result in context: the same command can be correct yet insufficient if a permission boundary, alternate configuration, or different backend changes what it reports.
Displays ownership and mode of a known privilege-relevant binary. In a production workflow, save the raw result when the observation contributes to a finding. That keeps later analysis honest and makes troubleshooting reproducible.
A practitioner’s checkpoint: compare the observed behavior with the assumption your script is about to make. If the assumption is broader than the evidence, narrow the rule. If the evidence is incomplete, report the uncertainty instead of converting it into a confident finding.
Lab discipline: stay inside the declared course environment, prefer read-only checks for learning exercises, and preserve the original output of security tools before transforming it.
Finish the lesson once you have worked through the material. This awards ★ 35 XP.