Bug 1896399

Summary: Policy Standards, Categories and Controls value listing is not consistent across pages
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Karel Srot <ksrot>
Component: GRC & PolicyAssignee: Yu Cao <ycao56>
Status: CLOSED ERRATA QA Contact: Derek Ho <dho>
Severity: low Docs Contact: Mikela Dockery <mdockery>
Priority: unspecified    
Version: rhacm-2.1CC: gghezzo
Target Milestone: ---Flags: gghezzo: rhacm-2.1.z+
Target Release: rhacm-2.1.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhacm-2.1.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-17 18:19:07 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 Karel Srot 2020-11-10 13:27:01 UTC
Description of problem:
multicloud/policies/all is not consistent in how NIST-CSF Standard is listed.

When creating a policy there is an option to use 'NIST-CSF' standard.
However at the policy listing (multicloud/policies/all) page the standard is listed as 'NIST CSF' (space instead of dash).
When listing policy details, 'NIST-CSF' is used again.

Since NIST-CSF is also listed in YAML, I would propose to use this instead of 'NIST CSF' at the policy listing page.

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


Aditional info:
Please make it consistent, it complicates test case writing unnecessarily.

Comment 1 Karel Srot 2020-11-10 13:46:45 UTC
The same applies to 'PR.DS Data Security' category and 'PR.DS-2 Data-in-transit' Control that are listed as 'PR DS Data Security' and 'PR DS 2 Data In Transit'.

Comment 2 Karel Srot 2020-11-10 13:56:38 UTC
And also notice the different letter case between PR DS 2 Data In Transit' and 'PR.DS-2 Data-in-transit'.

Comment 8 errata-xmlrpc 2021-02-17 18:19:07 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 (Moderate: Red Hat Advanced Cluster Management 2.1.3 security and bug fix update), 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/RHSA-2021:0607