Question 560
After completing this practical task on a disposable RHEL10 training node: A shell session creates files with default modes exposing group-readable secrets to unrelated users. Which operational safeguard helps keep the result correct and safe?
Explanation
Correct Answer
Set a restrictive umask in service startup or trusted shell policy for secret handling. This guards against recurrence of: A umask subtracts permission bits from default requested modes at object creation. Confirm the lab's final state by: A normal new file is mode `600` or more restrictive and a new directory is mode `700` or more restrictive.
Incorrect Answers
Use narrowly timed diagnostics and restore enforcing mode after analyzing denial logs. That control is best suited to a separate scenario: An administrator temporarily changes SELinux to permissive mode for diagnostics and believes it will remain so after reboot. It is not the best safeguard for the current mechanism: A umask subtracts permission bits from default requested modes at object creation.
Check runtime and configured SELinux modes after policy changes. That control is best suited to a separate scenario: A training VM must boot with SELinux enforcing but `/etc/selinux/config` is set to permissive. It is not the best safeguard for the current mechanism: A umask subtracts permission bits from default requested modes at object creation.
Provision and rotate private keys under managed mode and ownership controls. That control is best suited to a separate scenario: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. It is not the best safeguard for the current mechanism: A umask subtracts permission bits from default requested modes at object creation.