Bug 1493007
| Summary: | hardening makes computer not accessible by ssh [rhel-7.4.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | scap-security-guide | Assignee: | Watson Yuuma Sato <wsato> |
| Status: | CLOSED ERRATA | QA Contact: | Marek Haicman <mhaicman> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.4 | CC: | mgrepl, mhaicman, mjahoda, mmarhefk, mpreisle, mthacker, openscap-maint, toneata, wsato |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | scap-security-guide-0.1.33-6.el7_4 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, all strict SCAP Security Guide (SSG) profiles contained a remediation script, which set the firewalld default zone to "drop" preventing any connection to a machine that is not explicitly allowed. As a consequence, the machine was not accessible by SSH. With this update, the script has been removed from the SSG profiles, and the machine is now accessible by SSH after an SSG security hardening.
|
Story Points: | --- |
| Clone Of: | 1478414 | Environment: | |
| Last Closed: | 2017-10-19 15:12:37 UTC | Type: | --- |
| 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: | 1478414 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2017-09-19 07:20:43 UTC
Verified that installing machine using updated DataStream (package version scap-security-guide-0.1.33-6.el7_4), hardening it with PCI-DSS, DISA STIG, or OSPP profiles leaves machine hardened (similarly to 7.4.0 release), but still accessible by SSH. No regressions found during quality evaluation of the change. 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-2017:2933 |