--
On Tue, Jan 15, 2019 at 12:19 AM Watson Sato wrote:
>
> Hello,
>
> On Sun, Jan 13, 2019 at 3:22 AM Boyd Ako
> wrote:
>
>> So, after playing around with oscap remediation fix I think there should
>> be a standard on what commands “CAN” be used and
o
> ComplianceAsCode, on GitHub. https://github.com/ComplianceAsCode/content
>
>
> Regards
>
> Jan Černý
> Security Technologies | Red Hat, Inc.
>
> - Original Message -
> > From: "Boyd Ako"
> > To: "Jan Cerny"
> > Cc: open-scap-list@
So, after playing around with oscap remediation fix I think there should be a
standard on what commands “CAN” be used and have them set as a required package
for opens cap. Yes, I know that that “generate fix” should be used cautiously.
But, I noticed some of the FIX snippets in the SSGs used
ion but a DISA one. In my observations,
> it appears that Red Hat has worked with DISA to support CCI, but this does
> not mean that Red Hat is promoting the use of CCI outside of DoD. Is this
> correct?
>
>
> David Oliva
>
>
> -Original Message-
> From: Boyd Ak
sformation.
> It doesn't understand or doesn't analyze the rules that are there.
>
> It isn't clear to me what you need. Do you try to map SSG XCCDF to XCCDF
> provided by DISA?
>
> Regards
>
> Jan Černý
> Security Technologies | Red Hat, Inc.
>
> - Original Me
Aloha,
So I had a couple questions.
A) Is using the Fix Template function still being supported?
B) Is there more detailed documentation on creating the template? I'm
already aware of the XSL "legacy" files in /usr/share/openscap/xsl. I seem
to be having issues with openscap outputing anything
Can anyone point me in the direction of how I help submit remediation fix
scripts?
>From my understanding and correct me if I'm wrong, those scripts make a
finding compliant.
I'm aware of
https://github.com/OpenSCAP/scap-security-guide/tree/master/rhel7/fixes/bash
containing several fix scripts.
