Please do ask DISA to support the standard SCAP formats if at all possible.
I haven't been able to find any of their internal formats yet I'm trying to automate the generation of content for them. This really is not helpful to their user base. Trevor On Thu, Aug 17, 2017 at 9:58 PM, Shawn Wells <[email protected]> wrote: > > > On 8/17/17 1:02 PM, Paige, David B CTR USARMY ICOE (US) wrote: > > The DISA STIGViewer isn't about to correlate the Redhat STIG with any of > the items from a Rhel/CentOS xml file created by openscap. This means that > all of the items must be updated manually. > > > > Would it be possible to get the output to be recognized by the DISA > STIGViewer? I'm not sure what openscap does differently from the SPAWAR > SCC tool, which can be imported into the STIGViewer. > > > > The openscap xml output is also not processed by the vulnerator tool, > but it will handle the SCC xml files. > > OpenSCAP generates SCAP content. STIGViewer (and SCC) built in DISA's > proprietary extensions/formats. > > In theory this would be a matter of applying an XSLT to restructure the > properly formatted SCAP results into whatever DISA needs. > _______________________________________________ > scap-security-guide mailing list -- scap-security-guide@lists. > fedorahosted.org > To unsubscribe send an email to scap-security-guide-leave@ > lists.fedorahosted.org > -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 x788 -- This account not approved for unencrypted proprietary information --
_______________________________________________ scap-security-guide mailing list -- [email protected] To unsubscribe send an email to [email protected]
