Bug 1043110 - audit rules contents not being properly detected
Summary: audit rules contents not being properly detected
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: scap-security-guide
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Dave Smith
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-14 00:22 UTC by Christopher Kachigian
Modified: 2020-11-30 14:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-30 14:58:39 UTC
Type: Bug


Attachments (Terms of Use)

Description Christopher Kachigian 2013-12-14 00:22:05 UTC
The contents of the audit.rules file isn't being properly detected.  For example the files contains -a always,exit -F arch=b64 -S chmod  -F auid>=500 -F auid!=4294967295 -k perm_mod for STIG compliance but the check doesn't detect it.

Current false positives:
Record Events that Modify the System's Mandatory Access Controls	pass
Record Events that Modify the System's Discretionary Access Controls - chmod	fail
Record Events that Modify the System's Discretionary Access Controls - chown	fail
Record Events that Modify the System's Discretionary Access Controls - fchmod	fail
Record Events that Modify the System's Discretionary Access Controls - fchmodat	fail
Record Events that Modify the System's Discretionary Access Controls - fchown	fail
Record Events that Modify the System's Discretionary Access Controls - fchownat	fail
Record Events that Modify the System's Discretionary Access Controls - fremovexattr	fail
Record Events that Modify the System's Discretionary Access Controls - fsetxattr	fail
Record Events that Modify the System's Discretionary Access Controls - lchown	fail
Record Events that Modify the System's Discretionary Access Controls - lremovexattr	fail
Record Events that Modify the System's Discretionary Access Controls - lsetxattr	fail
Record Events that Modify the System's Discretionary Access Controls - removexattr	fail
Record Events that Modify the System's Discretionary Access Controls - setxattr	fail
Ensure auditd Collects Information on the Use of Privileged Commands	fail
Ensure auditd Collects Information on Exporting to Media (successful)	fail
Ensure auditd Collects File Deletion Events by User	fail
Ensure auditd Collects System Administrator Actions	fail
Ensure auditd Collects Information on Kernel Module Loading and Unloading	fail

Comment 1 Shawn Wells 2013-12-14 02:36:32 UTC
Hey Dave, bumping this to you.... should be taken care of during the audit review. I *swear* I didn't know this was coming prior to our call today!

Comment 2 Ben Cotton 2020-11-05 16:48:47 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 3 Ben Cotton 2020-11-30 14:58:39 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.