August 2013 - scap-security-guide - Fedora mailing-lists

[PATCH] OCIL content generation fixup
by Jeffrey Blank 23 Aug '13

23 Aug '13

This patch takes the "conditional clause" attribute from the contrived "ocil-transitional" check system and uses it to create a question for users. This should allow the scap-security-guide content to act as a bridge between the robotic and special "this is a finding" phrasing found in DISA STIGs, and OCIL designed for human interaction. We can generate both. Jeffrey Blank (1): added interrogatory phrase to OCIL questions RHEL6/transforms/xccdf-create-ocil.xslt | 10 +++++++--- 1 files changed, 7 insertions(+), 3 deletions(-)

2 2

[PATCH] Check will return list of all partitions without nodev instead of a complete list of all partitions and the return value of true/false will accurately reflect passing or failing
by Maura Dailey 22 Aug '13

22 Aug '13

Signed-off-by: Maura Dailey <maura(a)eclipse.ncsc.mil> --- ...mount_option_nodev_nonroot_local_partitions.xml | 28 ++++++++++--------- 1 files changed, 15 insertions(+), 13 deletions(-) diff --git a/RHEL6/input/checks/mount_option_nodev_nonroot_local_partitions.xml b/RHEL6/input/checks/mount_option_nodev_nonroot_local_partitions.xml index a5e6334..e0abd50 100644 --- a/RHEL6/input/checks/mount_option_nodev_nonroot_local_partitions.xml +++ b/RHEL6/input/checks/mount_option_nodev_nonroot_local_partitions.xml @@ -1,36 +1,38 @@ <def-group> - <definition class="compliance" id="mount_option_nodev_nonroot_local_partitions" version="1"> + <definition class="compliance" + id="mount_option_nodev_nonroot_local_partitions" version="1"> <metadata> <title>Add nodev Option to Non-Root Local Partitions</title> <affected family="unix"> <platform>Red Hat Enterprise Linux 6</platform> </affected> - <description>The nodev mount option prevents files from being - interpreted as character or block devices. Legitimate character and block - devices should exist in the /dev directory on the root partition or - within chroot jails built for system services. All other locations should not - allow character and block devices.</description> + <description>The nodev mount option prevents files from being interpreted + as character or block devices. Legitimate character and block devices + should exist in the /dev directory on the root partition or within chroot + jails built for system services. All other locations should not allow + character and block devices.</description> + <reference source="MED" ref_id="20130821" ref_url="test_attestation" /> </metadata> <criteria> - <criterion comment="nodev on local filesystems" test_ref="test_nodev_nonroot_local_partitions" /> + <criterion comment="nodev on local filesystems" + test_ref="test_nodev_nonroot_local_partitions" negate="true" /> </criteria> </definition> - - <linux:partition_test check="all" check_existence="all_exist" id="test_nodev_nonroot_local_partitions" version="1" comment="nodev on local filesystems"> + <linux:partition_test check="all" check_existence="all_exist" + id="test_nodev_nonroot_local_partitions" version="1" + comment="nodev on local filesystems"> <linux:object object_ref="object_non_root_partitions" /> <linux:state state_ref="state_local_nodev" /> </linux:partition_test> - <linux:partition_object id="object_non_root_partitions" version="1">  <linux:mount_point operation="pattern match">^/\w.*$</linux:mount_point> <filter action="include">state_local_nodev</filter> </linux:partition_object> - <linux:partition_state id="state_local_nodev" version="1">  <linux:device operation="pattern match">^/dev/.*$</linux:device> - <linux:mount_options datatype="string" entity_check="at least one" operation="equals">nodev</linux:mount_options> + <linux:mount_options datatype="string" entity_check="all" + operation="not equal">nodev</linux:mount_options> </linux:partition_state> - </def-group> -- 1.7.1

4 8

SSG line item references
by Robert Sanders 22 Aug '13

22 Aug '13

Quick question - I'm looking at the SSG content files and trying to determine the 'line item' number for a particular check. The DISA STIG content is layed out so that the line item information (i.e., rhel-06-0000001) is inline with a particular check. The SSG content doesn't appear to have this inline, and I suspect that the line items are being generated programmatically via the oscap command but I haven't drilled down to see what oscap is actually doing. Considering that the SSG is the upstream document for the RHEL6 STIG - is DISA responsible for remapping the SSG items to the STIG items, or will DISA adopt the way that the SSG is generating line items? If the latter, could this result in line item x.z.y from version A be a *very* different best than line item x.y.z from version B? -Rob

4 8

[PATCH] Another big batch of updates
by Maura Dailey 22 Aug '13

22 Aug '13

I went through a whole bunch more checks, tested them, tweaked their regex as necessary, and corrected comment fields. I also ran them through tidy and fixed them up a little. A few checks had "dead states" which were never referenced in a test field, so I deleted those. I also added rsyslog to the template file for installed packages, since it was apparently missing, even though the compiled check had been added in a previous commit. - Maura Dailey Maura Dailey (1): Another batch of tested checks. Includes some checks that had their comments expanded or were renamed from random values. RHEL6/input/checks/banner_etc_issue.xml | 1 + .../checks/dovecot_disable_plaintext_auth.xml | 10 ++++--- RHEL6/input/checks/dovecot_enable_ssl.xml | 12 ++++---- .../input/checks/logwatch_configured_hostlimit.xml | 8 ++--- .../checks/logwatch_configured_splithosts.xml | 10 +++---- RHEL6/input/checks/network_sniffer_disabled.xml | 1 + RHEL6/input/checks/ntp_remote_server.xml | 27 +++++++++---------- .../checks/postfix_network_listening_disabled.xml | 26 +++++++++--------- RHEL6/input/checks/postfix_server_banner.xml | 17 ++++-------- RHEL6/input/checks/restrict_serial_port_logins.xml | 7 +++-- .../checks/securetty_root_login_console_only.xml | 5 ++- RHEL6/input/checks/selinux_mode.xml | 9 ++++-- RHEL6/input/checks/selinux_policytype.xml | 18 +++++-------- .../set_password_hashing_algorithm_libuserconf.xml | 3 +- .../set_password_hashing_algorithm_logindefs.xml | 5 ++- RHEL6/input/checks/singleuser_password.xml | 19 ++++++-------- RHEL6/input/checks/smb_client_signing_smb_conf.xml | 23 +++++++++-------- .../sysconfig_networking_bootproto_ifcfg.xml | 20 +++++++------- RHEL6/input/checks/sysconfig_nozeroconf_yes.xml | 22 +++++++--------- .../input/checks/system_info_architecture_x86.xml | 22 ++++++++-------- .../checks/system_info_architecture_x86_64.xml | 22 ++++++++-------- .../input/checks/templates/packages_installed.csv | 3 +- RHEL6/input/checks/tftpd_uses_secure_mode.xml | 3 +- RHEL6/input/checks/xwindows_runlevel_setting.xml | 3 +- 24 files changed, 146 insertions(+), 150 deletions(-)

3 3

False Pass: PASS_MIN_DAYS /etc/login.defs
by Stuart Green 21 Aug '13

21 Aug '13

Just happened across this while I was modding an incorrect parameter. Rule password_min_age: PASS_MIN_DAYS in /etc/login.defs seems to pass regardless of the number being higher than 1. Mine was set to 7 and was passing, so I set it to 100 for another run through and it still passed. Note: I'm not sure if these login.defs are actually necessary, well not in a PAM environment. When PAM's handling the restrictions login.defs is not involved. Citation: http://www.linuxmanpages.com/man5/login.defs.5.php (bug section) Cheers, Stu

4 4

intermittent failure of oval check, how to debug?
by Brian Millett 21 Aug '13

21 Aug '13

Ok, how do I go about debugging this: [root@deckard scap]# ./testcheck.py dir_perms_world_writable_sticky_bits.xml Evaluating with OVAL tempfile : /tmp/dir_perms_world_writable_sticky_bitshof67c.xml OpenSCAP Error: Unable to receive a message from probe [oval_probe_ext.c:583] [root@deckard scap]# ./testcheck.py dir_perms_world_writable_sticky_bits.xml Evaluating with OVAL tempfile : /tmp/dir_perms_world_writable_sticky_bitsLT_H5A.xml OpenSCAP Error: Unable to receive a message from probe [oval_probe_ext.c:583] [root@deckard scap]# ./testcheck.py dir_perms_world_writable_sticky_bits.xml Evaluating with OVAL tempfile : /tmp/dir_perms_world_writable_sticky_bits6eM3gu.xml OpenSCAP Error: Unable to receive a message from probe [oval_probe_ext.c:583] [root@deckard scap]# ./testcheck.py dir_perms_world_writable_sticky_bits.xml Evaluating with OVAL tempfile : /tmp/dir_perms_world_writable_sticky_bitsIWHsj4.xml Definition oval:scap-security-guide.testing:def:100: false The dir_perms_world_writable_sticky_bits test on ONE rhel6 machine is failing, but sometimes it does not. When I run an evaluation with the stig-rhel policy, I get OpenSCAP Error: Unable to receive a message from probe [oval_probe_ext.c:584] No definition with ID: oval:ssg:def:509 in result model. [oval_agent.c:182] -- Brian Millett "We are not through with the Centauri yet." -- [ G'Kar (to Jha'dur), "Deathwalker"]

3 5

Generalising SSG ...
by Trey Henefield 20 Aug '13

20 Aug '13

Just food for thought. Has there been any desire to make changes to SSG to accommodate building other (non-rhel6) SSGs? I am getting up to speed on its processes, and for practice and actual need, was thinking of creating an SSG for Firefox and Java, and potentially webmin and apache. However, I noticed rhel6 is embedded all throughout. I have noticed that most of the processes in place can be repurposed. With some changes to the makefile and a repurposed input folder, should this be possible? I was just hoping to get some further insight before going down this long path. Thanks in advance! Best regards, Trey Henefield, CISSP Senior IAVA Engineer Ultra Electronics Advanced Tactical Systems, Inc. 4101 Smith School Road Building IV, Suite 100 Austin, TX 78744 USA Trey.Henefield(a)ultra-ats.com Tel: +1 512 327 6795 ext. 647 Fax: +1 512 327 8043 Mobile: +1 512 541 6450 www.ultra-ats.com Disclaimer The information contained in this communication from trey.henefield(a)ultra-ats.com sent at 2013-08-20 11:36:43 is confidential and may be legally privileged. It is intended solely for use by scap-security-guide(a)lists.fedorahosted.org and others authorized to receive it. If you are not scap-security-guide(a)lists.fedorahosted.org you are hereby notified that any disclosure, copying, distribution or taking action in reliance of the contents of this information is strictly prohibited and may be unlawful.

3 3

Re: Re: [PATCH 02/17] Mapped CCI-001436 to disable_vsftpd (UNCLASSIFIED)
by Beavers, Randall D. CTR (US) 20 Aug '13

20 Aug '13

Classification: UNCLASSIFIED Caveats: NONE Willy Santos & Shawn Wells, I'm seeing you guys mapping a lot of CCIs to RHEL 6 on the lists. (searching CCI information online). I'm doing some work mapping the NIST 800-53 (v.4) to CCIs to DISA SRGs to DISA STIGS for my program. Any help would be appreciated. Seems the DISA IASE website and the VMS site doesn't jive. Do you guys have some definitive mappings for RHEL 6.4 CCEs / CCIs that would help me? In excel format? In xml format? Please advise. Randy Beavers, GSLC, CISSP Information Assurance Engineer Joint Battle Command-Platform 6000-C Technology Drive Huntsville, AL 35805 256-842-5426 (work) 256-289-6054 (cell) 256-876-2576 (fax) randall.d.beavers.ctr(a)mail.mil randall.d.beavers.ctr(a)mail.smil.mil Classification: UNCLASSIFIED Caveats: NONE

3 2

Very basic question..
by Stuart Green 20 Aug '13

20 Aug '13

Hi Folks, I just noticed that in my /usr/share/xml/scap/ssg/content/ folder the files are time stamped Jul 5 19:03 but the files in here are from the 13th of July. http://people.redhat.com/swells/scap-security-guide/RHEL6/dist/content/ There's no updates available in yum, so is it just a matter these files have not been pushed to repo yet? Cheers, Stu

2 2

[PATCH 0/2] updates to transforms to show OVAL testing
by Jeffrey Blank 20 Aug '13

20 Aug '13

This update to the table transform will show (with a thick green line) when an OVAL check has been tested for each Rule. This can probably get far more complete-looking if the templated checks are tested. (Did we ever fix the OVAL check for system services, such that only runlevel 2-5 were disabled?) It also shows the Rule ID for each Rule now, which is the stable identifier for each Rule. Jeffrey Blank (2): made CSS adjustments to make <pre> wrap improved table to indicate when OVAL checks have been tested RHEL6/transforms/table-style.xslt | 5 ++++ RHEL6/transforms/xccdf2table-profileccirefs.xslt | 27 +++++++++++++++++----- 2 files changed, 26 insertions(+), 6 deletions(-)

2 4

[PATCH] Original check assumed that sha512 would always be the first option
by Maura Dailey 20 Aug '13

20 Aug '13

Small edit to ensure that sha512 can be set anywhere in the list of options in the pam_unix.so line. - Maura Dailey Signed-off-by: Maura Dailey <maura(a)eclipse.ncsc.mil> --- .../set_password_hashing_algorithm_systemauth.xml | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/RHEL6/input/checks/set_password_hashing_algorithm_systemauth.xml b/RHEL6/input/checks/set_password_hashing_algorithm_systemauth.xml index e999d0d..ac86592 100644 --- a/RHEL6/input/checks/set_password_hashing_algorithm_systemauth.xml +++ b/RHEL6/input/checks/set_password_hashing_algorithm_systemauth.xml @@ -6,6 +6,7 @@ <platform>Red Hat Enterprise Linux 6</platform> </affected> <description>The password hashing algorithm should be set correctly in /etc/pam.d/system-auth.</description> + <reference source="MED" ref_id="20130819" ref_url="test_attestation" /> </metadata> <criteria operator="AND"> <criterion test_ref="test_pam_unix_sha512" /> @@ -18,7 +19,7 @@ <ind:textfilecontent54_object comment="check /etc/pam.d/system-auth for correct settings" id="object_pam_unix_sha512" version="1"> <ind:filepath>/etc/pam.d/system-auth</ind:filepath> - <ind:pattern operation="pattern match">^\s*password\s+sufficient\s+pam_unix.so\s+sha512.*$</ind:pattern> + <ind:pattern operation="pattern match">^[\s]*password[\s]+sufficient[\s]+pam_unix\.so[\s]+.*sha512.*$</ind:pattern> <ind:instance datatype="int">1</ind:instance> </ind:textfilecontent54_object> -- 1.7.1

2 1

[PATCH] Existing check was screwed up (title was wrong, comments were wrong, etc.) and was easily replaced by a templated check
by Maura Dailey 20 Aug '13

20 Aug '13

I noticed that the name of the check didn't make any sense, delved in deeper, and discovered that the correct check more closely met the templated sysctl checks. - Maura Dailey Signed-off-by: Maura Dailey <maura(a)eclipse.ncsc.mil> --- .../checks/core_dump_suid_progs_limits_conf.xml | 30 -------------------- RHEL6/input/checks/sysctl_fs_suid_dumpable.xml | 28 ++++++++++++++++++ RHEL6/input/checks/templates/sysctl_values.csv | 1 + RHEL6/input/system/permissions/execution.xml | 2 +- 4 files changed, 30 insertions(+), 31 deletions(-) delete mode 100644 RHEL6/input/checks/core_dump_suid_progs_limits_conf.xml create mode 100644 RHEL6/input/checks/sysctl_fs_suid_dumpable.xml diff --git a/RHEL6/input/checks/core_dump_suid_progs_limits_conf.xml b/RHEL6/input/checks/core_dump_suid_progs_limits_conf.xml deleted file mode 100644 index 066957a..0000000 --- a/RHEL6/input/checks/core_dump_suid_progs_limits_conf.xml +++ /dev/null @@ -1,30 +0,0 @@ -<def-group> - <definition class="compliance" id="core_dump_suid_progs_limits_conf" - version="1"> - <metadata> - <title>Disable Core Dumps for setuid programs</title> - <affected family="unix"> - <platform>Red Hat Enterprise Linux 6</platform> - </affected> - <description>Core dumps for setuid programs should be - disabled</description> - </metadata> - <criteria> - <criterion comment="Are core dumps for setuid programs disabled?" - test_ref="test_core_dump_suid_progs_limits_conf" /> - </criteria> - </definition> - <ind:textfilecontent54_test check="all" check_existence="none_exist" - comment="Tests the value of the ^[\s]*fs\.suid_dumpable[\s]*=([\s]*) expression in the /etc/sysctl.conf file" - id="test_core_dump_suid_progs_limits_conf" version="2"> - <ind:object object_ref="object_core_dump_suid_progs_limits_conf" /> - </ind:textfilecontent54_test> - <ind:textfilecontent54_object id="object_core_dump_suid_progs_limits_conf" - version="1"> - <ind:path>/etc/security</ind:path> - <ind:filename>limits.conf</ind:filename> - <ind:pattern operation="pattern match"> - ^fs.suid_dumpable\s+=\s+1$</ind:pattern> - <ind:instance datatype="int">1</ind:instance> - </ind:textfilecontent54_object> -</def-group> diff --git a/RHEL6/input/checks/sysctl_fs_suid_dumpable.xml b/RHEL6/input/checks/sysctl_fs_suid_dumpable.xml new file mode 100644 index 0000000..e358366 --- /dev/null +++ b/RHEL6/input/checks/sysctl_fs_suid_dumpable.xml @@ -0,0 +1,28 @@ +<def-group> +  + <definition class="compliance" id="sysctl_fs_suid_dumpable" version="1"> + <metadata> + <title>Kernel Runtime Parameter "fs.suid_dumpable" Check</title> + <affected family="unix"> + <platform>Red Hat Enterprise Linux 6</platform> + </affected> + <description>The kernel runtime parameter "fs.suid_dumpable" should be set to "0".</description> + </metadata> + <criteria> + <criterion comment="kernel runtime parameter fs.suid_dumpable set to 0" test_ref="test_sysctl_fs_suid_dumpable" /> + </criteria> + </definition> + + <unix:sysctl_test check="all" check_existence="all_exist" comment="kernel runtime parameter fs.suid_dumpable set to 0" id="test_sysctl_fs_suid_dumpable" version="1"> + <unix:object object_ref="object_sysctl_fs_suid_dumpable" /> + <unix:state state_ref="state_sysctl_fs_suid_dumpable" /> + </unix:sysctl_test> + + <unix:sysctl_object id="object_sysctl_fs_suid_dumpable" version="1"> + <unix:name>fs.suid_dumpable</unix:name> + </unix:sysctl_object> + + <unix:sysctl_state id="state_sysctl_fs_suid_dumpable" version="1"> + <unix:value datatype="int" operation="equals">0</unix:value> + </unix:sysctl_state> +</def-group> diff --git a/RHEL6/input/checks/templates/sysctl_values.csv b/RHEL6/input/checks/templates/sysctl_values.csv index ae38b46..b318c47 100644 --- a/RHEL6/input/checks/templates/sysctl_values.csv +++ b/RHEL6/input/checks/templates/sysctl_values.csv @@ -17,3 +17,4 @@ net.ipv4.ip_forward,0 net.ipv4.tcp_syncookies,1 net.ipv6.conf.default.accept_redirects,0 net.ipv6.conf.default.accept_ra,0 +fs.suid_dumpable,0 diff --git a/RHEL6/input/system/permissions/execution.xml b/RHEL6/input/system/permissions/execution.xml index d742d60..86d2ea7 100644 --- a/RHEL6/input/system/permissions/execution.xml +++ b/RHEL6/input/system/permissions/execution.xml @@ -101,7 +101,7 @@ user who initiated execution of the program. Disabling the ability for any setuid program to write a core file decreases the risk of unauthorized access of such data.</rationale> <ident cce="27044-7" /> -<oval id="core_dump_suid_progs_limits_conf" /> +<oval id="sysctl_fs_suid_dumpable" /> <ref nist="SI-11" /> </Rule> </Group> -- 1.7.1

2 1

Rsyslog Permission Checks
by Maura Dailey 20 Aug '13

20 Aug '13

How do you think we should handle file owner and group permission checks on rsyslog files? Should we look for a predetermined list of files (trying to search for *.log is insufficient, since at the very least, /var/log/messages, /var/log/secure, and /var/log/maillog would get passed over)? Or should we try ninja regex to parse rsyslog.conf? - Maura Dailey

7 12

[PATCH] Guide refers to :omrelp: as a valid remote logging option, so I've updated the check to accept that format as well
by Maura Dailey 19 Aug '13

19 Aug '13

Signed-off-by: Maura Dailey <maura(a)eclipse.ncsc.mil> --- RHEL6/input/checks/rsyslog_remote_loghost.xml | 20 +++++++------------- 1 files changed, 7 insertions(+), 13 deletions(-) diff --git a/RHEL6/input/checks/rsyslog_remote_loghost.xml b/RHEL6/input/checks/rsyslog_remote_loghost.xml index b3ab6a8..81441eb 100644 --- a/RHEL6/input/checks/rsyslog_remote_loghost.xml +++ b/RHEL6/input/checks/rsyslog_remote_loghost.xml @@ -1,30 +1,24 @@ <def-group> - <definition class="compliance" - id="rsyslog_remote_loghost" version="1"> + <definition class="compliance" id="rsyslog_remote_loghost" version="1"> <metadata> <title>Send Logs to a Remote Loghost</title> <affected family="unix"> <platform>Red Hat Enterprise Linux 6</platform> </affected> - <description>Syslog logs should be sent to a remote - loghost</description> + <description>Syslog logs should be sent to a remote loghost</description> + <reference source="MED" ref_id="20130819" ref_url="test_attestation" /> </metadata> <criteria> - <criterion comment="Conditions are satisfied" - test_ref="test_rsyslog_remote_loghost" /> + <criterion comment="Conditions are satisfied" test_ref="test_rsyslog_remote_loghost" /> </criteria> </definition> - <ind:textfilecontent54_test check="all" - check_existence="all_exist" - comment="Tests the value of the \*\.\*[\s]+@ setting in the /etc/syslog.conf file" - id="test_rsyslog_remote_loghost" version="1"> + <ind:textfilecontent54_test check="all" check_existence="all_exist" comment="Tests the value of the \*\.\*[\s]+@ setting in the /etc/syslog.conf file" id="test_rsyslog_remote_loghost" version="1"> <ind:object object_ref="object_rsyslog_remote_loghost" /> </ind:textfilecontent54_test> - <ind:textfilecontent54_object id="object_rsyslog_remote_loghost" - version="1"> + <ind:textfilecontent54_object id="object_rsyslog_remote_loghost" version="1"> <ind:path>/etc</ind:path> <ind:filename>rsyslog.conf</ind:filename> - <ind:pattern operation="pattern match">^\*\.\*[\s]+@</ind:pattern> + <ind:pattern operation="pattern match">^\*\.\*[\s]+(?:@|\:omrelp\:)</ind:pattern> <ind:instance datatype="int">1</ind:instance> </ind:textfilecontent54_object> </def-group> -- 1.7.1

2 1

[PATCH] Adding reference tags to show test_attestation for various checks
by Maura Dailey 19 Aug '13

19 Aug '13

I intend to continue to test checks and commit tested results to checks. Here's the current batch I've completed from today and last week. - Maura Dailey Maura Dailey (1): Adding reference tags to show which checks I've tested. Some very slight whitespace corrections were made as well. .../checks/accounts_disable_post_pw_expiration.xml | 1 + .../checks/accounts_maximum_age_login_defs.xml | 1 + .../checks/accounts_minimum_age_login_defs.xml | 3 ++- RHEL6/input/checks/accounts_no_uid_except_zero.xml | 1 + RHEL6/input/checks/accounts_umask_bashrc.xml | 1 + RHEL6/input/checks/accounts_umask_cshrc.xml | 1 + RHEL6/input/checks/accounts_umask_etc_profile.xml | 1 + RHEL6/input/checks/accounts_umask_login_defs.xml | 1 + RHEL6/input/checks/core_dumps_limitsconf.xml | 4 ++-- .../checks/ensure_gpgcheck_never_disabled.xml | 9 ++++----- RHEL6/input/checks/file_owner_etc_group.xml | 1 + RHEL6/input/checks/file_owner_etc_gshadow.xml | 1 + RHEL6/input/checks/file_owner_etc_passwd.xml | 1 + RHEL6/input/checks/file_owner_etc_shadow.xml | 1 + RHEL6/input/checks/no_netrc_files.xml | 1 + RHEL6/input/checks/no_rsh_trust_files.xml | 3 ++- .../checks/yum_gpgcheck_global_activation.xml | 7 ++++--- 17 files changed, 26 insertions(+), 12 deletions(-)

3 3

[PATCH] Making SSH checks uniform and hopefully adding case insensitive matches properly
by Maura Dailey 19 Aug '13

19 Aug '13

There are a few things I did here. The first was to rewrite the regex to use (?i) for case insensitive matching. The second was to make the checks and the language in the comments uniform and run everything through tidy. The third was to test all the checks and add the test_attestation reference to each. - Maura Dailey Maura Dailey (1): Making SSH checks uniform and hopefully adding case insensitive matches properly RHEL6/input/checks/sshd_banner_set.xml | 24 +++++++-------- RHEL6/input/checks/sshd_clientalivecountmax.xml | 32 ++++++++----------- .../input/checks/sshd_hostbasedauthentication.xml | 19 ++++++++---- RHEL6/input/checks/sshd_idle_timeout.xml | 30 ++++++++++-------- RHEL6/input/checks/sshd_no_user_envset.xml | 24 ++++++-------- .../input/checks/sshd_permitemptypasswords_no.xml | 24 +++++++-------- RHEL6/input/checks/sshd_permitrootlogin_no.xml | 24 +++++++-------- RHEL6/input/checks/sshd_protocol_2.xml | 17 +++++++--- RHEL6/input/checks/sshd_rsh_emulation_disabled.xml | 24 +++++++-------- RHEL6/input/checks/sshd_use_approved_ciphers.xml | 28 ++++++++++------- 10 files changed, 126 insertions(+), 120 deletions(-)

2 2

[PATCH] Improbably, the input line for UDP is $UDPServerRun, not $InputUDPServerRun. Also, the check forgot to include the port number, so it always gave a false positive.
by Maura Dailey 19 Aug '13

19 Aug '13

This regex will match on $InputTCPServerRun, $InputRELPServerRun, and $UDPServerRun. - Maura Dailey Signed-off-by: Maura Dailey <maura(a)eclipse.ncsc.mil> --- RHEL6/input/checks/rsyslog_nolisten.xml | 21 +++++++++------------ 1 files changed, 9 insertions(+), 12 deletions(-) diff --git a/RHEL6/input/checks/rsyslog_nolisten.xml b/RHEL6/input/checks/rsyslog_nolisten.xml index 46cc285..d9376b6 100644 --- a/RHEL6/input/checks/rsyslog_nolisten.xml +++ b/RHEL6/input/checks/rsyslog_nolisten.xml @@ -1,31 +1,28 @@ <def-group> - <definition class="compliance" - id="rsyslog_nolisten" version="1"> + <definition class="compliance" id="rsyslog_nolisten" version="1"> <metadata> - <title>Disable Rsyslogd from Accepting Remote Messages on - Loghosts Only</title> + <title>Disable Rsyslogd from Accepting Remote Messages on Loghosts + Only</title> <affected family="unix"> <platform>Red Hat Enterprise Linux 6</platform> </affected> - <description>RSyslogd should reject remote - messages</description> + <description>rsyslogd should reject remote messages</description> + <reference source="MED" ref_id="20130819" ref_url="test_attestation" /> </metadata> <criteria> <criterion comment="Conditions are satisfied" test_ref="test_rsyslog_nolisten" /> </criteria> </definition> - <ind:textfilecontent54_test check="all" - check_existence="none_exist" - comment="Ensure that the /etc/rsyslog.conf does not contain $InputTCPServerRun | $InputUDPServerRun | $InputRELPServerRun" + <ind:textfilecontent54_test check="all" check_existence="none_exist" + comment="Ensure that the /etc/rsyslog.conf does not contain $InputTCPServerRun | $UDPServerRun | $InputRELPServerRun" id="test_rsyslog_nolisten" version="1"> <ind:object object_ref="object_rsyslog_nolisten" /> </ind:textfilecontent54_test> - <ind:textfilecontent54_object id="object_rsyslog_nolisten" - version="1"> + <ind:textfilecontent54_object id="object_rsyslog_nolisten" version="1"> <ind:path>/etc</ind:path> <ind:filename>rsyslog.conf</ind:filename> - <ind:pattern operation="pattern match">^\$Input(?:(TCP)|(UDP)|(RELP))ServerRun\s*$</ind:pattern> + <ind:pattern operation="pattern match">^\$(?:Input(?:TCP|RELP)|UDP)ServerRun</ind:pattern> <ind:instance datatype="int">1</ind:instance> </ind:textfilecontent54_object> </def-group> -- 1.7.1

1 0

Question on 'Verify File Hashes with RPM', and results in general
by Robert Sanders 15 Aug '13

15 Aug '13

Ok, I'm stumped now. I'm using the latest SSG content (downloaded today) on a RHEL6.4 64bit VM. On this box I loaded the latest SPAWAR release candidate as well as Security Blanket. Ran the scan, and this module passed, but it failed in Security Blanket. Poking through the SSG content I ran the command as indicated in the description manually and it *failed*. So looking in the check-content section for this rule I see 3 entries - one for the CCE reference one for a oval definition one for an ocil-transitional If I drill down through the oval definition it *looks* like there's an pattern match for only looking at things with a 'bin' as part of the path, which would skip the things that appeared to bork. Looked at the ocil-transitional definition I see a command using grep like I've *never* seen before (note the && was escaped in the xccdf file) description command -> rpm -Va | grep '^..5' check-content(ocil-trans) command -> rpm -Va | grep '$1 ~ /..5/ && $2 != "c"' So... question 1 - which command is actually being run? I'm assuming the one from the oval, as the ocil one doesn't make any sense to me unless the command is being mangled before execution, or someone snuck something into grep when I wasn't looking... Question 2 - Is there any way to have oscap spit out a log file of the commands/checks actually being run, so see why things may or may not have triggered a fail? Question 3 - If the command being run is actually from the oval, with the pathname pattern match, why doesn't the description detail the same exception? I've had this complaint with the RHEL5 STIG as well where there have been a few line items where the description says one thing and the actual check is doing some extra stuff. -Rob

2 2

Modifing report design
by Antonio Sebastian Salles M. 12 Aug '13

12 Aug '13

Hi all, Somebody knows how can I modify openscap report design? I need to put a logo in front and add contact information, and I cannot see any info in wiki. All info would be nice. Thanks a lot! -- Antonio Salles

2 1

Does aide_periodic_cron_checking have an incorrect fix documented?
by Hayden,Robert 09 Aug '13

09 Aug '13

I was reviewing the Rule: aide_periodic_cron_checking and noticed the following recommended fix: ----start quote---- To implement a daily execution of AIDE at 4:05am using cron, add the following line to /etc/crontab: 05 4 * * * root /usr/sbin/aide --check AIDE can be executed periodically through other means; this is merely one example. ---- end quote------ This fix is also documented in the RHEL STIG version 1 release 2. I believe that is an incorrect line for crontab as the 6th element is to be the executed command. On my RHEL 6.4 machine, "root" is not a valid command and I receive the following in local mail box # mail Heirloom Mail version 12.4 7/29/08. Type ? for help. "/var/spool/mail/root": 1 message 1 new >N 1 Cron Daemon Fri Aug 9 04:05 23/1036 "Cron <root@techval15> root /usr/sbin/aide --check" & 1 Message 1: From root(a)techval15.northamerica.cerner.net Fri Aug 9 04:05:01 2013 Return-Path: <root(a)techval15.northamerica.cerner.net> Date: Fri, 9 Aug 2013 04:05:01 -0500 From: root(a)techval15.northamerica.cerner.net (Cron Daemon) To: root(a)techval15.northamerica.cerner.net Subject: Cron <root@techval15> root /usr/sbin/aide --check Content-Type: text/plain; charset=ISO-8859-1 Auto-Submitted: auto-generated X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/root> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=root> X-Cron-Env: <USER=root> Status: R /bin/sh: root: command not found Am I missing something? Thanks Robert Robert Hayden | Sr. Technology Architect | Cerner Corporation | 816.201.4068 | rhayden(a)cerner.com<mailto:rhayden@cerner.com> | www.cerner.com CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.

3 3

[PATCH] Check needs to be reversed. As is, if you specified 10 as the maximum number of concurrent logins, it would allow 20.
by Maura Dailey 07 Aug '13

07 Aug '13

Self explanatory. I also added a test_attestation reference and corrected the comment for the external value. - Maura Dailey Signed-off-by: Maura Dailey <maura(a)eclipse.ncsc.mil> --- .../accounts_max_concurrent_login_sessions.xml | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/RHEL6/input/checks/accounts_max_concurrent_login_sessions.xml b/RHEL6/input/checks/accounts_max_concurrent_login_sessions.xml index eda8052..cb2e859 100644 --- a/RHEL6/input/checks/accounts_max_concurrent_login_sessions.xml +++ b/RHEL6/input/checks/accounts_max_concurrent_login_sessions.xml @@ -7,6 +7,7 @@ </affected> <description>The maximum number of concurrent login sessions per user should meet minimum requirements.</description> + <reference source="MED" ref_id="20130807" ref_url="test_attestation" /> </metadata> <criteria comment="the value maxlogins should be set appropriately in /etc/security/limits.conf"> <criterion test_ref="test_maxlogins" /> @@ -25,9 +26,9 @@ </ind:textfilecontent54_object> <ind:textfilecontent54_state id="state_maxlogins" version="1"> - <ind:subexpression operation="greater than or equal" var_ref="max_concurrent_login_sessions_value" datatype="int" /> + <ind:subexpression operation="less than or equal" var_ref="max_concurrent_login_sessions_value" datatype="int" /> </ind:textfilecontent54_state> - <external_variable comment="maximum password age" datatype="int" id="max_concurrent_login_sessions_value" version="1" /> + <external_variable comment="maximum number of concurrent logins per user" datatype="int" id="max_concurrent_login_sessions_value" version="1" /> </def-group> -- 1.7.1

2 1

Using OR operator for runlevel criteria
by Chen, Wei 07 Aug '13

07 Aug '13

Hello, Can someone explain the logic behind using the OR operator for runlevel test criteria? If runlevel 1 is set to true and runlevel 3 set to false, wouldn't the below criteria still return true? <criteria operator="OR" comment="service iptables is configured to start"> <criterion comment="iptables runlevel 0" test_ref="oval:ssg:tst:427"/> <criterion comment="iptables runlevel 1" test_ref="oval:ssg:tst:428"/> <criterion comment="iptables runlevel 2" test_ref="oval:ssg:tst:429"/> <criterion comment="iptables runlevel 3" test_ref="oval:ssg:tst:430"/> <criterion comment="iptables runlevel 4" test_ref="oval:ssg:tst:431"/> <criterion comment="iptables runlevel 5" test_ref="oval:ssg:tst:432"/> <criterion comment="iptables runlevel 6" test_ref="oval:ssg:tst:433"/> </criteria> Thanks, Wei Chen DS/SI/CS Chenw3(a)state.gov<mailto:Chenw3@state.gov> 571-345-2567

1 0

Suggestion on the 'Ensure All Files Are Owned...' items
by Robert Sanders 06 Aug '13

06 Aug '13

I was wondering why the tests for 'Ensure all Files Are Owned by a User' and 'Ensure all Files are Owned by a Group' kept on failing. Drilling down it looks like the underlying find command being used is along the lines of : find PARTITION -xdev -nouser -print When I run this command manually I've had complaints that find can't read files in /proc. Looking at the man page suggests this can be avoided by adding the '-ignore_readdir_race' option before the -xdev option. This change may need to be added for both SSG items 2.2.3.e and 2.2.3.f -Rob

7 22

[PATCH] Small patch to replace autogenerated ids with human readable ids
by Maura Dailey 06 Aug '13

06 Aug '13

I think some of these ids were leftover from the USGCB for RHEL 5. In any case, I've replaced them with human readable ones, which should make them easier to read for future editors. - Maura Dailey Maura Dailey (1): Small patch to replace autogenerated test, state, and object ids with human readable ones .../checks/accounts_root_path_dirs_no_write.xml | 57 +++++++------------- .../checks/core_dump_suid_progs_limits_conf.xml | 19 ++----- RHEL6/input/checks/core_dumps_limitsconf.xml | 23 +++----- RHEL6/input/checks/file_groupowner_etc_group.xml | 22 +++----- RHEL6/input/checks/file_groupowner_etc_gshadow.xml | 22 +++----- RHEL6/input/checks/file_groupowner_etc_passwd.xml | 22 +++----- RHEL6/input/checks/file_groupowner_etc_shadow.xml | 22 +++----- RHEL6/input/checks/file_owner_etc_group.xml | 22 +++----- RHEL6/input/checks/file_owner_etc_gshadow.xml | 22 +++----- RHEL6/input/checks/file_owner_etc_passwd.xml | 22 +++----- RHEL6/input/checks/file_permissions_etc_group.xml | 22 +++----- .../input/checks/file_permissions_ungroupowned.xml | 27 +++------ RHEL6/input/checks/interactive_boot_disable.xml | 18 ++---- 13 files changed, 112 insertions(+), 208 deletions(-)

2 5

MLS question from a new user
by Kordell, Luke T 06 Aug '13

06 Aug '13

Hello. I am new to SCAP and trying to determine how to modify a rule. I have downloaded the source code and have located an OVAL test I would like to change to suite my purposes. The file is selinux_policytype.xml. I have chosen this file because I am trying to make the SELinux enforcement rule pass for an MLS enforcement rather than targeted. My questions are as follows: The OVAL document references an object, test, state and variable but does not define them (as far as I can tell) within the OVAL file. Rather, it appears to be calling them from somewhere else. In particular I am referring to these lines. 13 test_ref = "test_selinux_policy" 21 object object_ref = obj_selinux_policy 22 state state_ref = state_selinux_policy Finally I think this is the variable I am going to need to change. var_ref = var_selinux_policy_name My question are: 1) where are these objects defined, and if it is possible how can I modify them? 2) Other than the OVAL website are there any other resources anyone can recommend that can help me learn this material? Luke

2 3

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

scap-security-guide August 2013