Bug 1993826
| Summary: | content_rule_audit_basic_configuration enforces using default buffer size (8192) for audit, which isn't always suitable on busy systems | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Renaud Métrich <rmetrich> |
| Component: | scap-security-guide | Assignee: | Vojtech Polasek <vpolasek> |
| Status: | CLOSED ERRATA | QA Contact: | Milan Lysonek <mlysonek> |
| Severity: | low | Docs Contact: | Khushbu Borole <kborole> |
| Priority: | low | ||
| Version: | 8.4 | CC: | ggasparb, jafiala, maburgha, matyc, mhaicman, mlysonek, wsato |
| Target Milestone: | rc | Keywords: | AutoVerified, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | scap-security-guide-0.1.60-1.el8 | Doc Type: | Enhancement |
| Doc Text: |
.SCAP rules now have a warning message to configure Audit log buffer for large systems
The SCAP rule `xccdf_org.ssgproject.content_rule_audit_basic_configuration` now displays a performance warning that suggests users of 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 this enhancement, users of large systems can stay compliant and have their Audit log buffer set correctly.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-10 14:14:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Renaud Métrich
2021-08-16 08:08:07 UTC
If you consider not changing the rule implementation to check for minimum settings instead of just comparing file contents, then please amend the 10-basic-config.rules template to tell customers not to modify the setting in that file but create another file alphanumerically sorted after this file that contains the custom setting, something like this: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- [...] ## Increase the buffers to survive stress events. ## Make this bigger for busy systems ## Don't modify the below value but create a file alphanumerically higher than ## "10-basic-config.rules" redefining the value, e.g. "99-custom-config.rules" -b 8192 [...] -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- 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? Fixed upstream: https://github.com/ComplianceAsCode/content/pull/7909/files 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:1900 |