Description of problem:
In upstream git repository of the scap-security-guide project there are example kickstart files available for Red Hat Enterprise Linux 7 system:
* https://github.com/OpenSCAP/scap-security-guide/blob/master/RHEL/7/kickstart/ssg-rhel7-ospp-ks.cfg
* https://github.com/OpenSCAP/scap-security-guide/blob/master/RHEL/7/kickstart/ssg-rhel7-pci-dss-server-with-gui-oaa-ks.cfg

These kickstarts allow to install RHEL 7 system that will be compliant with USGCB or PCI DSS profile requirements right after the installation is complete.

Similar kickstart files exist for Red Hat Enterprise Linux 6:
* https://github.com/OpenSCAP/scap-security-guide/blob/master/RHEL/6/kickstart/ssg-rhel6-pci-dss-with-gui-ks.cfg
* https://github.com/OpenSCAP/scap-security-guide/blob/master/RHEL/6/kickstart/ssg-rhel6-stig-ks.cfg
* https://github.com/OpenSCAP/scap-security-guide/blob/master/RHEL/6/kickstart/ssg-rhel6-usgcb-server-with-gui-ks.cfg

These kickstart files are not currently included in the scap-security-guide RPM package as shipped with Red Hat Enterprise Linux 7. Since they can simplify the deployment of compliant RHEL 7 systems, they should be included.

Moreover, during the SCAP Security Guide build process there are produced multiple HTML files (tables providing identifiers mappings between various security standards, like CCI, SRG etc).

The list of these files is as follows:
$ pwd
... scap-security-guide/RHEL/7
$ ls output/table-*.html
output/table-rhel5-stig.html         output/table-rhel7-cisrefs.html          output/table-rhel7-pcidss.html       output/table-stig-rhel7-testinfo.html
output/table-rhel5-stig-manual.html  output/table-rhel7-nistrefs-common.html  output/table-rhel7-srgmap-flat.html
output/table-rhel7-cces.html         output/table-rhel7-nistrefs.html         output/table-rhel7-srgmap.html
output/table-rhel7-cisrefs-c2s.html  output/table-rhel7-nistrefs-ospp.html    output/table-rhel7-stig.html
$ ls output/table-*.xhtml
output/table-rhel7-srgmap-flat.xhtml

Since these files provide additional information to scap-security-guide users (allow them to map present SSG requirements against different security standards), they should also be included in the scap-security-guide RPM package.