Red Hat seems to not be putting a lot of work into RHEL 5 STIG compliance. That's been one of my motivators. On Wed, Apr 29, 2015 at 2:01 PM, Jim Perrin <jperrin at centos.org> wrote: > > > On 04/29/2015 10:49 AM, leam hall wrote: > > On Wed, Apr 29, 2015 at 11:28 AM, Stephen John Smoogen <smooge at gmail.com > > > > wrote: > > > >> > >> On 29 April 2015 at 09:17, leam hall <leamhall at gmail.com> wrote: > >> > >>> My personal project goal is to work on scripts and Puppet content to > meet > >>> STIG requirements. I'm not really talented enough to putz around with > the > >>> kernel stuff but don't object if others do. > >>> > >>> > >> What kind of scripts are you looking for and need? There are several out > >> there for STIG requirements so I was wondering if they could be used. > >> > > > > I've used Aqueduct, and wrote some of them. Working on implementing a > newer > > project and focusing on Puppet code as that's what I'm need to learn > most. > > Still getting a handle on what all is out there. > > > It might be easier to look at the tooling mentioned here > https://access.redhat.com/comment/913583#comment-913583 (thanks Akemi > for pointing it out) and assessing the level of effort needed to make > that work for CentOS. > > -- > Jim Perrin > The CentOS Project | http://www.centos.org > twitter: @BitIntegrity | GPG Key: FA09AD77 > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > http://lists.centos.org/mailman/listinfo/centos-devel > -- Mind on a Mission <http://leamhall.blogspot.com/> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20150429/3150abe9/attachment-0008.html>