Bug 1457442

Summary: Two benchmarks shipped are titled the same
Product: Red Hat Enterprise Linux 7 Reporter: Marek Haicman <mhaicman>
Component: scap-security-guideAssignee: Martin Preisler <mpreisle>
Status: CLOSED ERRATA QA Contact: Marek Haicman <mhaicman>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.4CC: mhaicman, mpreisle, mthacker, openscap-maint, wsato
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: scap-security-guide-0.1.35-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 12:20:33 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 Marek Haicman 2017-05-31 18:01:00 UTC
Description of problem:
Two benchmarks / checklists shipped in rhel7 datastream of latest version scap-security-guide has the same title, user is not able to distinguish what is the difference between the two, and whether to use PCI-DSS profile from the main checklist, or the separate one.

Version-Release number of selected component (if applicable):
scap-security-guide-0.1.33-4.el7.noarch
(reproducer used scap-workbench-1.1.4-4.el7.x86_64)

How reproducible:
reliably

Steps to Reproduce:
1. open scap-workbench, select rhel7 content
2. try both checklists
3.

Actual results:
Title is the same, user has no indication what is the difference between those checlists

Expected results:
Title is different enough to give user clear information about difference.

Additional info:

Comment 1 Marek Haicman 2017-06-14 22:24:47 UTC
Note: pci-dss_centric profile should be different view of the same, with grouping based directly on PCI-DSS specification, and SCAP rules supplied where appropriate. (instead of rule-centric pci-dss).

Distiction should be explained, though.

Comment 9 errata-xmlrpc 2018-04-10 12:20:33 UTC
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