Question 480
After completing this practical task on a test RHEL10 instance: A private SSH key is world-readable, causing security risk and sometimes authentication refusal. Which operational safeguard helps keep the result correct and safe?
Explanation
Correct Answer
Provision and rotate private keys under managed mode and ownership controls. This guards against recurrence of: SSH private credentials require protected ownership and permissions distinct from public authorized keys. Confirm the lab's final state by: `stat` reports expected modes and the user's valid SSH connection works without insecure key exposure.
Incorrect Answers
Check active zone, SELinux port permission and service listener together. That control is best suited to a separate scenario: An application uses a nonstandard TCP port and a student opens it in firewalld but forgets the active zone. It is not the best safeguard for the current mechanism: SSH private credentials require protected ownership and permissions distinct from public authorized keys.
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: SSH private credentials require protected ownership and permissions distinct from public authorized keys.
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: SSH private credentials require protected ownership and permissions distinct from public authorized keys.