Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

We'd like to ease the use of the default scap-security-guide xml files. 
The scenario is: 
scap-security-guide xml files are on the client host.
A user creates policies on Foreman. The policies' data is synced via puppet to the client host.
The user does not need to copy / move scap-security-guide xml files to /var/lib/openscap/content/<digest>.xml

On Client host side
# Add scap-security-guide as an RPM dependency to foreman_scap_client RPM
# Post install creates a symlink between the security guide xmls to /var/lib/openscap/content/<digest>.xml:
## Extract scap-security-guide xml digest
## symlink scap-security-guide xml to /var/lib/openscap/content/<digest>.xml

On foreman_openscap
# Add scap-security-guide as an RPM dependency to rubygem-foreman_openscap RPM
# A seed which automatically creates a Scaptimony::ScapContent with the contents of the scap-security-guide

Created from redmine issue http://projects.theforeman.org/issues/9950

During my OSCAP demo I got to know that the data-stream.xml files can also be other than what is brought my scap-security-guide RPM, (ssg-rhel6-ds.xml or ssg-rhel7-ds.xml file).

Just wondering how will that be handled here, if the idea is to go as per the initial bug description.