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.

Description of problem:
One of the rules in all stricter RHEL7 policies is to set firewalld default zone to "drop". (rule_set_firewalld_default_zone) This prevents any connection not specifically allowed from succeeding.

Rule to explicitly enable SSH port (rule_firewalld_sshd_port_enabled) is shipped within datastream, but is actually not enabled in any profile. We need to enable it for all profiles which are dropping by default.

Version-Release number of selected component (if applicable):
scap-security-guide-0.1.33-5.el7.noarch


How reproducible:
reliably

Steps to Reproduce:
1. harden machine with ospp profile
2. connect with ssh, or firewall-cmd --list-all-zones
3.

Actual results:
ssh is not enabled in drop policy

Expected results:
ssh is enabled

Additional info:

Proposed fix upstream: https://github.com/OpenSCAP/scap-security-guide/pull/2328

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, 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-2018:0761