Translated: Instead of adhering to the US Government mandated standard for 
continuous monitoring, DISA intends to develop their own proprietary content 
that only works with DISA provided tooling.

Further, instead of partnering with DoD, NSA, NIST, industry, and the actual 
vendor, DISA intends to redevelop an entire body of automation content 
internally with no oversight from DoD, and pay a private subcontractor to 
duplicate over 5 years of work.




> On Aug 18, 2017, at 1:36 PM, Paige, David B CTR USARMY ICOE (US) 
> <[email protected]> wrote:
> 
> OpenSCAP will not be supported.  There is a benchmark in development which 
> will correspond to the RHEL7 STIG.
> 
> -----Original Message-----
> From: Shawn Wells [mailto:[email protected]] 
> Sent: Friday, August 18, 2017 9:13 AM
> To: [email protected]
> Subject: [Non-DoD Source] Re: oscap output and STIG Viewer
> 
> All active links contained in this email were disabled.  Please verify the 
> identity of the sender, and confirm the authenticity of all links contained 
> within the message prior to copying and pasting the address to a Web browser. 
>  
> 
> 
> 
> 
> ----
> 
> 
> 
>> On 8/18/17 10:20 AM, Trevor Vaughan wrote:
>> 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.
> 
> Having end-customers/users make the requests would be ideal:
> 
> Caution-https://iase.disa.mil/stigs/Pages/contact.aspx
> 
> [email protected]
> _______________________________________________
> scap-security-guide mailing list -- [email protected]
> To unsubscribe send an email to 
> [email protected]
> _______________________________________________
> scap-security-guide mailing list -- [email protected]
> To unsubscribe send an email to 
> [email protected]
_______________________________________________
scap-security-guide mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to