About this interactive
On a Linux host with SELinux, every access is checked twice. First come the ordinary Linux permissions, which are discretionary: a file's owner decides who may read or write it. Then comes SELinux, which is mandatory: a central policy, written by IT or security, decides what each process may reach, and no owner can change it from her own files.
SELinux can only narrow what the Linux permissions allow. If the permissions refuse an access, it fails there, and SELinux is never asked. If the permissions allow it, the SELinux mode decides what happens to anything the policy forbids. Enforcing: it is blocked, even for a service running as root. Permissive: it goes ahead and is written to the log, which makes permissive a dry run of what enforcing will block. Disabled: SELinux checks nothing and logs nothing, and the Linux permissions decide alone.
To predict an outcome, take the Linux permissions first, then the policy, then the mode.
About TechKnowSurge
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →