That's exactly correct. Basically, you would add a rule binding line for each type of connection that you want to make.
It can (and in my opinion should) be used across the board.
Thanks,
Trevor
On Mon, Feb 20, 2017 at 9:08 AM, Zbynek Moravec zmoravec@redhat.com wrote:
Hi,
database sounds like interesting idea. I didn't think about it in that way. In my opinion, XML DB could be way how to store many SSG "items", not only OVALs/remediations.
If I understood it correctly, only overhead of adding of new remediation would be adding bindings to product, right?
I don't have own experience with XML databases. What does rest of SSG community think about it?
Z. ----- Original Message -----
From: "Trevor Vaughan" tvaughan@onyxpoint.com To: "SCAP Security Guide" scap-security-guide@lists.fedorahosted.org Sent: Wednesday, February 15, 2017 3:14:33 PM Subject: Re: SSG structure without duplicates (OVAL/remediations)
I would structure it as a 3NF or 5NF XML database with join files.
Absolutely minimizes repetition and make is both easier to maintain and extend.
Trevor
On Mon, Feb 13, 2017 at 4:50 AM, Zbynek Moravec < zmoravec@redhat.com > wrote:
Hi,
we have lot of same files in SSG - especially OVAL checks and
remediations
and it becoming hard to maintain such many files. Every new product means copy&paste of many new files. Bugfix in one product doesn't fix same
files
in another product. We are not able to see, that we forgot remediation
for
OVAL check, etc.
Currently, I am trying to remove generated files and update old csv & templates.
I would like to introduce new structure to allow sharing of files between products. Do you have any ideas/requirements? https://github.com/OpenSCAP/scap-security-guide/issues/1668
Thank you
Z. _______________________________________________ scap-security-guide mailing list -- scap-security-guide@lists.fedorahosted.org To unsubscribe send an email to scap-security-guide-leave@lists.fedorahosted.org
-- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 x788
-- This account not approved for unencrypted proprietary information --
scap-security-guide mailing list -- scap-security-guide@lists.fedorahosted.org To unsubscribe send an email to scap-security-guide-leave@lists.fedorahosted.org
scap-security-guide mailing list -- scap-security-guide@lists. fedorahosted.org To unsubscribe send an email to scap-security-guide-leave@ lists.fedorahosted.org