I like the idea. The devil, as always, is in the details. DISA FSO has some unique requirements that need to be addressed somehow. If they can be isolated for STIG synchronization and maintenance without causing undue stress on the rest of the SSG content, it could be all to the good.
Thanks, Leland -- Leland Steinke, Security+ DISA FSO Technical Support Contractor tapestry technologies, Inc 717-267-5797 (DSN 570) [email protected] (gov't) [email protected] (com'l) > -----Original Message----- > From: [email protected] [mailto:scap- > [email protected]] On Behalf Of Shawn Wells > Sent: Friday, December 20, 2013 9:48 AM > To: [email protected] > Subject: [RFC] Rename stig-rhel6-server to stig-rhel6-server-upstream? > > SSG enjoys a fantastic working relationship with DISA FSO, however in > aspirations to clearly delineate between the upstream STIG profile > (e.g. > that of SSG) and the formal STIG (listed on iase.disa.mil), I'd like to > rename to stig-rhel6-server-upstream. > > Many community members realize the upstream->downstream relationship, > however I'd like to re-enforce this through the profile name itself. > > Thoughts? Objections? > _______________________________________________ > scap-security-guide mailing list > [email protected] > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ scap-security-guide mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
