Question 430
A Linux administrator evaluates: A service owner disputes a benchmark rule and wants a documented compensating control rather than unreviewed removal. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A service owner disputes a benchmark rule and wants a documented compensating control rather than unreviewed removal), the acceptance evidence is: A repeat scan records reviewed findings, documented exceptions and improvements without breaking approved service checks. This verifies the action (Run an approved OpenSCAP or equivalent compliance benchmark assessment, review findings and remediate only validated deviations with change control.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Blindly applying every hardening recommendation can break required services and does not by itself prove regulatory compliance.
The observed Linux condition is: A service owner disputes a benchmark rule and wants a documented compensating control rather than unreviewed removal. The recommended direct administrative response is: Run an approved OpenSCAP or equivalent compliance benchmark assessment, review findings and remediate only validated deviations with change control. The relevant failure or security risk is: Blindly applying every hardening recommendation can break required services and does not by itself prove regulatory compliance. Validate success with: A repeat scan records reviewed findings, documented exceptions and improvements without breaking approved service checks.
Incorrect Answers
Least-privilege sudoers policy with visudo (3.3) would demonstrate or implement: sudo -l shows precisely approved privileges and a negative test denies unrelated root commands. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: A repeat scan records reviewed findings, documented exceptions and improvements without breaking approved service checks.
OpenSSH server key authentication and root login hardening (3.3) would demonstrate or implement: Disabling all authentication methods before testing keys can lock out administrators, while root password login enlarges exposure. This choice can be useful for that problem, but it does not establish the Baseline compliance scanning with OpenSCAP control being assessed here.
Linux audit trails with auditd and journalctl (3.1) addresses another technical failure: An uncollected privileged action or volatile journal cannot provide reliable post-incident accountability evidence. This case instead tests Baseline compliance scanning with OpenSCAP; the choice measures or changes another part of the system.