This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2176927 - STIG scan fails on xccdf_org.ssgproject.content_rule_fapolicy_default_deny
Summary: STIG scan fails on xccdf_org.ssgproject.content_rule_fapolicy_default_deny
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: scap-security-guide
Version: 8.7
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Vojtech Polasek
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-09 16:42 UTC by Renaud Métrich
Modified: 2023-08-30 08:53 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-30 08:53:42 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-1817 0 None Migrated None 2023-08-30 08:53:36 UTC
Red Hat Issue Tracker RHELPLAN-151295 0 None None None 2023-03-09 16:43:46 UTC
Red Hat Issue Tracker SECENGSP-5106 0 None None None 2023-03-16 11:09:50 UTC
Red Hat Knowledge Base (Solution) 7003854 0 None None None 2023-03-22 13:53:30 UTC

Description Renaud Métrich 2023-03-09 16:42:43 UTC 
Description of problem:

We have a customer requiring to implement full STIG compliance, including xccdf_org.ssgproject.content_rule_fapolicy_default_deny rule:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Title   Configure Fapolicy Module to Employ a Deny-all, Permit-by-exception Policy to Allow the Execution of Authorized Software Programs.
Rule    xccdf_org.ssgproject.content_rule_fapolicy_default_deny
Ident   CCE-86478-5
Result  fail
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

On a system I installed with STIG profile selected at installation time, the rule fails, because there is no "deny perm=any all : all" in what we ship.
It looks like a "final rule" is missing, e.g. /etc/fapolicyd/rules.d/99-deny-everything.rules:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
deny perm=any all : all
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

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

scap-security-guide-0.1.66-2.el8_7.noarch

How reproducible:

Always
Comment 1 Vojtech Polasek 2023-03-13 08:40:32 UTC 
Hello Renaud,
I am not sure what you are asking for. Note that the rule xccdf_org.ssgproject.content_rule_fapolicy_default_deny has no remediation, it performs only the check because we can't know which applications should be permitted.
Do you suggest that the check should be altered? Or that the default shipped file should be altered?
Comment 2 Renaud Métrich 2023-03-13 09:25:56 UTC 
Sorry for confusion, I'm asking for a new file /etc/fapolicyd/rules.d/99-deny-everything.rules being shipped, so that the rule doesn't fail by default.
Comment 11 RHEL Program Management 2023-08-30 08:27:23 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 12 RHEL Program Management 2023-08-30 08:53:42 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.
Note You need to log in before you can comment on or make changes to this bug.