Hide Forgot
Description of problem: Some rules fail because of ordering in benchmark or because of dependency on another rule. Example of a problem with ordering: There are 2 rules in a benchmark ordered in the following way: 1. "Enable foo service" 2. "Install package foo" If both rules are asserted as fail openscap will remediate them with result: 1: error 2: fixed The rule remediation #1 will result in error because service foo is not yet installed on the system and it will be installed in the rule remediation #2 which will result in fixed. Also additional scan will result with fail for the rule #1 and pass for the rule #2. Example of a problem with dependency: There are 2 rules in a benchmark ordered in the following way: 1. Prevent user from disabling the screen lock (tmux should not be listed in /etc/shells file) 2. Install the tmux Package The tmux package is not installed by default, therefore result of remediation will be: 1: pass 2: fixed But additional scan of the system will result in: 1: fail 2: pass This is because the remediation of the rule #2 will add tmux into the /etc/shells file which will make the rule #1 to fail. Version-Release number of selected component (if applicable): scap-security-guide-0.1.46-1.el8 How reproducible: always
PR https://github.com/ComplianceAsCode/content/pull/4900 helps with ordering problem, but it doesn't solve the dependency problem.
*** Bug 1768512 has been marked as a duplicate of this bug. ***
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.