<div dir="ltr">Ok, so how do we make it happen?<div><br></div><div>Trevor</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 4, 2013 at 11:05 PM, Shawn Wells <span dir="ltr"><<a href="mailto:shawn@redhat.com" target="_blank">shawn@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 10/4/13 8:06 AM, Josh Kayse wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 10/04/2013 07:40 AM, Trevor Vaughan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is Augeas an option?<br>
<br>
This seems like the perfect opportunity to solidify the Augeas lenses<br>
regarding security settings while making life easier for everyone.<br>
<br>
Trevor<br>
<br>
<br>
On Thu, Oct 3, 2013 at 9:42 PM, Shawn Wells <<a href="mailto:shawn@redhat.com" target="_blank">shawn@redhat.com</a><br>
<mailto:<a href="mailto:shawn@redhat.com" target="_blank">shawn@redhat.com</a>>> wrote:<br>
<br>
On 10/3/13 3:11 PM, <a href="mailto:fcaviggi@redhat.com" target="_blank">fcaviggi@redhat.com</a> <mailto:<a href="mailto:fcaviggi@redhat.com" target="_blank">fcaviggi@redhat.com</a>><br>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
All,<br>
<br>
As a starting point for writing remediation fixes in the SSG - so,<br>
I did the following:<br>
<br>
$ ls ~//scap-security-guide/RHEL6/<u></u>input/checks//*.xml | awk '{<br>
print $1 }' | sed s/\.[^\.]*$// > ~/checks<br>
$ ls ~//scap-security-guide/RHEL6/<u></u>input/fixes//*.sh | awk '{<br>
print $1 }' | sed s/\.[^\.]*$// > ~/fixes<br>
$ sdiff ~/fixes ~/checks | less<br>
<br>
There's fair a bit of work to be done for the fix remediations...<br>
<br>
Since I'm new to the project, I was wondering if there was any<br>
ideas or standards to how the SSG should distribute some of these<br>
fixes - for example - a wholesale replacement of the audit.rules<br>
and auditd.conf might be preferable than doing piecemeal sed's.<br>
</blockquote>
<br>
It'd be omgz easier to `cp /usr/share/doc/audit-*/stig.<u></u>rules<br>
/etc/audit.rules`, and that likely is the right choice during an<br>
initial provisioning process. But then SysAdmins tailor audit rules,<br>
the system evolves, and we need to evaluate the audit.rules file<br>
against specific auditing guidance items after the pristine<br>
audit.rules template is manipulated.<br>
<br>
So, if a single rule must be remediated, we can't blow away the<br>
whole audit.rules file. Super fun sed scripts it is =/<br>
<br>
<snip><br>
</blockquote>
<br>
I think that augeas is a good idea. We need to be careful that rules that are inserted in to audit.rules happen before any '-e 2' line (if one exists). Otherwise they will fail to be inserted because the audit rules become locked.<br>
<br>
-josh <br>
</blockquote>
<br></div></div>
Augeas and puppet would be great, their downside is they don't ship natively with RHEL :( Part of the goal is to enable the remediation with native tooling first. IMO, Augeas scripts would be *fantastic* for Aqueduct!<div class="HOEnZb">
<div class="h5"><br>
______________________________<u></u>_________________<br>
scap-security-guide mailing list<br>
<a href="mailto:scap-security-guide@lists.fedorahosted.org" target="_blank">scap-security-guide@lists.<u></u>fedorahosted.org</a><br>
<a href="https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide" target="_blank">https://lists.fedorahosted.<u></u>org/mailman/listinfo/scap-<u></u>security-guide</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Trevor Vaughan<br>Vice President, Onyx Point, Inc<br>(410) 541-6699<br><a href="mailto:tvaughan@onyxpoint.com">tvaughan@onyxpoint.com</a><br><br>-- This account not approved for unencrypted proprietary information --
</div>