<div dir="ltr">Is Augeas an option?<div><br></div><div>This seems like the perfect opportunity to solidify the Augeas lenses regarding security settings while making life easier for everyone.</div><div><br></div><div>Trevor</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 3, 2013 at 9:42 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 bgcolor="#FFFFFF" text="#000000"><div class="im">
<div>On 10/3/13 3:11 PM, <a href="mailto:fcaviggi@redhat.com" target="_blank">fcaviggi@redhat.com</a>
wrote:<br>
</div>
<blockquote type="cite">All,
<br>
<br>
As a starting point for writing remediation fixes in the SSG - so,
I did the following:
<br>
<br>
$ ls ~<i><span>/</span>scap-security-guide/RHEL6/input/checks<span>/</span></i>*.xml | awk '{ print $1 }' |
sed s/\.[^\.]*$// > ~/checks
<br>
$ ls ~<i><span>/</span>scap-security-guide/RHEL6/input/fixes<span>/</span></i>*.sh | awk '{ 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
ideas or standards to how the SSG should distribute some of these
fixes - for example - a wholesale replacement of the audit.rules
and auditd.conf might be preferable than doing piecemeal sed's.</blockquote>
<br></div>
It'd be omgz easier to `cp /usr/share/doc/audit-*/stig.rules
/etc/audit.rules`, and that likely is the right choice during an
initial provisioning process. But then SysAdmins tailor audit rules,
the system evolves, and we need to evaluate the audit.rules file
against specific auditing guidance items after the pristine
audit.rules template is manipulated. <br>
<br>
So, if a single rule must be remediated, we can't blow away the
whole audit.rules file. Super fun sed scripts it is =/<div class="im"><br>
<br>
<br>
<blockquote type="cite"> I
also think the first script that needs to be run is to tar the
current existing configurations (as a backup) before applying any
fix just in case we do something that jacks the users
modifications to the system.
<br>
</blockquote>
<br></div>
A prevailing thought has been to address backups once the
remediations are finished, as we'll have a better handle for which
files will need addressing. <br>
<br>
Forcing the backup (through XCCDF/OVAL) is tricky. One thought has
been to create an OVAL check -- which is listed first in the profile
-- which will *always* fail. The remediation for said OVAL would be
to perform the backups. Anyone have a better idea? =/<div class="im"><br>
<br>
<blockquote type="cite">
Anyway, just trying to get an idea of how to proceed set some
goals for my contributions.
<br>
</blockquote>
<br></div>
These are <i>really</i> good questions. Thanks for starting the
conversation!<br>
<br>
</div>
<br>_______________________________________________<br>
scap-security-guide mailing list<br>
<a href="mailto:scap-security-guide@lists.fedorahosted.org">scap-security-guide@lists.fedorahosted.org</a><br>
<a href="https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide" target="_blank">https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide</a><br>
<br></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>