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 1993822 - content_rule_audit_basic_configuration enforces using default buffer size (8192) for audit, which isn't always suitable on busy systems [rhel-7.9.z]
Summary: content_rule_audit_basic_configuration enforces using default buffer size (81...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: scap-security-guide
Version: 7.9
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Vojtech Polasek
QA Contact: Matus Marhefka
Jan Fiala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-16 07:56 UTC by Renaud Métrich
Modified: 2024-12-20 20:42 UTC (History)
8 users (show)

Fixed In Version: scap-security-guide-0.1.63-1.el7_9
Doc Type: Enhancement
Doc Text:
.A warning message to configure Audit log buffer for large systems added to SCAP rule `audit_rules_for_ospp` The SCAP rule `xccdf_org.ssgproject.content_rule_audit_rules_for_ospp` now displays a performance warning on large systems where the Audit log buffer configured by this rule might be too small, and can override the custom value. The warning also describes the process to configure a larger Audit log buffer. With the release of the link:https://access.redhat.com/errata/RHBA-2022:6576[RHBA-2022:6576] advisory, you can keep large systems compliant and correctly set their Audit log buffer.
Clone Of:
Environment:
Last Closed: 2022-09-20 09:07:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-93561 0 None None None 2021-08-16 07:56:54 UTC

Description Renaud Métrich 2021-08-16 07:56:32 UTC 
Description of problem:

The content_rule_audit_basic_configuration rule enforces having 10-basic-config.rules be the default configuration file, which sets internally the buffer to 8192:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
[...]
## Increase the buffers to survive stress events.
## Make this bigger for busy systems
-b 8192
[...]
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

If the customer changes the value, the rule will fail. In theory the check should only make sure that the buffer is larger or equal to 8192.


Version-Release number of selected component (if applicable):

scap-security-guide-1.54-7.el7_9

How reproducible:

Always

Steps to Reproduce:
1. Modify /etc/audit/rules.d/10-basic-config.rules to increase the buffer to 16384
2. Execute xccdf_org.ssgproject.content_rule_audit_basic_configuration rule

Actual results:

Fails

Expected results:

Pass

Additional info:

Workaround is to create his own 99-custom.rules or similar file that modifies the buffer size
Comment 3 Vojtech Polasek 2021-08-30 12:56:47 UTC 
Hello,
thank you for raising this issue. This particular rule treats the file as one huge blob, so it can't be easily customized. The idea behind the rule is to match files provided by Audit package in /usr/share/audit/sample-rules.
Therefore, if we were about to add some explaining comment, I believe this would need to be coordinated with Audit developers as well, so that copying over the sample file does not make the rule fail.
However, I think we could add the explanation either to the rule description or into the rule warning section related to performance, I like the later approach more. This would bee modification only to the SCAP content. It would be visible in the HTML report and in the HTML guides.
Would this be feasible?
Comment 4 Renaud Métrich 2021-08-30 16:30:08 UTC 
Yes sure, as long as there is something that would help the customers to understand what's wrong, I'll be happy.
Comment 5 Vojtech Polasek 2021-09-02 13:14:51 UTC 
I have confirmed that the solution works. However, be ware that files starting with letters are processed even after files which start with numbers.
So if you have file:
99-my_config.rules with your custom configuration
and there will be file
audit.rules  with a different -b
it will overide your custom configuration.
Comment 7 Peter Vreman 2021-11-03 15:58:38 UTC 
Confirming also that it works for me, i now define the '-b <value>' in my 40-local.rules file and it gets applied
Having a better documentation guidance here on the idea of using the standard files verbatim and then have local customizations in a file like 40-local.rules or 90-my_config.rules is ok. It shall be at least before 99-finalize that is also part of the standard set of audit example files.
Comment 8 Vojtech Polasek 2021-11-26 13:15:54 UTC 
I believe I fixed it upstream, there is a new warning section:
https://github.com/ComplianceAsCode/content/pull/7909
Comment 31 Vojtech Polasek 2022-08-09 07:35:54 UTC 
Fixed upstream: https://github.com/ComplianceAsCode/content/pull/9303
Comment 46 errata-xmlrpc 2022-09-20 09:07:04 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (scap-security-guide bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:6576
Note You need to log in before you can comment on or make changes to this bug.