Shawn, Happy to contribute. As I get it together, I'll provide what I
have. I have a PCI-DSS QSA onsite for the foreseeable future to validate
what I'm doing against the PCI-DSS 2.0 standards (3.0 will be out soon
enough)..
I use openscap in conjunction with Red Hat Satellite for reporting purposes
to validate in scope systems
On Thu, Oct 24, 2013 at 2:01 PM, Shawn Wells <shawn(a)redhat.com> wrote:
On 10/24/13, 1:59 PM, wm-lists wrote:
> Thanks Shawn
> I'll grab the RPM when you get it done and diff it against my xml (I have
> my own custom rpm for deploying a PCI-DSS standard based on the server
> profile)
> Thanks for all the work on this too. this goes a long way towards
> helping me get compliancy reports!
>
> A PCI-DSS profile would be most welcome within the project! I'll buy you
a beer if you start one. Very happy to assist in the commit process.
I'm not kidding.
______________________________**_________________
scap-security-guide mailing list
scap-security-guide@lists.**fedorahosted.org<scap-security-guide(a)lists.fedorahosted.org>
https://lists.fedorahosted.**org/mailman/listinfo/scap-**security-guide&l...