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.
Bug 1284045 - please add CNSS No. 1253 Profile from upstream
Summary: please add CNSS No. 1253 Profile from upstream
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: scap-security-guide
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Lieskovsky
QA Contact: Marek Haicman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-20 16:06 UTC by Andrew Shewmaker
Modified: 2016-05-10 21:40 UTC (History)
5 users (show)

Fixed In Version: scap-security-guide-0.1.28-2.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 21:40:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0846 0 normal SHIPPED_LIVE scap-security-guide bug fix update 2016-05-10 22:42:59 UTC

Description Andrew Shewmaker 2015-11-20 16:06:29 UTC
Description of problem:

The current version of the SCAP Security Guide does not include the CNSS No. 1253 Profile, which is available from upstream.

https://github.com/OpenSCAP/scap-security-guide/blob/master/RHEL/6/input/profiles/nist-CL-IL-AL.xml

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

scap-security-guide-0.1.21-3

How reproducible:

Always

Steps to Reproduce:

1. oscap info /usr/share/xml/scap/ssg/content/ssg-rhel6-xccdf.xml 


Actual results:

Document type: XCCDF Checklist
Checklist version: 1.1
Status: draft
Generated: 2015-05-12
Imported: 2015-05-12T06:50:20
Resolved: true
Profiles:
CS2
common
server
stig-rhel6-server-upstream
usgcb-rhel6-server
rht-ccp
CSCF-RHEL6-MLS
C2S
Referenced check files:
ssg-rhel6-oval.xml
system: http://oval.mitre.org/XMLSchema/oval-definitions-5

Expected results:

List of profiles should include:

nist-cl-il-al

Additional info:

Comment 3 Šimon Lukašík 2015-11-23 11:13:50 UTC
Moving to POST, this has been already done in upstream. Thanks Andrew for raising this.

Note, to enable profile in distribution we also need this: https://github.com/OpenSCAP/scap-security-guide/pull/863

Comment 6 Jan Lieskovsky 2015-12-09 12:23:36 UTC
Another fix applicable to this profile (fixing invalid selectors):
  https://github.com/OpenSCAP/scap-security-guide/pull/904

Comment 8 Marek Haicman 2016-01-28 18:39:04 UTC
Hello Iankko, I know it is just a nitpick, but would you consider changing a profile name a bit? With all other profile names we move to less abbreviated format, but this is left pretty dense... :)

Proposal [well, the abbreviation itself probably cannot be expanded in any reasonable way]:
CNSSI 1253 with criterions Low/Low/Low

Comment 9 Jan Lieskovsky 2016-02-03 14:07:49 UTC
(In reply to Marek Haicman from comment #8)

@Marek

Thank you for checking this!

> Hello Iankko, I know it is just a nitpick, but would you consider changing a
> profile name a bit? With all other profile names we move to less abbreviated
> format, but this is left pretty dense... :)
> 
> Proposal [well, the abbreviation itself probably cannot be expanded in any
> reasonable way]:
> CNSSI 1253 with criterions Low/Low/Low

Would "CNSSI 1253 Low/Low/Low Control Baseline for Red Hat Enterprise Linux 6"
form be acceptable instead?

Those "Low/Low/Low" categorizations are important there (since they specify the overlays we are using in this profile) [*]

[*] Refer to: https://www.cnss.gov/CNSS/openDoc.cfm?6pTJzXxAC8oPWmAm+YQAsQ==
(page #4) (Section "2.3 RELATIONSHIP BETWEEN BASELINES AND OVERLAYS" for clarification what that overlay means)

Thanks, Jan.

Comment 10 Marek Haicman 2016-02-03 14:26:55 UTC
Hello Jan, it works for me just fine, thanks! :)

Comment 11 Jan Lieskovsky 2016-02-04 09:15:40 UTC
(In reply to Marek Haicman from comment #10)
> Hello Jan, it works for me just fine, thanks! :)

Brilliant. Thanks for confirmation!

Upstream PR proposing this form is here:
  https://github.com/OpenSCAP/scap-security-guide/pull/1032

Comment 13 Marek Haicman 2016-02-16 11:30:34 UTC
Verified there is "CNSSI 1253 Low/Low/Low Control Baseline for Red Hat Enterprise Linux 6" profile in scap-security-guide-0.1.28-2.el6, and its content looks sane.

Comment 15 errata-xmlrpc 2016-05-10 21:40:36 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://rhn.redhat.com/errata/RHBA-2016-0846.html


Note You need to log in before you can comment on or make changes to this bug.