| Description | Tests | Scoring | |||||
|---|---|---|---|---|---|---|---|
| Pass | Fail | Error | Unkn. | Score | Max | Percent | |
| 1 Initial Setup | 16 | 13 | 0 | 0 | 16.0 | 29.0 | 55% |
| 1.1 Filesystem Configuration | 11 | 8 | 0 | 0 | 11.0 | 19.0 | 58% |
| 1.1.1 Disable unused filesystems | 0 | 8 | 0 | 0 | 0.0 | 8.0 | 0% |
| 1.2 Configure Software Updates | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
| 1.3 Filesystem Integrity Checking | 0 | 2 | 0 | 0 | 0.0 | 2.0 | 0% |
| 1.4 Secure Boot Settings | 0 | 2 | 0 | 0 | 0.0 | 2.0 | 0% |
| 1.5 Additional Process Hardening | 2 | 1 | 0 | 0 | 2.0 | 3.0 | 67% |
| 1.6 Mandatory Access Control | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
| 1.6.1 Configure SELinux | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
| 1.6.2 Configure AppArmor | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
| 1.7 Warning Banners | 3 | 0 | 0 | 0 | 3.0 | 3.0 | 100% |
| 1.7.1 Command Line Warning Banners | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
| 2 Services | 29 | 4 | 0 | 0 | 29.0 | 33.0 | 88% |
| 2.1 inetd Services | 10 | 0 | 0 | 0 | 10.0 | 10.0 | 100% |
| 2.2 Special Purpose Services | 15 | 3 | 0 | 0 | 15.0 | 18.0 | 83% |
| 2.2.1 Time Synchronization | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
| 2.3 Service Clients | 4 | 1 | 0 | 0 | 4.0 | 5.0 | 80% |
| 3 Network Configuration | 12 | 7 | 0 | 0 | 12.0 | 19.0 | 63% |
| 3.1 Network Parameters (Host Only) | 1 | 1 | 0 | 0 | 1.0 | 2.0 | 50% |
| 3.2 Network Parameters (Host and Router) | 6 | 2 | 0 | 0 | 6.0 | 8.0 | 75% |
| 3.3 IPv6 | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
| 3.4 TCP Wrappers | 4 | 1 | 0 | 0 | 4.0 | 5.0 | 80% |
| 3.5 Uncommon Network Protocols | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
| 3.6 Firewall Configuration | 1 | 3 | 0 | 0 | 1.0 | 4.0 | 25% |
| 4 Logging and Auditing | 5 | 2 | 0 | 0 | 5.0 | 7.0 | 71% |
| 4.1 Configure System Accounting (auditd) | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
| 4.1.1 Configure Data Retention | 0 | 0 | 0 | 0 | 0.0 | 0.0 | 0% |
| 4.2 Configure Logging | 5 | 2 | 0 | 0 | 5.0 | 7.0 | 71% |
| 4.2.1 Configure rsyslog | 2 | 1 | 0 | 0 | 2.0 | 3.0 | 67% |
| 4.2.2 Configure syslog-ng | 2 | 0 | 0 | 0 | 2.0 | 2.0 | 100% |
| 5 Access, Authentication and Authorization | 9 | 25 | 0 | 0 | 9.0 | 34.0 | 26% |
| 5.1 Configure cron | 1 | 7 | 0 | 0 | 1.0 | 8.0 | 12% |
| 5.2 SSH Server Configuration | 5 | 10 | 0 | 0 | 5.0 | 15.0 | 33% |
| 5.3 Configure PAM | 1 | 2 | 0 | 0 | 1.0 | 3.0 | 33% |
| 5.4 User Accounts and Environment | 2 | 5 | 0 | 0 | 2.0 | 7.0 | 29% |
| 5.4.1 Set Shadow Password Suite Parameters | 1 | 3 | 0 | 0 | 1.0 | 4.0 | 25% |
| 6 System Maintenance | 28 | 3 | 0 | 0 | 28.0 | 31.0 | 90% |
| 6.1 System File Permissions | 11 | 0 | 0 | 0 | 11.0 | 11.0 | 100% |
| 6.2 User and Group Settings | 17 | 3 | 0 | 0 | 17.0 | 20.0 | 85% |
| Total | 99 | 54 | 0 | 0 | 99.0 | 153.0 | 65% |
Note: Actual scores are subject to rounding errors. The sum of these values may not result in the exact overall score.
This benchmark contains 4 profiles.The Level 1 - Server profile was used for this assessment.
| Title | Description |
|---|---|
| Level 1 - Server |
Items in this profile intend to:
This profile is intended for servers. Show Profile XML
<Profile xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:sce="http://open-scap.org/page/SCE_xccdf_stream"
xmlns:cat="urn:oasis:names:tc:entity:xmlns:xml:catalog"
xmlns:ds="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
id="xccdf_org.cisecurity.benchmarks_profile_Level_1_-_Server">
<title xml:lang="en">Level 1 - Server</title>
<description xml:lang="en">
<p xmlns="http://www.w3.org/1999/xhtml">Items in this profile intend to:</p>
<ul xmlns="http://www.w3.org/1999/xhtml">
<li>be practical and prudent;</li>
<li>provide a clear security benefit; and</li>
<li>not inhibit the utility of the technology beyond acceptable means.</li>
</ul>
<p xmlns="http://www.w3.org/1999/xhtml">This profile is intended for servers.</p>
</description>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_mounting_of_cramfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_mounting_of_freevxfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_mounting_of_jffs2_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_mounting_of_hfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_mounting_of_hfsplus_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_mounting_of_squashfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_mounting_of_udf_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_mounting_of_FAT_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.3_Ensure_nodev_option_set_on_tmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.4_Ensure_nosuid_option_set_on_tmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.7_Ensure_nodev_option_set_on_vartmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.8_Ensure_nosuid_option_set_on_vartmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.9_Ensure_noexec_option_set_on_vartmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.13_Ensure_nodev_option_set_on_home_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.14_Ensure_nodev_option_set_on_runshm_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.15_Ensure_nosuid_option_set_on_runshm_partitionrun"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.16_Ensure_noexec_option_set_on_runshm_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.17_Ensure_nodev_option_set_on_removable_media_partitions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.18_Ensure_nosuid_option_set_on_removable_media_partitions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.19_Ensure_noexec_option_set_on_removable_media_partitions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.20_Ensure_sticky_bit_is_set_on_all_world-writable_directories"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.21_Disable_Automounting"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.1_Ensure_package_manager_repositories_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.2_Ensure_GPG_keys_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.3.1_Ensure_AIDE_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.3.2_Ensure_filesystem_integrity_is_regularly_checked"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_permissions_on_bootloader_config_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_bootloader_password_is_set"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.4.3_Ensure_authentication_required_for_single_user_mode"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_core_dumps_are_restricted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_XDNX_support_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_address_space_layout_randomization_ASLR_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.1_Ensure_message_of_the_day_is_configured_properly"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.2_Ensure_local_login_warning_banner_is_configured_properly"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.3_Ensure_remote_login_warning_banner_is_configured_properly"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.4_Ensure_permissions_on_etcmotd_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.5_Ensure_permissions_on_etcissue_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.6_Ensure_permissions_on_etcissue.net_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.8_Ensure_updates_patches_and_additional_security_software_are_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_chargen_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_daytime_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_discard_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_echo_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_time_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_rsh_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_talk_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_telnet_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_tftp_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_xinetd_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.1_Ensure_time_synchronization_is_in_use"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.2_Ensure_ntp_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.3_Ensure_chrony_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_X_Window_System_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_Avahi_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_CUPS_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_DHCP_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_LDAP_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.7_Ensure_NFS_and_RPC_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.8_Ensure_DNS_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.9_Ensure_FTP_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.10_Ensure_HTTP_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.11_Ensure_IMAP_and_POP3_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.12_Ensure_Samba_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.13_Ensure_HTTP_Proxy_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.14_Ensure_SNMP_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.15_Ensure_mail_transfer_agent_is_configured_for_local-only_mode"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.16_Ensure_rsync_service_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.17_Ensure_NIS_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1_Ensure_NIS_Client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2_Ensure_rsh_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.3_Ensure_talk_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4_Ensure_telnet_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.5_Ensure_LDAP_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IP_forwarding_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_packet_redirect_sending_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_source_routed_packets_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_ICMP_redirects_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_secure_ICMP_redirects_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_suspicious_packets_are_logged"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.5_Ensure_broadcast_ICMP_requests_are_ignored"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.6_Ensure_bogus_ICMP_responses_are_ignored"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.7_Ensure_Reverse_Path_Filtering_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.8_Ensure_TCP_SYN_Cookies_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_IPv6_router_advertisements_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_IPv6_redirects_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_IPv6_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.1_Ensure_TCP_Wrappers_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.2_Ensure_etchosts.allow_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.3_Ensure_etchosts.deny_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.4_Ensure_permissions_on_etchosts.allow_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.5_Ensure_permissions_on_etchosts.deny_are_644"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.1_Ensure_DCCP_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.2_Ensure_SCTP_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.3_Ensure_RDS_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.4_Ensure_TIPC_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.1_Ensure_iptables_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.2_Ensure_default_deny_firewall_policy"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.3_Ensure_loopback_traffic_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.4_Ensure_outbound_and_established_connections_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.5_Ensure_firewall_rules_exist_for_all_open_ports"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.7_Ensure_wireless_interfaces_are_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.1_Ensure_rsyslog_Service_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.2_Ensure_logging_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.3_Ensure_rsyslog_default_file_permissions_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.4_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.5_Ensure_remote_rsyslog_messages_are_only_accepted_on_designated_log_hosts."
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.1_Ensure_syslog-ng_service_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.2_Ensure_logging_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.3_Ensure_syslog-ng_default_file_permissions_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.4_Ensure_syslog-ng_is_configured_to_send_logs_to_a_remote_log_host"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.5_Ensure_remote_syslog-ng_messages_are_only_accepted_on_designated_log_hosts"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_rsyslog_or_syslog-ng_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_permissions_on_all_logfiles_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.3_Ensure_logrotate_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_cron_daemon_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_etccrontab_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_etccron.hourly_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_permissions_on_etccron.daily_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_permissions_on_etccron.weekly_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_permissions_on_etccron.monthly_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_permissions_on_etccron.d_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_atcron_is_restricted_to_authorized_users"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_permissions_on_etcsshsshd_config_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_SSH_Protocol_is_set_to_2"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_SSH_LogLevel_is_set_to_INFO"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_SSH_X11_forwarding_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_SSH_MaxAuthTries_is_set_to_4_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_SSH_IgnoreRhosts_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_SSH_HostbasedAuthentication_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.8_Ensure_SSH_root_login_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.9_Ensure_SSH_PermitEmptyPasswords_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.10_Ensure_SSH_PermitUserEnvironment_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.11_Ensure_only_approved_MAC_algorithms_are_used"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.12_Ensure_SSH_Idle_Timeout_Interval_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.13_Ensure_SSH_LoginGraceTime_is_set_to_one_minute_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.14_Ensure_SSH_access_is_limited"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.15_Ensure_SSH_warning_banner_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.1_Ensure_password_creation_requirements_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.2_Ensure_lockout_for_failed_password_attempts_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.3_Ensure_password_reuse_is_limited"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.4_Ensure_password_hashing_algorithm_is_SHA-512"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_90_days_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_days_between_password_changes_is_7_or_more"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_7_or_more"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_inactive_password_lock_is_30_days_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.2_Ensure_system_accounts_are_non-login"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.3_Ensure_default_group_for_the_root_account_is_GID_0"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.4_Ensure_default_user_umask_is_027_or_more_restrictive"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.5_Ensure_root_login_is_restricted_to_system_console"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.6_Ensure_access_to_the_su_command_is_restricted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.2_Ensure_permissions_on_etcpasswd_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.3_Ensure_permissions_on_etcshadow_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.4_Ensure_permissions_on_etcgroup_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.5_Ensure_permissions_on_etcgshadow_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.6_Ensure_permissions_on_etcpasswd-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.7_Ensure_permissions_on_etcshadow-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.8_Ensure_permissions_on_etcgroup-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.9_Ensure_permissions_on_etcgshadow-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.10_Ensure_no_world_writable_files_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.11_Ensure_no_unowned_files_or_directories_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.12_Ensure_no_ungrouped_files_or_directories_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.13_Audit_SUID_executables"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.14_Audit_SGID_executables"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.1_Ensure_password_fields_are_not_empty"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.2_Ensure_no_legacy__entries_exist_in_etcpasswd"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.3_Ensure_no_legacy__entries_exist_in_etcshadow"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.4_Ensure_no_legacy__entries_exist_in_etcgroup"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.5_Ensure_root_is_the_only_UID_0_account"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.6_Ensure_root_PATH_Integrity"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.7_Ensure_all_users_home_directories_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.8_Ensure_users_home_directories_permissions_are_750_or_more_restrictive"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.9_Ensure_users_own_their_home_directories"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.10_Ensure_users_dot_files_are_not_group_or_world_writable"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.11_Ensure_no_users_have_.forward_files"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.12_Ensure_no_users_have_.netrc_files"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.13_Ensure_users_.netrc_Files_are_not_group_or_world_accessible"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.14_Ensure_no_users_have_.rhosts_files"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.15_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.16_Ensure_no_duplicate_UIDs_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.17_Ensure_no_duplicate_GIDs_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.18_Ensure_no_duplicate_user_names_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.19_Ensure_no_duplicate_group_names_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.20_Ensure_shadow_group_is_empty"
selected="true"/>
</Profile>
|
| Level 2 - Server |
This profile extends the "Level 1 - Server" profile. Items in this profile exhibit one or more of the following characteristics:
This profile is intended for servers. Show Profile XML
<Profile xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:sce="http://open-scap.org/page/SCE_xccdf_stream"
xmlns:cat="urn:oasis:names:tc:entity:xmlns:xml:catalog"
xmlns:ds="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
id="xccdf_org.cisecurity.benchmarks_profile_Level_2_-_Server">
<title xml:lang="en">Level 2 - Server</title>
<description xml:lang="en">
<p xmlns="http://www.w3.org/1999/xhtml">This profile extends the "Level 1 - Server" profile. Items in this profile exhibit one or more of the following characteristics:</p>
<ul xmlns="http://www.w3.org/1999/xhtml">
<li>are intended for environments or use cases where security is paramount.</li>
<li>acts as defense in depth measure.</li>
<li>may negatively inhibit the utility or performance of the technology.</li>
</ul>
<p xmlns="http://www.w3.org/1999/xhtml">This profile is intended for servers.</p>
</description>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_mounting_of_cramfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_mounting_of_freevxfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_mounting_of_jffs2_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_mounting_of_hfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_mounting_of_hfsplus_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_mounting_of_squashfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_mounting_of_udf_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_mounting_of_FAT_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.2_Ensure_separate_partition_exists_for_tmp"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.3_Ensure_nodev_option_set_on_tmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.4_Ensure_nosuid_option_set_on_tmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.5_Ensure_separate_partition_exists_for_var"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.6_Ensure_separate_partition_exists_for_vartmp"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.7_Ensure_nodev_option_set_on_vartmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.8_Ensure_nosuid_option_set_on_vartmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.9_Ensure_noexec_option_set_on_vartmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.10_Ensure_separate_partition_exists_for_varlog"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.11_Ensure_separate_partition_exists_for_varlogaudit"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.12_Ensure_separate_partition_exists_for_home"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.13_Ensure_nodev_option_set_on_home_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.14_Ensure_nodev_option_set_on_runshm_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.15_Ensure_nosuid_option_set_on_runshm_partitionrun"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.16_Ensure_noexec_option_set_on_runshm_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.17_Ensure_nodev_option_set_on_removable_media_partitions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.18_Ensure_nosuid_option_set_on_removable_media_partitions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.19_Ensure_noexec_option_set_on_removable_media_partitions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.20_Ensure_sticky_bit_is_set_on_all_world-writable_directories"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.21_Disable_Automounting"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.1_Ensure_package_manager_repositories_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.2_Ensure_GPG_keys_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.3.1_Ensure_AIDE_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.3.2_Ensure_filesystem_integrity_is_regularly_checked"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_permissions_on_bootloader_config_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_bootloader_password_is_set"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.4.3_Ensure_authentication_required_for_single_user_mode"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_core_dumps_are_restricted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_XDNX_support_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_address_space_layout_randomization_ASLR_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.1.1_Ensure_SELinux_is_not_disabled_in_bootloader_configuration"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.1.2_Ensure_the_SELinux_state_is_enforcing"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.1.3_Ensure_SELinux_policy_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.1.4_Ensure_no_unconfined_daemons_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.2.1_Ensure_AppArmor_is_not_disabled_in_bootloader_configuration"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.2.2_Ensure_all_AppArmor_Profiles_are_enforcing"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_SELinux_or_AppArmor_are_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.1_Ensure_message_of_the_day_is_configured_properly"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.2_Ensure_local_login_warning_banner_is_configured_properly"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.3_Ensure_remote_login_warning_banner_is_configured_properly"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.4_Ensure_permissions_on_etcmotd_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.5_Ensure_permissions_on_etcissue_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.6_Ensure_permissions_on_etcissue.net_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.8_Ensure_updates_patches_and_additional_security_software_are_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_chargen_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_daytime_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_discard_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_echo_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_time_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_rsh_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_talk_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_telnet_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_tftp_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_xinetd_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.1_Ensure_time_synchronization_is_in_use"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.2_Ensure_ntp_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.3_Ensure_chrony_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_X_Window_System_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_Avahi_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_CUPS_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_DHCP_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_LDAP_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.7_Ensure_NFS_and_RPC_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.8_Ensure_DNS_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.9_Ensure_FTP_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.10_Ensure_HTTP_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.11_Ensure_IMAP_and_POP3_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.12_Ensure_Samba_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.13_Ensure_HTTP_Proxy_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.14_Ensure_SNMP_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.15_Ensure_mail_transfer_agent_is_configured_for_local-only_mode"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.16_Ensure_rsync_service_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.17_Ensure_NIS_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1_Ensure_NIS_Client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2_Ensure_rsh_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.3_Ensure_talk_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4_Ensure_telnet_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.5_Ensure_LDAP_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IP_forwarding_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_packet_redirect_sending_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_source_routed_packets_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_ICMP_redirects_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_secure_ICMP_redirects_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_suspicious_packets_are_logged"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.5_Ensure_broadcast_ICMP_requests_are_ignored"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.6_Ensure_bogus_ICMP_responses_are_ignored"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.7_Ensure_Reverse_Path_Filtering_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.8_Ensure_TCP_SYN_Cookies_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_IPv6_router_advertisements_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_IPv6_redirects_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_IPv6_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.1_Ensure_TCP_Wrappers_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.2_Ensure_etchosts.allow_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.3_Ensure_etchosts.deny_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.4_Ensure_permissions_on_etchosts.allow_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.5_Ensure_permissions_on_etchosts.deny_are_644"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.1_Ensure_DCCP_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.2_Ensure_SCTP_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.3_Ensure_RDS_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.4_Ensure_TIPC_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.1_Ensure_iptables_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.2_Ensure_default_deny_firewall_policy"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.3_Ensure_loopback_traffic_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.4_Ensure_outbound_and_established_connections_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.5_Ensure_firewall_rules_exist_for_all_open_ports"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.7_Ensure_wireless_interfaces_are_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.1.1_Ensure_audit_log_storage_size_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.1.2_Ensure_system_is_disabled_when_audit_logs_are_full"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.1.3_Ensure_audit_logs_are_not_automatically_deleted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.2_Ensure_auditd_service_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.3_Ensure_auditing_for_processes_that_start_prior_to_auditd_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.4_Ensure_events_that_modify_date_and_time_information_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.5_Ensure_events_that_modify_usergroup_information_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.6_Ensure_events_that_modify_the_systems_network_environment_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.7_Ensure_events_that_modify_the_systems_Mandatory_Access_Controls_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.8_Ensure_login_and_logout_events_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.9_Ensure_session_initiation_information_is_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.10_Ensure_discretionary_access_control_permission_modification_events_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.11_Ensure_unsuccessful_unauthorized_file_access_attempts_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.12_Ensure_use_of_privileged_commands_is_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.13_Ensure_successful_file_system_mounts_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.14_Ensure_file_deletion_events_by_users_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.15_Ensure_changes_to_system_administration_scope_sudoers_is_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.16_Ensure_system_administrator_actions_sudolog_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.17_Ensure_kernel_module_loading_and_unloading_is_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.18_Ensure_the_audit_configuration_is_immutable"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.1_Ensure_rsyslog_Service_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.2_Ensure_logging_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.3_Ensure_rsyslog_default_file_permissions_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.4_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.5_Ensure_remote_rsyslog_messages_are_only_accepted_on_designated_log_hosts."
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.1_Ensure_syslog-ng_service_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.2_Ensure_logging_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.3_Ensure_syslog-ng_default_file_permissions_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.4_Ensure_syslog-ng_is_configured_to_send_logs_to_a_remote_log_host"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.5_Ensure_remote_syslog-ng_messages_are_only_accepted_on_designated_log_hosts"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_rsyslog_or_syslog-ng_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_permissions_on_all_logfiles_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.3_Ensure_logrotate_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_cron_daemon_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_etccrontab_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_etccron.hourly_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_permissions_on_etccron.daily_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_permissions_on_etccron.weekly_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_permissions_on_etccron.monthly_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_permissions_on_etccron.d_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_atcron_is_restricted_to_authorized_users"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_permissions_on_etcsshsshd_config_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_SSH_Protocol_is_set_to_2"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_SSH_LogLevel_is_set_to_INFO"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_SSH_X11_forwarding_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_SSH_MaxAuthTries_is_set_to_4_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_SSH_IgnoreRhosts_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_SSH_HostbasedAuthentication_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.8_Ensure_SSH_root_login_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.9_Ensure_SSH_PermitEmptyPasswords_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.10_Ensure_SSH_PermitUserEnvironment_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.11_Ensure_only_approved_MAC_algorithms_are_used"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.12_Ensure_SSH_Idle_Timeout_Interval_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.13_Ensure_SSH_LoginGraceTime_is_set_to_one_minute_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.14_Ensure_SSH_access_is_limited"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.15_Ensure_SSH_warning_banner_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.1_Ensure_password_creation_requirements_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.2_Ensure_lockout_for_failed_password_attempts_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.3_Ensure_password_reuse_is_limited"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.4_Ensure_password_hashing_algorithm_is_SHA-512"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_90_days_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_days_between_password_changes_is_7_or_more"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_7_or_more"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_inactive_password_lock_is_30_days_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.2_Ensure_system_accounts_are_non-login"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.3_Ensure_default_group_for_the_root_account_is_GID_0"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.4_Ensure_default_user_umask_is_027_or_more_restrictive"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.5_Ensure_root_login_is_restricted_to_system_console"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.6_Ensure_access_to_the_su_command_is_restricted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.1_Audit_system_file_permissions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.2_Ensure_permissions_on_etcpasswd_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.3_Ensure_permissions_on_etcshadow_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.4_Ensure_permissions_on_etcgroup_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.5_Ensure_permissions_on_etcgshadow_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.6_Ensure_permissions_on_etcpasswd-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.7_Ensure_permissions_on_etcshadow-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.8_Ensure_permissions_on_etcgroup-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.9_Ensure_permissions_on_etcgshadow-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.10_Ensure_no_world_writable_files_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.11_Ensure_no_unowned_files_or_directories_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.12_Ensure_no_ungrouped_files_or_directories_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.13_Audit_SUID_executables"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.14_Audit_SGID_executables"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.1_Ensure_password_fields_are_not_empty"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.2_Ensure_no_legacy__entries_exist_in_etcpasswd"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.3_Ensure_no_legacy__entries_exist_in_etcshadow"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.4_Ensure_no_legacy__entries_exist_in_etcgroup"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.5_Ensure_root_is_the_only_UID_0_account"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.6_Ensure_root_PATH_Integrity"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.7_Ensure_all_users_home_directories_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.8_Ensure_users_home_directories_permissions_are_750_or_more_restrictive"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.9_Ensure_users_own_their_home_directories"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.10_Ensure_users_dot_files_are_not_group_or_world_writable"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.11_Ensure_no_users_have_.forward_files"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.12_Ensure_no_users_have_.netrc_files"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.13_Ensure_users_.netrc_Files_are_not_group_or_world_accessible"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.14_Ensure_no_users_have_.rhosts_files"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.15_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.16_Ensure_no_duplicate_UIDs_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.17_Ensure_no_duplicate_GIDs_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.18_Ensure_no_duplicate_user_names_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.19_Ensure_no_duplicate_group_names_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.20_Ensure_shadow_group_is_empty"
selected="true"/>
</Profile>
|
| Level 1 - Workstation |
Items in this profile intend to:
This profile is intended for workstations. Show Profile XML
<Profile xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:sce="http://open-scap.org/page/SCE_xccdf_stream"
xmlns:cat="urn:oasis:names:tc:entity:xmlns:xml:catalog"
xmlns:ds="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
id="xccdf_org.cisecurity.benchmarks_profile_Level_1_-_Workstation">
<title xml:lang="en">Level 1 - Workstation</title>
<description xml:lang="en">
<p xmlns="http://www.w3.org/1999/xhtml">Items in this profile intend to:</p>
<ul xmlns="http://www.w3.org/1999/xhtml">
<li>be practical and prudent;</li>
<li>provide a clear security benefit; and</li>
<li>not inhibit the utility of the technology beyond acceptable means.</li>
</ul>
<p xmlns="http://www.w3.org/1999/xhtml">This profile is intended for workstations.</p>
</description>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_mounting_of_cramfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_mounting_of_freevxfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_mounting_of_jffs2_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_mounting_of_hfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_mounting_of_hfsplus_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_mounting_of_squashfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_mounting_of_udf_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.3_Ensure_nodev_option_set_on_tmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.4_Ensure_nosuid_option_set_on_tmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.7_Ensure_nodev_option_set_on_vartmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.8_Ensure_nosuid_option_set_on_vartmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.9_Ensure_noexec_option_set_on_vartmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.13_Ensure_nodev_option_set_on_home_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.14_Ensure_nodev_option_set_on_runshm_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.15_Ensure_nosuid_option_set_on_runshm_partitionrun"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.16_Ensure_noexec_option_set_on_runshm_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.17_Ensure_nodev_option_set_on_removable_media_partitions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.18_Ensure_nosuid_option_set_on_removable_media_partitions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.19_Ensure_noexec_option_set_on_removable_media_partitions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.20_Ensure_sticky_bit_is_set_on_all_world-writable_directories"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.1_Ensure_package_manager_repositories_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.2_Ensure_GPG_keys_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.3.1_Ensure_AIDE_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.3.2_Ensure_filesystem_integrity_is_regularly_checked"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_permissions_on_bootloader_config_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_bootloader_password_is_set"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.4.3_Ensure_authentication_required_for_single_user_mode"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_core_dumps_are_restricted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_XDNX_support_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_address_space_layout_randomization_ASLR_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.1_Ensure_message_of_the_day_is_configured_properly"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.2_Ensure_local_login_warning_banner_is_configured_properly"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.3_Ensure_remote_login_warning_banner_is_configured_properly"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.4_Ensure_permissions_on_etcmotd_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.5_Ensure_permissions_on_etcissue_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.6_Ensure_permissions_on_etcissue.net_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.8_Ensure_updates_patches_and_additional_security_software_are_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_chargen_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_daytime_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_discard_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_echo_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_time_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_rsh_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_talk_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_telnet_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_tftp_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_xinetd_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.1_Ensure_time_synchronization_is_in_use"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.2_Ensure_ntp_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.3_Ensure_chrony_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_Avahi_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_DHCP_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_LDAP_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.7_Ensure_NFS_and_RPC_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.8_Ensure_DNS_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.9_Ensure_FTP_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.10_Ensure_HTTP_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.11_Ensure_IMAP_and_POP3_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.12_Ensure_Samba_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.13_Ensure_HTTP_Proxy_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.14_Ensure_SNMP_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.15_Ensure_mail_transfer_agent_is_configured_for_local-only_mode"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.16_Ensure_rsync_service_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.17_Ensure_NIS_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1_Ensure_NIS_Client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2_Ensure_rsh_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.3_Ensure_talk_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4_Ensure_telnet_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.5_Ensure_LDAP_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IP_forwarding_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_packet_redirect_sending_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_source_routed_packets_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_ICMP_redirects_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_secure_ICMP_redirects_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_suspicious_packets_are_logged"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.5_Ensure_broadcast_ICMP_requests_are_ignored"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.6_Ensure_bogus_ICMP_responses_are_ignored"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.7_Ensure_Reverse_Path_Filtering_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.8_Ensure_TCP_SYN_Cookies_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_IPv6_router_advertisements_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_IPv6_redirects_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_IPv6_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.1_Ensure_TCP_Wrappers_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.2_Ensure_etchosts.allow_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.3_Ensure_etchosts.deny_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.4_Ensure_permissions_on_etchosts.allow_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.5_Ensure_permissions_on_etchosts.deny_are_644"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.1_Ensure_DCCP_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.2_Ensure_SCTP_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.3_Ensure_RDS_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.4_Ensure_TIPC_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.1_Ensure_iptables_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.2_Ensure_default_deny_firewall_policy"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.3_Ensure_loopback_traffic_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.4_Ensure_outbound_and_established_connections_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.5_Ensure_firewall_rules_exist_for_all_open_ports"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.1_Ensure_rsyslog_Service_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.2_Ensure_logging_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.3_Ensure_rsyslog_default_file_permissions_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.4_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.5_Ensure_remote_rsyslog_messages_are_only_accepted_on_designated_log_hosts."
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.1_Ensure_syslog-ng_service_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.2_Ensure_logging_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.3_Ensure_syslog-ng_default_file_permissions_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.4_Ensure_syslog-ng_is_configured_to_send_logs_to_a_remote_log_host"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.5_Ensure_remote_syslog-ng_messages_are_only_accepted_on_designated_log_hosts"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_rsyslog_or_syslog-ng_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_permissions_on_all_logfiles_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.3_Ensure_logrotate_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_cron_daemon_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_etccrontab_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_etccron.hourly_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_permissions_on_etccron.daily_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_permissions_on_etccron.weekly_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_permissions_on_etccron.monthly_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_permissions_on_etccron.d_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_atcron_is_restricted_to_authorized_users"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_permissions_on_etcsshsshd_config_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_SSH_Protocol_is_set_to_2"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_SSH_LogLevel_is_set_to_INFO"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_SSH_X11_forwarding_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_SSH_MaxAuthTries_is_set_to_4_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_SSH_IgnoreRhosts_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_SSH_HostbasedAuthentication_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.8_Ensure_SSH_root_login_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.9_Ensure_SSH_PermitEmptyPasswords_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.10_Ensure_SSH_PermitUserEnvironment_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.11_Ensure_only_approved_MAC_algorithms_are_used"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.12_Ensure_SSH_Idle_Timeout_Interval_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.13_Ensure_SSH_LoginGraceTime_is_set_to_one_minute_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.14_Ensure_SSH_access_is_limited"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.15_Ensure_SSH_warning_banner_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.1_Ensure_password_creation_requirements_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.2_Ensure_lockout_for_failed_password_attempts_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.3_Ensure_password_reuse_is_limited"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.4_Ensure_password_hashing_algorithm_is_SHA-512"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_90_days_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_days_between_password_changes_is_7_or_more"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_7_or_more"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_inactive_password_lock_is_30_days_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.2_Ensure_system_accounts_are_non-login"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.3_Ensure_default_group_for_the_root_account_is_GID_0"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.4_Ensure_default_user_umask_is_027_or_more_restrictive"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.5_Ensure_root_login_is_restricted_to_system_console"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.6_Ensure_access_to_the_su_command_is_restricted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.2_Ensure_permissions_on_etcpasswd_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.3_Ensure_permissions_on_etcshadow_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.4_Ensure_permissions_on_etcgroup_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.5_Ensure_permissions_on_etcgshadow_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.6_Ensure_permissions_on_etcpasswd-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.7_Ensure_permissions_on_etcshadow-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.8_Ensure_permissions_on_etcgroup-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.9_Ensure_permissions_on_etcgshadow-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.10_Ensure_no_world_writable_files_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.11_Ensure_no_unowned_files_or_directories_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.12_Ensure_no_ungrouped_files_or_directories_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.13_Audit_SUID_executables"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.14_Audit_SGID_executables"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.1_Ensure_password_fields_are_not_empty"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.2_Ensure_no_legacy__entries_exist_in_etcpasswd"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.3_Ensure_no_legacy__entries_exist_in_etcshadow"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.4_Ensure_no_legacy__entries_exist_in_etcgroup"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.5_Ensure_root_is_the_only_UID_0_account"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.6_Ensure_root_PATH_Integrity"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.7_Ensure_all_users_home_directories_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.8_Ensure_users_home_directories_permissions_are_750_or_more_restrictive"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.9_Ensure_users_own_their_home_directories"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.10_Ensure_users_dot_files_are_not_group_or_world_writable"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.11_Ensure_no_users_have_.forward_files"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.12_Ensure_no_users_have_.netrc_files"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.13_Ensure_users_.netrc_Files_are_not_group_or_world_accessible"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.14_Ensure_no_users_have_.rhosts_files"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.15_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.16_Ensure_no_duplicate_UIDs_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.17_Ensure_no_duplicate_GIDs_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.18_Ensure_no_duplicate_user_names_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.19_Ensure_no_duplicate_group_names_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.20_Ensure_shadow_group_is_empty"
selected="true"/>
</Profile>
|
| Level 2 - Workstation |
This profile extends the "Level 1 - Workstation" profile. Items in this profile exhibit one or more of the following characteristics:
This profile is intended for workstations. Show Profile XML
<Profile xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:sce="http://open-scap.org/page/SCE_xccdf_stream"
xmlns:cat="urn:oasis:names:tc:entity:xmlns:xml:catalog"
xmlns:ds="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
id="xccdf_org.cisecurity.benchmarks_profile_Level_2_-_Workstation">
<title xml:lang="en">Level 2 - Workstation</title>
<description xml:lang="en">
<p xmlns="http://www.w3.org/1999/xhtml">This profile extends the "Level 1 - Workstation" profile. Items in this profile exhibit one or more of the following characteristics:</p>
<ul xmlns="http://www.w3.org/1999/xhtml">
<li>are intended for environments or use cases where security is paramount.</li>
<li>acts as defense in depth measure.</li>
<li>may negatively inhibit the utility or performance of the technology.</li>
</ul>
<p xmlns="http://www.w3.org/1999/xhtml">This profile is intended for workstations.</p>
</description>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_mounting_of_cramfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_mounting_of_freevxfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_mounting_of_jffs2_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_mounting_of_hfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_mounting_of_hfsplus_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_mounting_of_squashfs_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_mounting_of_udf_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_mounting_of_FAT_filesystems_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.2_Ensure_separate_partition_exists_for_tmp"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.3_Ensure_nodev_option_set_on_tmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.4_Ensure_nosuid_option_set_on_tmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.5_Ensure_separate_partition_exists_for_var"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.6_Ensure_separate_partition_exists_for_vartmp"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.7_Ensure_nodev_option_set_on_vartmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.8_Ensure_nosuid_option_set_on_vartmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.9_Ensure_noexec_option_set_on_vartmp_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.10_Ensure_separate_partition_exists_for_varlog"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.11_Ensure_separate_partition_exists_for_varlogaudit"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.12_Ensure_separate_partition_exists_for_home"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.13_Ensure_nodev_option_set_on_home_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.14_Ensure_nodev_option_set_on_runshm_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.15_Ensure_nosuid_option_set_on_runshm_partitionrun"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.16_Ensure_noexec_option_set_on_runshm_partition"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.17_Ensure_nodev_option_set_on_removable_media_partitions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.18_Ensure_nosuid_option_set_on_removable_media_partitions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.19_Ensure_noexec_option_set_on_removable_media_partitions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.20_Ensure_sticky_bit_is_set_on_all_world-writable_directories"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.1.21_Disable_Automounting"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.1_Ensure_package_manager_repositories_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.2.2_Ensure_GPG_keys_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.3.1_Ensure_AIDE_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.3.2_Ensure_filesystem_integrity_is_regularly_checked"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_permissions_on_bootloader_config_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_bootloader_password_is_set"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.4.3_Ensure_authentication_required_for_single_user_mode"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_core_dumps_are_restricted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_XDNX_support_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_address_space_layout_randomization_ASLR_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.1.1_Ensure_SELinux_is_not_disabled_in_bootloader_configuration"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.1.2_Ensure_the_SELinux_state_is_enforcing"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.1.3_Ensure_SELinux_policy_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.1.4_Ensure_no_unconfined_daemons_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.2.1_Ensure_AppArmor_is_not_disabled_in_bootloader_configuration"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.2.2_Ensure_all_AppArmor_Profiles_are_enforcing"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.6.3_Ensure_SELinux_or_AppArmor_are_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.1_Ensure_message_of_the_day_is_configured_properly"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.2_Ensure_local_login_warning_banner_is_configured_properly"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.3_Ensure_remote_login_warning_banner_is_configured_properly"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.4_Ensure_permissions_on_etcmotd_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.5_Ensure_permissions_on_etcissue_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.6_Ensure_permissions_on_etcissue.net_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_1.8_Ensure_updates_patches_and_additional_security_software_are_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_chargen_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_daytime_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_discard_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_echo_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_time_services_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_rsh_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_talk_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_telnet_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_tftp_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_xinetd_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.1_Ensure_time_synchronization_is_in_use"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.2_Ensure_ntp_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.3_Ensure_chrony_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_Avahi_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_CUPS_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_DHCP_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_LDAP_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.7_Ensure_NFS_and_RPC_are_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.8_Ensure_DNS_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.9_Ensure_FTP_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.10_Ensure_HTTP_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.11_Ensure_IMAP_and_POP3_server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.12_Ensure_Samba_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.13_Ensure_HTTP_Proxy_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.14_Ensure_SNMP_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.15_Ensure_mail_transfer_agent_is_configured_for_local-only_mode"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.16_Ensure_rsync_service_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.2.17_Ensure_NIS_Server_is_not_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1_Ensure_NIS_Client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2_Ensure_rsh_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.3_Ensure_talk_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4_Ensure_telnet_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_2.3.5_Ensure_LDAP_client_is_not_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IP_forwarding_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_packet_redirect_sending_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_source_routed_packets_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_ICMP_redirects_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_secure_ICMP_redirects_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_suspicious_packets_are_logged"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.5_Ensure_broadcast_ICMP_requests_are_ignored"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.6_Ensure_bogus_ICMP_responses_are_ignored"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.7_Ensure_Reverse_Path_Filtering_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.2.8_Ensure_TCP_SYN_Cookies_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_IPv6_router_advertisements_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_IPv6_redirects_are_not_accepted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_IPv6_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.1_Ensure_TCP_Wrappers_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.2_Ensure_etchosts.allow_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.3_Ensure_etchosts.deny_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.4_Ensure_permissions_on_etchosts.allow_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.4.5_Ensure_permissions_on_etchosts.deny_are_644"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.1_Ensure_DCCP_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.2_Ensure_SCTP_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.3_Ensure_RDS_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.5.4_Ensure_TIPC_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.1_Ensure_iptables_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.2_Ensure_default_deny_firewall_policy"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.3_Ensure_loopback_traffic_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.4_Ensure_outbound_and_established_connections_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.6.5_Ensure_firewall_rules_exist_for_all_open_ports"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_3.7_Ensure_wireless_interfaces_are_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.1.1_Ensure_audit_log_storage_size_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.1.2_Ensure_system_is_disabled_when_audit_logs_are_full"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.1.3_Ensure_audit_logs_are_not_automatically_deleted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.2_Ensure_auditd_service_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.3_Ensure_auditing_for_processes_that_start_prior_to_auditd_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.4_Ensure_events_that_modify_date_and_time_information_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.5_Ensure_events_that_modify_usergroup_information_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.6_Ensure_events_that_modify_the_systems_network_environment_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.7_Ensure_events_that_modify_the_systems_Mandatory_Access_Controls_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.8_Ensure_login_and_logout_events_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.9_Ensure_session_initiation_information_is_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.10_Ensure_discretionary_access_control_permission_modification_events_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.11_Ensure_unsuccessful_unauthorized_file_access_attempts_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.12_Ensure_use_of_privileged_commands_is_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.13_Ensure_successful_file_system_mounts_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.14_Ensure_file_deletion_events_by_users_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.15_Ensure_changes_to_system_administration_scope_sudoers_is_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.16_Ensure_system_administrator_actions_sudolog_are_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.17_Ensure_kernel_module_loading_and_unloading_is_collected"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.1.18_Ensure_the_audit_configuration_is_immutable"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.1_Ensure_rsyslog_Service_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.2_Ensure_logging_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.3_Ensure_rsyslog_default_file_permissions_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.4_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.5_Ensure_remote_rsyslog_messages_are_only_accepted_on_designated_log_hosts."
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.1_Ensure_syslog-ng_service_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.2_Ensure_logging_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.3_Ensure_syslog-ng_default_file_permissions_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.4_Ensure_syslog-ng_is_configured_to_send_logs_to_a_remote_log_host"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.5_Ensure_remote_syslog-ng_messages_are_only_accepted_on_designated_log_hosts"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_rsyslog_or_syslog-ng_is_installed"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_permissions_on_all_logfiles_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_4.3_Ensure_logrotate_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_cron_daemon_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_etccrontab_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_etccron.hourly_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_permissions_on_etccron.daily_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_permissions_on_etccron.weekly_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_permissions_on_etccron.monthly_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_permissions_on_etccron.d_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_atcron_is_restricted_to_authorized_users"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_permissions_on_etcsshsshd_config_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_SSH_Protocol_is_set_to_2"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_SSH_LogLevel_is_set_to_INFO"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_SSH_X11_forwarding_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_SSH_MaxAuthTries_is_set_to_4_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_SSH_IgnoreRhosts_is_enabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_SSH_HostbasedAuthentication_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.8_Ensure_SSH_root_login_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.9_Ensure_SSH_PermitEmptyPasswords_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.10_Ensure_SSH_PermitUserEnvironment_is_disabled"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.11_Ensure_only_approved_MAC_algorithms_are_used"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.12_Ensure_SSH_Idle_Timeout_Interval_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.13_Ensure_SSH_LoginGraceTime_is_set_to_one_minute_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.14_Ensure_SSH_access_is_limited"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.2.15_Ensure_SSH_warning_banner_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.1_Ensure_password_creation_requirements_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.2_Ensure_lockout_for_failed_password_attempts_is_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.3_Ensure_password_reuse_is_limited"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.3.4_Ensure_password_hashing_algorithm_is_SHA-512"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_90_days_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_days_between_password_changes_is_7_or_more"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_7_or_more"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_inactive_password_lock_is_30_days_or_less"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.2_Ensure_system_accounts_are_non-login"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.3_Ensure_default_group_for_the_root_account_is_GID_0"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.4.4_Ensure_default_user_umask_is_027_or_more_restrictive"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.5_Ensure_root_login_is_restricted_to_system_console"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_5.6_Ensure_access_to_the_su_command_is_restricted"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.1_Audit_system_file_permissions"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.2_Ensure_permissions_on_etcpasswd_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.3_Ensure_permissions_on_etcshadow_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.4_Ensure_permissions_on_etcgroup_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.5_Ensure_permissions_on_etcgshadow_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.6_Ensure_permissions_on_etcpasswd-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.7_Ensure_permissions_on_etcshadow-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.8_Ensure_permissions_on_etcgroup-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.9_Ensure_permissions_on_etcgshadow-_are_configured"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.10_Ensure_no_world_writable_files_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.11_Ensure_no_unowned_files_or_directories_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.12_Ensure_no_ungrouped_files_or_directories_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.13_Audit_SUID_executables"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.1.14_Audit_SGID_executables"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.1_Ensure_password_fields_are_not_empty"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.2_Ensure_no_legacy__entries_exist_in_etcpasswd"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.3_Ensure_no_legacy__entries_exist_in_etcshadow"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.4_Ensure_no_legacy__entries_exist_in_etcgroup"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.5_Ensure_root_is_the_only_UID_0_account"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.6_Ensure_root_PATH_Integrity"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.7_Ensure_all_users_home_directories_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.8_Ensure_users_home_directories_permissions_are_750_or_more_restrictive"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.9_Ensure_users_own_their_home_directories"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.10_Ensure_users_dot_files_are_not_group_or_world_writable"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.11_Ensure_no_users_have_.forward_files"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.12_Ensure_no_users_have_.netrc_files"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.13_Ensure_users_.netrc_Files_are_not_group_or_world_accessible"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.14_Ensure_no_users_have_.rhosts_files"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.15_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.16_Ensure_no_duplicate_UIDs_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.17_Ensure_no_duplicate_GIDs_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.18_Ensure_no_duplicate_user_names_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.19_Ensure_no_duplicate_group_names_exist"
selected="true"/>
<select idref="xccdf_org.cisecurity.benchmarks_rule_6.2.20_Ensure_shadow_group_is_empty"
selected="true"/>
</Profile>
|
Items in this section are advised for all systems, but may be difficult or require extensive preparation after the initial setup of the system.
Directories that are used for system-wide functions can be further protected by placing them on separate partitions. This provides protection for resource exhaustion and enables the use of mounting options that are applicable to the directory's intended use. Users' data can be stored on separate partitions and have stricter mount options. A user partition is a filesystem that has been established for use by the users and does not contain software for system operations.
The recommendations in this section are easier to perform during initial system installation. If the system is already installed, it is recommended that a full backup be performed before repartitioning the system.
Note: If you are repartitioning a system that has already been installed, make sure the data has been copied over to the new partition, unmount it and then remove the data from the directory that was in the old partition. Otherwise it will still consume space in the old partition that will be masked when the new filesystem is mounted. For example, if a system is in single-user mode with no filesystems mounted and the administrator adds a lot of data to the /tmp directory, this data will still consume space in / once the /tmp filesystem is mounted unless it is removed first.
A number of uncommon filesystem types are supported under Linux. Removing support for unneeded filesystem types reduces the local attack surface of the system. If a filesystem type is not needed it should be disabled. Native Linux file systems are designed to ensure that built-in security controls function as expected. Non-native filesystems can lead to unexpected consequences to both the security and functionality of the system and should be used with caution. Many filesystems are created for niche use cases and are not maintained and supported as the operating systems are updated and patched. Users of non-native filesystems should ensure that there is attention and ongoing support for them, especially in light of frequent operating system changes.
Standard network connectivity and Internet access to cloud storage may make the use of non-standard filesystem formats to directly attach heterogeneous devices much less attractive.
Note : This should not be considered a comprehensive list of filesystems. You may wish to consider additions to those listed here for your environment.
The cramfs filesystem type is a compressed read-only Linux filesystem embedded in small footprint systems. A cramfs image can be used without having to first decompress the image.
Removing support for unneeded filesystem types reduces the local attack surface of the server. If this filesystem type is not needed, disable it.
Edit or create the file /etc/modprobe.d/CIS.conf and add the following line:
install cramfs /bin/true
| Ensure mounting of cramfs filesystems is disabled | Fail |
| Ensure mounting of cramfs filesystems is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.1_Ensure_mounting_of_cramfs_filesystems_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.424-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1002"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1003"/>
</check>
</complex-check>
</rule-result>
The freevxfs filesystem type is a free version of the Veritas type filesystem. This is the primary filesystem type for HP-UX operating systems.
Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.
Edit or create the file /etc/modprobe.d/CIS.conf and add the following line:
install freevxfs /bin/true
| Ensure mounting of freevxfs filesystems is disabled | Fail |
| Ensure mounting of freevxfs filesystems is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.2_Ensure_mounting_of_freevxfs_filesystems_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.425-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1004"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1005"/>
</check>
</complex-check>
</rule-result>
The jffs2 (journaling flash filesystem 2) filesystem type is a log-structured filesystem used in flash memory devices.
Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.
Edit or create the file /etc/modprobe.d/CIS.conf and add the following line:
install jffs2 /bin/true
| Ensure mounting of jffs2 filesystems is disabled | Fail |
| Ensure mounting of jffs2 filesystems is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.3_Ensure_mounting_of_jffs2_filesystems_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.427-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1006"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1007"/>
</check>
</complex-check>
</rule-result>
The hfs filesystem type is a hierarchical filesystem that allows you to mount Mac OS filesystems.
Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.
Edit or create the file /etc/modprobe.d/CIS.conf and add the following line:
install hfs /bin/true
| Ensure mounting of hfs filesystems is disabled | Fail |
| Ensure mounting of hfs filesystems is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.4_Ensure_mounting_of_hfs_filesystems_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.430-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1008"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1009"/>
</check>
</complex-check>
</rule-result>
The hfsplus filesystem type is a hierarchical filesystem designed to replace hfs that allows you to mount Mac OS filesystems.
Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.
Edit or create the file /etc/modprobe.d/CIS.conf and add the following line:
install hfsplus /bin/true
| Ensure mounting of hfsplus filesystems is disabled | Fail |
| Ensure mounting of hfsplus filesystems is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.5_Ensure_mounting_of_hfsplus_filesystems_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.432-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1010"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1011"/>
</check>
</complex-check>
</rule-result>
The squashfs filesystem type is a compressed read-only Linux filesystem embedded in small footprint systems (similar to cramfs ). A squashfs image can be used without having to first decompress the image.
Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.
Edit or create the file /etc/modprobe.d/CIS.conf and add the following line:
install squashfs /bin/true
| Ensure mounting of squashfs filesystems is disabled | Fail |
| Ensure mounting of squashfs filesystems is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.6_Ensure_mounting_of_squashfs_filesystems_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.433-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1012"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1013"/>
</check>
</complex-check>
</rule-result>
The udf filesystem type is the universal disk format used to implement ISO/IEC 13346 and ECMA-167 specifications. This is an open vendor filesystem type for data storage on a broad range of media. This filesystem type is necessary to support writing DVDs and newer optical disc formats.
Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.
Edit or create the file /etc/modprobe.d/CIS.conf and add the following line:
install udf /bin/true
| Ensure mounting of udf filesystems is disabled | Fail |
| Ensure mounting of udf filesystems is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.7_Ensure_mounting_of_udf_filesystems_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.434-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1014"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1015"/>
</check>
</complex-check>
</rule-result>
The FAT filesystem format is primarily used on older windows systems and portable USB drives or flash modules. It comes in three types FAT12 , FAT16 , and FAT32 all of which are supported by the vfat kernel module.
Removing support for unneeded filesystem types reduces the local attack surface of the system. If this filesystem type is not needed, disable it.
Edit or create the file /etc/modprobe.d/CIS.conf and add the following line:
install vfat /bin/trueImpact:
FAT filesystems are often used on portable USB sticks and other flash media are commonly used to transfer files between workstations, removing VFAT support may prevent the ability to transfer files in this way.
| Ensure mounting of FAT filesystems is disabled | Fail |
| Ensure mounting of FAT filesystems is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.1.8_Ensure_mounting_of_FAT_filesystems_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.435-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1016"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1017"/>
</check>
</complex-check>
</rule-result>
The nodev mount option specifies that the filesystem cannot contain special devices.
Since the /tmp filesystem is not intended to support devices, set this option to ensure that users cannot attempt to create block or character special devices in /tmp .
Edit the /etc/fstab file and add nodev to the fourth field (mounting options) for the /tmp partition. See the fstab(5) manual page for more information.
Run the following command to remount /tmp :
# mount -o remount,nodev /tmp
| Ensure nodev option set on /tmp partition | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.3_Ensure_nodev_option_set_on_tmp_partition"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.436-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1019"/>
</check>
</complex-check>
</rule-result>
The nosuid mount option specifies that the filesystem cannot contain setuid files.
Since the /tmp filesystem is only intended for temporary file storage, set this option to ensure that users cannot create setuid files in /tmp .
Edit the /etc/fstab file and add nosuid to the fourth field (mounting options) for the /tmp partition. See the fstab(5) manual page for more information.
Run the following command to remount /tmp :
# mount -o remount,nosuid /tmp
| Ensure nosuid option set on /tmp partition | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.4_Ensure_nosuid_option_set_on_tmp_partition"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.436-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1020"/>
</check>
</complex-check>
</rule-result>
The nodev mount option specifies that the filesystem cannot contain special devices.
Since the /var/tmp filesystem is not intended to support devices, set this option to ensure that users cannot attempt to create block or character special devices in /var/tmp .
Edit the /etc/fstab file and add nodev to the fourth field (mounting options) for the /var/tmp partition. See the fstab(5) manual page for more information.
Run the following command to remount /var/tmp :
# mount -o remount,nodev /var/tmp
| Ensure nodev option set on /var/tmp partition | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.7_Ensure_nodev_option_set_on_vartmp_partition"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.437-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1023"/>
</check>
</complex-check>
</rule-result>
The nosuid mount option specifies that the filesystem cannot contain setuid files.
Since the /var/tmp filesystem is only intended for temporary file storage, set this option to ensure that users cannot create setuid files in /var/tmp .
Edit the /etc/fstab file and add nosuid to the fourth field (mounting options) for the /var/tmp partition. See the fstab(5) manual page for more information.
Run the following command to remount /var/tmp :
# mount -o remount,nosuid /var/tmp
| Ensure nosuid option set on /var/tmp partition | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.8_Ensure_nosuid_option_set_on_vartmp_partition"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.438-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1024"/>
</check>
</complex-check>
</rule-result>
The noexec mount option specifies that the filesystem cannot contain executable binaries.
Since the /var/tmp filesystem is only intended for temporary file storage, set this option to ensure that users cannot run executable binaries from /var/tmp .
Edit the /etc/fstab file and add noexec to the fourth field (mounting options) for the /var/tmp partition. See the fstab(5) manual page for more information.
Run the following command to remount /var/tmp :
# mount -o remount,noexec /var/tmp
| Ensure noexec option set on /var/tmp partition | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.9_Ensure_noexec_option_set_on_vartmp_partition"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.438-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1025"/>
</check>
</complex-check>
</rule-result>
The nodev mount option specifies that the filesystem cannot contain special devices.
Since the user partitions are not intended to support devices, set this option to ensure that users cannot attempt to create block or character special devices.
Edit the /etc/fstab file and add nodev to the fourth field (mounting options) for the /home partition. See the fstab(5) manual page for more information.
# mount -o remount,nodev /home
| Ensure nodev option set on /home partition | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.13_Ensure_nodev_option_set_on_home_partition"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.439-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1029"/>
</check>
</complex-check>
</rule-result>
The nodev mount option specifies that the filesystem cannot contain special devices.
Since the /run/shm filesystem is not intended to support devices, set this option to ensure that users cannot attempt to create special devices in /run/shm partitions.
Edit the /etc/fstab file and add nodev to the fourth field (mounting options) for the /run/shm partition. See the fstab(5) manual page for more information.
Run the following command to remount /run/shm :
# mount -o remount,nodev /run/shm
| Ensure nodev option set on /run/shm partition | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.14_Ensure_nodev_option_set_on_runshm_partition"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.439-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1030"/>
</check>
</complex-check>
</rule-result>
The nosuid mount option specifies that the filesystem cannot contain setuid files.
Setting this option on a file system prevents users from introducing privileged programs onto the system and allowing non-root users to execute them.
Edit the /etc/fstab file and add nosuid to the fourth field (mounting options) for the /run/shm partition. See the fstab(5) manual page for more information.
Run the following command to remount /run/shm :
# mount -o remount,nosuid /run/shm
| Ensure nosuid option set on /run/shm partitionrun | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.15_Ensure_nosuid_option_set_on_runshm_partitionrun"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.440-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1031"/>
</check>
</complex-check>
</rule-result>
The noexec mount option specifies that the filesystem cannot contain executable binaries.
Setting this option on a file system prevents users from executing programs from shared memory. This deters users from introducing potentially malicious software on the system.
Edit the /etc/fstab file and add noexec to the fourth field (mounting options) for the /run/shm partition. See the fstab(5) manual page for more information.
Run the following command to remount /run/shm :
# mount -o remount,noexec /run/shm
| Ensure noexec option set on /run/shm partition | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.16_Ensure_noexec_option_set_on_runshm_partition"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.440-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1032"/>
</check>
</complex-check>
</rule-result>
Setting the sticky bit on world writable directories prevents users from deleting or renaming files in that directory that are not owned by them.
This feature prevents the ability to delete or rename files in world writable directories (such as /tmp ) that are owned by another user.
Run the following command to set the sticky bit on all world writable directories:
# df --local -P | awk {'if (NR!=1) print $6'} | xargs -I '{}' find '{}' -xdev -type
d -perm -0002 2>/dev/null | chmod a+t
| Script: sce/world_writable_dirs_sticky.sh | Exit Code: 101 | pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.20_Ensure_sticky_bit_is_set_on_all_world-writable_directories"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.441-05:00"
version="1"
weight="1.0">
<result>pass</result>
<check system="http://open-scap.org/page/SCE"
negate="false"
multi-check="false">
<check-content-ref href="sce/world_writable_dirs_sticky.sh"/>
<check-content>
<command_result script="C:\CIS\Assessor-CLI\sce\world_writable_dirs_sticky.sh"
href="sce/world_writable_dirs_sticky.sh"
xccdf="pass"
exit-value="101">
<out/>
<err/>
<env/>
</command_result>
</check-content>
</check>
</rule-result>
autofs allows automatic mounting of devices, typically including CD/DVDs and USB drives.
With automounting enabled anyone with physical access could attach a USB drive or disc and have its contents available in system even if they lacked permissions to mount it themselves.
Remove or comment out start lines in /etc/init/autofs.conf :
#start on runlevel [2345]Impact:
The use portable hard drives is very common for workstation users. If your organization allows the use of portable storage or media on workstations and physical access controls to workstations is considered adequate there is little value add in turning off automounting.
| Disable Automounting | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.1.21_Disable_Automounting"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.441-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1034"/>
</check>
</complex-check>
</rule-result>
Ubuntu Linux uses apt to install and update software packages. Patch management procedures may vary widely between enterprises. Large enterprises may choose to install a local updates server that can be used in place of Ubuntu's servers, whereas a single deployment of a system may prefer to get updates directly. Updates can be performed automatically or manually, depending on the site's policy for patch management. Many large enterprises prefer to test patches on a non-production system before rolling out to production.
For the purpose of this benchmark, the requirement is to ensure that a patch management system is configured and maintained. The specifics on patch update procedures are left to the organization.
AIDE is a file integrity checking tool, similar in nature to Tripwire. While it cannot prevent intrusions, it can detect unauthorized changes to configuration files by alerting when the files are changed. When setting up AIDE, decide internally what the site policy will be concerning integrity checking. Review the AIDE quick start guide and AIDE documentation before proceeding.
AIDE takes a snapshot of filesystem state including modification times, permissions, and file hashes which can then be used to compare against the current state of the filesystem to detect modifications to the system.
By monitoring the filesystem state compromised files can be detected to prevent or limit the exposure of accidental or malicious misconfigurations or modified binaries.
Run the following command to install AIDE:
# apt-get install aideConfigure AIDE as appropriate for your environment. Consult the AIDE documentation for options.
Initialize AIDE:
# aide --init
| Ensure AIDE is installed | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.3.1_Ensure_AIDE_is_installed"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.441-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1035"/>
</check>
</complex-check>
</rule-result>
Periodic checking of the filesystem integrity is needed to detect changes to the filesystem.
Periodic file checking allows the system administrator to determine on a regular basis if critical files have been changed in an unauthorized fashion.
Run the following command:
# crontab -u root -eAdd the following line to the crontab:
0 5 * * * /usr/bin/aide --check
| Ensure filesystem integrity is regularly checked | Fail |
| Ensure filesystem integrity is regularly checked | Fail |
| Ensure filesystem integrity is regularly checked | Fail |
| Ensure filesystem integrity is regularly checked | Fail |
| Ensure filesystem integrity is regularly checked | Fail |
| Ensure filesystem integrity is regularly checked | Fail |
| Ensure filesystem integrity is regularly checked | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.3.2_Ensure_filesystem_integrity_is_regularly_checked"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.443-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="OR" negate="false">
<complex-check operator="OR" negate="false">
<complex-check operator="OR" negate="false">
<complex-check operator="OR" negate="false">
<complex-check operator="OR" negate="false">
<complex-check operator="OR" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1036"
value-id="xccdf_org.cisecurity.benchmarks_value_1.3.2.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1036"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1037"
value-id="xccdf_org.cisecurity.benchmarks_value_1.3.2.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1037"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1038"
value-id="xccdf_org.cisecurity.benchmarks_value_1.3.2.3_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1038"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1039"
value-id="xccdf_org.cisecurity.benchmarks_value_1.3.2.4_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1039"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1040"
value-id="xccdf_org.cisecurity.benchmarks_value_1.3.2.5_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1040"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1041"
value-id="xccdf_org.cisecurity.benchmarks_value_1.3.2.6_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1041"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1042"
value-id="xccdf_org.cisecurity.benchmarks_value_1.3.2.7_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1042"/>
</check>
</complex-check>
</rule-result>
The recommendations in this section focus on securing the bootloader and settings involved in the boot process directly.
The grub configuration file contains information on boot settings and passwords for unlocking boot options. The grub configuration is usually grub.cfg stored in /boot/grub.
Setting the permissions to read and write for root only prevents non-root users from seeing the boot parameters or changing them. Non-root users who read the boot parameters may be able to identify weaknesses in security upon boot and be able to exploit them.
Run the following commands to set permissions on your grub configuration:
# chown root:root /boot/grub/grub.cfg
# chmod og-rwx /boot/grub/grub.cfg
| Ensure permissions on bootloader config are configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.4.1_Ensure_permissions_on_bootloader_config_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.443-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1043"/>
</check>
</complex-check>
</rule-result>
Setting the boot loader password will require that anyone rebooting the system must enter a password before being able to set command line boot parameters
Requiring a boot password upon execution of the boot loader will prevent an unauthorized user from entering boot parameters or changing the boot partition. This prevents users from weakening security (e.g. turning off SELinux at boot time).
Create an encrypted password with grub-mkpasswd-pbkdf2 :
# grub-mkpasswd-pbkdf2
Enter password:
<password>
Reenter password:
<password>
Your PBKDF2 is
<encrypted-password>Add the following into /etc/grub.d/00_header or a custom /etc/grub.d configuration file:
cat <<EOF
set superusers="
<username>
"
password_pbkdf2
<username><encrypted-password>
EOF Run the following command to update the grub2 configuration:
# update-grub
| Ensure bootloader password is set | Fail |
| Ensure bootloader password is set | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.4.2_Ensure_bootloader_password_is_set"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.443-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="OR" negate="false">
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1045"
value-id="xccdf_org.cisecurity.benchmarks_value_1.4.2.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1045"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1044"
value-id="xccdf_org.cisecurity.benchmarks_value_1.4.2.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1044"/>
</check>
</complex-check>
</rule-result>
A core dump is the memory of an executable program. It is generally used to determine why a program aborted. It can also be used to glean confidential information from a core file. The system provides the ability to set a soft limit for core dumps, but this can be overridden by the user.
Setting a hard limit on core dumps prevents users from overriding the soft variable. If core dumps are required, consider setting limits for user groups (see limits.conf(5) ). In addition, setting the fs.suid_dumpable variable to 0 will prevent setuid programs from dumping core.
Add the following line to the /etc/security/limits.conf file or a /etc/security/limits.d/* file:
* hard core 0Set the following parameter in the /etc/sysctl.conf file:
fs.suid_dumpable = 0Run the following command to set the active kernel parameter:
# sysctl -w fs.suid_dumpable=0| Ensure core dumps are restricted | Fail |
| Ensure core dumps are restricted | Fail |
| Ensure core dumps are restricted | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.5.1_Ensure_core_dumps_are_restricted"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.443-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<complex-check operator="OR" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1046"
value-id="xccdf_org.cisecurity.benchmarks_value_1.5.1.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1046"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1047"
value-id="xccdf_org.cisecurity.benchmarks_value_1.5.1.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1047"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1048"
value-id="xccdf_org.cisecurity.benchmarks_value_1.5.1.3_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1048"/>
</check>
</complex-check>
</rule-result>
Recent processors in the x86 family support the ability to prevent code execution on a per memory page basis. Generically and on AMD processors, this ability is called No Execute (NX), while on Intel processors it is called Execute Disable (XD). This ability can help prevent exploitation of buffer overflow vulnerabilities and should be activated whenever possible. Extra steps must be taken to ensure that this protection is enabled, particularly on 32-bit x86 systems. Other processors, such as Itanium and POWER, have included such support since inception and the standard kernel for those platforms supports the feature.
Enabling any feature that can protect against buffer overflow attacks enhances the security of the system.
On 32 bit systems install a kernel with PAE support, no installation is required on 64 bit systems:
If necessary configure your bootloader to load the new kernel and reboot the system.
You may need to enable NX or XD support in your bios.
| Ensure XD/NX support is enabled | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.5.2_Ensure_XDNX_support_is_enabled"
role="unscored"
severity="unknown"
time="2019-11-19T23:30:03.443-05:00"
version="1"
weight="0.0">
<result>informational</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1049"
value-id="xccdf_org.cisecurity.benchmarks_value_1.5.2.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1049"/>
</check>
</complex-check>
</rule-result>
Address space layout randomization (ASLR) is an exploit mitigation technique which randomly arranges the address space of key data areas of a process.
Randomly placing virtual memory regions will make it difficult to write memory page exploits as the memory placement will be consistently shifting.
Set the following parameter in the /etc/sysctl.conf file:
kernel.randomize_va_space = 2Run the following command to set the active kernel parameter:
# sysctl -w kernel.randomize_va_space=2
| Ensure address space layout randomization (ASLR) is enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.5.3_Ensure_address_space_layout_randomization_ASLR_is_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.443-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1050"
value-id="xccdf_org.cisecurity.benchmarks_value_1.5.3.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1050"/>
</check>
</complex-check>
</rule-result>
prelink is a program that modifies ELF shared libraries and ELF dynamically linked binaries in such a way that the time needed for the dynamic linker to perform relocations at startup significantly decreases.
The prelinking feature can interfere with the operation of AIDE, because it changes binaries. Prelinking can also increase the vulnerability of the system if a malicious user is able to compromise a common library such as libc.
Run the following command to restore binaries to normal:
# prelink -uaRun the following command to uninstall prelink :
# apt-get remove prelink
| Ensure prelink is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.5.4_Ensure_prelink_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.444-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1051"/>
</check>
</complex-check>
</rule-result>
Mandatory Access Control (MAC) provides an additional layer of access restrictions to processes on top of the base Discretionary Access Controls. By restricting how processes can access files and resources on a system the potential impact from vulnerabilities in the processes can be reduced.
Impact: Mandatory Access Control limits the capabilities of applications and daemons on a system, while this can prevent unauthorized access the configuration of MAC can be complex and difficult to implement correctly preventing legitimate access from occurring.
SELinux provides a Mandatory Access Control (MAC) system that greatly augments the default Discretionary Access Control (DAC) model. Under SELinux, every process and every object (files, sockets, pipes) on the system is assigned a security context, a label that includes detailed type information about the object. The kernel allows processes to access objects only if that access is explicitly allowed by the policy in effect. The policy defines transitions, so that a user can be allowed to run software, but the software can run under a different context than the user's default. This automatically limits the damage that the software can do to files accessible by the calling user. The user does not need to take any action to gain this benefit. For an action to occur, both the traditional DAC permissions must be satisfied as well as the SELinux MAC rules. The action will not be allowed if either one of these models does not permit the action. In this way, SELinux rules can only make a system's permissions more restrictive and secure. SELinux requires a complex policy to allow all the actions required of a system under normal operation. Three such policies have been available for use with Ubuntu and are included with the system: ubuntu , default , strict , and mls . These are described as follows:
This section provides guidance for the configuration of the targeted policy.
Note: This section only applies if SELinux is in use on the system. Recommendations for AppArmor are also included, and additional Mandatory Access Control systems exist beyond these two. AppArmor is the standard MAC system for Ubuntu systems.
References:
AppArmor provides a Mandatory Access Control (MAC) system that greatly augments the default Discretionary Access Control (DAC) model. Under AppArmor MAC rules are applied by file paths instead of by security contexts as in other MAC systems. As such it does not require support in the filesystem and can be applied to network mounted filesystems for example. AppArmor security policies define what system resources applications can access and what privileges they can do so with. This automatically limits the damage that the software can do to files accessible by the calling user. The user does not need to take any action to gain this benefit. For an action to occur, both the traditional DAC permissions must be satisfied as well as the AppArmor MAC rules. The action will not be allowed if either one of these models does not permit the action. In this way, AppArmor rules can only make a system's permissions more restrictive and secure.
Note: This section only applies if AppArmor is in use on the system. Recommendations for SELinux are also included, and additional Mandatory Access Control systems exist beyond these two.
References:
Presenting a warning message prior to the normal user login may assist in the prosecution of trespassers on the computer system. Changing some of these login banners also has the side effect of hiding OS version information and other detailed system information from attackers attempting to target specific exploits at a system.
Guidelines published by the US Department of Defense require that warning messages include at least the name of the organization that owns the system, the fact that the system is subject to monitoring and that such monitoring is in compliance with local statutes, and that use of the system implies consent to such monitoring. It is important that the organization's legal counsel review the content of all messages before any system modifications are made, as these warning messages are inherently site-specific. More information (including citations of relevant case law) can be found at http://www.justice.gov/criminal/cybercrime/
Note: The text provided in the remediation actions for these items is intended as an example only. Please edit to include the specific text for your organization as approved by your legal department.
The /etc/motd , /etc/issue , and /etc/issue.net files govern warning banners for standard command line logins for both local and remote users.
The contents of the /etc/motd file are displayed to users after login and function as a message of the day for authenticated users.
Unix-based systems have typically displayed information about the OS release and patch
level upon logging in to the system. This information can be useful to developers
who are developing software for a particular OS platform. If
mingetty(8)
supports the following options, they display operating system information:
\m
- machine architecture
\r
- operating system release
\s
- operating system name
\v
- operating system version
Warning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place. Displaying OS and patch level information in login banners also has the side effect of providing detailed system information to attackers attempting to target specific exploits of a system. Authorized users can easily get this information by running the " uname -a " command once they have logged in.
Edit the /etc/motd file with the appropriate contents according to your site policy, remove any instances of \m , \r , \s , or \v.
| Ensure message of the day is configured properly | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.1_Ensure_message_of_the_day_is_configured_properly"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.444-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1073"/>
</check>
</complex-check>
</rule-result>
The contents of the /etc/issue file are displayed to users prior to login for local terminals.
Unix-based systems have typically displayed information about the OS release and patch level upon logging in to the system. This information can be useful to developers who are developing software for a particular OS platform. If mingetty(8) supports the following options, they display operating system information:
\m- machine architecture
\r- operating system release
\s- operating system name
\v- operating system version
Warning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place. Displaying OS and patch level information in login banners also has the side effect of providing detailed system information to attackers attempting to target specific exploits of a system. Authorized users can easily get this information by running the "uname -a" command once they have logged in.
Edit the /etc/issue file with the appropriate contents according to your site policy, remove any instances of \m , \r , \s , or \v :
# echo "Authorized uses only. All activity may be monitored and reported." > /etc/issue
| Ensure local login warning banner is configured properly | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.2_Ensure_local_login_warning_banner_is_configured_properly"
role="unscored"
severity="unknown"
time="2019-11-19T23:30:03.444-05:00"
version="1"
weight="0.0">
<result>informational</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1074"/>
</check>
</complex-check>
</rule-result>
The contents of the /etc/issue.net file are displayed to users prior to login for remote connections from configured services.
Unix-based systems have typically displayed information about the OS release and patch
level upon logging in to the system. This information can be useful to developers
who are developing software for a particular OS platform. If mingetty(8) supports the following options, they display operating system information:
\m- machine architecture
\r- operating system release
\s- operating system name
\v- operating system version
Warning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place. Displaying OS and patch level information in login banners also has the side effect of providing detailed system information to attackers attempting to target specific exploits of a system. Authorized users can easily get this information by running the "uname -a" command once they have logged in.
Edit the /etc/issue.net file with the appropriate contents according to your site policy, remove any instances of \m , \r , \s , or \v :
# echo "Authorized uses only. All activity may be monitored and reported." > /etc/issue.net
| Ensure remote login warning banner is configured properly | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.3_Ensure_remote_login_warning_banner_is_configured_properly"
role="unscored"
severity="unknown"
time="2019-11-19T23:30:03.444-05:00"
version="1"
weight="0.0">
<result>informational</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1075"/>
</check>
</complex-check>
</rule-result>
The contents of the /etc/motd file are displayed to users after login and function as a message of the day for authenticated users.
If the /etc/motd file does not have the correct ownership it could be modified by unauthorized users with incorrect or misleading information.
Run the following commands to set permissions on /etc/motd :
# chown root:root /etc/motd
# chmod 644 /etc/motd
| Ensure permissions on /etc/motd are configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.4_Ensure_permissions_on_etcmotd_are_configured"
role="unscored"
severity="unknown"
time="2019-11-19T23:30:03.444-05:00"
version="1"
weight="0.0">
<result>informational</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1076"/>
</check>
</complex-check>
</rule-result>
The contents of the /etc/issue file are displayed to users prior to login for local terminals.
If the /etc/issue file does not have the correct ownership it could be modified by unauthorized users with incorrect or misleading information.
Run the following commands to set permissions on /etc/issue :
# chown root:root /etc/issue
# chmod 644 /etc/issue
| Ensure permissions on /etc/issue are configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.5_Ensure_permissions_on_etcissue_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.444-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1077"/>
</check>
</complex-check>
</rule-result>
The contents of the /etc/issue.net file are displayed to users prior to login for remote connections from configured services.
If the /etc/issue.net file does not have the correct ownership it could be modified by unauthorized users with incorrect or misleading information.
Run the following commands to set permissions on /etc/issue.net :
# chown root:root /etc/issue.net
# chmod 644 /etc/issue.net
| Ensure permissions on /etc/issue.net are configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.7.1.6_Ensure_permissions_on_etcissue.net_are_configured"
role="unscored"
severity="unknown"
time="2019-11-19T23:30:03.445-05:00"
version="1"
weight="0.0">
<result>informational</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1078"/>
</check>
</complex-check>
</rule-result>
GDM is the GNOME Display Manager which handles graphical login for GNOME based systems.
Warning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place.
Create the /etc/dconf/profile/gdm file with the following contents:
user-db:user
system-db:gdm
file-db:/usr/share/gdm/greeter-dconf-defaults
Create or edit the banner-message-enable and banner-message-text options in /etc/dconf/db/gdm.d/01-banner-message :
[org/gnome/login-screen]
banner-message-enable=true
banner-message-text='Authorized uses only. All activity may be monitored and reported.'
Run the following command to update the system databases:
# dconf update
| Ensure GDM login banner is configured | Fail |
| Ensure GDM login banner is configured | Fail |
| Ensure GDM login banner is configured | Fail |
| Ensure GDM login banner is configured | Fail |
| Ensure GDM login banner is configured | Fail |
| Ensure GDM login banner is configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_1.7.2_Ensure_GDM_login_banner_is_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.445-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="OR" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1079"
value-id="xccdf_org.cisecurity.benchmarks_value_1.7.2.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1079"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1080"
value-id="xccdf_org.cisecurity.benchmarks_value_1.7.2.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1080"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1081"
value-id="xccdf_org.cisecurity.benchmarks_value_1.7.2.3_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1081"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1082"
value-id="xccdf_org.cisecurity.benchmarks_value_1.7.2.4_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1082"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1083"
value-id="xccdf_org.cisecurity.benchmarks_value_1.7.2.5_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1083"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1084"/>
</check>
</complex-check>
</rule-result>
While applying system updates and patches helps correct known vulnerabilities, one of the best ways to protect the system against as yet unreported vulnerabilities is to disable all services that are not required for normal system operation. This prevents the exploitation of vulnerabilities discovered at a later date. If a service is not enabled, it cannot be exploited. The actions in this section of the document provide guidance on some services which can be safely disabled and under which circumstances, greatly reducing the number of possible threats to the resulting system. Additionally some services which should remain enabled but with secure configuration are covered as well as insecure service clients.
inetd is a super-server daemon that provides internet services and passes connections to configured services. While not commonly used inetd and any unneeded inetd based services should be disabled if possible.
chargen is a network service that responds with 0 to 512 ASCII characters for each connection it receives. This service is intended for debugging and testing purposes. It is recommended that this service be disabled.
Disabling this service will reduce the remote attack surface of the system.
Comment out or remove any lines starting with chargen from /etc/inetd.conf and /etc/inetd.d/* .
Set disable = yes on all chargen services in /etc/xinetd.conf and /etc/xinetd.d/* .
| Ensure chargen services are not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.1.1_Ensure_chargen_services_are_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.445-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1085"/>
</check>
</complex-check>
</rule-result>
daytime is a network service that responds with the server's current date and time. This service is intended for debugging and testing purposes. It is recommended that this service be disabled.
Disabling this service will reduce the remote attack surface of the system.
Comment out or remove any lines starting with daytime from /etc/inetd.conf and /etc/inetd.d/* .
Set disable = yes on all daytime services in /etc/xinetd.conf and /etc/xinetd.d/* .
| Ensure daytime services are not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.1.2_Ensure_daytime_services_are_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.445-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1086"/>
</check>
</complex-check>
</rule-result>
discard is a network service that simply discards all data it receives. This service is intended for debugging and testing purposes. It is recommended that this service be disabled.
Disabling this service will reduce the remote attack surface of the system.
Comment out or remove any lines starting with discard from /etc/inetd.conf and /etc/inetd.d/* .
Set disable = yes on all discard services in /etc/xinetd.conf and /etc/xinetd.d/* .
| Ensure discard services are not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.1.3_Ensure_discard_services_are_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.445-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1087"/>
</check>
</complex-check>
</rule-result>
echo is a network service that responds to clients with the data sent to it by the client. This service is intended for debugging and testing purposes. It is recommended that this service be disabled.
Disabling this service will reduce the remote attack surface of the system.
Comment out or remove any lines starting with echo from /etc/inetd.conf and /etc/inetd.d/* .
Set disable = yes on all echo services in /etc/xinetd.conf and /etc/xinetd.d/* .
| Ensure echo services are not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.1.4_Ensure_echo_services_are_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.445-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1088"/>
</check>
</complex-check>
</rule-result>
time is a network service that responds with the server's current date and time as a 32 bit integer. This service is intended for debugging and testing purposes. It is recommended that this service be disabled.
Disabling this service will reduce the remote attack surface of the system.
Comment out or remove any lines starting with time from /etc/inetd.conf and /etc/inetd.d/* .
Set disable = yes on all time services in /etc/xinetd.conf and /etc/xinetd.d/* .
| Ensure time services are not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.1.5_Ensure_time_services_are_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.446-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1089"/>
</check>
</complex-check>
</rule-result>
The Berkeley rsh-server ( rsh , rlogin , rexec ) package contains legacy services that exchange credentials in clear-text.
These legacy services contain numerous security exposures and have been replaced with the more secure SSH package.
Comment out or remove any lines starting with shell , login , or exec from /etc/inetd.conf and /etc/inetd.d/* .
Set disable = yes on all rsh , rlogin , and rexec services in /etc/xinetd.conf and /etc/xinetd.d/* .
| Ensure rsh server is not enabled | Pass |
| Ensure rsh server is not enabled | Pass |
| Ensure rsh server is not enabled | Pass |
| Ensure rsh server is not enabled | Pass |
| Ensure rsh server is not enabled | Pass |
| Ensure rsh server is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.1.6_Ensure_rsh_server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.446-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1090"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1091"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1092"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1093"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1094"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1095"/>
</check>
</complex-check>
</rule-result>
The talk software makes it possible for users to send and receive messages across systems through a terminal session. The talk client (allows initiate of talk sessions) is installed by default.
The software presents a security risk as it uses unencrypted protocols for communication.
Comment out or remove any lines starting with talk or ntalk from /etc/inetd.conf and /etc/inetd.d/* .
Set disable = yes on all talk services in /etc/xinetd.conf and /etc/xinetd.d/* .
| Ensure talk server is not enabled | Pass |
| Ensure talk server is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.1.7_Ensure_talk_server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.446-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1096"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1097"/>
</check>
</complex-check>
</rule-result>
The telnet-server package contains the telnet daemon, which accepts connections from users from other systems via the telnet protocol.
The telnet protocol is insecure and unencrypted. The use of an unencrypted transmission medium could allow a user with access to sniff network traffic the ability to steal credentials. The ssh package provides an encrypted session and stronger security.
Comment out or remove any lines starting with telnet from /etc/inetd.conf and /etc/inetd.d/* .
Set disable = yes on all telnet services in /etc/xinetd.conf and /etc/xinetd.d/* .
| Ensure telnet server is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.1.8_Ensure_telnet_server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.446-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1098"/>
</check>
</complex-check>
</rule-result>
Trivial File Transfer Protocol (TFTP) is a simple file transfer protocol, typically used to automatically transfer configuration or boot machines from a boot server. The packages tftp and atftp are both used to define and support a TFTP server.
TFTP does not support authentication nor does it ensure the confidentiality or integrity of data. It is recommended that TFTP be removed, unless there is a specific need for TFTP. In that case, extreme caution must be used when configuring the services.
Comment out or remove any lines starting with tftp from /etc/inetd.conf and /etc/inetd.d/* .
Set disable = yes on all tftp services in /etc/xinetd.conf and /etc/xinetd.d/* .
| Ensure tftp server is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.1.9_Ensure_tftp_server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.446-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1099"/>
</check>
</complex-check>
</rule-result>
The eXtended InterNET Daemon ( xinetd ) is an open source super daemon that replaced the original inetd daemon. The xinetd daemon listens for well known services and dispatches the appropriate daemon to properly respond to service requests.
If there are no xinetd services required, it is recommended that the daemon be disabled.
Remove or comment out start lines in /etc/init/xinetd.conf :
#start on runlevel [2345]
| Ensure xinetd is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.1.10_Ensure_xinetd_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.447-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1100"/>
</check>
</complex-check>
</rule-result>
This section describes services that are installed on systems that specifically need to run these services. If any of these services are not required, it is recommended that they be disabled or deleted from the system to reduce the potential attack surface.
It is recommended that physical systems and virtual guests lacking direct access to the physical host's clock be configured to synchronize their time using a service such as NTP or chrony.
System time should be synchronized between all systems in an environment. This is typically done by establishing an authoritative time server or set of servers and having all systems synchronize their clocks to them.
Time synchronization is important to support time sensitive security mechanisms like Kerberos and also ensures log files have consistent time records across the enterprise, which aids in forensic investigations.
On physical systems or virtual systems where host based time synchronization is not available install NTP or chrony using one of the following commands:
# apt-get install ntp
# apt-get install chrony
On virtual systems where host based time synchronization is available consult your virtualization software documentation and setup host based synchronization.
| Ensure time synchronization is in use | Pass |
| Ensure time synchronization is in use | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.1_Ensure_time_synchronization_is_in_use"
role="unscored"
severity="unknown"
time="2019-11-19T23:30:03.447-05:00"
version="1"
weight="0.0">
<result>informational</result>
<complex-check operator="OR" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1101"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1102"/>
</check>
</complex-check>
</rule-result>
ntp is a daemon which implements the Network Time Protocol (NTP). It is designed to synchronize system clocks across a variety of systems and use a source that is highly accurate. More information on NTP can be found at http://www.ntp.org . ntp can be configured to be a client and/or a server.
This recommendation only applies if ntp is in use on the system.
If ntp is in use on the system proper configuration is vital to ensuring time synchronization is working properly.
Add or edit restrict lines in /etc/ntp.conf to match the following:
restrict -4 default kod nomodify notrap nopeer noquery
restrict -6 default kod nomodify notrap nopeer noquery
Add or edit server lines to /etc/ntp.conf as appropriate:
server
<remote-server>Configure ntp to run as the ntp user by adding or editing the following file:
/etc/init.d/ntp :
RUNASUSER=ntp
| Ensure ntp is configured | Pass |
| Ensure ntp is configured | Pass |
| Ensure ntp is configured | Pass |
| Ensure ntp is configured | Pass |
| Ensure ntp is configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.2_Ensure_ntp_is_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.447-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="OR" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1103"
value-id="xccdf_org.cisecurity.benchmarks_value_2.2.1.2.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1103"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1104"
value-id="xccdf_org.cisecurity.benchmarks_value_2.2.1.2.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1104"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1105"
value-id="xccdf_org.cisecurity.benchmarks_value_2.2.1.2.3_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1105"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1106"
value-id="xccdf_org.cisecurity.benchmarks_value_2.2.1.2.4_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1106"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1107"/>
</check>
</complex-check>
</rule-result>
chrony is a daemon which implements the Network Time Protocol (NTP) is designed to synchronize system clocks across a variety of systems and use a source that is highly accurate. More information on chrony can be found at http://chrony.tuxfamily.org/ . chrony can be configured to be a client and/or a server.
If chrony is in use on the system proper configuration is vital to ensuring time synchronization is working properly.
This recommendation only applies if chrony is in use on the system.
Add or edit server lines to /etc/chrony/chrony.conf as appropriate:
server
<remote-server>
| Ensure chrony is configured | Fail |
| Ensure chrony is configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.1.3_Ensure_chrony_is_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.447-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="OR" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1108"
value-id="xccdf_org.cisecurity.benchmarks_value_2.2.1.3.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1108"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1109"/>
</check>
</complex-check>
</rule-result>
The X Window System provides a Graphical User Interface (GUI) where users can have multiple windows in which to run programs and various add on. The X Windows system is typically used on workstations where users login, but not on servers where users typically do not login.
Unless your organization specifically requires graphical login access via X Windows, remove it to reduce the potential attack surface.
Run the following command to remove the X Windows System packages:
apt-get remove xserver-xorg*
| Ensure X Window System is not installed | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.2_Ensure_X_Window_System_is_not_installed"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.448-05:00"
version="1"
weight="1.0">
<result>pass</result>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1110"/>
</check>
</rule-result>
Avahi is a free zeroconf implementation, including a system for multicast DNS/DNS-SD service discovery. Avahi allows programs to publish and discover services and hosts running on a local network with no specific configuration. For example, a user can plug a computer into a network and Avahi automatically finds printers to print to, files to look at and people to talk to, as well as network services running on the machine.
Automatic discovery of network services is not normally required for system functionality. It is recommended to disable the service to reduce the potential attach surface.
Remove or comment out start lines in /etc/init/avahi-daemon.conf :
#start on runlevel [2345]
| Ensure Avahi Server is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.3_Ensure_Avahi_Server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.448-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1111"/>
</check>
</complex-check>
</rule-result>
The Common Unix Print System (CUPS) provides the ability to print to both local and network printers. A system running CUPS can also accept print jobs from remote systems and print them to local printers. It also provides a web based remote administration capability.
If the system does not need to print jobs or accept print jobs from other systems, it is recommended that CUPS be disabled to reduce the potential attack surface.
Remove or comment out start lines in /etc/init/cups.conf :
#start on runlevel [2345]Impact:
Disabling CUPS will prevent printing from the system, a common task for workstation systems.
| Ensure CUPS is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.4_Ensure_CUPS_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.448-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1112"/>
</check>
</complex-check>
</rule-result>
The Dynamic Host Configuration Protocol (DHCP) is a service that allows machines to be dynamically assigned IP addresses.
Unless a system is specifically set up to act as a DHCP server, it is recommended that this service be deleted to reduce the potential attack surface.
Remove or comment out start lines in /etc/init/isc-dhcp-server.conf and /etc/init/isc-dhcp-server6.conf :
#start on runlevel [2345]
| Ensure DHCP Server is not enabled | Pass |
| Ensure DHCP Server is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.5_Ensure_DHCP_Server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.448-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1113"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1114"/>
</check>
</complex-check>
</rule-result>
The Lightweight Directory Access Protocol (LDAP) was introduced as a replacement for NIS/YP. It is a service that provides a method for looking up information from a central database.
If the system will not need to act as an LDAP server, it is recommended that the software be disabled to reduce the potential attack surface.
Run the following command to disable slapd :
# update-rc.d slapd disable
| Ensure LDAP server is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.6_Ensure_LDAP_server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.449-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1115"/>
</check>
</complex-check>
</rule-result>
The Network File System (NFS) is one of the first and most widely distributed file systems in the UNIX environment. It provides the ability for systems to mount file systems of other servers through the network.
If the system does not export NFS shares or act as an NFS client, it is recommended that these services be disabled to reduce remote attack surface.
Remove or comment out start lines in /etc/init/rpcbind.conf :
#start on start-rpcbindRun the following command to disable nfs-kernel-server :
# update-rc.d nfs-kernel-server disable
| Ensure NFS and RPC are not enabled | Pass |
| Ensure NFS and RPC are not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.7_Ensure_NFS_and_RPC_are_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.449-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1116"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1117"/>
</check>
</complex-check>
</rule-result>
The Domain Name System (DNS) is a hierarchical naming system that maps names to IP addresses for computers, services and other resources connected to a network.
Unless a system is specifically designated to act as a DNS server, it is recommended that the package be deleted to reduce the potential attack surface.
Run the following command to disable bind9 :
# update-rc.d bind9 disable
| Ensure DNS Server is not enabled | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.8_Ensure_DNS_Server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.449-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1118"/>
</check>
</complex-check>
</rule-result>
The File Transfer Protocol (FTP) provides networked computers with the ability to transfer files.
FTP does not protect the confidentiality of data or authentication credentials. It is recommended sftp be used if file transfer is required. Unless there is a need to run the system as a FTP server (for example, to allow anonymous downloads), it is recommended that the package be deleted to reduce the potential attack surface.
Remove or comment out start lines in /etc/init/vsftpd.conf :
#start on runlevel [2345] or net-device-up IFACE!=lo
| Ensure FTP Server is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.9_Ensure_FTP_Server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.449-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1119"/>
</check>
</complex-check>
</rule-result>
HTTP or web servers provide the ability to host web site content.
Unless there is a need to run the system as a web server, it is recommended that the package be deleted to reduce the potential attack surface.
Run the following command to disable apache2 :
# update-rc.d apache2 disable
| Ensure HTTP server is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.10_Ensure_HTTP_server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.450-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1120"/>
</check>
</complex-check>
</rule-result>
dovecot is an open source IMAP and POP3 server for Linux based systems.
Unless POP3 and/or IMAP servers are to be provided by this system, it is recommended that the service be deleted to reduce the potential attack surface.
Remove or comment out start lines in /etc/init/dovecot.conf :
#start on runlevel [2345]
| Ensure IMAP and POP3 server is not enabled | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.11_Ensure_IMAP_and_POP3_server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.450-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1121"/>
</check>
</complex-check>
</rule-result>
The Samba daemon allows system administrators to configure their Linux systems to share file systems and directories with Windows desktops. Samba will advertise the file systems and directories via the Small Message Block (SMB) protocol. Windows desktop users will be able to mount these directories and file systems as letter drives on their systems.
If there is no need to mount directories and file systems to Windows systems, then this service can be deleted to reduce the potential attack surface.
Remove or comment out start lines in /etc/init/smbd.conf :
#start on (local-filesystems and net-device-up)
| Ensure Samba is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.12_Ensure_Samba_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.450-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1122"/>
</check>
</complex-check>
</rule-result>
Squid is a standard proxy server used in many distributions and environments.
If there is no need for a proxy server, it is recommended that the squid proxy be deleted to reduce the potential attack surface.
Remove or comment out start lines in /etc/init/squid3.conf :
#start on runlevel [2345]
| Ensure HTTP Proxy Server is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.13_Ensure_HTTP_Proxy_Server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.450-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1123"/>
</check>
</complex-check>
</rule-result>
The Simple Network Management Protocol (SNMP) server is used to listen for SNMP commands from an SNMP management system, execute the commands or collect the information and then send results back to the requesting system.
The SNMP server communicates using SNMP v1, which transmits data in the clear and does not require authentication to execute commands. Unless absolutely necessary, it is recommended that the SNMP service not be used.
Run the following command to disable snmpd :
# update-rc.d snmpd disable
| Ensure SNMP Server is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.14_Ensure_SNMP_Server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.450-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1124"/>
</check>
</complex-check>
</rule-result>
Mail Transfer Agents (MTA), such as sendmail and Postfix, are used to listen for incoming mail and transfer the messages to the appropriate user or mail server. If the system is not intended to be a mail server, it is recommended that the MTA be configured to only process local mail.
The software for all Mail Transfer Agents is complex and most have a long history of security issues. While it is important to ensure that the system can process local mail messages, it is not necessary to have the MTA's daemon listening on a port unless the server is intended to be a mail server that receives and processes mail from other systems.
Edit /etc/postfix/main.cf and add the following line to the RECEIVING MAIL section. If the line already exists, change it to look like the line below:
inet_interfaces = localhostRestart postfix:
# service postfix restart
| Ensure mail transfer agent is configured for local-only mode | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.15_Ensure_mail_transfer_agent_is_configured_for_local-only_mode"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.451-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1125"/>
</check>
</complex-check>
</rule-result>
The rsyncd service can be used to synchronize files between systems over network links.
The rsyncd service presents a security risk as it uses unencrypted protocols for communication.
Edit the /etc/default/rsync file and set RSYNC_ENABLE to false :
RSYNC_ENABLE=false
| Ensure rsync service is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.16_Ensure_rsync_service_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.451-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1126"
value-id="xccdf_org.cisecurity.benchmarks_value_2.2.16.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1126"/>
</check>
</complex-check>
</rule-result>
The Network Information Service (NIS) (formally known as Yellow Pages) is a client-server directory service protocol for distributing system configuration files. The NIS server is a collection of programs that allow for the distribution of configuration files.
The NIS service is inherently an insecure system that has been vulnerable to DOS attacks, buffer overflows and has poor authentication for querying NIS maps. NIS generally been replaced by such protocols as Lightweight Directory Access Protocol (LDAP). It is recommended that the service be disabled and other, more secure services be used
Remove or comment out start lines in /etc/init/ypserv.conf :
#start on (started portmap ON_BOOT=
# or (started portmap ON_BOOT=y
# and ((filesystem and static-network-up) or failsafe-boot)))
| Ensure NIS Server is not enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.2.17_Ensure_NIS_Server_is_not_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.451-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1127"/>
</check>
</complex-check>
</rule-result>
A number of insecure services exist. While disabling the servers prevents a local attack against these services, it is advised to remove their clients unless they are required.
Note: This should not be considered a comprehensive list of insecure service clients. You may wish to consider additions to those listed here for your environment.
The Network Information Service (NIS), formerly known as Yellow Pages, is a client-server directory service protocol used to distribute system configuration files. The NIS client ( ypbind ) was used to bind a machine to an NIS server and receive the distributed configuration files.
The NIS service is inherently an insecure system that has been vulnerable to DOS attacks, buffer overflows and has poor authentication for querying NIS maps. NIS generally has been replaced by such protocols as Lightweight Directory Access Protocol (LDAP). It is recommended that the service be removed.
Run the following command to uninstall nis :
apt-get remove nisImpact:
Many insecure service clients are used as troubleshooting tools and in testing environments. Uninstalling them can inhibit capability to test and troubleshoot. If they are required it is advisable to remove the clients after use to prevent accidental or intentional misuse.
| Ensure NIS Client is not installed | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.3.1_Ensure_NIS_Client_is_not_installed"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.451-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1128"/>
</check>
</complex-check>
</rule-result>
The rsh package contains the client commands for the rsh services.
These legacy clients contain numerous security exposures and have been replaced with the more secure SSH package. Even if the server is removed, it is best to ensure the clients are also removed to prevent users from inadvertently attempting to use these commands and therefore exposing their credentials. Note that removing the rsh package removes the clients for rsh , rcp and rlogin .
Run the following command to uninstall rsh :
apt-get remove rsh-client rsh-redone-clientImpact:
Many insecure service clients are used as troubleshooting tools and in testing environments. Uninstalling them can inhibit capability to test and troubleshoot. If they are required it is advisable to remove the clients after use to prevent accidental or intentional misuse.
| Ensure rsh client is not installed | Pass |
| Ensure rsh client is not installed | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.3.2_Ensure_rsh_client_is_not_installed"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.452-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1129"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1130"/>
</check>
</complex-check>
</rule-result>
The talk software makes it possible for users to send and receive messages across systems through a terminal session. The talk client, which allows initialization of talk sessions, is installed by default.
The software presents a security risk as it uses unencrypted protocols for communication.
Run the following command to uninstall talk :
apt-get remove talkImpact:
Many insecure service clients are used as troubleshooting tools and in testing environments. Uninstalling them can inhibit capability to test and troubleshoot. If they are required it is advisable to remove the clients after use to prevent accidental or intentional misuse.
| Ensure talk client is not installed | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.3.3_Ensure_talk_client_is_not_installed"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.452-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1131"/>
</check>
</complex-check>
</rule-result>
The telnet package contains the telnet client, which allows users to start connections to other systems via the telnet protocol.
The telnet protocol is insecure and unencrypted. The use of an unencrypted transmission medium could allow an unauthorized user to steal credentials. The ssh package provides an encrypted session and stronger security and is included in most Linux distributions.
Run the following command to uninstall telnet :
# apt-get remove telnetImpact:
Many insecure service clients are used as troubleshooting tools and in testing environments. Uninstalling them can inhibit capability to test and troubleshoot. If they are required it is advisable to remove the clients after use to prevent accidental or intentional misuse.
| Ensure telnet client is not installed | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.3.4_Ensure_telnet_client_is_not_installed"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.452-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1132"/>
</check>
</complex-check>
</rule-result>
The Lightweight Directory Access Protocol (LDAP) was introduced as a replacement for NIS/YP. It is a service that provides a method for looking up information from a central database.
If the system will not need to act as an LDAP client, it is recommended that the software be removed to reduce the potential attack surface.
Uninstall ldap-utils using the appropriate package manager or manual installation:
# apt-get remove ldap-utilsImpact:
Removing the LDAP client will prevent or inhibit using LDAP for authentication in your environment.
| Ensure LDAP client is not installed | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_2.3.5_Ensure_LDAP_client_is_not_installed"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.452-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1133"/>
</check>
</complex-check>
</rule-result>
This section provides guidance on for securing the network configuration of the system through kernel parameters, access list control, and firewall settings.
The following network parameters are intended for use if the system is to act as a host only. A system is considered host only if the system has a single interface, or has multiple interfaces but will not be configured as a router.
The net.ipv4.ip_forward flag is used to tell the system whether it can forward packets or not.
Setting the flag to 0 ensures that a system with multiple interfaces (for example, a hard proxy), will never be able to forward packets, and therefore, never serve as a router.
Set the following parameter in the /etc/sysctl.conf file:
net.ipv4.ip_forward = 0Run the following commands to set the active kernel parameters:
# sysctl -w net.ipv4.ip_forward=0
# sysctl -w net.ipv4.route.flush=1
| Ensure IP forwarding is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.1.1_Ensure_IP_forwarding_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.452-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1134"
value-id="xccdf_org.cisecurity.benchmarks_value_3.1.1.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1134"/>
</check>
</complex-check>
</rule-result>
ICMP Redirects are used to send routing information to other hosts. As a host itself does not act as a router (in a host only configuration), there is no need to send redirects.
An attacker could use a compromised host to send invalid ICMP redirects to other router devices in an attempt to corrupt routing and have users access a system set up by the attacker as opposed to a valid system.
Set the following parameters in the /etc/sysctl.conf file:
net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.default.send_redirects = 0
Run the following commands to set the active kernel parameters:
# sysctl -w net.ipv4.conf.all.send_redirects=0
# sysctl -w net.ipv4.conf.default.send_redirects
=0
# sysctl -w net.ipv4.route.flush=1
| Ensure packet redirect sending is disabled | Fail |
| Ensure packet redirect sending is disabled | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.1.2_Ensure_packet_redirect_sending_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.452-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1135"
value-id="xccdf_org.cisecurity.benchmarks_value_3.1.2.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1135"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1136"
value-id="xccdf_org.cisecurity.benchmarks_value_3.1.2.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1136"/>
</check>
</complex-check>
</rule-result>
The following network parameters are intended for use on both host only and router systems. A system acts as a router if it has at least two interfaces and is configured to perform routing functions.
In networking, source routing allows a sender to partially or fully specify the route packets take through a network. In contrast, non-source routed packets travel a path determined by routers in the network. In some cases, systems may not be routable or reachable from some locations (e.g. private addresses vs. Internet routable), and so source routed packets would need to be used.
Setting net.ipv4.conf.all.accept_source_route and net.ipv4.conf.default.accept_source_route to 0 disables the system from accepting source routed packets. Assume this system was capable of routing packets to Internet routable addresses on one interface and private addresses on another interface. Assume that the private addresses were not routable to the Internet routable addresses and vice versa. Under normal routing circumstances, an attacker from the Internet routable addresses could not use the system as a way to reach the private address systems. If, however, source routed packets were allowed, they could be used to gain access to the private address systems as the route could be specified, rather than rely on routing protocols that did not allow this routing.
Set the following parameters in the /etc/sysctl.conf file:
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.
conf.default.accept_source_route = 0Run the following commands to set the active kernel parameters:
# sysctl -w net.ipv4.conf.all.accept_source_route=0
# sysctl -w net.ipv4.conf.default.accept_source_route=0
# sysctl -w net.ipv4.route.flush=1
| Ensure source routed packets are not accepted | Pass |
| Ensure source routed packets are not accepted | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.2.1_Ensure_source_routed_packets_are_not_accepted"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.453-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1137"
value-id="xccdf_org.cisecurity.benchmarks_value_3.2.1.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1137"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1138"
value-id="xccdf_org.cisecurity.benchmarks_value_3.2.1.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1138"/>
</check>
</complex-check>
</rule-result>
ICMP redirect messages are packets that convey routing information and tell your host (acting as a router) to send packets via an alternate path. It is a way of allowing an outside routing device to update your system routing tables. By setting net.ipv4.conf.all.accept_redirects to 0, the system will not accept any ICMP redirect messages, and therefore, won't allow outsiders to update the system's routing tables.
Attackers could use bogus ICMP redirect messages to maliciously alter the system routing tables and get them to send packets to incorrect networks and allow your system packets to be captured.
Set the following parameters in the /etc/sysctl.conf file:
net.ipv4.conf.all.accept_redirects = 0
net.ipv4.conf.default.accept_redirects = 0
Run the following commands to set the active kernel parameters:
# sysctl -w net.ipv4.conf.all.accept_redirects=0
# sysctl -w net.ipv4.conf.default.accept_redirects=0
# sysctl -w net.ipv4.route.flush=1
| Ensure ICMP redirects are not accepted | Pass |
| Ensure ICMP redirects are not accepted | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.2.2_Ensure_ICMP_redirects_are_not_accepted"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.453-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1139"
value-id="xccdf_org.cisecurity.benchmarks_value_3.2.2.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1139"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1140"
value-id="xccdf_org.cisecurity.benchmarks_value_3.2.2.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1140"/>
</check>
</complex-check>
</rule-result>
Secure ICMP redirects are the same as ICMP redirects, except they come from gateways listed on the default gateway list. It is assumed that these gateways are known to your system, and that they are likely to be secure.
It is still possible for even known gateways to be compromised. Setting net.ipv4.conf.all.secure_redirects to 0 protects the system from routing table updates by possibly compromised known gateways.
Set the following parameters in the /etc/sysctl.conf file:
net.ipv4.conf.all.secure_redirects = 0
net.ipv4.conf.default.secure_redirects = 0
Run the following commands to set the active kernel parameters:
# sysctl -w net.ipv4.conf.all.secure_redirects=0
# sysctl -w net.ipv4.conf.default.secure_redirects=0
# sysctl -w net.ipv4.route.flush=1
| Ensure secure ICMP redirects are not accepted | Fail |
| Ensure secure ICMP redirects are not accepted | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.2.3_Ensure_secure_ICMP_redirects_are_not_accepted"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.453-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1141"
value-id="xccdf_org.cisecurity.benchmarks_value_3.2.3.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1141"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1142"
value-id="xccdf_org.cisecurity.benchmarks_value_3.2.3.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1142"/>
</check>
</complex-check>
</rule-result>
When enabled, this feature logs packets with un-routable source addresses to the kernel log.
Enabling this feature and logging these packets allows an administrator to investigate the possibility that an attacker is sending spoofed packets to their system.
Set the following parameters in the /etc/sysctl.conf file:
net.ipv4.conf.all.log_martians = 1
net.ipv4.conf.default.log_martians = 1
Run the following commands to set the active kernel parameters:
# sysctl -w net.ipv4.conf.all.log_martians=1
# sysctl -w net.ipv4.conf.default.log_martians=1
# sysctl -w net.ipv4.route.flush=1
| Ensure suspicious packets are logged | Fail |
| Ensure suspicious packets are logged | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.2.4_Ensure_suspicious_packets_are_logged"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.453-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1143"
value-id="xccdf_org.cisecurity.benchmarks_value_3.2.4.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1143"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1144"
value-id="xccdf_org.cisecurity.benchmarks_value_3.2.4.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1144"/>
</check>
</complex-check>
</rule-result>
Setting net.ipv4.icmp_echo_ignore_broadcasts to 1 will cause the system to ignore all ICMP echo and timestamp requests to broadcast and multicast addresses.
Accepting ICMP echo and timestamp requests with broadcast or multicast destinations for your network could be used to trick your host into starting (or participating) in a Smurf attack. A Smurf attack relies on an attacker sending large amounts of ICMP broadcast messages with a spoofed source address. All hosts receiving this message and responding would send echo-reply messages back to the spoofed address, which is probably not routable. If many hosts respond to the packets, the amount of traffic on the network could be significantly multiplied.
Set the following parameter in the /etc/sysctl.conf file:
net.ipv4.icmp_echo_ignore_broadcasts = 1Run the following commands to set the active kernel parameters:
# sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=1
# sysctl -w net.ipv4.route.flush=1
| Ensure broadcast ICMP requests are ignored | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.2.5_Ensure_broadcast_ICMP_requests_are_ignored"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.453-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1145"
value-id="xccdf_org.cisecurity.benchmarks_value_3.2.5.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1145"/>
</check>
</complex-check>
</rule-result>
Setting icmp_ignore_bogus_error_responses to 1 prevents the kernel from logging bogus responses (RFC-1122 non-compliant) from broadcast reframes, keeping file systems from filling up with useless log messages.
Some routers (and some attackers) will send responses that violate RFC-1122 and attempt to fill up a log file system with many useless error messages.
Set the following parameter in the /etc/sysctl.conf file:
net.ipv4.icmp_ignore_bogus_error_responses = 1Run the following commands to set the active kernel parameters:
# sysctl -w net.ipv4.icmp_ignore_bogus_error_responses=1
# sysctl -w net.ipv4.route.flush=1
| Ensure bogus ICMP responses are ignored | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.2.6_Ensure_bogus_ICMP_responses_are_ignored"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.453-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1146"
value-id="xccdf_org.cisecurity.benchmarks_value_3.2.6.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1146"/>
</check>
</complex-check>
</rule-result>
Setting net.ipv4.conf.all.rp_filter and net.ipv4.conf.default.rp_filter to 1 forces the Linux kernel to utilize reverse path filtering on a received packet to determine if the packet was valid. Essentially, with reverse path filtering, if the return packet does not go out the same interface that the corresponding source packet came from, the packet is dropped (and logged if log_martians is set).
Setting these flags is a good way to deter attackers from sending your system bogus packets that cannot be responded to. One instance where this feature breaks down is if asymmetrical routing is employed. This would occur when using dynamic routing protocols (bgp, ospf, etc) on your system. If you are using asymmetrical routing on your system, you will not be able to enable this feature without breaking the routing.
Set the following parameters in the /etc/sysctl.conf file:
net.ipv4.conf.all.rp_filter = 1
net.ipv4.conf.default.rp_filter = 1
Run the following commands to set the active kernel parameters:
# sysctl -w net.ipv4.conf.all.rp_filter=1
# sysctl -w net.ipv4.conf.default.rp_filter=1
# sysctl -w net.ipv4.route.flush=1
| Ensure Reverse Path Filtering is enabled | Pass |
| Ensure Reverse Path Filtering is enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.2.7_Ensure_Reverse_Path_Filtering_is_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.454-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1147"
value-id="xccdf_org.cisecurity.benchmarks_value_3.2.7.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1147"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1148"
value-id="xccdf_org.cisecurity.benchmarks_value_3.2.7.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1148"/>
</check>
</complex-check>
</rule-result>
When tcp_syncookies is set, the kernel will handle TCP SYN packets normally until the half-open connection queue is full, at which time, the SYN cookie functionality kicks in. SYN cookies work by not using the SYN queue at all. Instead, the kernel simply replies to the SYN with a SYN|ACK, but will include a specially crafted TCP sequence number that encodes the source and destination IP address and port number and the time the packet was sent. A legitimate connection would send the ACK packet of the three way handshake with the specially crafted sequence number. This allows the system to verify that it has received a valid response to a SYN cookie and allow the connection, even though there is no corresponding SYN in the queue.
Attackers use SYN flood attacks to perform a denial of service attacked on a system by sending many SYN packets without completing the three way handshake. This will quickly use up slots in the kernel's half-open connection queue and prevent legitimate connections from succeeding. SYN cookies allow the system to keep accepting valid connections, even if under a denial of service attack.
Set the following parameter in the /etc/sysctl.conf file:
net.ipv4.tcp_syncookies = 1Run the following commands to set the active kernel parameters:
# sysctl -w net.ipv4.tcp_syncookies=1
# sysctl -w net.ipv4.route.flush=1
| Ensure TCP SYN Cookies is enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.2.8_Ensure_TCP_SYN_Cookies_is_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.454-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1149"
value-id="xccdf_org.cisecurity.benchmarks_value_3.2.8.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1149"/>
</check>
</complex-check>
</rule-result>
IPv6 is a networking protocol that supersedes IPv4. It has more routable addresses and has built in security. If IPv6 is to be used, follow this section of the benchmark to configure IPv6, otherwise disable IPv6.
This setting disables the system's ability to accept IPv6 router advertisements.
It is recommended that systems not accept router advertisements as they could be tricked into routing traffic to compromised machines. Setting hard routes within the system (usually a single default route to a trusted router) protects the system from bad routes.
Set the following parameters in the /etc/sysctl.conf file:
net.ipv6.conf.all.accept_ra = 0
net.ipv6.conf.default.accept_ra = 0
Run the following commands to set the active kernel parameters:
# sysctl -w net.ipv6.conf.all.accept_ra=0
# sysctl -w net.ipv6.conf.default.accept_ra=0
# sysctl -w net.ipv6.route.flush=1
| Ensure IPv6 router advertisements are not accepted | Fail |
| Ensure IPv6 router advertisements are not accepted | Fail |
| Ensure IPv6 router advertisements are not accepted | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.3.1_Ensure_IPv6_router_advertisements_are_not_accepted"
role="unscored"
severity="unknown"
time="2019-11-19T23:30:03.455-05:00"
version="1"
weight="0.0">
<result>informational</result>
<complex-check operator="OR" negate="false">
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1150"
value-id="xccdf_org.cisecurity.benchmarks_value_3.3.1.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1150"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1151"
value-id="xccdf_org.cisecurity.benchmarks_value_3.3.1.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1151"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1152"
value-id="xccdf_org.cisecurity.benchmarks_value_3.3.1.3_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1152"/>
</check>
</complex-check>
</rule-result>
This setting prevents the system from accepting ICMP redirects. ICMP redirects tell the system about alternate routes for sending traffic.
It is recommended that systems not accept ICMP redirects as they could be tricked into routing traffic to compromised machines. Setting hard routes within the system (usually a single default route to a trusted router) protects the system from bad routes.
Set the following parameters in the /etc/sysctl.conf file:
net.ipv6.conf.all.accept_redirects = 0
net.ipv6.conf.default.accept_redirects = 0
Run the following commands to set the active kernel parameters:
# sysctl -w net.ipv6.conf.all.accept_redirects=0
# sysctl -w net.ipv6.conf.default.accept_redirects=0
# sysctl -w net.ipv6.route.flush=1
| Ensure IPv6 redirects are not accepted | Pass |
| Ensure IPv6 redirects are not accepted | Pass |
| Ensure IPv6 redirects are not accepted | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.3.2_Ensure_IPv6_redirects_are_not_accepted"
role="unscored"
severity="unknown"
time="2019-11-19T23:30:03.455-05:00"
version="1"
weight="0.0">
<result>informational</result>
<complex-check operator="OR" negate="false">
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1153"
value-id="xccdf_org.cisecurity.benchmarks_value_3.3.2.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1153"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1154"
value-id="xccdf_org.cisecurity.benchmarks_value_3.3.2.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1154"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1155"
value-id="xccdf_org.cisecurity.benchmarks_value_3.3.2.3_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1155"/>
</check>
</complex-check>
</rule-result>
Although IPv6 has many advantages over IPv4, few organizations have implemented IPv6.
If IPv6 is not to be used, it is recommended that it be disabled to reduce the attack surface of the system.
Edit /etc/default/grub and add 'ipv6.disable=1' to GRUB_CMDLINE_LINUX:
GRUB_CMDLINE_LINUX="ipv6.disable=1"Run the following command to update the grub2 configuration:
# update-grub
| Ensure IPv6 is disabled | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.3.3_Ensure_IPv6_is_disabled"
role="unscored"
severity="unknown"
time="2019-11-19T23:30:03.455-05:00"
version="1"
weight="0.0">
<result>informational</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1156"
value-id="xccdf_org.cisecurity.benchmarks_value_3.3.3.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1156"/>
</check>
</complex-check>
</rule-result>
TCP Wrappers provides a simple access list and standardized logging method for services capable of supporting it. In the past, services that were called from inetd and xinetd supported the use of tcp wrappers. As inetd and xinetd have been falling in disuse, any service that can support tcp wrappers will have the libwrap.so library attached to it.
TCP Wrappers provide a good simple access list mechanism to services that may not have that support built in. It is recommended that all services that can support TCP Wrappers, use it.
Run the following command to install TCP Wrappers:
apt-get install tcpd
| Ensure TCP Wrappers is installed | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.4.1_Ensure_TCP_Wrappers_is_installed"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.455-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1157"/>
</check>
</complex-check>
</rule-result>
The /etc/hosts.allow file specifies which IP addresses are permitted to connect to the host. It is intended to be used in conjunction with the /etc/hosts.deny file.
The /etc/hosts.allow file supports access control by IP and helps ensure that only authorized systems can connect to the system.
Run the following command to create /etc/hosts.allow :
# echo "ALL:
<net>
/ <mask>
,
<net>
/ <mask>
, ..." >/etc/hosts.allow
where each <net>/<mask> combination (for example, "192.168.1.0/255.255.255.0") represents one network block in use by your organization that requires access to this system.
| Ensure /etc/hosts.allow is configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.4.2_Ensure_etchosts.allow_is_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.455-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1158"/>
</check>
</complex-check>
</rule-result>
The /etc/hosts.deny file specifies which IP addresses are not permitted to connect to the host. It is intended to be used in conjunction with the /etc/hosts.allow file.
The /etc/hosts.deny file serves as a failsafe so that any host not specified in /etc/hosts.allow is denied access to the system.
Run the following command to create /etc/hosts.deny :
# echo "ALL: ALL" >> /etc/hosts.deny
| Ensure /etc/hosts.deny is configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.4.3_Ensure_etchosts.deny_is_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.456-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1159"
value-id="xccdf_org.cisecurity.benchmarks_value_3.4.3.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1159"/>
</check>
</complex-check>
</rule-result>
The /etc/hosts.allow file contains networking information that is used by many applications and therefore must be readable for these applications to operate.
It is critical to ensure that the /etc/hosts.allow file is protected from unauthorized write access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.
Run the following commands to set permissions on /etc/hosts.allow :
# chown root:root /etc/hosts.allow
# chmod 644 /etc/hosts.allow
| Ensure permissions on /etc/hosts.allow are configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.4.4_Ensure_permissions_on_etchosts.allow_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.456-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1160"/>
</check>
</complex-check>
</rule-result>
The /etc/hosts.deny file contains network information that is used by many system applications and therefore must be readable for these applications to operate.
It is critical to ensure that the /etc/hosts.deny file is protected from unauthorized write access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.
Run the following commands to set permissions on /etc/hosts.deny :
# chown root:root /etc/hosts.deny
# chmod 644 /etc/hosts.deny
| Ensure permissions on /etc/hosts.deny are 644 | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.4.5_Ensure_permissions_on_etchosts.deny_are_644"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.456-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1161"/>
</check>
</complex-check>
</rule-result>
The Linux kernel modules support several network protocols that are not commonly used. If these protocols are not needed, it is recommended that they be disabled in the kernel.
Note: This should not be considered a comprehensive list of uncommon network protocols, you may wish to consider additions to those listed here for your environment.
The Datagram Congestion Control Protocol (DCCP) is a transport layer protocol that supports streaming media and telephony. DCCP provides a way to gain access to congestion control, without having to do it at the application layer, but does not provide in-sequence delivery.
If the protocol is not required, it is recommended that the drivers not be installed
to reduce the potential attack surface.
Edit or create the file /etc/modprobe.d/CIS.conf and add the following line:
install dccp /bin/true
| Ensure DCCP is disabled | Fail |
| Ensure DCCP is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.5.1_Ensure_DCCP_is_disabled"
role="unscored"
severity="unknown"
time="2019-11-19T23:30:03.456-05:00"
version="1"
weight="0.0">
<result>informational</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1162"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1163"/>
</check>
</complex-check>
</rule-result>
The Stream Control Transmission Protocol (SCTP) is a transport layer protocol used to support message oriented communication, with several streams of messages in one connection. It serves a similar function as TCP and UDP, incorporating features of both. It is message-oriented like UDP, and ensures reliable in-sequence transport of messages with congestion control like TCP.
If the protocol is not being used, it is recommended that kernel module not be loaded, disabling the service to reduce the potential attack surface.
Edit or create the file /etc/modprobe.d/CIS.conf and add the following line:
install sctp /bin/true
| Ensure SCTP is disabled | Fail |
| Ensure SCTP is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.5.2_Ensure_SCTP_is_disabled"
role="unscored"
severity="unknown"
time="2019-11-19T23:30:03.456-05:00"
version="1"
weight="0.0">
<result>informational</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1164"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1165"/>
</check>
</complex-check>
</rule-result>
The Reliable Datagram Sockets (RDS) protocol is a transport layer protocol designed to provide low-latency, high-bandwidth communications between cluster nodes. It was developed by the Oracle Corporation.
If the protocol is not being used, it is recommended that kernel module not be loaded, disabling the service to reduce the potential attack surface.
Edit or create the file /etc/modprobe.d/CIS.conf and add the following line:
install rds /bin/true
| Ensure RDS is disabled | Fail |
| Ensure RDS is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.5.3_Ensure_RDS_is_disabled"
role="unscored"
severity="unknown"
time="2019-11-19T23:30:03.457-05:00"
version="1"
weight="0.0">
<result>informational</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1166"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1167"/>
</check>
</complex-check>
</rule-result>
The Transparent Inter-Process Communication (TIPC) protocol is designed to provide communication between cluster nodes.
If the protocol is not being used, it is recommended that kernel module not be loaded, disabling the service to reduce the potential attack surface.
Edit or create the file /etc/modprobe.d/CIS.conf and add the following line:
install tipc /bin/true
| Ensure TIPC is disabled | Fail |
| Ensure TIPC is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.5.4_Ensure_TIPC_is_disabled"
role="unscored"
severity="unknown"
time="2019-11-19T23:30:03.457-05:00"
version="1"
weight="0.0">
<result>informational</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1168"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1169"/>
</check>
</complex-check>
</rule-result>
IPtables is an application that allows a system administrator to configure the IPv4 tables, chains and rules provided by the Linux kernel firewall. While several methods of configuration exist this section is intended only to ensure the resulting IPtables rules are in place, not how they are configured. If IPv6 is in use in your environment, similar settings should be applied to the IP6tables as well.
Note: This section broadly assumes starting with an empty IPtables firewall ruleset (established by flushing the rules with iptables -F ). Remediation steps included only affect the live system, you will also need to configure your default firewall configuration to apply on boot. Configuration of a live systems firewall directly over a remote connection will often result in being locked out. It is advised to have a known good firewall configuration set to run on boot and to configure an entire firewall structure in a script that is then run and tested before saving to boot. The following script will implement the firewall rules of this section and open port 22(ssh) from anywhere:
#!/bin/bash
# Flush IPtables rules
iptables -F
# Ensure default deny firewall policy
iptables -P INPUT DROP
iptables -P OUTPUT DROP
iptables -P FORWARD DROP
# Ensure loopback traffic is configured
iptables -A INPUT -i lo -j ACCEPT
iptables -A OUTPUT -o lo -j ACCEPT
iptables -A INPUT -s 127.0.0.0/8 -j DROP
# Ensure outbound and established connections are configured
iptables -A OUTPUT -p tcp -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -p udp -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -p icmp -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A INPUT -p tcp -m state --state ESTABLISHED -j ACCEPT
iptables -A INPUT -p udp -m state --state ESTABLISHED -j ACCEPT
iptables -A INPUT -p icmp -m state --state ESTABLISHED -j ACCEPT
# Open inbound ssh(tcp port 22) connections
iptables -A INPUT -p tcp --dport 22 -m state --state NEW -j ACCEPT
Ubuntu is distributed with the UFW service which acts as a front end to iptables. The default configuration of UFW implements a configuration very similar to that recommended here. IPTables configuration allows for far more complex implementations than those listed here which may satisfy the intent of these recommendations without strictly matching the examples provided. Note: UFW may interfere with sysctl settings.
iptables allows configuration of the IPv4 tables in the linux kernel and the rules stored within them. Most firewall configuration utilities operate as a front end to iptables .
iptables is required for firewall management and configuration.
Run the following command to install iptables :
# apt-get install iptables
| Ensure iptables is installed | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.6.1_Ensure_iptables_is_installed"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.457-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1170"/>
</check>
</complex-check>
</rule-result>
A default deny all policy on connections ensures that any unconfigured network usage will be rejected.
With a default accept policy the firewall will accept any packet that is not configured to be denied. It is easier to white list acceptable usage than to black list unacceptable usage.
Run the following commands to implement a default DROP policy:
# iptables -P INPUT DROP
# iptables -P OUTPUT DROP
# iptables -P FORWARD DROP
| Ensure default deny firewall policy | Pass |
| Ensure default deny firewall policy | Pass |
| Ensure default deny firewall policy | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.6.2_Ensure_default_deny_firewall_policy"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.457-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1171"
value-id="xccdf_org.cisecurity.benchmarks_value_3.6.2.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1171"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1172"
value-id="xccdf_org.cisecurity.benchmarks_value_3.6.2.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1172"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1173"
value-id="xccdf_org.cisecurity.benchmarks_value_3.6.2.3_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1173"/>
</check>
</complex-check>
</rule-result>
Configure the loopback interface to accept traffic. Configure all other interfaces to deny traffic to the loopback network (127.0.0.0/8).
Loopback traffic is generated between processes on machine and is typically critical to operation of the system. The loopback interface is the only place that loopback network (127.0.0.0/8) traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure.
Run the following commands to implement the loopback rules:
# iptables -A INPUT -i lo -j ACCEPT
# iptables -A OUTPUT -o lo -j ACCEPT
# iptables -A INPUT -s 127.0.0.0/8 -j DROP
| Ensure loopback traffic is configured | Fail |
| Ensure loopback traffic is configured | Fail |
| Ensure loopback traffic is configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.6.3_Ensure_loopback_traffic_is_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.458-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1174"
value-id="xccdf_org.cisecurity.benchmarks_value_3.6.3.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1174"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1175"
value-id="xccdf_org.cisecurity.benchmarks_value_3.6.3.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1175"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1176"
value-id="xccdf_org.cisecurity.benchmarks_value_3.6.3.3_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1176"/>
</check>
</complex-check>
</rule-result>
Any ports that have been opened on non-loopback addresses need firewall rules to govern traffic.
Without a firewall rule configured for open ports default firewall policy will drop all packets to these ports.
For each port identified in the audit which does not have a firewall rule establish a proper rule for accepting inbound connections:
# iptables -A INPUT -p
<protocol>
--dport
<port>
-m state --state NEW -j ACCEPT
| Ensure firewall rules exist for all open ports | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_3.6.5_Ensure_firewall_rules_exist_for_all_open_ports"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.458-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1177"/>
</check>
</complex-check>
</rule-result>
The items in this section describe how to configure logging, log monitoring, and auditing, using tools included in Ubuntu.
It is recommended that rsyslog be used for logging (with logwatch providing summarization) and auditd be used for auditing (with aureport providing summarization) to automatically monitor logs for intrusion attempts and other suspicious system behavior.
In addition to the local log files created by the steps in this section, it is also recommended that sites collect copies of their system logs on a secure, centralized log server via an encrypted connection. Not only does centralized logging help sites correlate events that may be occurring on multiple systems, but having a second copy of the system log information may be critical after a system compromise where the attacker has modified the local log files on the affected system(s). If a log correlation system is deployed, configure it to process the logs described in this section.
Because it is often necessary to correlate log information from many different systems (particularly after a security incident) it is recommended that the time be synchronized among systems and devices connected to the local network. The standard Internet protocol for time synchronization is the Network Time Protocol (NTP), which is supported by most network-ready devices. See the ntpd(8) manual page for more information on configuring NTP.
It is important that all logs described in this section be monitored on a regular basis and correlated to determine trends. A seemingly innocuous entry in one log could be more significant when compared to an entry in another log.
Note on log file permissions: There really isn't a "one size fits all" solution to the permissions on log files. Many sites utilize group permissions so that administrators who are in a defined security group, such as "wheel" do not have to elevate privileges to root in order to read log files. Also, if a third party log aggregation tool is used, it may need to have group permissions to read the log files, which is preferable to having it run setuid to root. Therefore, there are two remediation and audit steps for log file permissions. One is for systems that do not have a secured group method implemented that only permits root to read the log files ( root:root 600 ). The other is for sites that do have such a setup and are designated as root:securegrp 640 where securegrp is the defined security group (in some cases wheel ).
System auditing, through auditd , allows system administrators to monitor their systems such that they can detect unauthorized access or modification of data. By default, auditd will audit SELinux AVC denials, system logins, account modifications, and authentication events. Events will be logged to /var/log/audit/audit.log . The recording of these events will use a modest amount of disk space on a system. If significantly more events are captured, additional on system or off system storage may need to be allocated.
The recommendations in this section implement an audit policy that produces large
quantities of logged data. In some environments it can be challenging to store or
process these logs and as such they are marked as Level 2 for both Servers and Workstations.
Note:
For 64 bit systems that have arch as a rule parameter, you will need two rules: one
for 64 bit and one for 32 bit systems. For 32 bit systems, only one rule is needed.
Note: Once all configuration changes have been made to /etc/audit/audit.rules , the auditd configuration must be reloaded:
# service auditd reloadWhen auditing, it is important to carefully configure the storage requirements for audit logs. By default, auditd will max out the log files at 5MB and retain only 4 copies of them. Older versions will be deleted. It is possible on a system that the 20 MBs of audit logs may fill up the system causing loss of audit data. While the recommendations here provide guidance, check your site policy for audit storage requirements.
Logging services should be configured to prevent information leaks and to aggregate logs on a remote server so that they can be reviewed in the event of a system compromise and ease log analysis.
The rsyslog
software is recommended as a replacement for the
syslogd
daemon and provides improvements over
syslogd
, such as connection-oriented (i.e. TCP) transmission of logs, the option to log to
database formats, and the encryption of log data en route to a central logging server.
Note:
This section only applies if
rsyslog
is installed on the system.
Once the rsyslog package is installed it needs to be activated.
If the rsyslog service is not activated the system may default to the syslogd service or lack logging instead.
Set the proper start conditions in /etc/init/rsyslog.conf :
start on filesystem
| Ensure rsyslog Service is enabled | Fail |
| Ensure rsyslog Service is enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.1_Ensure_rsyslog_Service_is_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.458-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="OR" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1243"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1244"/>
</check>
</complex-check>
</rule-result>
rsyslog will create logfiles that do not already exist on the system. This setting controls what permissions will be applied to these newly created files.
It is important to ensure that log files have the correct permissions to ensure that sensitive data is archived and protected.
Edit the /etc/rsyslog.conf and set $FileCreateMode to 0640 or more restrictive:
$FileCreateMode 0640
| Ensure rsyslog default file permissions configured | Pass |
| Ensure rsyslog default file permissions configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.3_Ensure_rsyslog_default_file_permissions_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.458-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="OR" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1245"
value-id="xccdf_org.cisecurity.benchmarks_value_4.2.1.3.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1245"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1246"/>
</check>
</complex-check>
</rule-result>
The rsyslog utility supports the ability to send logs it gathers to a remote log host running syslogd(8) or to receive messages from remote hosts, reducing administrative overhead.
Storing log data on a remote host protects log integrity from local attacks. If an attacker gains root access on the local system, they could tamper with or remove log data that is stored on the local system
Edit the /etc/rsyslog.conf file and add the following line (where loghost.example.com is the name of your central log host).
*.* @@loghost.example.comRun the following command to restart rsyslog :
# pkill -HUP rsyslogd
| Ensure rsyslog is configured to send logs to a remote log host | Fail |
| Ensure rsyslog is configured to send logs to a remote log host | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_4.2.1.4_Ensure_rsyslog_is_configured_to_send_logs_to_a_remote_log_host"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.459-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="OR" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1247"
value-id="xccdf_org.cisecurity.benchmarks_value_4.2.1.4.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1247"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1248"/>
</check>
</complex-check>
</rule-result>
The syslog-ng
software is recommended as a replacement for the
syslogd
daemon and provides improvements over
syslogd
, such as connection-oriented (i.e. TCP) transmission of logs, the option to log to
database formats, and the encryption of log data en route to a central logging server.
Note:
This section only applies if
syslog-ng
is installed on the system.
Once the syslog-ng package is installed it needs to be activated.
If the syslog-ng service is not activated the system may default to the syslogd service or lack logging instead.
Run the following command to enable syslog-ng :
# update-rc.d syslog-ng enable
| Ensure syslog-ng service is enabled | Fail |
| Ensure syslog-ng service is enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.1_Ensure_syslog-ng_service_is_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.459-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="OR" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1249"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1250"/>
</check>
</complex-check>
</rule-result>
syslog-ng will create logfiles that do not already exist on the system. This setting controls what permissions will be applied to these newly created files.
It is important to ensure that log files exist and have the correct permissions to ensure that sensitive syslog-ng data is archived and protected.
Edit the /etc/syslog-ng/syslog-ng.conf and set perm option to 0640 or more restrictive:
options { chain_hostnames(off); flush_lines(0); perm(0640); stats_freq(3600); threaded(yes);
};
| Ensure syslog-ng default file permissions configured | Fail |
| Ensure syslog-ng default file permissions configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_4.2.2.3_Ensure_syslog-ng_default_file_permissions_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.459-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="OR" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1251"
value-id="xccdf_org.cisecurity.benchmarks_value_4.2.2.3.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1251"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1252"/>
</check>
</complex-check>
</rule-result>
The rsyslog and syslog-ng software are recommended replacements to the original syslogd daemon which provide improvements over syslogd , such as connection-oriented (i.e. TCP) transmission of logs, the option to log to database formats, and the encryption of log data en route to a central logging server.
The security enhancements of rsyslog and syslog-ng such as connection-oriented (i.e. TCP) transmission of logs, the option to log to database formats, and the encryption of log data en route to a central logging server) justify installing and configuring the package.
Install rsyslog or syslog-ng using one of the following commands:
# apt-get install rsyslog
# apt-get install syslog-ng
| Ensure rsyslog or syslog-ng is installed | Pass |
| Ensure rsyslog or syslog-ng is installed | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_4.2.3_Ensure_rsyslog_or_syslog-ng_is_installed"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.459-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="OR" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1253"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1254"/>
</check>
</complex-check>
</rule-result>
Log files stored in /var/log/ contain logged information from many services on the system, or on log hosts others as well.
It is important to ensure that log files have the correct permissions to ensure that sensitive data is archived and protected.
Run the following command to set permissions on all existing log files:
# chmod -R g-wx,o-rwx /var/log/*
| Ensure permissions on all logfiles are configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_4.2.4_Ensure_permissions_on_all_logfiles_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.459-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1255"/>
</check>
</complex-check>
</rule-result>
The cron daemon is used to execute batch jobs on the system.
While there may not be user jobs that need to be run on the system, the system does have maintenance jobs that may include security monitoring that have to run, and cron is used to execute them.
Edit start lines in /etc/init/cron.conf to match the following:
start on runlevel [2345]
| Ensure cron daemon is enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.1.1_Ensure_cron_daemon_is_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.460-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1256"/>
</check>
</complex-check>
</rule-result>
The /etc/crontab file is used by cron to control its own jobs. The commands in this item make sure that root is the user and group owner of the file and that only the owner can access the file.
This file contains information on what system jobs are run by cron. Write access to these files could provide unprivileged users with the ability to elevate their privileges. Read access to these files could provide users with the ability to gain insight on system jobs that run on the system and could provide them a way to gain unauthorized privileged access.
Run the following commands to set ownership and permissions on /etc/crontab :
# chown root:root /etc/crontab
# chmod og-rwx /etc/crontab
| Ensure permissions on /etc/crontab are configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.1.2_Ensure_permissions_on_etccrontab_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.460-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1257"/>
</check>
</complex-check>
</rule-result>
This directory contains system cron jobs that need to run on an hourly basis. The files in this directory cannot be manipulated by the crontab command, but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory.
Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls.
Run the following commands to set ownership and permissions on /etc/cron.hourly :
# chown root:root /etc/cron.hourly
# chmod og-rwx /etc/cron.hourly
| Ensure permissions on /etc/cron.hourly are configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.1.3_Ensure_permissions_on_etccron.hourly_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.460-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1258"/>
</check>
</complex-check>
</rule-result>
The /etc/cron.daily directory contains system cron jobs that need to run on a daily basis. The files in this directory cannot be manipulated by the crontab command, but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory.
Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls.
Run the following commands to set ownership and permissions on /etc/cron.daily :
# chown root:root /etc/cron.daily
# chmod og-rwx /etc/cron.daily
| Ensure permissions on /etc/cron.daily are configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.1.4_Ensure_permissions_on_etccron.daily_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.460-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1259"/>
</check>
</complex-check>
</rule-result>
The /etc/cron.weekly directory contains system cron jobs that need to run on a weekly basis. The files in this directory cannot be manipulated by the crontab command, but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory.
Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls.
Run the following commands to set ownership and permissions on /etc/cron.weekly :
# chown root:root /etc/cron.weekly
# chmod og-rwx /etc/cron.weekly
| Ensure permissions on /etc/cron.weekly are configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.1.5_Ensure_permissions_on_etccron.weekly_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.460-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1260"/>
</check>
</complex-check>
</rule-result>
The /etc/cron.monthly directory contains system cron jobs that need to run on a monthly basis. The files in this directory cannot be manipulated by the crontab command, but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory.
Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls.
Run the following commands to set ownership and permissions on /etc/cron.monthly :
# chown root:root /etc/cron.monthly
# chmod og-rwx /etc/cron.monthly
| Ensure permissions on /etc/cron.monthly are configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.1.6_Ensure_permissions_on_etccron.monthly_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.460-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1261"/>
</check>
</complex-check>
</rule-result>
The /etc/cron.d directory contains system cron jobs that need to run in a similar manner to the hourly, daily weekly and monthly jobs from /etc/crontab , but require more granular control as to when they run. The files in this directory cannot be manipulated by the crontab command, but are instead edited by system administrators using a text editor. The commands below restrict read/write and search access to user and group root, preventing regular users from accessing this directory.
Granting write access to this directory for non-privileged users could provide them the means for gaining unauthorized elevated privileges. Granting read access to this directory could give an unprivileged user insight in how to gain elevated privileges or circumvent auditing controls.
Run the following commands to set ownership and permissions on /etc/cron.d :
# chown root:root /etc/cron.d
# chmod og-rwx /etc/cron.d
| Ensure permissions on /etc/cron.d are configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.1.7_Ensure_permissions_on_etccron.d_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.461-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1262"/>
</check>
</complex-check>
</rule-result>
Configure /etc/cron.allow and /etc/at.allow to allow specific users to use these services. If /etc/cron.allow or /etc/at.allow do not exist, then /etc/at.deny and /etc/cron.deny are checked. Any user not specifically defined in those files is allowed to use at and cron. By removing the files, only users in /etc/cron.allow and /etc/at.allow are allowed to use at and cron. Note that even though a given user is not listed in cron.allow , cron jobs can still be run as that user. The cron.allow file only controls administrative access to the crontab command for scheduling and modifying cron jobs.
On many systems, only the system administrator is authorized to schedule cron jobs. Using the cron.allow file to control who can run cron jobs enforces this policy. It is easier to manage an allow list than a deny list. In a deny list, you could potentially add a user ID to the system and forget to add it to the deny files.
Run the following commands to remove /etc/cron.deny and /etc/at.deny and create and set permissions and ownership for /etc/cron.allow and /etc/at.allow :
# rm /etc/cron.deny
# rm /etc/at.deny
# touch /etc/cron.allow
# touch /etc/at.allow
# chmod og-rwx /etc/cron.allow
# chmod og-rwx /etc/at.allow
# chown root:root /etc/cron.allow
# chown root:root /etc/at.allow
| Ensure at/cron is restricted to authorized users | Pass |
| Ensure at/cron is restricted to authorized users | Fail |
| Ensure at/cron is restricted to authorized users | Fail |
| Ensure at/cron is restricted to authorized users | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.1.8_Ensure_atcron_is_restricted_to_authorized_users"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.461-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1263"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1264"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1265"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1266"/>
</check>
</complex-check>
</rule-result>
SSH is a secure, encrypted replacement for common login services such as telnet , ftp , rlogin , rsh , and rcp . It is strongly recommended that sites abandon older clear-text login protocols and use SSH to prevent session hijacking and sniffing of sensitive data off the network.
Note: The recommendations in this section only apply if the SSH daemon is installed on the system, if remote access is not required the SSH daemon can be removed and this section skipped.
Note: Once all configuration changes have been made to /etc/ssh/sshd_config , the sshd configuration must be reloaded:
# service sshd reloadThe /etc/ssh/sshd_config file contains configuration specifications for sshd . The command below sets the owner and group of the file to root.
The /etc/ssh/sshd_config file needs to be protected from unauthorized changes by non-privileged users.
Run the following commands to set ownership and permissions on /etc/ssh/sshd_config :
# chown root:root /etc/ssh/sshd_config
# chmod og-rwx /etc/ssh/sshd_config
| Ensure permissions on /etc/ssh/sshd_config are configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.1_Ensure_permissions_on_etcsshsshd_config_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.462-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1267"/>
</check>
</complex-check>
</rule-result>
SSH supports two different and incompatible protocols: SSH1 and SSH2. SSH1 was the original protocol and was subject to security issues. SSH2 is more advanced and secure.
SSH v1 suffers from insecurities that do not affect SSH v2.
Edit the /etc/ssh/sshd_config file to set the parameter as follows:
Protocol 2
| Ensure SSH Protocol is set to 2 | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.2_Ensure_SSH_Protocol_is_set_to_2"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.462-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1268"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.2.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1268"/>
</check>
</complex-check>
</rule-result>
The INFO parameter specifies that login and logout activity will be logged.
SSH provides several logging levels with varying amounts of verbosity. DEBUG is specifically not recommended other than strictly for debugging SSH communications since it provides so much data that it is difficult to identify important security information. INFO level is the basic level that only records login activity of SSH users. In many situations, such as Incident Response, it is important to determine when a particular user was active on a system. The logout record can eliminate those users who disconnected, which helps narrow the field.
Edit the /etc/ssh/sshd_config file to set the parameter as follows:
LogLevel INFO
| Ensure SSH LogLevel is set to INFO | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.3_Ensure_SSH_LogLevel_is_set_to_INFO"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.462-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1269"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.3.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1269"/>
</check>
</complex-check>
</rule-result>
The X11Forwarding parameter provides the ability to tunnel X11 traffic through the connection to enable remote graphic connections.
Disable X11 forwarding unless there is an operational requirement to use X11 applications directly. There is a small risk that the remote X11 servers of users who are logged in via SSH with X11 forwarding could be compromised by other users on the X11 server. Note that even if X11 forwarding is disabled, users can always install their own forwarders.
Edit the /etc/ssh/sshd_config file to set the parameter as follows:
X11Forwarding no
| Ensure SSH X11 forwarding is disabled | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.4_Ensure_SSH_X11_forwarding_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.462-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1270"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.4.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1270"/>
</check>
</complex-check>
</rule-result>
The MaxAuthTries parameter specifies the maximum number of authentication attempts permitted per connection. When the login failure count reaches half the number, error messages will be written to the syslog file detailing the login failure.
Setting the MaxAuthTries parameter to a low number will minimize the risk of successful brute force attacks to the SSH server. While the recommended setting is 4, set the number based on site policy.
Edit the /etc/ssh/sshd_config file to set the parameter as follows:
MaxAuthTries 4
| Ensure SSH MaxAuthTries is set to 4 or less | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.5_Ensure_SSH_MaxAuthTries_is_set_to_4_or_less"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.463-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1271"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.5.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1271"/>
</check>
</complex-check>
</rule-result>
The IgnoreRhosts parameter specifies that .rhosts and .shosts files will not be used in RhostsRSAAuthentication or HostbasedAuthentication .
Setting this parameter forces users to enter a password when authenticating with ssh.
Edit the /etc/ssh/sshd_config file to set the parameter as follows:
IgnoreRhosts yes
| Ensure SSH IgnoreRhosts is enabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.6_Ensure_SSH_IgnoreRhosts_is_enabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.463-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1272"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.6.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1272"/>
</check>
</complex-check>
</rule-result>
The HostbasedAuthentication parameter specifies if authentication is allowed through trusted hosts via the user of .rhosts , or /etc/hosts.equiv , along with successful public key client host authentication. This option only applies to SSH Protocol Version 2.
Even though the .rhosts files are ineffective if support is disabled in /etc/pam.conf , disabling the ability to use .rhosts files in SSH provides an additional layer of protection .
Edit the /etc/ssh/sshd_config file to set the parameter as follows:
HostbasedAuthentication no
| Ensure SSH HostbasedAuthentication is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.7_Ensure_SSH_HostbasedAuthentication_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.463-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1273"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.7.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1273"/>
</check>
</complex-check>
</rule-result>
The PermitRootLogin parameter specifies if the root user can log in using ssh(1). The default is no.
Disallowing root logins over SSH requires system admins to authenticate using their own individual account, then escalating to root via sudo or su . This in turn limits opportunity for non-repudiation and provides a clear audit trail in the event of a security incident
Edit the /etc/ssh/sshd_config file to set the parameter as follows:
PermitRootLogin no
| Ensure SSH root login is disabled | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.8_Ensure_SSH_root_login_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.463-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1274"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.8.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1274"/>
</check>
</complex-check>
</rule-result>
The PermitEmptyPasswords parameter specifies if the SSH server allows login to accounts with empty password strings.
Disallowing remote shell access to accounts that have an empty password reduces the probability of unauthorized access to the system
Edit the /etc/ssh/sshd_config file to set the parameter as follows:
PermitEmptyPasswords no
| Ensure SSH PermitEmptyPasswords is disabled | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.9_Ensure_SSH_PermitEmptyPasswords_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.463-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1275"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.9.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1275"/>
</check>
</complex-check>
</rule-result>
The PermitUserEnvironment option allows users to present environment options to the ssh daemon.
Permitting users the ability to set environment variables through the SSH daemon could potentially allow users to bypass security controls (e.g. setting an execution path that has ssh executing trojan'd programs)
Edit the /etc/ssh/sshd_config file to set the parameter as follows:
PermitUserEnvironment no
| Ensure SSH PermitUserEnvironment is disabled | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.10_Ensure_SSH_PermitUserEnvironment_is_disabled"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.464-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1276"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.10.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1276"/>
</check>
</complex-check>
</rule-result>
This variable limits the types of MAC algorithms that SSH can use during communication.
MD5 and 96-bit MAC algorithms are considered weak and have been shown to increase exploitability in SSH downgrade attacks. Weak algorithms continue to have a great deal of attention as a weak spot that can be exploited with expanded computing power. An attacker that breaks the algorithm could take advantage of a MiTM position to decrypt the SSH tunnel and capture credentials and information
Edit the /etc/ssh/sshd_config file to set the parameter as follows:
MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256,umac-128@openssh.com
| Ensure only approved MAC algorithms are used | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.11_Ensure_only_approved_MAC_algorithms_are_used"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.464-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1277"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.11.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1277"/>
</check>
</complex-check>
</rule-result>
The two options ClientAliveInterval and ClientAliveCountMax control the timeout of ssh sessions. When the ClientAliveInterval variable is set, ssh sessions that have no activity for the specified length of time are terminated. When the ClientAliveCountMax variable is set, sshd will send client alive messages at every ClientAliveInterval interval. When the number of consecutive client alive messages are sent with no response from the client, the ssh session is terminated. For example, if the ClientAliveInterval is set to 15 seconds and the ClientAliveCountMax is set to 3, the client ssh session will be terminated after 45 seconds of idle time.
Having no timeout value associated with a connection could allow an unauthorized user access to another user's ssh session (e.g. user walks away from their computer and doesn't lock the screen). Setting a timeout value at least reduces the risk of this happening..
While the recommended setting is 300 seconds (5 minutes), set this timeout value based on site policy. The recommended setting for ClientAliveCountMax is 0. In this case, the client session will be terminated after 5 minutes of idle time and no keepalive messages will be sent.
Edit the /etc/ssh/sshd_config file to set the parameters as follows:
ClientAliveInterval 300
ClientAliveCountMax 0
| Ensure SSH Idle Timeout Interval is configured | Fail |
| Ensure SSH Idle Timeout Interval is configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.12_Ensure_SSH_Idle_Timeout_Interval_is_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.464-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1278"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.12.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1278"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1279"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.12.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1279"/>
</check>
</complex-check>
</rule-result>
The LoginGraceTime parameter specifies the time allowed for successful authentication to the SSH server. The longer the Grace period is the more open unauthenticated connections can exist. Like other session controls in this session the Grace Period should be limited to appropriate organizational limits to ensure the service is available for needed access.
Setting the LoginGraceTime parameter to a low number will minimize the risk of successful brute force attacks to the SSH server. It will also limit the number of concurrent unauthenticated connections While the recommended setting is 60 seconds (1 Minute), set the number based on site policy.
Edit the /etc/ssh/sshd_config file to set the parameter as follows:
LoginGraceTime 60
| Ensure SSH LoginGraceTime is set to one minute or less | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.13_Ensure_SSH_LoginGraceTime_is_set_to_one_minute_or_less"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.464-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1280"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.13.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1280"/>
</check>
</complex-check>
</rule-result>
There are several options available to limit which users and group can access the system via SSH. It is recommended that at least one of the following options be leveraged:
AllowUsers
The AllowUsers variable gives the system administrator the option of allowing specific users to ssh into the system. The list consists of comma separated user names. Numeric user IDs are not recognized with this variable. If a system administrator wants to restrict user access further by only allowing the allowed users to log in from a particular host, the entry can be specified in the form of user@host.
AllowGroups
The AllowGroups variable gives the system administrator the option of allowing specific groups of users to ssh into the system. The list consists of comma separated group names. Numeric group IDs are not recognized with this variable.
DenyUsers
The DenyUsers variable gives the system administrator the option of denying specific users to ssh into the system. The list consists of comma separated user names. Numeric user IDs are not recognized with this variable. If a system administrator wants to restrict user access further by specifically denying a user's access from a particular host, the entry can be specified in the form of user@host.
DenyGroups
The DenyGroups variable gives the system administrator the option of denying specific groups of users to ssh into the system. The list consists of comma separated group names. Numeric group IDs are not recognized with this variable.
Restricting which users can remotely access the system via SSH will help ensure that only authorized users access the system.
Edit the /etc/ssh/sshd_config file to set one or more of the parameter as follows:
AllowUsers
<userlist>
AllowGroups
<grouplist>
DenyUsers
<userlist>
DenyGroups
<grouplist>
| Ensure SSH access is limited | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.14_Ensure_SSH_access_is_limited"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.464-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1281"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.14.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1281"/>
</check>
</complex-check>
</rule-result>
The Banner parameter specifies a file whose contents must be sent to the remote user before authentication is permitted. By default, no banner is displayed.
Banners are used to warn connecting users of the particular site's policy regarding connection. Presenting a warning message prior to the normal user login may assist the prosecution of trespassers on the computer system.
Edit the /etc/ssh/sshd_config file to set the parameter as follows:
Banner /etc/issue.net
| Ensure SSH warning banner is configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.2.15_Ensure_SSH_warning_banner_is_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.464-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1282"
value-id="xccdf_org.cisecurity.benchmarks_value_5.2.15.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1282"/>
</check>
</complex-check>
</rule-result>
PAM (Pluggable Authentication Modules) is a service that implements modular authentication modules on UNIX systems. PAM is implemented as a set of shared objects that are loaded and executed when a program needs to authenticate a user. Files for PAM are typically located in the /etc/pam.d directory. PAM must be carefully configured to secure system authentication. While this section covers some of PAM, please consult other PAM resources to fully understand the configuration capabilities.
The pam_pwquality.so module checks the strength of passwords. It performs checks such as making sure a password is not a dictionary word, it is a certain length, contains a mix of characters (e.g. alphabet, numeric, other) and more. The following are definitions of the pam_pwquality .so options.
The following options are set in the /etc/security/pwquality.conf file:
The settings shown above are one possible policy. Alter these values to conform to your own organization's password policies.
Strong passwords protect systems from being hacked through brute force methods.
Run the following command to install the pam_pwquality module:
apt-get install libpam-pwqualityEdit the /etc/pam.d/common-passwd file to include the appropriate options for pam_pwquality.so and to conform to site policy:
password requisite pam_pwquality.so try_first_pass retry=3Edit /etc/security/pwquality.conf to add or update the following settings to conform to site policy:
minlen=14
dcredit=-1
ucredit=-1
ocredit=-1
lcredit=-1
| Ensure password creation requirements are configured | Fail |
| Ensure password creation requirements are configured | Fail |
| Ensure password creation requirements are configured | Fail |
| Ensure password creation requirements are configured | Fail |
| Ensure password creation requirements are configured | Fail |
| Ensure password creation requirements are configured | Fail |
| Ensure password creation requirements are configured | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.3.1_Ensure_password_creation_requirements_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.465-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1283"
value-id="xccdf_org.cisecurity.benchmarks_value_5.3.1.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1283"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1284"
value-id="xccdf_org.cisecurity.benchmarks_value_5.3.1.2_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1284"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1285"
value-id="xccdf_org.cisecurity.benchmarks_value_5.3.1.3_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1285"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1286"
value-id="xccdf_org.cisecurity.benchmarks_value_5.3.1.4_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1286"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1287"
value-id="xccdf_org.cisecurity.benchmarks_value_5.3.1.5_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1287"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1288"
value-id="xccdf_org.cisecurity.benchmarks_value_5.3.1.6_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1288"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1289"
value-id="xccdf_org.cisecurity.benchmarks_value_5.3.1.7_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1289"/>
</check>
</complex-check>
</rule-result>
The /etc/security/opasswd file stores the users' old passwords and can be checked to ensure that users are not recycling recent passwords.
Forcing users not to reuse their past 5 passwords make it less likely that an attacker will be able to guess the password.
Note that these change only apply to accounts configured on the local system.
Edit the /etc/pam.d/common-password file to include the remember option and conform to site policy as shown:
password sufficient pam_unix.so remember=5
| Ensure password reuse is limited | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.3.3_Ensure_password_reuse_is_limited"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.465-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1290"
value-id="xccdf_org.cisecurity.benchmarks_value_5.3.3.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1290"/>
</check>
</complex-check>
</rule-result>
The commands below change password encryption from md5 to sha512 (a much stronger hashing algorithm). All existing accounts will need to perform a password change to upgrade the stored hashes to the new algorithm.
The SHA-512 algorithm provides much stronger hashing than MD5, thus providing additional protection to the system by increasing the level of effort for an attacker to successfully determine passwords.
Note that these change only apply to accounts configured on the local system.
Edit the /etc/pam.d/common-password file to include the sha512 option for pam_unix.so as shown:
password [success=1 default=ignore] pam_unix.so sha512
| Ensure password hashing algorithm is SHA-512 | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.3.4_Ensure_password_hashing_algorithm_is_SHA-512"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.465-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1291"
value-id="xccdf_org.cisecurity.benchmarks_value_5.3.4.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1291"/>
</check>
</complex-check>
</rule-result>
This section provides guidance on setting up secure defaults for system and user accounts and their environment.
While a majority of the password control parameters have been moved to PAM, some parameters are still available through the shadow password suite. Any changes made to /etc/login.defs will only be applied if the usermod command is used. If user IDs are added a different way, use the chage command to effect changes to individual user IDs.
The PASS_MAX_DAYS parameter in /etc/login.defs allows an administrator to force passwords to expire once they reach a defined age. It is recommended that the PASS_MAX_DAYS parameter be set to less than or equal to 90 days.
The window of opportunity for an attacker to leverage compromised credentials or successfully compromise credentials via an online brute force attack is limited by the age of the password. Therefore, reducing the maximum age of a password also reduces an attacker's window of opportunity.
Set the PASS_MAX_DAYS parameter to 90 in /etc/login.defs :
PASS_MAX_DAYS 90Modify user parameters for all users with a password set to match:
# chage --maxdays 90
<user>
| Ensure password expiration is 90 days or less | Fail |
| Ensure password expiration is 90 days or less | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.1_Ensure_password_expiration_is_90_days_or_less"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.465-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1292"
value-id="xccdf_org.cisecurity.benchmarks_value_5.4.1.1.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1292"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1293"/>
</check>
</complex-check>
</rule-result>
The PASS_MIN_DAYS parameter in /etc/login.defs allows an administrator to prevent users from changing their password until a minimum number of days have passed since the last time the user changed their password. It is recommended that PASS_MIN_DAYS parameter be set to 7 or more days.
By restricting the frequency of password changes, an administrator can prevent users from repeatedly changing their password in an attempt to circumvent password reuse controls.
Set the PASS_MIN_DAYS parameter to 7 in /etc/login.defs :
PASS_MIN_DAYS 7Modify user parameters for all users with a password set to match:
# chage --mindays 7
<user>
| Ensure minimum days between password changes is 7 or more | Fail |
| Ensure minimum days between password changes is 7 or more | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.2_Ensure_minimum_days_between_password_changes_is_7_or_more"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.466-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1294"
value-id="xccdf_org.cisecurity.benchmarks_value_5.4.1.2.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1294"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1295"/>
</check>
</complex-check>
</rule-result>
The PASS_WARN_AGE parameter in /etc/login.defs allows an administrator to notify users that their password will expire in a defined number of days. It is recommended that the PASS_WARN_AGE parameter be set to 7 or more days.
Providing an advance warning that a password will be expiring gives users time to think of a secure password. Users caught unaware may choose a simple password or write it down where it may be discovered.
Set the PASS_WARN_AGE parameter to 7 in /etc/login.defs :
PASS_WARN_AGE 7Modify user parameters for all users with a password set to match:
# chage --warndays 7
<user>
| Ensure password expiration warning days is 7 or more | Pass |
| Ensure password expiration warning days is 7 or more | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.3_Ensure_password_expiration_warning_days_is_7_or_more"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.466-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1296"
value-id="xccdf_org.cisecurity.benchmarks_value_5.4.1.3.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1296"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1297"/>
</check>
</complex-check>
</rule-result>
User accounts that have been inactive for over a given period of time can be automatically disabled. It is recommended that accounts that are inactive for 30 days after password expiration be disabled.
Inactive accounts pose a threat to system security since the users are not logging in to notice failed login attempts or other anomalies.
Run the following command to set the default password inactivity period to 30 days:
# useradd -D -f 30Modify user parameters for all users with a password set to match:
# chage --inactive 30
<user>| Ensure inactive password lock is 30 days or less | Fail |
| Ensure inactive password lock is 30 days or less | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.4.1.4_Ensure_inactive_password_lock_is_30_days_or_less"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.466-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1298"
value-id="xccdf_org.cisecurity.benchmarks_value_5.4.1.4.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1298"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1299"/>
</check>
</complex-check>
</rule-result>
There are a number of accounts provided with Ubuntu that are used to manage applications and are not intended to provide an interactive shell.
It is important to make sure that accounts that are not being used by regular users are prevented from being used to provide an interactive shell. By default, Ubuntu sets the password field for these accounts to an invalid string, but it is also recommended that the shell field in the password file be set to /sbin/nologin . This prevents the account from potentially being used to run any commands.
Set the shell for any accounts returned by the audit script to /usr/sbin/nologin :
# usermod -s /usr/sbin/nologin
<user>The following script will automatically set all user shells required to /usr/sbin/nologin and lock the sync , shutdown , and halt users:
#!/bin/bash
for user in `awk -F: '($3 < 1000) {print $1 }' /etc/passwd`; do
if [ $user != "root" ]; then
usermod -L $user
if [ $user != "sync" ] && [ $user != "shutdown" ] && [ $user != "halt" ]; then
usermod -s /usr/sbin/nologin $user
fi
fi
done
| Ensure system accounts are non-login | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.4.2_Ensure_system_accounts_are_non-login"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.466-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1300"/>
</check>
</complex-check>
</rule-result>
The usermod command can be used to specify which group the root user belongs to. This affects permissions of files that are created by the root user.
Using GID 0 for the root account helps prevent root -owned files from accidentally becoming accessible to non-privileged users.
Run the following command to set the root user default group to GID 0 :
# usermod -g 0 root
| Ensure default group for the root account is GID 0 | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.4.3_Ensure_default_group_for_the_root_account_is_GID_0"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.466-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1301"/>
</check>
</complex-check>
</rule-result>
The default umask determines the permissions of files created by users. The user creating the file has the discretion of making their files and directories readable by others via the chmod command. Users who wish to allow their files and directories to be readable by others by default may choose a different default umask by inserting the umask command into the standard shell configuration files ( .profile , .bashrc , etc.) in their home directories.
Setting a very secure default value for umask ensures that users make a conscious choice about their file permissions. A default umask setting of 077 causes files and directories created by users to not be readable by any other user on the system. A umask of 027 would make files and directories readable by users in the same Unix group, while a umask of 022 would make files readable by every user on the system.
Edit the /etc/bash.bashrc and /etc/profile files (and the appropriate files for any other shell supported on your system) and add or edit any umask parameters as follows:
umask 027
| Ensure default user umask is 027 or more restrictive | Fail |
| Ensure default user umask is 027 or more restrictive | Pass |
| Ensure default user umask is 027 or more restrictive | Fail |
| Ensure default user umask is 027 or more restrictive | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.4.4_Ensure_default_user_umask_is_027_or_more_restrictive"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.466-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1302"
value-id="xccdf_org.cisecurity.benchmarks_value_5.4.4.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1302"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1303"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1304"
value-id="xccdf_org.cisecurity.benchmarks_value_5.4.4.3_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1304"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1305"/>
</check>
</complex-check>
</rule-result>
The su command allows a user to run a command or shell as another user. The program has been superseded by sudo , which allows for more granular control over privileged access. Normally, the su command can be executed by any user. By uncommenting the pam_wheel.so statement in /etc/pam.d/su , the su command will only allow users in the wheel group to execute su .
Restricting the use of su , and using sudo in its place, provides system administrators better control of the escalation of user privileges to execute privileged commands. The sudo utility also provides a better logging and audit mechanism, as it can log each command executed via sudo , whereas su can only record that a user executed the su program.
Add the following line to the /etc/pam.d/su file:
auth required pam_wheel.so use_uidCreate a comma separated list of users in the wheel statement in the /etc/group file:
wheel:x:10:root,
<user list>
| Ensure access to the su command is restricted | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_5.6_Ensure_access_to_the_su_command_is_restricted"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.467-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1306"
value-id="xccdf_org.cisecurity.benchmarks_value_5.6.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1306"/>
</check>
</complex-check>
</rule-result>
Recommendations in this section are intended as maintenance and are intended to be checked on a frequent basis to ensure system stability. Many recommendations do not have quick remediations and require investigation into the cause and best fix available and may indicate an attempted breach of system security.
This section provides guidance on securing aspects of system files and directories.
The /etc/passwd file contains user account information that is used by many system utilities and therefore must be readable for these utilities to operate.
It is critical to ensure that the /etc/passwd file is protected from unauthorized write access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.
Run the following command to set permissions on /etc/passwd :
# chown root:root /etc/passwd
# chmod 644 /etc/passwd
| Ensure permissions on /etc/passwd are configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.1.2_Ensure_permissions_on_etcpasswd_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.467-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1307"/>
</check>
</complex-check>
</rule-result>
The /etc/shadow file is used to store the information about user accounts that is critical to the security of those accounts, such as the hashed password and other security information.
If attackers can gain read access to the /etc/shadow file, they can easily run a password cracking program against the hashed password to break it. Other security information that is stored in the /etc/shadow file (such as expiration) could also be useful to subvert the user accounts.
Run the one following commands to set permissions on /etc/shadow :
# chown root:shadow /etc/shadow
# chmod o-rwx,g-wx /etc/shadow
| Ensure permissions on /etc/shadow are configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.1.3_Ensure_permissions_on_etcshadow_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.467-05:00"
version="1"
weight="1.0">
<result>pass</result>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1308"/>
</check>
</rule-result>
The /etc/group file contains a list of all the valid groups defined in the system. The command below allows read/write access for root and read access for everyone else.
The /etc/group file needs to be protected from unauthorized changes by non-privileged users, but needs to be readable as this information is used with many non-privileged programs.
Run the following command to set permissions on /etc/group :
# chown root:root /etc/group
# chmod 644 /etc/group
| Ensure permissions on /etc/group are configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.1.4_Ensure_permissions_on_etcgroup_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.467-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1309"/>
</check>
</complex-check>
</rule-result>
The /etc/gshadow file is used to store the information about groups that is critical to the security of those accounts, such as the hashed password and other security information.
If attackers can gain read access to the /etc/gshadow file, they can easily run a password cracking program against the hashed password to break it. Other security information that is stored in the /etc/gshadow file (such as group administrators) could also be useful to subvert the group.
Run the the following commands to set permissions on /etc/gshadow :
# chown root:shadow /etc/gshadow
# chmod o-rwx,g-rw /etc/gshadow
| Ensure permissions on /etc/gshadow are configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.1.5_Ensure_permissions_on_etcgshadow_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.467-05:00"
version="1"
weight="1.0">
<result>pass</result>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1310"/>
</check>
</rule-result>
The /etc/passwd- file contains backup user account information.
It is critical to ensure that the /etc/passwd- file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.
Run the following command to set permissions on /etc/passwd- :
# chown root:root /etc/passwd-
# chmod 600 /etc/passwd-
| Ensure permissions on /etc/passwd- are configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.1.6_Ensure_permissions_on_etcpasswd-_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.467-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1311"/>
</check>
</complex-check>
</rule-result>
The /etc/shadow- file is used to store backup information about user accounts that is critical to the security of those accounts, such as the hashed password and other security information.
It is critical to ensure that the /etc/shadow- file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.
Run the following command to set permissions on /etc/shadow- :
# chown root:root /etc/shadow-
# chmod 600 /etc/shadow-
| Ensure permissions on /etc/shadow- are configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.1.7_Ensure_permissions_on_etcshadow-_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.468-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1312"/>
</check>
</complex-check>
</rule-result>
The /etc/group- file contains a backup list of all the valid groups defined in the system.
It is critical to ensure that the /etc/group- file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.
Run the following command to set permissions on /etc/group- :
# chown root:root /etc/group-
# chmod 600 /etc/group-
| Ensure permissions on /etc/group- are configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.1.8_Ensure_permissions_on_etcgroup-_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.468-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1313"/>
</check>
</complex-check>
</rule-result>
The /etc/gshadow- file is used to store backup information about groups that is critical to the security of those accounts, such as the hashed password and other security information.
It is critical to ensure that the /etc/gshadow- file is protected from unauthorized access. Although it is protected by default, the file permissions could be changed either inadvertently or through malicious actions.
Run the following command to set permissions on /etc/gshadow- :
# chown root:root /etc/gshadow-
# chmod 600 /etc/gshadow-
| Ensure permissions on /etc/gshadow- are configured | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.1.9_Ensure_permissions_on_etcgshadow-_are_configured"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.468-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1314"/>
</check>
</complex-check>
</rule-result>
Unix-based systems support variable settings to control access to files. World writable files are the least secure. See the chmod(2) man page for more information.
Data in world-writable files can be modified and compromised by any user on the system. World writable files may also indicate an incorrectly written script or program that could potentially be the cause of a larger compromise to the system's integrity.
Removing write access for the "other" category ( chmod o-w <filename>) is advisable, but always consult relevant vendor documentation to avoid breaking any application dependencies on a given file.
| Script: sce/world_writable_files.sh | Exit Code: 101 | pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.1.10_Ensure_no_world_writable_files_exist"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.468-05:00"
version="1"
weight="1.0">
<result>pass</result>
<check system="http://open-scap.org/page/SCE"
negate="false"
multi-check="false">
<check-content-ref href="sce/world_writable_files.sh"/>
<check-content>
<command_result script="C:\CIS\Assessor-CLI\sce\world_writable_files.sh"
href="sce/world_writable_files.sh"
xccdf="pass"
exit-value="101">
<out/>
<err/>
<env/>
</command_result>
</check-content>
</check>
</rule-result>
Sometimes when administrators delete users from the password file they neglect to remove all files owned by those users from the system.
A new user who is assigned the deleted user's user ID or group ID may then end up "owning" these files, and thus have more access on the system than was intended.
Locate files that are owned by users or groups not listed in the system configuration files, and reset the ownership of these files to some active user on the system as appropriate.
| Script: sce/no_unowned_files_and_directories.sh | Exit Code: 101 | pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.1.11_Ensure_no_unowned_files_or_directories_exist"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.469-05:00"
version="1"
weight="1.0">
<result>pass</result>
<check system="http://open-scap.org/page/SCE"
negate="false"
multi-check="false">
<check-content-ref href="sce/no_unowned_files_and_directories.sh"/>
<check-content>
<command_result script="C:\CIS\Assessor-CLI\sce\no_unowned_files_and_directories.sh"
href="sce/no_unowned_files_and_directories.sh"
xccdf="pass"
exit-value="101">
<out/>
<err/>
<env/>
</command_result>
</check-content>
</check>
</rule-result>
Sometimes when administrators delete users or groups from the system they neglect to remove all files owned by those users or groups.
A new user who is assigned the deleted user's user ID or group ID may then end up "owning" these files, and thus have more access on the system than was intended.
Locate files that are owned by users or groups not listed in the system configuration files, and reset the ownership of these files to some active user on the system as appropriate.
| Script: sce/no_ungrouped_files_and_directories.sh | Exit Code: 101 | pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.1.12_Ensure_no_ungrouped_files_or_directories_exist"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.469-05:00"
version="1"
weight="1.0">
<result>pass</result>
<check system="http://open-scap.org/page/SCE"
negate="false"
multi-check="false">
<check-content-ref href="sce/no_ungrouped_files_and_directories.sh"/>
<check-content>
<command_result script="C:\CIS\Assessor-CLI\sce\no_ungrouped_files_and_directories.sh"
href="sce/no_ungrouped_files_and_directories.sh"
xccdf="pass"
exit-value="101">
<out/>
<err/>
<env/>
</command_result>
</check-content>
</check>
</rule-result>
This section provides guidance on securing aspects of the users and groups.
An account with an empty password field means that anybody may log in as that user without providing a password.
All accounts must have passwords or be locked to prevent the account from being used by an unauthorized user.
If any accounts in the /etc/shadow file do not have a password, run the following command to lock the account until it can be determined why it does not have a password:
# passwd -l
<username>Also, check to see if the account is logged in and investigate what it is being used for to determine if it needs to be forced off.
| Ensure password fields are not empty | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.1_Ensure_password_fields_are_not_empty"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.469-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-export export-name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:var:1318"
value-id="xccdf_org.cisecurity.benchmarks_value_6.2.1.1_var"/>
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1318"/>
</check>
</complex-check>
</rule-result>
The character + in various files used to be markers for systems to insert data from NIS maps at a certain point in a system configuration file. These entries are no longer required on most systems, but may exist in files that have been imported from other platforms.
These entries may provide an avenue for attackers to gain privileged access on the system.
Remove any legacy '+' entries from /etc/passwd if they exist.
| Ensure no legacy "+" entries exist in /etc/passwd | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.2_Ensure_no_legacy__entries_exist_in_etcpasswd"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.469-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1319"/>
</check>
</complex-check>
</rule-result>
The character + in various files used to be markers for systems to insert data from NIS maps at a certain point in a system configuration file. These entries are no longer required on most systems, but may exist in files that have been imported from other platforms.
These entries may provide an avenue for attackers to gain privileged access on the system.
Remove any legacy '+' entries from /etc/shadow if they exist.
| Ensure no legacy "+" entries exist in /etc/shadow | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.3_Ensure_no_legacy__entries_exist_in_etcshadow"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.469-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1320"/>
</check>
</complex-check>
</rule-result>
The character + in various files used to be markers for systems to insert data from NIS maps at a certain point in a system configuration file. These entries are no longer required on most systems, but may exist in files that have been imported from other platforms.
These entries may provide an avenue for attackers to gain privileged access on the system.
Remove any legacy '+' entries from /etc/group if they exist.
| Ensure no legacy "+" entries exist in /etc/group | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.4_Ensure_no_legacy__entries_exist_in_etcgroup"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.469-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1321"/>
</check>
</complex-check>
</rule-result>
Any account with UID 0 has superuser privileges on the system.
This access must be limited to only the default root account and only from the system console. Administrative access must be through an unprivileged account using an approved mechanism as noted in Item 5.6 Ensure access to the su command is restricted.
Remove any users other than root with UID 0 or assign them a new UID if appropriate.
| Ensure root is the only UID 0 account | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.5_Ensure_root_is_the_only_UID_0_account"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.469-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1322"/>
</check>
</complex-check>
</rule-result>
The root user can execute any command on the system and could be fooled into executing programs unintentionally if the PATH is not set correctly.
Including the current working directory (.) or other writable directory in root 's executable path makes it likely that an attacker can gain superuser access by forcing an administrator operating as root to execute a Trojan horse program.
Correct or justify any items discovered in the Audit step.
| Ensure root PATH Integrity | Pass |
| Ensure root PATH Integrity | Pass |
| Ensure root PATH Integrity | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.6_Ensure_root_PATH_Integrity"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.469-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1323"/>
</check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1324"/>
</check>
</complex-check>
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1325"/>
</check>
</complex-check>
</rule-result>
Users can be defined in /etc/passwd without a home directory or with a home directory that does not actually exist.
If the user's home directory does not exist or is unassigned, the user will be placed in "/" and will not be able to write any files or have local environment variables set.
If any users' home directories do not exist, create them and make sure the respective user owns the directory. Users without an assigned home directory should be removed or assigned a home directory as appropriate.
| Ensure all users' home directories exist | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.7_Ensure_all_users_home_directories_exist"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.470-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1326"/>
</check>
</complex-check>
</rule-result>
While the system administrator can establish secure permissions for users' home directories, the users can easily override these.
Group or world-writable user home directories may enable malicious users to steal or modify other users' data or to gain another user's system privileges.
Making global modifications to user home directories without alerting the user community can result in unexpected outages and unhappy users. Therefore, it is recommended that a monitoring policy be established to report user file permissions and determine the action to be taken in accordance with site policy.
| Ensure users' home directories permissions are 750 or more restrictive | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.8_Ensure_users_home_directories_permissions_are_750_or_more_restrictive"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.470-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1327"/>
</check>
</complex-check>
</rule-result>
The user home directory is space defined for the particular user to set local environment variables and to store personal files.
Since the user is accountable for files stored in the user home directory, the user must be the owner of the directory.
Change the ownership of any home directories that are not owned by the defined user to the correct user.
| Ensure users own their home directories | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.9_Ensure_users_own_their_home_directories"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.470-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1328"/>
</check>
</complex-check>
</rule-result>
While the system administrator can establish secure permissions for users' "dot" files, the users can easily override these.
Group or world-writable user configuration files may enable malicious users to steal or modify other users' data or to gain another user's system privileges.
Making global modifications to users' files without alerting the user community can result in unexpected outages and unhappy users. Therefore, it is recommended that a monitoring policy be established to report user dot file permissions and determine the action to be taken in accordance with site policy.
| Ensure users' dot files are not group or world writable | Fail |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.10_Ensure_users_dot_files_are_not_group_or_world_writable"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.470-05:00"
version="1"
weight="1.0">
<result>fail</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1329"/>
</check>
</complex-check>
</rule-result>
The .forward file specifies an email address to forward the user's mail to.
Use of the .forward file poses a security risk in that sensitive data may be inadvertently transferred outside the organization. The .forward file also poses a risk as it can be used to execute commands that may perform unintended actions.
Making global modifications to users' files without alerting the user community can result in unexpected outages and unhappy users. Therefore, it is recommended that a monitoring policy be established to report user .forward files and determine the action to be taken in accordance with site policy.
| Ensure no users have .forward files | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.11_Ensure_no_users_have_.forward_files"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.470-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1330"/>
</check>
</complex-check>
</rule-result>
The .netrc file contains data for logging into a remote host for file transfers via FTP.
The .netrc file presents a significant security risk since it stores passwords in unencrypted form. Even if FTP is disabled, user accounts may have brought over .netrc files from other systems which could pose a risk to those systems.
Making global modifications to users' files without alerting the user community can result in unexpected outages and unhappy users. Therefore, it is recommended that a monitoring policy be established to report user .netrc files and determine the action to be taken in accordance with site policy.
| Ensure no users have .netrc files | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.12_Ensure_no_users_have_.netrc_files"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.470-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1331"/>
</check>
</complex-check>
</rule-result>
While the system administrator can establish secure permissions for users' .netrc files, the users can easily override these.
.netrc files may contain unencrypted passwords that may be used to attack other systems.
Making global modifications to users' files without alerting the user community can result in unexpected outages and unhappy users. Therefore, it is recommended that a monitoring policy be established to report user .netrc file permissions and determine the action to be taken in accordance with site policy.
| Ensure users' .netrc Files are not group or world accessible | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.13_Ensure_users_.netrc_Files_are_not_group_or_world_accessible"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.471-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1332"/>
</check>
</complex-check>
</rule-result>
While no .rhosts files are shipped by default, users can easily create them.
This action is only meaningful if .rhosts support is permitted in the file /etc/pam.conf . Even though the .rhosts files are ineffective if support is disabled in /etc/pam.conf , they may have been brought over from other systems and could contain information useful to an attacker for those other systems.
Making global modifications to users' files without alerting the user community can result in unexpected outages and unhappy users. Therefore, it is recommended that a monitoring policy be established to report user .rhosts files and determine the action to be taken in accordance with site policy.
| Ensure no users have .rhosts files | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.14_Ensure_no_users_have_.rhosts_files"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.471-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1333"/>
</check>
</complex-check>
</rule-result>
Over time, system administration errors and changes can lead to groups being defined in /etc/passwd but not in /etc/group .
Groups defined in the /etc/passwd file but not in the /etc/group file pose a threat to system security since group permissions are not properly managed.
Analyze the output of the Audit step above and perform the appropriate action to correct any discrepancies found.
| Ensure all groups in /etc/passwd exist in /etc/group | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.15_Ensure_all_groups_in_etcpasswd_exist_in_etcgroup"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.471-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1334"/>
</check>
</complex-check>
</rule-result>
Although the useradd program will not let you create a duplicate User ID (UID), it is possible for an administrator to manually edit the /etc/passwd file and change the UID field.
Users must be assigned unique UIDs for accountability and to ensure appropriate access protections.
Based on the results of the audit script, establish unique UIDs and review all files owned by the shared UIDs to determine which UID they are supposed to belong to.
| Ensure no duplicate UIDs exist | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.16_Ensure_no_duplicate_UIDs_exist"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.471-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1335"/>
</check>
</complex-check>
</rule-result>
Although the groupadd program will not let you create a duplicate Group ID (GID), it is possible for an administrator to manually edit the /etc/group file and change the GID field.
User groups must be assigned unique GIDs for accountability and to ensure appropriate access protections.
Based on the results of the audit script, establish unique GIDs and review all files owned by the shared GID to determine which group they are supposed to belong to.
| Ensure no duplicate GIDs exist | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.17_Ensure_no_duplicate_GIDs_exist"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.471-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1336"/>
</check>
</complex-check>
</rule-result>
Although the useradd program will not let you create a duplicate user name, it is possible for an administrator to manually edit the /etc/passwd file and change the user name.
If a user is assigned a duplicate user name, it will create and have access to files with the first UID for that username in /etc/passwd . For example, if "test4" has a UID of 1000 and a subsequent "test4" entry has a UID of 2000, logging in as "test4" will use UID 1000. Effectively, the UID is shared, which is a security problem.
Based on the results of the audit script, establish unique user names for the users. File ownerships will automatically reflect the change as long as the users have unique UIDs.
| Ensure no duplicate user names exist | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.18_Ensure_no_duplicate_user_names_exist"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.471-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1337"/>
</check>
</complex-check>
</rule-result>
Although the groupadd program will not let you create a duplicate group name, it is possible for an administrator to manually edit the /etc/group file and change the group name.
If a group is assigned a duplicate group name, it will create and have access to files with the first GID for that group in /etc/group . Effectively, the GID is shared, which is a security problem.
Based on the results of the audit script, establish unique names for the user groups. File group ownerships will automatically reflect the change as long as the groups have unique GIDs.
| Ensure no duplicate group names exist | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.19_Ensure_no_duplicate_group_names_exist"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.471-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1338"/>
</check>
</complex-check>
</rule-result>
The shadow group allows system programs which require access the ability to read the /etc/shadow file. No users should be assigned to the shadow group.
Any users assigned to the shadow group would be granted read access to the /etc/shadow file. If attackers can gain read access to the /etc/shadow file, they can easily run a password cracking program against the hashed passwords to break them. Other security information that is stored in the /etc/shadow file (such as expiration) could also be useful to subvert additional user accounts.
Remove all users from the shadow group, and change the primary group of any users with shadow as their primary group.
| Ensure shadow group is empty | Pass |
<rule-result xmlns:xccdf="http://checklists.nist.gov/xccdf/1.2"
xmlns="http://checklists.nist.gov/xccdf/1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:scap-con="http://scap.nist.gov/schema/scap/constructs/1.2"
xmlns:arf="http://scap.nist.gov/schema/asset-reporting-format/1.1"
xmlns:dsc="http://scap.nist.gov/schema/scap/source/1.2"
xmlns:ai="http://scap.nist.gov/schema/asset-identification/1.1"
idref="xccdf_org.cisecurity.benchmarks_rule_6.2.20_Ensure_shadow_group_is_empty"
role="full"
severity="unknown"
time="2019-11-19T23:30:03.471-05:00"
version="1"
weight="1.0">
<result>pass</result>
<complex-check operator="AND" negate="false">
<check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"
negate="false"
multi-check="false">
<check-content-ref href="#OVAL-Results-1"
name="oval:org.cisecurity.benchmarks.o_canonical_ubuntu_linux:def:1339"/>
</check>
</complex-check>
</rule-result>