📖 ~1 min read
Table of contents
Symptom & Impact
Security audit fails because SELinux is permissive instead of enforcing on regulated SLES 15 nodes.
Environment & Reproduction
Seen after testing windows or accidental `setenforce 0` left in place across reboots.
Root Cause Analysis
`/etc/selinux/config` is set to `SELINUX=permissive` or boot parameter `enforcing=0` persists.
Quick Triage
Check current mode with `getenforce` and `sestatus`.
Step-by-Step Diagnosis
Inspect `/etc/selinux/config` and `/proc/cmdline` for permissive overrides.

Solution – Primary Fix
Set `SELINUX=enforcing`, remove `enforcing=0` from GRUB, then reboot or `setenforce 1`.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Use SUSE Manager states to enforce mode across the fleet.
Verification & Acceptance Criteria
`getenforce` returns `Enforcing` after reboot and policy denials are logged correctly.
Rollback Plan
Drop back to permissive only during controlled debugging windows.
Prevention & Hardening
Audit SELinux state via configuration management daily.
Related Errors & Cross-Refs
Pairs with `SELinux is preventing` AVC messages once enforcing is restored.
Related tutorial: View the step-by-step tutorial for sles-15.
View all sles-15 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
SUSE SELinux quickstart and policy management notes.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.