Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
After applying ansible remediation generated from a scanned RHEL 7.5 Beta host, the contents of the root crontab are different than the pattern in the OVAL check, causing the "Configure Periodic Execution of AIDE" item to be marked as failed.
The bash remediation sets the expected values.
Version-Release number of selected component (if applicable):
scap-security-guide-0.1.36-7.el7.noarch
How reproducible:
Steps to Reproduce:
1. Scan host using C2S profile which includes the affected check
2. Generate Ansible remediation
3. Run playbook against host and rescan
Actual results:
"Configure Periodic Execution of AIDE" check marked as failed
Expected results:
Check should pass as an entry in /var/spool/cron/root exists
Additional info:
The Description of the check and the pattern in OVAL are not consistent. In the OVAL check, the scan must run every day according to this pattern:
^[0-9]*[\s]*[0-9]*[\s]*\*[\s]*\*[\s]*\*[\s]*(root|)/usr/sbin/aide[\s]*\-\-check.*$
The bash remediation creates a schedule that runs every day according to the OVAL check.
05 4 * * * root /usr/sbin/aide --check
The Description allows for "At a minimum, AIDE should be configured to run a weekly scan."
This is the schedule created by the ansible remediation but fails the OVAL check.
05 4 * * 5 root /usr/sbin/aide --check
At a minimum the ansible and bash remediation should take the same action and match the OVAL check. It should also be clear to the user that the remediation is the strictest match in the Description.