Bug 2235606

Summary: anssi_bp28_high profile's audit rules are invalid on aarch64 architecture
Product: Red Hat Enterprise Linux 9 Reporter: Vojtech Polasek <vpolasek>
Component: scap-security-guideAssignee: Vojtech Polasek <vpolasek>
Status: CLOSED MIGRATED QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 9.3CC: ggasparb, matyc, mhaicman, mlysonek, mmarhefk, qe-baseos-security
Target Milestone: rcKeywords: MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Cause: The following SCAP rules configuring Audit included in ANSSI BP28 High profile are applied on aarch64 platform, although they are invalid on this architecture. - audit_rules_unsuccessful_file_modification_creat - audit_rules_unsuccessful_file_modification_open - audit_rules_file_deletion_events_rename - audit_rules_file_deletion_events_rmdir - audit_rules_file_deletion_events_unlink - audit_rules_dac_modification_chmod - audit_rules_dac_modification_chown - audit_rules_dac_modification_lchown Consequence: Audit fails to start because its configuration contains invalid syscalls. Workaround (if any): There are two ways how to workaround this: 1. Remove mentioned rules from the datastream via tailoring. 2. edit files in /etc/audit/rules.d and remove the "-S <syscall>" snippets for the following syscalls: - creat - open - rename - rmdir - unlink - chmod - chown - lchown Result: The Audit will be able to start and compliance of the system will not be affected in any way.
Story Points: ---
Clone Of: 2232607 Environment:
Last Closed: 2023-08-31 09:14:20 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:
Bug Depends On: 2232607    
Bug Blocks:    

Comment 1 RHEL Program Management 2023-08-31 09:09:20 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-08-31 09:14:20 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.

Users watching this BZ may not be automatically added to the Jira ticket.  Be sure to add yourself to the Watchers field in the Jira issue if you desire to continue following this issue.