Question 720
After completing this practical task on a test RHEL10 instance: An administrator changes SELinux policy mode in `/etc/selinux/config` but the runtime `getenforce` output remains unchanged until the next reboot. Which operational safeguard helps keep the result correct and safe?
Explanation
Correct Answer
Record both fields in security posture checks and require a reboot verification for boot setting changes. This guards against recurrence of: Boot-time configuration and current kernel enforcement state are separate values. Confirm the lab's final state by: Current and configured SELinux modes converge to the intended approved state after reboot.
Incorrect Answers
Reapply default file contexts after moving service data into standard labeled directories. That control is best suited to a separate scenario: A protected lab directory was copied from `/home` and now has inappropriate user-home SELinux contexts under `/var/www/html`. It is not the best safeguard for the current mechanism: Boot-time configuration and current kernel enforcement state are separate values.
Test positive and negative access after SSH authorization changes. That control is best suited to a separate scenario: A server's `sshd` service is enabled but remote login fails because host key authentication was never established for the test user. It is not the best safeguard for the current mechanism: Boot-time configuration and current kernel enforcement state are separate values.
Use persistent Boolean changes only when justified and test their effects after restart. That control is best suited to a separate scenario: A trainee enables an SELinux Boolean with `setsebool` but loses the change after restart. It is not the best safeguard for the current mechanism: Boot-time configuration and current kernel enforcement state are separate values.