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.
Bug 1392683 - SCAP Security Guide remediation fail - CCE-26952-2 - Configure Periodic Execution of AIDE
Summary: SCAP Security Guide remediation fail - CCE-26952-2 - Configure Periodic Execu...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: scap-security-guide
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Watson Yuuma Sato
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-08 02:27 UTC by Shawn Wells
Modified: 2018-06-01 04:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-23 21:07:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Shawn Wells 2016-11-08 02:27:56 UTC 
When installing RHEL 7.3 using SCAP security profile, "CCE-26952-2 - Configure Periodic Execution of AIDE" fails to be set.
Comment 2 Marek Haicman 2018-03-23 21:07:45 UTC 
This bug is fixed in RHEL7.5 beta.

OLD scap-security-guide-0.1.33-6.el7.noarch:
[dahaic@dhcp-24-168 tests]$ sudo ./test_suite.py rule --hypervisor qemu:///system --domain ssg-test-suite --datastream ./ssg-0.1.33-6-ds.xml --xccdf-id scap_org.open-scap_cref_ssg-rhel7-xccdf-1.2.xml rule_aide_periodic_cron_checking
Setting console output to log level INFO
...
INFO - xccdf_org.ssgproject.content_rule_aide_periodic_cron_checking
INFO - Script not_in_cron.fail.sh using profile xccdf_org.ssgproject.content_profile_C2S OK
ERROR - Scan has exited with return code 2, instead of expected 0 during stage remediation
ERROR - The remediation failed for rule 'xccdf_org.ssgproject.content_rule_aide_periodic_cron_checking'.
INFO - All snapshots reverted successfully

NEW scap-security-guide-0.1.36-7.el7.noarch:
[dahaic@dhcp-24-168 tests]$ sudo ./test_suite.py rule --hypervisor qemu:///system --domain ssg-test-suite --datastream ./ssg-0.1.36-7-ds.xml --xccdf-id scap_org.open-scap_cref_ssg-rhel7-xccdf-1.2.xml rule_aide_periodic_cron_checking
Setting console output to log level INFO
...
INFO - xccdf_org.ssgproject.content_rule_aide_periodic_cron_checking
INFO - Script not_in_cron.fail.sh using profile xccdf_org.ssgproject.content_profile_C2S OK
INFO - All snapshots reverted successfully
Comment 3 cezar abellera 2018-06-01 04:28:26 UTC 
Bug is still occurring for both NIST and STIG profiles in the RHEL7.5 release.

Running scan report using scap-security-guide-0.1.36-9.el7.5.noarch and for remediation SCAP Security Guide 0.1.39 version.

Have to add entry on remediation task by adding cron_file: /etc/crontab
as it creates the crontab entry but not updating the /etc/crontab file.
Note You need to log in before you can comment on or make changes to this bug.