Hello,
I am trying to test how new rules can be added to SUSE. I could not find any documentation so this is what I have done so far:
1) Added a new file input/xccdf/system/permissions/files.xml with a couple of rules to check file ownership and permissions of the passwd file. These are copies on the same in RHEL/6 folder. 2) Updated the guide.xslt file for including this group. 3) Added "<platform>multi_platform_sle</platform>" to the appropriate OVAL checks in shared/oval. 4) Added "# platform = multi_platform_sle" to the appropriate fix scripts in /shared/templates/static/bash. 5) Modified Make to remove CentOS related operations from derivatives, guide and validate because they were breaking and are possibly not relevant to SUSE anyhow.
With this I am able to complete the build without errors and generate the output files. [Make fails for the latest sources fetched from the git repo]
I would like to start contributing the rules into SUSE directory. Would the above process be alright? Also, I do not know what needs to be done for the reference and ident tags in XCCDF. Please advise.
Thank you.
Regards, Gautam.
On Fri, Sep 30, 2016 at 2:19 AM, gautams@hpe.com wrote:
Hello,
I am trying to test how new rules can be added to SUSE. I could not find any documentation so this is what I have done so far:
- Added a new file input/xccdf/system/permissions/files.xml with a
couple of rules to check file ownership and permissions of the passwd file. These are copies on the same in RHEL/6 folder. 2) Updated the guide.xslt file for including this group. 3) Added "<platform>multi_platform_sle</platform>" to the appropriate OVAL checks in shared/oval. 4) Added "# platform = multi_platform_sle" to the appropriate fix scripts in /shared/templates/static/bash.
Make sure that fix scripts match the XCCDF content you added in xccdf/system/permissions/files.xml
- Modified Make to remove CentOS related operations from derivatives,
guide and validate because they were breaking and are possibly not relevant to SUSE anyhow.
With this I am able to complete the build without errors and generate the output files. [Make fails for the latest sources fetched from the git repo]
If possible, it needs to work with the latest master, but in this case since SUSE is not incorporated into the build process, it might be okay to just submit a PR.
I would like to start contributing the rules into SUSE directory. Would the above process be alright? Also, I do not know what needs to be done for the reference and ident tags in XCCDF. Please advise.
Leave references alone for now. Remove any ident tags or change them to TBD and change any stigid tags to TBD.
Thank you.
Regards, Gautam. _______________________________________________ scap-security-guide mailing list -- scap-security-guide@lists. fedorahosted.org To unsubscribe send an email to scap-security-guide-leave@ lists.fedorahosted.org
Hi
I would like to help with the SUSE SLES 11/12 content.
@Gautam: How far are you? Could we start work together?
Hi
I also would like to help with the SUSE content.
I just used customized RHEL7's XCCDF file with openSUSE 42.1 for test, then I want to get official SUSE SLES content from project.
Below is the content which I spoke in openSUSE.Asia 2016 about it. http://www.slideshare.net/KazukiOmo/scap-for-opensuse
Kind Regards,
OMO
2016-11-07 18:46 GMT+09:00 Stephan Joerrens stephan.joerrens@fiduciagad.de:
Hi
I would like to help with the SUSE SLES 11/12 content.
@Gautam: How far are you? Could we start work together? _______________________________________________ scap-security-guide mailing list -- scap-security-guide@lists.fedorahosted.org To unsubscribe send an email to scap-security-guide-leave@lists.fedorahosted.org
On 11/7/16 11:49 AM, 面和毅 wrote:
Hi
I also would like to help with the SUSE content.
I just used customized RHEL7's XCCDF file with openSUSE 42.1 for test, then I want to get official SUSE SLES content from project.
Below is the content which I spoke in openSUSE.Asia 2016 about it. http://www.slideshare.net/KazukiOmo/scap-for-opensuse
There aren't many presentations out there for OpenSCAP on SuSE. Would you be OK if we added a link to your presentation from the Collateral & References page?
https://github.com/OpenSCAP/scap-security-guide/wiki/Collateral-and-Referenc...
May help get the word out that you and others are working on SuSE content :)
Dear Shawn,
Below is the content which I spoke in openSUSE.Asia 2016 about it. http://www.slideshare.net/KazukiOmo/scap-for-opensuse
There aren't many presentations out there for OpenSCAP on SuSE. Would you be OK if we added a link to your presentation from the Collateral & References page?
https://github.com/OpenSCAP/scap-security-guide/wiki/Collateral-and-Referenc...
Thanks. That would be great to me. :-)
Kind Regards,
OMO
2016-11-08 2:27 GMT+09:00 Shawn Wells shawn@redhat.com:
On 11/7/16 11:49 AM, 面和毅 wrote:
Hi
I also would like to help with the SUSE content.
I just used customized RHEL7's XCCDF file with openSUSE 42.1 for test, then I want to get official SUSE SLES content from project.
Below is the content which I spoke in openSUSE.Asia 2016 about it. http://www.slideshare.net/KazukiOmo/scap-for-opensuse
There aren't many presentations out there for OpenSCAP on SuSE. Would you be OK if we added a link to your presentation from the Collateral & References page?
https://github.com/OpenSCAP/scap-security-guide/wiki/Collateral-and-Referenc...
May help get the word out that you and others are working on SuSE content :) _______________________________________________ scap-security-guide mailing list -- scap-security-guide@lists.fedorahosted.org To unsubscribe send an email to scap-security-guide-leave@lists.fedorahosted.org
On 11/8/16 12:17 AM, 面和毅 wrote:
Dear Shawn,
Below is the content which I spoke in openSUSE.Asia 2016 about it. http://www.slideshare.net/KazukiOmo/scap-for-opensuse
There aren't many presentations out there for OpenSCAP on SuSE. Would you be OK if we added a link to your presentation from the Collateral & References page?
https://github.com/OpenSCAP/scap-security-guide/wiki/Collateral-and-Referenc...
Thanks. That would be great to me. :-)
Omo-san,
Great, thank you! I've added your SlideShare to the wiki.
-Shawn
Hello folks,
I have been trying to build openscap on SUSE 12. A couple of probes like process58, rpmverify etc. are not working on SUSE. I have just started looking at them, but very few SSG rules rely on these probes.
On SUSE 12, the input XCCDF templates are already in place. I assume they are copies of the same on RHEL. So when we build SSG for SUSE 12, all the rules are present. As a next step, we need to add "SUSE 12" to the applicable platform tag to the OVAL checks and bash remediation in the common folder wherever applicable.
We could figure out some kind of plan and work on this.
Regards, Gautam.
-----Original Message----- From: 面和毅 [mailto:ka-omo@sios.com] Sent: Monday, November 07, 2016 10:19 PM To: SCAP Security Guide scap-security-guide@lists.fedorahosted.org Subject: Re: Adding rules for SUSE.
Hi
I also would like to help with the SUSE content.
I just used customized RHEL7's XCCDF file with openSUSE 42.1 for test, then I want to get official SUSE SLES content from project.
Below is the content which I spoke in openSUSE.Asia 2016 about it. http://www.slideshare.net/KazukiOmo/scap-for-opensuse
Kind Regards,
OMO
2016-11-07 18:46 GMT+09:00 Stephan Joerrens stephan.joerrens@fiduciagad.de:
Hi
I would like to help with the SUSE SLES 11/12 content.
@Gautam: How far are you? Could we start work together? _______________________________________________ scap-security-guide mailing list -- scap-security-guide@lists.fedorahosted.org To unsubscribe send an email to scap-security-guide-leave@lists.fedorahosted.org
-- Kazuki Omo: ka-omo@sios.com OSS &Security Evangelist OSS Business Planning Dept. CISSP #366942 Tel: +81364015149 _______________________________________________ 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@lists.fedorahosted.org
-
Gabe Alford -
S, Gautam -
Shawn Wells -
Stephan Joerrens -
面和毅