Bug 1306653

Summary:	Save as a DataStream
Product:	Red Hat Enterprise Linux 7	Reporter:	Šimon Lukašík <slukasik>
Component:	scap-workbench	Assignee:	Watson Yuuma Sato <wsato>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	high
Version:	7.2	CC:	cww, jlieskov, mgrepl, mhaicman, openscap-maint, sroza
Target Milestone:	rc	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-26 17:16:20 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:
Bug Depends On:
Bug Blocks:	1477664

Description Šimon Lukašík 2016-02-11 14:19:36 UTC

Description of problem:
We have users that want to save the Tailoring file directly to the DataStream. This is actually quite common use-case outside of OpenSCAP. Even though its merits are not warranted.

See new validation requirements NIST 7511r4 for more details on usage of DataStreams and Tailorings.

There are two possible scenarios.
 - Save Tailoring as a DataStream with a benchmark hint to another DataStream.
 - Save Tailoring as a DataStream with Benchmark included in the same DataStream.

Steps to Reproduce:
1. Customize
2. Save As -> DataStream
3.

Comment 4 Marek Haicman 2017-11-29 22:04:30 UTC

Just FYI:

This issue can be workarounded by this script:
https://github.com/mpreisler/combine-tailoring/blob/master/combine-tailoring.py

Included tailoring can be then referenced as any other profile.

Comment 6 Šimon Lukašík 2017-11-30 11:57:10 UTC

Wouldn't it be awesome to have it implemented anyway?

Comment 9 Marek Haicman 2019-02-26 17:16:20 UTC

This issue was not selected to be included in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small number of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise, we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.