Bug 1841612
| Summary: | Missing documentation on supported SSG profiles for each RHEL minor version | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Andrew Kofink <akofink> |
| Component: | scap-security-guide | Assignee: | Vojtech Polasek <vpolasek> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | unspecified | Docs Contact: | Jan Fiala <jafiala> |
| Priority: | unspecified | ||
| Version: | --- | CC: | ggasparb, jafiala, matyc, mgoyal, mhaicman, mthacker, wsato |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-13 08:49:05 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
Andrew Kofink
2020-05-29 14:29:11 UTC
As we have established in Bug 1834801, the supported version of SSG for any given minor release of RHEL is the one that is shipped withing this minor release channel. And the list of profiles is determined by the SSG. You can print out which profiles are shipped with command: `oscap info --profiles <datastream>` More remarks: - We cannot assume the number of profiles shipped during GA will not change (there might be addition of another profile after GA, theoretically). - We do not remove profiles, except when they are obsoleted by something else. - I would expect users to be also curious about version of the policy the profile covers. Unfortunately it's not recorded in the datastream. Marek, During the documentation review for SSG version, perhaps we could mention some of your remarks as well with respect to the supported profiles. The fact that we will not remove profiles seems to be pretty important to customers for (scanning) automation stability during/after OS or SSG upgrades and something that we could commit to in the docs. What about rules and values? Could those change between OS minor versions? Are rules potentially added but never removed from the benchmark like you've stated for profiles? What about rules in a profile: could a profile's rules change change between OS minor releases or SSG versions? Thanks for the info, Andrew Hi Andrew, (In reply to Andrew Kofink from comment #3) > What about rules and values? Could those change between OS minor versions? Yes, values can be added to allow new customizations. And rules can change to fix bugs, or follow changes in the technology they are configuring. > Are rules potentially added but never removed from the benchmark like you've stated for profiles? Some rules may be superseded by new ones, typically they are kept in the Benchmark, but not selected in the profile. > What about rules in a profile: could a profile's rules change change between OS minor releases or SSG versions? Yes, the profiles are developed iteratively, so the rule set improves over time. New versions of a policy will also be a reason to change the rule set in a profile. I have just published the updated documentation on the Customer Portal RHEL8: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/security_hardening/index?lb_target=production#scap-security-guide-profiles-supported-in-rhel_scanning-the-system-for-configuration-compliance-and-vulnerabilities] RHEL7: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/security_guide/index#scap-security-guide-profiles-supported-in-rhel-7_scanning-the-system-for-configuration-compliance-and-vulnerabilities] |