kriterion 0.0.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.gitignore +2 -0
- data/.ruby-version +1 -0
- data/.travis.yml +5 -0
- data/Dockerfile +18 -0
- data/Gemfile +12 -0
- data/Gemfile.lock +62 -0
- data/LICENSE.txt +21 -0
- data/README.md +58 -0
- data/Rakefile +6 -0
- data/bin/setup +8 -0
- data/bin/update_stigs.rb +42 -0
- data/criterion.gemspec +31 -0
- data/docker-compose.yml +14 -0
- data/exe/kriterion +16 -0
- data/lib/kriterion.rb +16 -0
- data/lib/kriterion/api.rb +27 -0
- data/lib/kriterion/backend.rb +13 -0
- data/lib/kriterion/backend/mongodb.rb +235 -0
- data/lib/kriterion/cli.rb +28 -0
- data/lib/kriterion/cli/api.rb +35 -0
- data/lib/kriterion/cli/worker.rb +35 -0
- data/lib/kriterion/event.rb +36 -0
- data/lib/kriterion/item.rb +42 -0
- data/lib/kriterion/logs.rb +14 -0
- data/lib/kriterion/metrics.rb +22 -0
- data/lib/kriterion/object.rb +50 -0
- data/lib/kriterion/report.rb +69 -0
- data/lib/kriterion/resource.rb +60 -0
- data/lib/kriterion/section.rb +32 -0
- data/lib/kriterion/standard.rb +65 -0
- data/lib/kriterion/version.rb +3 -0
- data/lib/kriterion/worker.rb +280 -0
- data/standards/cis_red_hat_enterprise_linux_7.json +34 -0
- data/standards/stig_a10_networks_adc_alg.json +209 -0
- data/standards/stig_a10_networks_adc_ndm.json +233 -0
- data/standards/stig_active_directory_domain.json +257 -0
- data/standards/stig_active_directory_forest.json +41 -0
- data/standards/stig_active_directory_service_2003.json +173 -0
- data/standards/stig_active_directory_service_2008.json +167 -0
- data/standards/stig_adobe_acrobat_pro_xi.json +167 -0
- data/standards/stig_adobe_acrobat_reader_dc_classic_track.json +179 -0
- data/standards/stig_adobe_acrobat_reader_dc_continuous_track.json +179 -0
- data/standards/stig_adobe_coldfusion_11.json +611 -0
- data/standards/stig_airwatch_mdm.json +185 -0
- data/standards/stig_aix_5.3.json +3095 -0
- data/standards/stig_aix_6.1.json +3047 -0
- data/standards/stig_akamai_ksd_service_impact_level_2_alg.json +209 -0
- data/standards/stig_akamai_ksd_service_impact_level_2_ndm.json +155 -0
- data/standards/stig_android_2.2_dell.json +311 -0
- data/standards/stig_apache_2.2_serverwindows.json +347 -0
- data/standards/stig_apache_2.2_sitewindows_security_implementation_guide.json +179 -0
- data/standards/stig_apache_server_2.0unix.json +341 -0
- data/standards/stig_apache_server_2.0windows.json +341 -0
- data/standards/stig_apache_server_2.2unix.json +347 -0
- data/standards/stig_apache_server_2.2windows.json +347 -0
- data/standards/stig_apache_site_2.0unix.json +185 -0
- data/standards/stig_apache_site_2.0windows.json +179 -0
- data/standards/stig_apache_site_2.2unix.json +185 -0
- data/standards/stig_apache_site_2.2windows.json +179 -0
- data/standards/stig_apple_ios6.json +341 -0
- data/standards/stig_apple_ios_10.json +245 -0
- data/standards/stig_apple_ios_11.json +269 -0
- data/standards/stig_apple_ios_4_good_mobility_suite_interim_security_configuration_guide_iscg.json +257 -0
- data/standards/stig_apple_ios_5.json +329 -0
- data/standards/stig_apple_ios_6.json +335 -0
- data/standards/stig_apple_ios_6_interim_security_configuration_guide_iscg.json +371 -0
- data/standards/stig_apple_ios_7.json +185 -0
- data/standards/stig_apple_ios_8_interim_security_configuration_guide.json +251 -0
- data/standards/stig_apple_ios_9_interim_security_configuration_guide.json +245 -0
- data/standards/stig_apple_os_x_10.10_yosemite_workstation.json +851 -0
- data/standards/stig_apple_os_x_10.11.json +725 -0
- data/standards/stig_apple_os_x_10.12.json +737 -0
- data/standards/stig_apple_os_x_10.8_mountain_lion_workstation.json +1241 -0
- data/standards/stig_apple_os_x_10.9_mavericks_workstation.json +809 -0
- data/standards/stig_application_layer_gateway_alg_security_requirements_guide_srg.json +911 -0
- data/standards/stig_application_layer_gateway_security_requirements_guide.json +911 -0
- data/standards/stig_application_security_and_development.json +1745 -0
- data/standards/stig_application_security_and_development_checklist.json +959 -0
- data/standards/stig_application_security_requirements_guide.json +1961 -0
- data/standards/stig_application_server_security_requirements_guide.json +791 -0
- data/standards/stig_arcgisserver_10.3.json +143 -0
- data/standards/stig_arista_mls_dcs-7000_series_l2s.json +53 -0
- data/standards/stig_arista_mls_dcs-7000_series_ndm.json +197 -0
- data/standards/stig_arista_mls_dcs-7000_series_rtr.json +143 -0
- data/standards/stig_bind_9.x.json +431 -0
- data/standards/stig_bind_dns.json +317 -0
- data/standards/stig_blackberry_10.2.x_os.json +179 -0
- data/standards/stig_blackberry_10_os.json +227 -0
- data/standards/stig_blackberry_bes_12.3.x_mdm.json +65 -0
- data/standards/stig_blackberry_bes_12.5.x_mdm.json +65 -0
- data/standards/stig_blackberry_device_service_6.2.json +425 -0
- data/standards/stig_blackberry_enterprise_mobility_server_2.x.json +149 -0
- data/standards/stig_blackberry_enterprise_server,_part_1.json +35 -0
- data/standards/stig_blackberry_enterprise_server,_part_2.json +155 -0
- data/standards/stig_blackberry_enterprise_server,_part_3.json +647 -0
- data/standards/stig_blackberry_enterprise_server_version_5.x,_part_1.json +35 -0
- data/standards/stig_blackberry_enterprise_server_version_5.x,_part_2.json +155 -0
- data/standards/stig_blackberry_enterprise_server_version_5.x,_part_3.json +653 -0
- data/standards/stig_blackberry_enterprise_service_v10.1.x_blackberry_device_service.json +317 -0
- data/standards/stig_blackberry_enterprise_service_v10.2.x_blackberry_device_service.json +263 -0
- data/standards/stig_blackberry_handheld_device.json +125 -0
- data/standards/stig_blackberry_os_10.3.x.json +257 -0
- data/standards/stig_blackberry_os_7.x.json +107 -0
- data/standards/stig_blackberry_os_7.x.x.json +101 -0
- data/standards/stig_blackberry_os_version_5-7.json +107 -0
- data/standards/stig_blackberry_playbook.json +65 -0
- data/standards/stig_blackberry_playbook_os_nea_mode.json +65 -0
- data/standards/stig_blackberry_playbook_os_v2.1.json +197 -0
- data/standards/stig_blackberry_uem_12.7.json +59 -0
- data/standards/stig_bluetoothzigbee.json +35 -0
- data/standards/stig_ca_api_gateway_alg.json +497 -0
- data/standards/stig_cisco_css_dns.json +71 -0
- data/standards/stig_cisco_ios_xe_release_3_ndm.json +395 -0
- data/standards/stig_cisco_ios_xe_release_3_rtr.json +149 -0
- data/standards/stig_cmd_management_server_policy.json +53 -0
- data/standards/stig_commercial_mobile_device_cmd_policy.json +83 -0
- data/standards/stig_csfc_campus_wlan_policy_security_implementation_guide.json +95 -0
- data/standards/stig_database_security_requirements_guide.json +767 -0
- data/standards/stig_dbn-6300_idps.json +107 -0
- data/standards/stig_dbn-6300_ndm.json +359 -0
- data/standards/stig_defense_switched_network.json +683 -0
- data/standards/stig_defense_switched_network_dsn.json +653 -0
- data/standards/stig_desktop_applications_general.json +41 -0
- data/standards/stig_dns_policy.json +155 -0
- data/standards/stig_domain_name_system_dns_security_requirements_guide.json +599 -0
- data/standards/stig_draft_aix.json +3503 -0
- data/standards/stig_edb_postgres_advanced_server.json +665 -0
- data/standards/stig_email_services_policy.json +137 -0
- data/standards/stig_exchange_2010_client_access_server.json +179 -0
- data/standards/stig_exchange_2010_edge_transport_server.json +389 -0
- data/standards/stig_exchange_2010_hub_transport_server.json +269 -0
- data/standards/stig_exchange_2010_mailbox_server.json +209 -0
- data/standards/stig_f5_big-ip_access_policy_manager_11.x.json +149 -0
- data/standards/stig_f5_big-ip_advanced_firewall_manager_11.x.json +41 -0
- data/standards/stig_f5_big-ip_application_security_manager_11.x.json +89 -0
- data/standards/stig_f5_big-ip_device_management_11.x.json +467 -0
- data/standards/stig_f5_big-ip_local_traffic_manager_11.x.json +407 -0
- data/standards/stig_final_draft_general_wireless_policy.json +71 -0
- data/standards/stig_firewall.json +449 -0
- data/standards/stig_firewall_-_cisco.json +449 -0
- data/standards/stig_firewall_security_requirements_guide.json +257 -0
- data/standards/stig_forescout_counteract_alg.json +83 -0
- data/standards/stig_forescout_counteract_ndm.json +239 -0
- data/standards/stig_free_space_optics_device.json +143 -0
- data/standards/stig_general_mobile_device_policy_non-enterprise_activated.json +113 -0
- data/standards/stig_general_mobile_device_technical_non-enterprise_activated.json +59 -0
- data/standards/stig_general_purpose_operating_system_srg.json +1199 -0
- data/standards/stig_general_wireless_policy.json +71 -0
- data/standards/stig_good_mobility_suite_server_android_os.json +203 -0
- data/standards/stig_good_mobility_suite_server_apple_ios_4_interim_security_configuration_guide_iscg.json +209 -0
- data/standards/stig_good_mobility_suite_server_windows_phone_6.5.json +449 -0
- data/standards/stig_goodenterprise_8.x.json +401 -0
- data/standards/stig_google_chrome_browser.json +209 -0
- data/standards/stig_google_chrome_current_windows.json +215 -0
- data/standards/stig_google_chrome_draft.json +281 -0
- data/standards/stig_google_chrome_v23_windows.json +275 -0
- data/standards/stig_google_chrome_v24_windows.json +263 -0
- data/standards/stig_google_chrome_v24_windows_benchmark.json +227 -0
- data/standards/stig_google_search_appliance.json +209 -0
- data/standards/stig_harris_secnet_11_54.json +89 -0
- data/standards/stig_hp-ux_11.23.json +3215 -0
- data/standards/stig_hp-ux_11.31.json +3155 -0
- data/standards/stig_hp-ux_smse.json +431 -0
- data/standards/stig_hpe_3par_storeserv_3.2.x.json +131 -0
- data/standards/stig_ibm_datapower_alg.json +401 -0
- data/standards/stig_ibm_datapower_network_device_management.json +395 -0
- data/standards/stig_ibm_db2_v10.5_luw.json +575 -0
- data/standards/stig_ibm_hardware_management_console_hmc.json +221 -0
- data/standards/stig_ibm_hardware_management_console_hmc_policies.json +35 -0
- data/standards/stig_ibm_maas360_v2.3.x_mdm.json +59 -0
- data/standards/stig_ibm_zvm_using_ca_vm:secure.json +473 -0
- data/standards/stig_idps_security_requirements_guide_srg.json +1865 -0
- data/standards/stig_idsips.json +257 -0
- data/standards/stig_iis6_server.json +221 -0
- data/standards/stig_iis6_site.json +263 -0
- data/standards/stig_iis_7.0_web_server.json +155 -0
- data/standards/stig_iis_7.0_web_site.json +299 -0
- data/standards/stig_iis_8.5_server.json +293 -0
- data/standards/stig_iis_8.5_site.json +347 -0
- data/standards/stig_infoblox_7.x_dns.json +419 -0
- data/standards/stig_infrastructure_l3_switch.json +599 -0
- data/standards/stig_infrastructure_l3_switch_-_cisco.json +659 -0
- data/standards/stig_infrastructure_l3_switch_secure_technical_implementation_guide_-_cisco.json +659 -0
- data/standards/stig_infrastructure_router.json +479 -0
- data/standards/stig_infrastructure_router_-_cisco.json +539 -0
- data/standards/stig_infrastructure_router_-_juniper.json +485 -0
- data/standards/stig_infrastructure_router__cisco.json +539 -0
- data/standards/stig_infrastructure_router__juniper.json +485 -0
- data/standards/stig_internet_explorer_8.json +821 -0
- data/standards/stig_internet_explorer_9.json +815 -0
- data/standards/stig_intrusion_detection_and_prevention_systems_idps_security_requirements_guide.json +371 -0
- data/standards/stig_ipsec_vpn_gateway.json +521 -0
- data/standards/stig_java_runtime_environment_jre_6_unix.json +65 -0
- data/standards/stig_java_runtime_environment_jre_6_win7.json +65 -0
- data/standards/stig_java_runtime_environment_jre_6_windows_xp.json +77 -0
- data/standards/stig_java_runtime_environment_jre_6_winxp.json +65 -0
- data/standards/stig_java_runtime_environment_jre_7_unix.json +65 -0
- data/standards/stig_java_runtime_environment_jre_7_win7.json +65 -0
- data/standards/stig_java_runtime_environment_jre_7_winxp.json +65 -0
- data/standards/stig_java_runtime_environment_jre_version_6_unix.json +77 -0
- data/standards/stig_java_runtime_environment_jre_version_6_windows_7.json +77 -0
- data/standards/stig_java_runtime_environment_jre_version_6_windows_xp.json +65 -0
- data/standards/stig_java_runtime_environment_jre_version_7_unix.json +77 -0
- data/standards/stig_java_runtime_environment_jre_version_7_windows_7.json +77 -0
- data/standards/stig_java_runtime_environment_jre_version_7_winxp.json +77 -0
- data/standards/stig_java_runtime_environment_jre_version_8_unix.json +107 -0
- data/standards/stig_java_runtime_environment_jre_version_8_windows.json +107 -0
- data/standards/stig_jboss_eap_6.3.json +413 -0
- data/standards/stig_juniper_srx_sg_alg.json +155 -0
- data/standards/stig_juniper_srx_sg_idps.json +179 -0
- data/standards/stig_juniper_srx_sg_ndm.json +443 -0
- data/standards/stig_juniper_srx_sg_vpn.json +185 -0
- data/standards/stig_keyboard_video_and_mouse_switch.json +269 -0
- data/standards/stig_l3_kov-26_talon_wireless_role.json +77 -0
- data/standards/stig_layer_2_switch.json +347 -0
- data/standards/stig_layer_2_switch_-_cisco.json +365 -0
- data/standards/stig_lg_android_5.x_interim_security_configuration_guide.json +245 -0
- data/standards/stig_lg_android_6.x.json +281 -0
- data/standards/stig_mac_osx_10.6_workstation.json +1319 -0
- data/standards/stig_mac_osx_10.6_workstation_draft.json +1319 -0
- data/standards/stig_mainframe_product_security_requirements_guide.json +1115 -0
- data/standards/stig_mcafee_application_control_7.x.json +203 -0
- data/standards/stig_mcafee_move_2.63.6.1_multi-platform_client.json +149 -0
- data/standards/stig_mcafee_move_2.63.6.1_multi-platform_oss.json +101 -0
- data/standards/stig_mcafee_move_2.6_multi-platform_client.json +149 -0
- data/standards/stig_mcafee_move_2.6_multi-platform_oss.json +101 -0
- data/standards/stig_mcafee_move_3.6.1_multi-platform_client.json +149 -0
- data/standards/stig_mcafee_move_3.6.1_multi-platform_oss.json +101 -0
- data/standards/stig_mcafee_move_agentless_3.03.6.1_security_virtual_appliance.json +167 -0
- data/standards/stig_mcafee_move_agentless_3.0_security_virtual_appliance.json +167 -0
- data/standards/stig_mcafee_move_agentless_3.0_vsel_1.9sva.json +203 -0
- data/standards/stig_mcafee_move_agentless_3.6.1_security_virtual_appliance.json +167 -0
- data/standards/stig_mcafee_move_av_agentless_4.5.json +155 -0
- data/standards/stig_mcafee_move_av_multi-platform_4.5.json +215 -0
- data/standards/stig_mcafee_virusscan_8.8_local_client.json +533 -0
- data/standards/stig_mcafee_virusscan_8.8_managed_client.json +533 -0
- data/standards/stig_mcafee_vsel_1.92.0_local_client.json +245 -0
- data/standards/stig_mcafee_vsel_1.92.0_managed_client.json +239 -0
- data/standards/stig_mdm_server_policy.json +47 -0
- data/standards/stig_microsoft_access_2003.json +47 -0
- data/standards/stig_microsoft_access_2007.json +77 -0
- data/standards/stig_microsoft_access_2010.json +119 -0
- data/standards/stig_microsoft_access_2013.json +113 -0
- data/standards/stig_microsoft_access_2016.json +107 -0
- data/standards/stig_microsoft_dot_net_framework_4.0.json +101 -0
- data/standards/stig_microsoft_excel_2003.json +47 -0
- data/standards/stig_microsoft_excel_2007.json +155 -0
- data/standards/stig_microsoft_excel_2010.json +287 -0
- data/standards/stig_microsoft_excel_2013.json +293 -0
- data/standards/stig_microsoft_excel_2016.json +257 -0
- data/standards/stig_microsoft_exchange_2010_client_access_server_role.json +71 -0
- data/standards/stig_microsoft_exchange_2010_core_server.json +47 -0
- data/standards/stig_microsoft_exchange_2010_edge_transport_server_role.json +233 -0
- data/standards/stig_microsoft_exchange_2010_hub_transport_server_role.json +125 -0
- data/standards/stig_microsoft_exchange_2010_mailbox_server_role.json +107 -0
- data/standards/stig_microsoft_exchange_server_2003.json +647 -0
- data/standards/stig_microsoft_groove_2013.json +71 -0
- data/standards/stig_microsoft_ie_version_6.json +599 -0
- data/standards/stig_microsoft_ie_version_7.json +749 -0
- data/standards/stig_microsoft_infopath_2003.json +41 -0
- data/standards/stig_microsoft_infopath_2007.json +167 -0
- data/standards/stig_microsoft_infopath_2010.json +155 -0
- data/standards/stig_microsoft_infopath_2013.json +149 -0
- data/standards/stig_microsoft_internet_explorer_10.json +857 -0
- data/standards/stig_microsoft_internet_explorer_11.json +839 -0
- data/standards/stig_microsoft_internet_explorer_9.json +821 -0
- data/standards/stig_microsoft_lync_2013.json +29 -0
- data/standards/stig_microsoft_office_system_2007.json +221 -0
- data/standards/stig_microsoft_office_system_2010.json +233 -0
- data/standards/stig_microsoft_office_system_2013.json +293 -0
- data/standards/stig_microsoft_office_system_2016.json +131 -0
- data/standards/stig_microsoft_onedrivebusiness_2016.json +89 -0
- data/standards/stig_microsoft_onenote_2010.json +77 -0
- data/standards/stig_microsoft_onenote_2013.json +71 -0
- data/standards/stig_microsoft_onenote_2016.json +71 -0
- data/standards/stig_microsoft_outlook_2003.json +65 -0
- data/standards/stig_microsoft_outlook_2007.json +479 -0
- data/standards/stig_microsoft_outlook_2010.json +515 -0
- data/standards/stig_microsoft_outlook_2013.json +497 -0
- data/standards/stig_microsoft_outlook_2016.json +359 -0
- data/standards/stig_microsoft_powerpoint_2003.json +47 -0
- data/standards/stig_microsoft_powerpoint_2007.json +131 -0
- data/standards/stig_microsoft_powerpoint_2010.json +191 -0
- data/standards/stig_microsoft_powerpoint_2013.json +251 -0
- data/standards/stig_microsoft_powerpoint_2016.json +233 -0
- data/standards/stig_microsoft_project_2010.json +83 -0
- data/standards/stig_microsoft_project_2013.json +95 -0
- data/standards/stig_microsoft_project_2016.json +95 -0
- data/standards/stig_microsoft_publisher_2010.json +107 -0
- data/standards/stig_microsoft_publisher_2013.json +101 -0
- data/standards/stig_microsoft_publisher_2016.json +101 -0
- data/standards/stig_microsoft_sharepoint_designer_2013.json +71 -0
- data/standards/stig_microsoft_skypebusiness_2016.json +29 -0
- data/standards/stig_microsoft_sql_server_2005_database.json +167 -0
- data/standards/stig_microsoft_sql_server_2005_instance.json +1001 -0
- data/standards/stig_microsoft_sql_server_2012_database.json +179 -0
- data/standards/stig_microsoft_sql_server_2012_database_instance.json +929 -0
- data/standards/stig_microsoft_visio_2013.json +89 -0
- data/standards/stig_microsoft_visio_2016.json +89 -0
- data/standards/stig_microsoft_windows_10_mobile.json +215 -0
- data/standards/stig_microsoft_windows_2008_server_domain_name_system.json +269 -0
- data/standards/stig_microsoft_windows_2012_server_domain_name_system.json +551 -0
- data/standards/stig_microsoft_windows_phone_8.1.json +161 -0
- data/standards/stig_microsoft_windows_server_2012_domain_controller.json +2633 -0
- data/standards/stig_microsoft_windows_server_2012_member_server.json +2411 -0
- data/standards/stig_microsoft_word_2003.json +47 -0
- data/standards/stig_microsoft_word_2007.json +119 -0
- data/standards/stig_microsoft_word_2010.json +221 -0
- data/standards/stig_microsoft_word_2013.json +221 -0
- data/standards/stig_microsoft_word_2016.json +215 -0
- data/standards/stig_mobile_application_management_mam_server.json +95 -0
- data/standards/stig_mobile_application_security_requirements_guide.json +233 -0
- data/standards/stig_mobile_device_integrity_scanning_mdis_server.json +119 -0
- data/standards/stig_mobile_device_management_mdm_server.json +125 -0
- data/standards/stig_mobile_device_manager_security_requirements_guide.json +2555 -0
- data/standards/stig_mobile_email_management_mem_server.json +197 -0
- data/standards/stig_mobile_operating_system_security_requirements_guide.json +1943 -0
- data/standards/stig_mobile_policy.json +35 -0
- data/standards/stig_mobile_policy_security_requirements_guide.json +437 -0
- data/standards/stig_mobileiron_core_v9.x_mdm.json +89 -0
- data/standards/stig_mobility_policy.json +65 -0
- data/standards/stig_mozilla_firefox.json +161 -0
- data/standards/stig_ms_exchange_2013_client_access_server.json +209 -0
- data/standards/stig_ms_exchange_2013_edge_transport_server.json +443 -0
- data/standards/stig_ms_exchange_2013_mailbox_server.json +437 -0
- data/standards/stig_ms_sharepoint_2010.json +269 -0
- data/standards/stig_ms_sharepoint_2013.json +245 -0
- data/standards/stig_ms_sharepoint_designer_2013.json +71 -0
- data/standards/stig_ms_sql_server_2014_database.json +263 -0
- data/standards/stig_ms_sql_server_2014_instance.json +575 -0
- data/standards/stig_ms_sql_server_2016_database.json +185 -0
- data/standards/stig_ms_sql_server_2016_instance.json +731 -0
- data/standards/stig_ms_windows_defender_antivirus.json +257 -0
- data/standards/stig_multifunction_device_and_network_printers.json +131 -0
- data/standards/stig_network_device_management_security_requirements_guide.json +863 -0
- data/standards/stig_network_devices.json +389 -0
- data/standards/stig_network_infrastructure_policy.json +455 -0
- data/standards/stig_network_security_requirements_guide.json +1961 -0
- data/standards/stig_operating_system_security_requirements_guide.json +1961 -0
- data/standards/stig_oracle_10_database_installation.json +527 -0
- data/standards/stig_oracle_10_database_instance.json +569 -0
- data/standards/stig_oracle_11_database_installation.json +527 -0
- data/standards/stig_oracle_11_database_instance.json +551 -0
- data/standards/stig_oracle_database_10g_installation.json +527 -0
- data/standards/stig_oracle_database_10g_instance.json +581 -0
- data/standards/stig_oracle_database_11.2g.json +1229 -0
- data/standards/stig_oracle_database_11g_installation.json +527 -0
- data/standards/stig_oracle_database_11g_instance.json +575 -0
- data/standards/stig_oracle_database_12c.json +1217 -0
- data/standards/stig_oracle_http_server_12.1.3.json +1703 -0
- data/standards/stig_oracle_linux_5.json +3431 -0
- data/standards/stig_oracle_linux_6.json +1583 -0
- data/standards/stig_oracle_weblogic_server_12c.json +443 -0
- data/standards/stig_palo_alto_networks_alg.json +311 -0
- data/standards/stig_palo_alto_networks_idps.json +185 -0
- data/standards/stig_palo_alto_networks_ndm.json +251 -0
- data/standards/stig_pda.json +83 -0
- data/standards/stig_pdasmartphone.json +95 -0
- data/standards/stig_perimeter_l3_switch.json +923 -0
- data/standards/stig_perimeter_l3_switch_-_cisco.json +1001 -0
- data/standards/stig_perimeter_router.json +803 -0
- data/standards/stig_perimeter_router_cisco.json +881 -0
- data/standards/stig_perimeter_router_juniper.json +803 -0
- data/standards/stig_postgresql_9.x.json +677 -0
- data/standards/stig_red_hat_enterprise_linux_5.json +3437 -0
- data/standards/stig_red_hat_enterprise_linux_6.json +1565 -0
- data/standards/stig_red_hat_enterprise_linux_7.json +1451 -0
- data/standards/stig_remote_access_policy.json +317 -0
- data/standards/stig_removable_storage_and_external_connection_technologies.json +143 -0
- data/standards/stig_removable_storage_and_external_connections.json +137 -0
- data/standards/stig_rfid_scanner.json +35 -0
- data/standards/stig_rfid_workstation.json +23 -0
- data/standards/stig_riverbed_steelhead_cx_v8_alg.json +83 -0
- data/standards/stig_riverbed_steelhead_cx_v8_ndm.json +371 -0
- data/standards/stig_router_security_requirements_guide.json +575 -0
- data/standards/stig_samsung_android_os_5_with_knox_2.0.json +365 -0
- data/standards/stig_samsung_android_os_6_with_knox_2.x.json +377 -0
- data/standards/stig_samsung_android_os_7_with_knox_2.x.json +443 -0
- data/standards/stig_samsung_android_with_knox_1.x.json +293 -0
- data/standards/stig_samsung_android_with_knox_2.x.json +371 -0
- data/standards/stig_samsung_knox_android_1.0.json +167 -0
- data/standards/stig_sharepoint_2010.json +269 -0
- data/standards/stig_sharepoint_2013.json +245 -0
- data/standards/stig_smartphone_policy.json +131 -0
- data/standards/stig_solaris_10_sparc.json +3029 -0
- data/standards/stig_solaris_10_x86.json +3065 -0
- data/standards/stig_solaris_11_sparc.json +1427 -0
- data/standards/stig_solaris_11_x86.json +1421 -0
- data/standards/stig_solaris_9_sparc.json +2915 -0
- data/standards/stig_solaris_9_x86.json +2915 -0
- data/standards/stig_sun_ray_4.json +185 -0
- data/standards/stig_sun_ray_4_policy.json +77 -0
- data/standards/stig_suse_linux_enterprise_server_v11system_z.json +3311 -0
- data/standards/stig_symantec_endpoint_protection_12.1_local_client_antivirus.json +689 -0
- data/standards/stig_symantec_endpoint_protection_12.1_managed_client_antivirus.json +695 -0
- data/standards/stig_tanium_6.5.json +461 -0
- data/standards/stig_tanium_7.0.json +803 -0
- data/standards/stig_test_and_development_zone_a.json +167 -0
- data/standards/stig_test_and_development_zone_b.json +179 -0
- data/standards/stig_test_and_development_zone_c.json +143 -0
- data/standards/stig_test_and_development_zone_d.json +143 -0
- data/standards/stig_traditional_security.json +917 -0
- data/standards/stig_unix_srg.json +3287 -0
- data/standards/stig_video_services_policy.json +497 -0
- data/standards/stig_video_teleconference.json +47 -0
- data/standards/stig_video_teleconference_vtc.json +12 -0
- data/standards/stig_vmware_esx_3_policy.json +155 -0
- data/standards/stig_vmware_esx_3_server.json +3791 -0
- data/standards/stig_vmware_esx_3_virtual_center.json +257 -0
- data/standards/stig_vmware_esx_3_virtual_machine.json +53 -0
- data/standards/stig_vmware_esxi_server_5.0.json +809 -0
- data/standards/stig_vmware_esxi_v5.json +5177 -0
- data/standards/stig_vmware_esxi_version_5_virtual_machine.json +317 -0
- data/standards/stig_vmware_nsx_distributed_firewall.json +83 -0
- data/standards/stig_vmware_nsx_distributed_logical_router.json +35 -0
- data/standards/stig_vmware_nsx_manager.json +191 -0
- data/standards/stig_vmware_vcenter_server.json +179 -0
- data/standards/stig_vmware_vcenter_server_version_5.json +149 -0
- data/standards/stig_vmware_vsphere_esxi_6.0.json +659 -0
- data/standards/stig_vmware_vsphere_vcenter_server_version_6.json +311 -0
- data/standards/stig_vmware_vsphere_virtual_machine_version_6.json +269 -0
- data/standards/stig_voice_and_video_over_internet_protocol_vvoip_policy.json +407 -0
- data/standards/stig_voice_video_endpoint_security_requirements_guide.json +395 -0
- data/standards/stig_voice_video_services_policy.json +671 -0
- data/standards/stig_voice_video_session_management_security_requirements_guide.json +329 -0
- data/standards/stig_voicevideo_over_internet_protocol.json +419 -0
- data/standards/stig_voicevideo_over_internet_protocol_vvoip.json +263 -0
- data/standards/stig_voicevideo_services_policy.json +569 -0
- data/standards/stig_web_policy.json +95 -0
- data/standards/stig_web_server.json +317 -0
- data/standards/stig_web_server_security_requirements_guide.json +587 -0
- data/standards/stig_win2k3_audit.json +761 -0
- data/standards/stig_win2k8_audit.json +1085 -0
- data/standards/stig_win2k8_r2_audit.json +1637 -0
- data/standards/stig_win7_audit.json +1613 -0
- data/standards/stig_windows_10.json +1691 -0
- data/standards/stig_windows_2003_domain_controller.json +893 -0
- data/standards/stig_windows_2003_member_server.json +845 -0
- data/standards/stig_windows_2008_domain_controller.json +1475 -0
- data/standards/stig_windows_2008_member_server.json +1301 -0
- data/standards/stig_windows_7.json +1781 -0
- data/standards/stig_windows_8.json +2399 -0
- data/standards/stig_windows_88.1.json +2273 -0
- data/standards/stig_windows_8_8.1.json +2297 -0
- data/standards/stig_windows_defender_antivirus.json +239 -0
- data/standards/stig_windows_dns.json +185 -0
- data/standards/stig_windows_firewall_with_advanced_security.json +137 -0
- data/standards/stig_windows_paw.json +155 -0
- data/standards/stig_windows_phone_6.5_with_good_mobility_suite.json +65 -0
- data/standards/stig_windows_server_2008_r2_domain_controller.json +1961 -0
- data/standards/stig_windows_server_2008_r2_member_server.json +1745 -0
- data/standards/stig_windows_server_20122012_r2_domain_controller.json +2255 -0
- data/standards/stig_windows_server_20122012_r2_member_server.json +2045 -0
- data/standards/stig_windows_server_2012_2012_r2_domain_controller.json +2279 -0
- data/standards/stig_windows_server_2012_2012_r2_member_server.json +2075 -0
- data/standards/stig_windows_server_2012_domain_controller.json +2471 -0
- data/standards/stig_windows_server_2012_member_server.json +2249 -0
- data/standards/stig_windows_server_2016.json +1661 -0
- data/standards/stig_windows_vista.json +1517 -0
- data/standards/stig_windows_xp.json +893 -0
- data/standards/stig_wireless_keyboard_and_mouse.json +23 -0
- data/standards/stig_wireless_management_server_policy.json +53 -0
- data/standards/stig_wireless_remote_access_policy_security_implementation_guide.json +29 -0
- data/standards/stig_wlan_access_point_enclave-niprnet_connected.json +227 -0
- data/standards/stig_wlan_access_point_internet_gateway_only_connection.json +209 -0
- data/standards/stig_wlan_access_point_policy.json +17 -0
- data/standards/stig_wlan_authentication_server.json +29 -0
- data/standards/stig_wlan_bridge.json +209 -0
- data/standards/stig_wlan_client.json +65 -0
- data/standards/stig_wlan_controller.json +215 -0
- data/standards/stig_wlan_ids_sensorserver.json +23 -0
- data/standards/stig_wman_access_point.json +263 -0
- data/standards/stig_wman_bridge.json +209 -0
- data/standards/stig_wman_subscriber.json +65 -0
- data/standards/stig_zos_acf2.json +1451 -0
- data/standards/stig_zos_bmc_control-dacf2.json +53 -0
- data/standards/stig_zos_bmc_control-dracf.json +59 -0
- data/standards/stig_zos_bmc_control-dtss.json +65 -0
- data/standards/stig_zos_bmc_control-macf2.json +59 -0
- data/standards/stig_zos_bmc_control-mracf.json +65 -0
- data/standards/stig_zos_bmc_control-mrestartacf2.json +23 -0
- data/standards/stig_zos_bmc_control-mrestartracf.json +23 -0
- data/standards/stig_zos_bmc_control-mrestarttss.json +23 -0
- data/standards/stig_zos_bmc_control-mtss.json +71 -0
- data/standards/stig_zos_bmc_control-oacf2.json +53 -0
- data/standards/stig_zos_bmc_control-oracf.json +59 -0
- data/standards/stig_zos_bmc_control-otss.json +65 -0
- data/standards/stig_zos_bmc_ioaacf2.json +53 -0
- data/standards/stig_zos_bmc_ioaracf.json +59 -0
- data/standards/stig_zos_bmc_ioatss.json +65 -0
- data/standards/stig_zos_bmc_mainviewzosacf2.json +47 -0
- data/standards/stig_zos_bmc_mainviewzosracf.json +53 -0
- data/standards/stig_zos_bmc_mainviewzostss.json +59 -0
- data/standards/stig_zos_ca_1_tape_managementacf2.json +65 -0
- data/standards/stig_zos_ca_1_tape_managementracf.json +77 -0
- data/standards/stig_zos_ca_1_tape_managementtss.json +77 -0
- data/standards/stig_zos_ca_auditoracf2.json +29 -0
- data/standards/stig_zos_ca_auditorracf.json +29 -0
- data/standards/stig_zos_ca_auditortss.json +29 -0
- data/standards/stig_zos_ca_common_servicesacf2.json +23 -0
- data/standards/stig_zos_ca_common_servicesracf.json +29 -0
- data/standards/stig_zos_ca_common_servicestss.json +29 -0
- data/standards/stig_zos_ca_micsacf2.json +23 -0
- data/standards/stig_zos_ca_micsracf.json +23 -0
- data/standards/stig_zos_ca_micstss.json +23 -0
- data/standards/stig_zos_ca_mimacf2.json +41 -0
- data/standards/stig_zos_ca_mimracf.json +47 -0
- data/standards/stig_zos_ca_mimtss.json +47 -0
- data/standards/stig_zos_ca_vtapeacf2.json +29 -0
- data/standards/stig_zos_ca_vtaperacf.json +35 -0
- data/standards/stig_zos_ca_vtapetss.json +35 -0
- data/standards/stig_zos_catalog_solutionsacf2.json +23 -0
- data/standards/stig_zos_catalog_solutionsracf.json +23 -0
- data/standards/stig_zos_catalog_solutionstss.json +23 -0
- data/standards/stig_zos_clsupersessionacf2.json +53 -0
- data/standards/stig_zos_clsupersessionracf.json +65 -0
- data/standards/stig_zos_clsupersessiontss.json +71 -0
- data/standards/stig_zos_compuware_abend-aidacf2.json +47 -0
- data/standards/stig_zos_compuware_abend-aidracf.json +53 -0
- data/standards/stig_zos_compuware_abend-aidtss.json +53 -0
- data/standards/stig_zos_cssmtpacf2.json +23 -0
- data/standards/stig_zos_cssmtpracf.json +29 -0
- data/standards/stig_zos_cssmtptss.json +29 -0
- data/standards/stig_zos_fdracf2.json +23 -0
- data/standards/stig_zos_fdrracf.json +23 -0
- data/standards/stig_zos_fdrtss.json +23 -0
- data/standards/stig_zos_hcdacf2.json +29 -0
- data/standards/stig_zos_hcdracf.json +29 -0
- data/standards/stig_zos_hcdtss.json +29 -0
- data/standards/stig_zos_ibm_cics_transaction_serveracf2.json +17 -0
- data/standards/stig_zos_ibm_cics_transaction_serverracf.json +17 -0
- data/standards/stig_zos_ibm_cics_transaction_servertss.json +17 -0
- data/standards/stig_zos_ibm_health_checkeracf2.json +23 -0
- data/standards/stig_zos_ibm_health_checkerracf.json +29 -0
- data/standards/stig_zos_ibm_health_checkertss.json +29 -0
- data/standards/stig_zos_ibm_system_display_and_search_facility_sdsfacf2.json +53 -0
- data/standards/stig_zos_ibm_system_display_and_search_facility_sdsfracf.json +59 -0
- data/standards/stig_zos_ibm_system_display_and_search_facility_sdsftss.json +53 -0
- data/standards/stig_zos_icsfacf2.json +29 -0
- data/standards/stig_zos_icsfracf.json +35 -0
- data/standards/stig_zos_icsftss.json +35 -0
- data/standards/stig_zos_netviewacf2.json +41 -0
- data/standards/stig_zos_netviewracf.json +47 -0
- data/standards/stig_zos_netviewtss.json +53 -0
- data/standards/stig_zos_quest_nc-passacf2.json +35 -0
- data/standards/stig_zos_quest_nc-passracf.json +41 -0
- data/standards/stig_zos_quest_nc-passtss.json +47 -0
- data/standards/stig_zos_racf.json +1415 -0
- data/standards/stig_zos_roscoeacf2.json +47 -0
- data/standards/stig_zos_roscoeracf.json +53 -0
- data/standards/stig_zos_roscoetss.json +59 -0
- data/standards/stig_zos_srrauditacf2.json +23 -0
- data/standards/stig_zos_srrauditracf.json +23 -0
- data/standards/stig_zos_srraudittss.json +23 -0
- data/standards/stig_zos_tadzacf2.json +29 -0
- data/standards/stig_zos_tadzracf.json +35 -0
- data/standards/stig_zos_tadztss.json +35 -0
- data/standards/stig_zos_tdmfacf2.json +23 -0
- data/standards/stig_zos_tdmfracf.json +23 -0
- data/standards/stig_zos_tdmftss.json +23 -0
- data/standards/stig_zos_tss.json +1523 -0
- data/standards/stig_zos_vssracf.json +29 -0
- metadata +691 -0
|
@@ -0,0 +1,161 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "stig_microsoft_windows_phone_8.1",
|
|
3
|
+
"date": "2015-05-13",
|
|
4
|
+
"description": "This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.",
|
|
5
|
+
"title": "Microsoft Windows Phone 8.1 Security Technical Implementation Guide",
|
|
6
|
+
"version": "1",
|
|
7
|
+
"item_syntax": "^\\w-\\d+$",
|
|
8
|
+
"section_separator": null,
|
|
9
|
+
"items": [
|
|
10
|
+
{
|
|
11
|
+
"id": "V-58931",
|
|
12
|
+
"title": "Windows Phone 8.1 must be configured to disable developer modes.",
|
|
13
|
+
"description": "Developer modes circumvent certain security measures, so their use for standard operation is not recommended. Developer modes may increase the likelihood of compromise of confidentiality, integrity, and availability.\n\nSFR ID: FMT_SMF.1.1 #21",
|
|
14
|
+
"severity": "medium"
|
|
15
|
+
},
|
|
16
|
+
{
|
|
17
|
+
"id": "V-58933",
|
|
18
|
+
"title": "Windows Phone 8.1 must be configured to enforce an application installation policy by specifying one or more authorized application repositories.",
|
|
19
|
+
"description": "Forcing all applications to be installed from authorized application repositories can prevent unauthorized and malicious applications from being installed and executed on mobile devices. Allowing such installations and executions could cause a compromise of DoD data accessible by these unauthorized/malicious applications.\n\nSFR ID: FMT_SMF.1.1 #10",
|
|
20
|
+
"severity": "medium"
|
|
21
|
+
},
|
|
22
|
+
{
|
|
23
|
+
"id": "V-58935",
|
|
24
|
+
"title": "Windows Phone 8.1 must be configured to enforce an application installation policy through an application whitelist specifying a set of allowed applications and versions.",
|
|
25
|
+
"description": "Requiring all authorized applications to be in an application whitelist prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the whitelist. Failure to configure an application whitelist properly could allow unauthorized and malicious applications to be downloaded, installed, and executed on the mobile device, causing a compromise of DoD data accessible by these applications. The actions of some enterprise apps cannot be controlled by whitelist, such as backup of application information to OneDrive. Other mitigation techniques will be required to facilitate those actions to safeguard data.\n\nSFR ID: FMT_SMF.1.1 #10",
|
|
26
|
+
"severity": "medium"
|
|
27
|
+
},
|
|
28
|
+
{
|
|
29
|
+
"id": "V-58937",
|
|
30
|
+
"title": "Windows Phone 8.1 must be configured to disable USB mass storage mode.",
|
|
31
|
+
"description": "This data transfer capability could allow users to transfer sensitive DoD data onto unauthorized USB storage devices, thus leading to the compromise of this DoD data.\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
32
|
+
"severity": "medium"
|
|
33
|
+
},
|
|
34
|
+
{
|
|
35
|
+
"id": "V-58939",
|
|
36
|
+
"title": "Windows Phone 8.1 must be configured to prohibit more than 10 consecutive failed authentication attempts.",
|
|
37
|
+
"description": "Users must not be able to override the system policy on the maximum number of consecutive failed authentication attempts because this could allow them to raise the maximum, thus giving adversaries more chances to guess/brute-force passwords, which increases the risk of the mobile device being compromised. Therefore, only administrators should have the authority to set consecutive failed authentication attempt policies.\n\nSFR ID: FMT_SMF.1.1 #02",
|
|
38
|
+
"severity": "low"
|
|
39
|
+
},
|
|
40
|
+
{
|
|
41
|
+
"id": "V-58941",
|
|
42
|
+
"title": "Windows Phone 8.1 must be configured to lock the display after 15 minutes (or less) of inactivity.",
|
|
43
|
+
"description": "The screen lock time-out must be set to a value that helps protect the device from unauthorized access. Having a too-long time-out would increase the window of opportunity for adversaries who gain physical access to the mobile device through loss, theft, etc. Such devices are much more likely to be in an unlocked state when acquired by an adversary, thus granting immediate access to the data on the mobile device. The maximum time-out period of 15 minutes has been selected to balance functionality and security; shorter time-out periods may be appropriate, depending on the risks posed to the mobile device.\n\nSFR ID: FMT_SMF.1.1 #02",
|
|
44
|
+
"severity": "medium"
|
|
45
|
+
},
|
|
46
|
+
{
|
|
47
|
+
"id": "V-58943",
|
|
48
|
+
"title": "Windows Phone 8.1 must be configured to enforce a minimum password length of 6 characters.",
|
|
49
|
+
"description": "Password strength is a measure of the effectiveness of a password in resisting guessing and brute-force attacks. The ability to crack a password is a function of how many attempts an adversary is permitted, how quickly an adversary can do each attempt, and the size of the password space. The longer the minimum length of the password is, the larger the password space. Having a too-short minimum password length significantly reduces password strength, increasing the chance of password compromise and resulting device and data compromise.\n\nSFR ID: FMT_SMF.1.1 #01",
|
|
50
|
+
"severity": "low"
|
|
51
|
+
},
|
|
52
|
+
{
|
|
53
|
+
"id": "V-58945",
|
|
54
|
+
"title": "Windows Phone 8.1 must be configured to enable data-at-rest protection for built-in storage media.",
|
|
55
|
+
"description": "The operating system must ensure the data being written to the mobile device's built-in storage media is protected from unauthorized access. If data at rest is unencrypted, it is vulnerable to disclosure. Even if the operating system enforces permissions on data access, an adversary can read storage media directly, thereby circumventing operating system controls. Encrypting the data ensures confidentiality is protected even when the operating system is not running.\n\nSFR ID: FMT_SMF.1.1 #22",
|
|
56
|
+
"severity": "high"
|
|
57
|
+
},
|
|
58
|
+
{
|
|
59
|
+
"id": "V-58947",
|
|
60
|
+
"title": "Windows Phone 8.1 must be configured to enable data-at-rest protection for removable storage media or to disable the removable storage media.",
|
|
61
|
+
"description": "The operating system must ensure the data being written to the mobile device's removable media is protected from unauthorized access. If data at rest is unencrypted, it is vulnerable to disclosure. Even if the operating system enforces permissions on data access, an adversary can read removable media directly, thereby circumventing operating system controls. Encrypting the data ensures confidentiality is protected even when the operating system is not running. Windows Phone 8.1 platform cannot enforce encryption for removable media, so the use of removable media must be disabled. This alternative mitigation, prohibiting the use of removable storage media using an IA control, eliminates the threat of data vulnerabilities since no data can be stored on such media.\n\nSFR ID: FMT_SMF.1.1 #23",
|
|
62
|
+
"severity": "high"
|
|
63
|
+
},
|
|
64
|
+
{
|
|
65
|
+
"id": "V-58949",
|
|
66
|
+
"title": "Before establishing a user session, Windows Phone 8.1 must display an administrator-specified advisory notice and consent warning banner regarding use of Windows Phone 8.1.",
|
|
67
|
+
"description": "The operating system is required to display the DoD-approved system use notification message or banner before granting access to the system that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. This ensures the legal requirements for auditing and monitoring are met. System use notification messages can be displayed when individuals log on to the information system. The approved DoD text must be used as specified in the DoD CIO memorandum dated 9 May 2008.\n\nSFR ID: FTA_TAB.1.1",
|
|
68
|
+
"severity": "low"
|
|
69
|
+
},
|
|
70
|
+
{
|
|
71
|
+
"id": "V-58951",
|
|
72
|
+
"title": "Windows Phone 8.1 must be configured to implement the management setting:\n\nDisable the capability of being able to show notifications in the Action Center while a device is locked.",
|
|
73
|
+
"description": "When a mobile device is locked, there should be no access to its protected/sensitive data since it could enable unauthorized people with physical access to the device to bring up and view confidential information. The Action Center on the Windows Phone 8.1 platform allows the viewing of recent notifications including emails, calendar reminders, instant messages, and other potentially sensitive information. Disabling this feature mitigates the exposure of this data.\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
74
|
+
"severity": "medium"
|
|
75
|
+
},
|
|
76
|
+
{
|
|
77
|
+
"id": "V-58953",
|
|
78
|
+
"title": "Windows Phone 8.1 must be configured to implement the management setting:\n\nDisable the ability of users to be able to manually turn off the VPN.",
|
|
79
|
+
"description": "For consumer use, the ability to turn off or suspend a VPN connection may be useful in cases of bypassing server issues or decreasing battery utilization, but, in a DoD environment, a VPN connection needs to be retained to provide a consistent secure tunnel for communications with DoD networks. Therefore, disabling the ability for a user to be able to turn off VPN makes it more difficult for an adversary to capture network traffic.\n\nFor Windows Phone 8.1, this requirement is needed to prevent access to cloud services like OneDrive by OS applications and components such as:\n\nOffice Hub/Applications\nOneNote\nBackup\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
80
|
+
"severity": "medium"
|
|
81
|
+
},
|
|
82
|
+
{
|
|
83
|
+
"id": "V-58955",
|
|
84
|
+
"title": "Windows Phone 8.1 must be configured to implement the management setting:\n\nNot allow the device unlock password to contain more than two sequential or repeating characters (e.g., 456, aaa).",
|
|
85
|
+
"description": "Password complexity or strength refers to how difficult it is to determine a password using a dictionary or brute-force attack. Passwords with sequential or repeating numbers or alphabetic characters (e.g., 456, 987, 222, abc, ddd) are considered easier to crack than random patterns. Therefore, disallowing sequential or repeating numbers or alphabetic characters makes it more difficult for an adversary to discover the password.\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
86
|
+
"severity": "medium"
|
|
87
|
+
},
|
|
88
|
+
{
|
|
89
|
+
"id": "V-58957",
|
|
90
|
+
"title": "Windows Phone 8.1 must be configured to implement the management setting: Disable the capability of the Cortana personal assistant A.I. to be functional when the device is locked.",
|
|
91
|
+
"description": "When a mobile device is locked, there should be no access to its protected/sensitive data since it could enable unauthorized people with physical access to the device to bring up and view confidential information. The Cortana personal assistant can perform a number of voice-related queries and actions that can aid productivity but also allows some of its actions to be done while the device is locked. Disabling this feature mitigates the exposure of potentially sensitive information that should remain secured when a device is locked.\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
92
|
+
"severity": "medium"
|
|
93
|
+
},
|
|
94
|
+
{
|
|
95
|
+
"id": "V-58959",
|
|
96
|
+
"title": "Windows Phone 8.1 must be configured to implement the management setting:\n\nDisable the capability for a user to manually unenroll from MDM management.",
|
|
97
|
+
"description": "The use of an MDM allows an organization to assign values to security-related parameters across all the devices it manages. This provides assurance that the required mobile OS security controls are being enforced and that the device user or an adversary has not modified or disabled the controls. If a user has the ability on their device to manually unenroll from MDM management, this removes all IA controls and exposes the device and the user to a number of threat vectors and takes them out of compliance. Disabling this feature mitigates the risk from loss of control and ensures that the devices maintain the required locked down state.\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
98
|
+
"severity": "medium"
|
|
99
|
+
},
|
|
100
|
+
{
|
|
101
|
+
"id": "V-58961",
|
|
102
|
+
"title": "Windows Phone 8.1 must be configured to implement the management setting:\n\nDisable the sharing of Office documents through service providers like email and cloud.",
|
|
103
|
+
"description": "Generally, when doing document collaboration, it is useful, from a productivity perspective, to be able to share those documents with peers who can review and edit those documents. But, if those same documents can be shared to public locations through email and cloud storage services, data leakage scenarios are possible, enabling sensitive data to be shared outside of secure DoD locations. To mitigate these threats, the sharing capability of documents should be disabled to prevent this possibility.\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
104
|
+
"severity": "medium"
|
|
105
|
+
},
|
|
106
|
+
{
|
|
107
|
+
"id": "V-58963",
|
|
108
|
+
"title": "Windows Phone 8.1 must be configured to implement the management setting:\n\nDisable the capability for syncing settings such as the theme, application settings, Internet Explorer sites visited, and cached passwords to Microsoft OneDrive cloud storage.",
|
|
109
|
+
"description": "A public cloud backup feature may gather a user's information, such as PII, or sensitive documents. With this feature enabled, sensitive information will be backed up to the manufacturer's servers and database. This data is stored at a location that has unauthorized employees accessing this data. This data is stored on a server that has a location unknown to the DoD. Disabling this feature mitigates the risk of a backup feature that stores sensitive data on a server that has the potential to be located in a country other than the United States.\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
110
|
+
"severity": "medium"
|
|
111
|
+
},
|
|
112
|
+
{
|
|
113
|
+
"id": "V-58965",
|
|
114
|
+
"title": "Windows Phone 8.1 must be configured to implement the management setting:\n\nDisallow the sharing of device telemetry captured as a result of crashes and other logging processes.",
|
|
115
|
+
"description": "Applications and OS processes have a capability to have telemetry data called Software Quality Metrics (SQM) that can send software instrumentation metrics to the SQM service and to the client to download client-specific control data. The protocol allows applications and operating system components to collect and send instrumentation metrics, including customer experience data, crash reports, and traces to a hosted service over HTTP/HTTPS. That data, while not including any privacy-sensitive information, could potentially contain information sensitive to DoD. Disabling this feature mitigates the risk of any unknown information being stored in Microsoft telemetry tracking databases.\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
116
|
+
"severity": "medium"
|
|
117
|
+
},
|
|
118
|
+
{
|
|
119
|
+
"id": "V-58967",
|
|
120
|
+
"title": "Windows Phone 8.1 must be configured to implement the management setting:\n\nEmploy mobile device management services to centrally manage security-relevant configuration and policy settings.",
|
|
121
|
+
"description": "Security-related parameters are those parameters impacting the security state of the system and include parameters related to the implementation of other IA controls. If these controls are not implemented, the system may be vulnerable to a variety of attacks. The use of an MDM allows an organization to assign values to security-related parameters across all the devices it manages. This provides assurance that the required mobile OS security controls are being enforced and that the device user or an adversary has not modified or disabled the controls. It also greatly increases efficiency and manageability of devices in a large-scale environment relative to an environment in which each device must be configured separately.\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
122
|
+
"severity": "medium"
|
|
123
|
+
},
|
|
124
|
+
{
|
|
125
|
+
"id": "V-58971",
|
|
126
|
+
"title": "Windows Phone 8.1 must be designed to implement protected and secure OS Updates.",
|
|
127
|
+
"description": "MOS updates and upgrades are an essential part of the life cycle of modern smartphones and generally occur annually. OS updates need to be a trusted process to prevent compromise of OS code, drivers, code signing, and malware injection. That process needs to be delivered over a securely encrypted and mutually authenticated method. If the MOS update process security cannot be documented, then the ability to disable updates or manage their availability by MDM is an acceptable option. The UBE action on the mobile device ensures that all approved (whitelist) apps will receive important functional and security updates, in addition to system security updates.\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
128
|
+
"severity": "medium"
|
|
129
|
+
},
|
|
130
|
+
{
|
|
131
|
+
"id": "V-58973",
|
|
132
|
+
"title": "Windows Phone 8.1 must disable split-tunneling on the VPN client.",
|
|
133
|
+
"description": "Without strong mutual authentication, a mobile device may connect to an unauthorized network. In many cases, the user may falsely believe that the device is connected to an authorized network and then provide authentication credentials and other sensitive information. A strong bidirectional, cryptographically based authentication method over VPN mitigates this risk.\n\nFor Windows Phone 8.1, this requirement is needed to prevent access to cloud services like OneDrive by OS applications and components such as:\n\nOffice Hub/Applications\nOneNote\nBackup\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
134
|
+
"severity": "medium"
|
|
135
|
+
},
|
|
136
|
+
{
|
|
137
|
+
"id": "V-58975",
|
|
138
|
+
"title": "Windows Phone 8.1 must have a mechanism to restrict capabilities of applications and OS components that leverage cloud storage by blocking access to OneDrive at the firewall level.",
|
|
139
|
+
"description": "While backup and collaboration of data is useful from a productivity perspective, if that same data can be shared to public locations through cloud storage services, data leakage scenarios are possible, enabling sensitive data to be shared outside of secure DoD locations. To mitigate these threats, the ability to store or backup data in public cloud areas should be blocked.\n\nFor Windows Phone 8.1, this requirement is needed to prevent access to cloud services like OneDrive by OS applications and components such as:\n\nOffice Hub/Applications\nOneNote\nBackup\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
140
|
+
"severity": "medium"
|
|
141
|
+
},
|
|
142
|
+
{
|
|
143
|
+
"id": "V-58977",
|
|
144
|
+
"title": "Windows Phone 8.1 must require an Always On VPN session when used.",
|
|
145
|
+
"description": "Without strong mutual authentication, a mobile device may connect to an unauthorized network. In many cases, the user may falsely believe that the device is connected to an authorized network and then provide authentication credentials and other sensitive information. A strong bidirectional, cryptographically based authentication method over VPN mitigates this risk. A VPN can be configured to time out when idle, which, depending on the configuration for a triggered connection, might enable scenarios where the VPN is not on and unprotected access to the Internet is possible. Requiring the VPN connection to be Always On ensures that the VPN is at all times protecting and securing traffic.\n\nFor Windows Phone 8.1, this configuration supports the DoD requirement that applications cannot access or store data to cloud storage services.\n\nFor Windows Phone 8.1, this requirement is needed to prevent access to cloud services like OneDrive by OS applications and components such as:\n\nOffice Hub/Applications\nOneNote\nBackup\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
146
|
+
"severity": "medium"
|
|
147
|
+
},
|
|
148
|
+
{
|
|
149
|
+
"id": "V-58979",
|
|
150
|
+
"title": "Windows Phone 8.1 must have a mechanism to restrict capabilities of applications and OS components that leverage cloud storage by disabling the Backup feature.",
|
|
151
|
+
"description": "While backup and collaboration of data is useful from a productivity perspective, if that same data can be shared to public locations through cloud storage services, data leakage scenarios are possible, enabling sensitive data to be shared outside of secure DoD locations. To mitigate these threats, the ability to store or backup data in public cloud areas should be blocked.\n\nFor Windows Phone 8.1, this requirement is needed to prevent access to cloud services like OneDrive by OS applications and components such as:\n\nOffice Hub/Applications\nOneNote\nBackup\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
152
|
+
"severity": "medium"
|
|
153
|
+
},
|
|
154
|
+
{
|
|
155
|
+
"id": "V-59025",
|
|
156
|
+
"title": "Windows Phone 8.1 must be running build 8.10.15116 or higher (GDR2).",
|
|
157
|
+
"description": "Throughout ongoing operating system development, Windows Phone has a process of MOS updates to add new features including improved enterprise and security capabilities as well as fixes to issues discovered after its initial release. These releases are termed General Distribution Releases (GDR). In working with DoD and our enterprise customers worldwide, requirements and issues were discovered that resulted in necessary changes to the Windows Phone MOS. One of those changes in the General Distribution Release 2 (GDR2) provides the capability needed to implement the VPN process required by the DoD to ensure that personal cloud services are blocked from use by the end user, and is the key to success for all associated requirements.\n\nSFR ID: FMT_SMF.1.1 #42",
|
|
158
|
+
"severity": "medium"
|
|
159
|
+
}
|
|
160
|
+
]
|
|
161
|
+
}
|
|
@@ -0,0 +1,2633 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "stig_microsoft_windows_server_2012_domain_controller",
|
|
3
|
+
"date": "2013-07-25",
|
|
4
|
+
"description": "Microsoft Windows Server 2012 Security Technical Implementation Guide (STIG) is published as a tool to improve the security of Department of Defense (DoD) information systems. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.letterkenny.FSO.mbx.stig-customer-support-mailbox@mail.mil.",
|
|
5
|
+
"title": "Microsoft Windows Server 2012 Domain Controller Security Technical Implementation Guide",
|
|
6
|
+
"version": "1",
|
|
7
|
+
"item_syntax": "^\\w-\\d+$",
|
|
8
|
+
"section_separator": null,
|
|
9
|
+
"items": [
|
|
10
|
+
{
|
|
11
|
+
"id": "WN12-00-000001",
|
|
12
|
+
"title": "Server systems must be located in a controlled access area.",
|
|
13
|
+
"description": "Inadequate physical protection can undermine all other security precautions utilized to protect the system. This can jeopardize the confidentiality, availability, and integrity of the system. Physical security is the first line of protection of any system.",
|
|
14
|
+
"severity": "medium"
|
|
15
|
+
},
|
|
16
|
+
{
|
|
17
|
+
"id": "WN12-00-000002",
|
|
18
|
+
"title": "System BIOS or system controllers supporting password protection must have administrator accounts/passwords only configured, and no others.",
|
|
19
|
+
"description": "A system's BIOS or system controller handles the initial startup of a system, and its configuration must be protected from unauthorized modification. When the BIOS or system controller supports the creation of user accounts or passwords, such protections must be used and accounts/passwords only assigned to system administrators. Failure to protect BIOS or system controller settings could result in Denial of Service or compromise of the system resulting from unauthorized configuration changes.",
|
|
20
|
+
"severity": "medium"
|
|
21
|
+
},
|
|
22
|
+
{
|
|
23
|
+
"id": "WN12-00-000003",
|
|
24
|
+
"title": "The system must not use removable media as the boot loader.",
|
|
25
|
+
"description": "Malicious users with removable boot media can gain access to a system configured to use removable media as the boot loader.",
|
|
26
|
+
"severity": "high"
|
|
27
|
+
},
|
|
28
|
+
{
|
|
29
|
+
"id": "WN12-00-000004",
|
|
30
|
+
"title": "Users with administrative privilege must be documented.",
|
|
31
|
+
"description": "Administrative accounts may perform any action on a system. Users with administrative accounts must be documented to ensure those with this level of access are clearly identified.",
|
|
32
|
+
"severity": "medium"
|
|
33
|
+
},
|
|
34
|
+
{
|
|
35
|
+
"id": "WN12-00-000005",
|
|
36
|
+
"title": "Users with Administrative privileges must have separate accounts for administrative duties and normal operational tasks.",
|
|
37
|
+
"description": "Using a privileged account to perform routine functions makes the computer vulnerable to malicious software inadvertently introduced during a session that has been granted full privileges.",
|
|
38
|
+
"severity": "high"
|
|
39
|
+
},
|
|
40
|
+
{
|
|
41
|
+
"id": "WN12-00-000006",
|
|
42
|
+
"title": "Policy must require that system administrators (SAs) be trained for the operating systems used by systems under their control.",
|
|
43
|
+
"description": "If SAs are assigned to systems running operating systems for which they have no training, these systems are at additional risk of unintentional misconfiguration that may result in vulnerabilities or decreased availability of the system.",
|
|
44
|
+
"severity": "medium"
|
|
45
|
+
},
|
|
46
|
+
{
|
|
47
|
+
"id": "WN12-00-000007",
|
|
48
|
+
"title": "Passwords for the built-in Administrator account must be changed regularly.",
|
|
49
|
+
"description": "The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the password. Passwords for the built-in Administrator account must be changed at least annually or when any member of the administrative team leaves the organization.",
|
|
50
|
+
"severity": "medium"
|
|
51
|
+
},
|
|
52
|
+
{
|
|
53
|
+
"id": "WN12-00-000008",
|
|
54
|
+
"title": "Policy must require that administrative user accounts not be used with applications that access the Internet, such as web browsers, or with potential Internet sources, such as email.",
|
|
55
|
+
"description": "Using applications that access the Internet or have potential Internet sources using administrative privileges exposes a system to compromise. If a flaw in an application is exploited while running as a privileged user, the entire system could be compromised. Web browsers and email are common attack vectors for introducing malicious code and must not be run with an administrative user account.\n\nSince administrative user accounts may generally change or work around technical restrictions for running a web browser or other applications, it is essential that policy requires administrative users to not access the Internet or use applications, such as email.\n\nThe policy should define specific exceptions for local service administration. These exceptions may include HTTP(S)-based tools that are used for the administration of the local system, services, or attached devices.",
|
|
56
|
+
"severity": "high"
|
|
57
|
+
},
|
|
58
|
+
{
|
|
59
|
+
"id": "WN12-00-000009",
|
|
60
|
+
"title": "Members of the Backup Operators group must have separate accounts for backup duties and normal operational tasks.",
|
|
61
|
+
"description": "Backup Operators are able to read and write to any file in the system, regardless of the rights assigned to it. Backup and restore rights permit users to circumvent the file access restrictions present on NTFS disk drives for backup and restore purposes. Members of the Backup Operators group must have separate logon accounts for performing backup duties.",
|
|
62
|
+
"severity": "medium"
|
|
63
|
+
},
|
|
64
|
+
{
|
|
65
|
+
"id": "WN12-00-000010",
|
|
66
|
+
"title": "Application account passwords must be at least 15 characters in length.",
|
|
67
|
+
"description": "Application/service account passwords must be of sufficient length to prevent being easily cracked. Application/service accounts that are manually managed must have passwords at least 15 characters in length.",
|
|
68
|
+
"severity": "medium"
|
|
69
|
+
},
|
|
70
|
+
{
|
|
71
|
+
"id": "WN12-00-000011",
|
|
72
|
+
"title": "Application account passwords must be changed at least annually or when a system administrator with knowledge of the password leaves the organization.",
|
|
73
|
+
"description": "Setting application accounts to expire may cause applications to stop functioning. However, not changing them on a regular basis exposes them to attack. The site will have a policy that application account passwords are changed at least annually or when a system administrator with knowledge of the password leaves the organization.",
|
|
74
|
+
"severity": "medium"
|
|
75
|
+
},
|
|
76
|
+
{
|
|
77
|
+
"id": "WN12-00-000012",
|
|
78
|
+
"title": "Shared user accounts must not be permitted on the system.",
|
|
79
|
+
"description": "Shared accounts (accounts where two or more people log in with the same user identification) do not provide adequate identification and authentication. There is no way to provide for nonrepudiation or individual accountability for system access and resource usage. Documentation must include a list of personnel that have access to each shared account.",
|
|
80
|
+
"severity": "medium"
|
|
81
|
+
},
|
|
82
|
+
{
|
|
83
|
+
"id": "WN12-00-000013",
|
|
84
|
+
"title": "Security configuration tools or equivalent processes must be used to configure and maintain platforms for security compliance.",
|
|
85
|
+
"description": "Security configuration tools such as Group Policies and Security Templates allow system administrators to consolidate security-related system settings into a single configuration file. These settings can then be applied consistently to any number of Windows machines.",
|
|
86
|
+
"severity": "low"
|
|
87
|
+
},
|
|
88
|
+
{
|
|
89
|
+
"id": "WN12-00-000014",
|
|
90
|
+
"title": "System-level information must be backed up per organization defined frequency consistent with recovery time and recovery point objectives.",
|
|
91
|
+
"description": "Operating system backup is a critical step in maintaining data assurance and availability. \n\nSystem-level information includes system-state information, operating system and application software, and licenses. \n\nBackups must be consistent with organizational recovery time and recovery point objectives.",
|
|
92
|
+
"severity": "low"
|
|
93
|
+
},
|
|
94
|
+
{
|
|
95
|
+
"id": "WN12-00-000015",
|
|
96
|
+
"title": "User-level information must be backed up per organization defined frequency consistent with recovery time and recovery point objectives.",
|
|
97
|
+
"description": "Operating system backup is a critical step in maintaining data assurance and availability. \n\nUser-level information is data generated by information system and/or application users.\n\nBackups shall be consistent with organizational recovery time and recovery point objectives.",
|
|
98
|
+
"severity": "low"
|
|
99
|
+
},
|
|
100
|
+
{
|
|
101
|
+
"id": "WN12-00-000016",
|
|
102
|
+
"title": "Backups of system-level information must be protected.",
|
|
103
|
+
"description": "A system backup will usually include sensitive information such as user accounts that could be used in an attack. As a valuable system resource, the system backup must be protected and stored in a physically secure location.",
|
|
104
|
+
"severity": "low"
|
|
105
|
+
},
|
|
106
|
+
{
|
|
107
|
+
"id": "WN12-00-000017",
|
|
108
|
+
"title": "System-related documentation must be backed up per organization defined frequency consistent with recovery time and recovery point objectives.",
|
|
109
|
+
"description": "Operating system backup is a critical step in maintaining data assurance and availability. \n\nInformation system and security-related documentation contains information pertaining to system configuration and security settings. \n\nBackups shall be consistent with organizational recovery time and recovery point objectives.",
|
|
110
|
+
"severity": "low"
|
|
111
|
+
},
|
|
112
|
+
{
|
|
113
|
+
"id": "WN12-00-000018",
|
|
114
|
+
"title": "Unencrypted remote access to system services must not be permitted.",
|
|
115
|
+
"description": "Unencrypted access to system services may permit an intruder to intercept user identification and passwords that are being transmitted in clear text. This could give an intruder unlimited access to the network.",
|
|
116
|
+
"severity": "high"
|
|
117
|
+
},
|
|
118
|
+
{
|
|
119
|
+
"id": "WN12-AC-000001",
|
|
120
|
+
"title": "The lockout duration must be configured to require an administrator to unlock an account.",
|
|
121
|
+
"description": "The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that an account will remain locked after the specified number of failed logon attempts. A value of 0 will require an administrator to unlock the account.",
|
|
122
|
+
"severity": "medium"
|
|
123
|
+
},
|
|
124
|
+
{
|
|
125
|
+
"id": "WN12-AC-000002",
|
|
126
|
+
"title": "The number of allowed bad logon attempts must meet minimum requirements.",
|
|
127
|
+
"description": "The account lockout feature, when enabled, prevents brute-force password attacks on the system. The higher this value is, the less effective the account lockout feature will be in protecting the local system. The number of bad logon attempts must be reasonably small to minimize the possibility of a successful password attack, while allowing for honest errors made during a normal user logon.",
|
|
128
|
+
"severity": "medium"
|
|
129
|
+
},
|
|
130
|
+
{
|
|
131
|
+
"id": "WN12-AC-000003",
|
|
132
|
+
"title": "The period of time before the bad logon counter is reset must meet minimum requirements.",
|
|
133
|
+
"description": "The account lockout feature, when enabled, prevents brute-force password attacks on the system. This parameter specifies the period of time that must pass after failed logon attempts before the counter is reset to 0. The smaller this value is, the less effective the account lockout feature will be in protecting the local system.",
|
|
134
|
+
"severity": "medium"
|
|
135
|
+
},
|
|
136
|
+
{
|
|
137
|
+
"id": "WN12-AC-000004",
|
|
138
|
+
"title": "The password uniqueness must meet minimum requirements.",
|
|
139
|
+
"description": "A system is more vulnerable to unauthorized access when system users recycle the same password several times without being required to change to a unique password on a regularly scheduled basis. This enables users to effectively negate the purpose of mandating periodic password changes.",
|
|
140
|
+
"severity": "medium"
|
|
141
|
+
},
|
|
142
|
+
{
|
|
143
|
+
"id": "WN12-AC-000005",
|
|
144
|
+
"title": "The maximum password age must meet requirements.",
|
|
145
|
+
"description": "The longer a password is in use, the greater the opportunity for someone to gain unauthorized knowledge of the passwords. Scheduled changing of passwords hinders the ability of unauthorized system users to crack passwords and gain access to a system.",
|
|
146
|
+
"severity": "medium"
|
|
147
|
+
},
|
|
148
|
+
{
|
|
149
|
+
"id": "WN12-AC-000006",
|
|
150
|
+
"title": "The minimum password age must meet requirements.",
|
|
151
|
+
"description": "Permitting passwords to be changed in immediate succession within the same day allows users to cycle passwords through their history database. This enables users to effectively negate the purpose of mandating periodic password changes.",
|
|
152
|
+
"severity": "medium"
|
|
153
|
+
},
|
|
154
|
+
{
|
|
155
|
+
"id": "WN12-AC-000007",
|
|
156
|
+
"title": "Passwords must, at a minimum, be 14 characters.",
|
|
157
|
+
"description": "Information systems not protected with strong password schemes (including passwords of minimum length) provide the opportunity for anyone to crack the password, thus gaining access to the system and compromising the device, information, or the local network.",
|
|
158
|
+
"severity": "medium"
|
|
159
|
+
},
|
|
160
|
+
{
|
|
161
|
+
"id": "WN12-AC-000008",
|
|
162
|
+
"title": "The built-in Microsoft password complexity filter must be enabled.",
|
|
163
|
+
"description": "The use of complex passwords increases their strength against guessing and brute-force attacks. This setting configures the system to verify that newly created passwords conform to the Windows password complexity policy.",
|
|
164
|
+
"severity": "low"
|
|
165
|
+
},
|
|
166
|
+
{
|
|
167
|
+
"id": "WN12-AC-000009",
|
|
168
|
+
"title": "Reversible password encryption must be disabled.",
|
|
169
|
+
"description": "Storing passwords using reversible encryption is essentially the same as storing clear-text versions of the passwords. For this reason, this policy must never be enabled.",
|
|
170
|
+
"severity": "high"
|
|
171
|
+
},
|
|
172
|
+
{
|
|
173
|
+
"id": "WN12-AC-000010-DC",
|
|
174
|
+
"title": "Kerberos user logon restrictions must be enforced.",
|
|
175
|
+
"description": "This policy setting determines whether the Kerberos Key Distribution Center (KDC) validates every request for a session ticket against the user rights policy of the target computer. The policy is enabled by default which is the most secure setting for validating access to target resources is not circumvented.",
|
|
176
|
+
"severity": "medium"
|
|
177
|
+
},
|
|
178
|
+
{
|
|
179
|
+
"id": "WN12-AC-000011-DC",
|
|
180
|
+
"title": "The Kerberos service ticket maximum lifetime must be limited to 600 minutes or less.",
|
|
181
|
+
"description": "This setting determines the maximum amount of time (in minutes) that a granted session ticket can be used to access a particular service. Session tickets are used only to authenticate new connections with servers. Ongoing operations are not interrupted if the session ticket used to authenticate the connection expires during the connection.",
|
|
182
|
+
"severity": "medium"
|
|
183
|
+
},
|
|
184
|
+
{
|
|
185
|
+
"id": "WN12-AC-000012-DC",
|
|
186
|
+
"title": "The Kerberos user ticket lifetime must be limited to 10 hours or less.",
|
|
187
|
+
"description": "In Kerberos, there are 2 types of tickets: Ticket Granting Tickets (TGTs) and Service Tickets. Kerberos tickets have a limited lifetime so the time an attacker has to implement an attack is limited. This policy controls how long TGTs can be renewed. With Kerberos, the user's initial authentication to the domain controller results in a TGT which is then used to request Service Tickets to resources. Upon startup, each computer gets a TGT before requesting a service ticket to the domain controller and any other computers it needs to access. For services that startup under a specified user account, users must always get a TGT first, then get Service Tickets to all computers and services accessed.",
|
|
188
|
+
"severity": "medium"
|
|
189
|
+
},
|
|
190
|
+
{
|
|
191
|
+
"id": "WN12-AC-000013-DC",
|
|
192
|
+
"title": "The Kerberos policy user ticket renewal maximum lifetime must be limited to 7 days or less.",
|
|
193
|
+
"description": "This setting determines the period of time (in days) during which a user's TGT may be renewed. This security configuration limits the amount of time an attacker has to crack the TGT and gain access.",
|
|
194
|
+
"severity": "medium"
|
|
195
|
+
},
|
|
196
|
+
{
|
|
197
|
+
"id": "WN12-AC-000014-DC",
|
|
198
|
+
"title": "The computer clock synchronization tolerance must be limited to 5 minutes or less.",
|
|
199
|
+
"description": "This setting determines the maximum time difference (in minutes) that Kerberos will tolerate between the time on a client's clock and the time on a server's clock while still considering the two clocks synchronous. In order to prevent replay attacks, Kerberos uses timestamps as part of its protocol definition. For timestamps to work properly, the clocks of the client and the server need to be in sync as much as possible.",
|
|
200
|
+
"severity": "medium"
|
|
201
|
+
},
|
|
202
|
+
{
|
|
203
|
+
"id": "WN12-AD-000001-DC",
|
|
204
|
+
"title": "Active Directory data files must have proper access control permissions.",
|
|
205
|
+
"description": "Improper access permissions for directory data related files could allow unauthorized users to read, modify, or delete directory data or audit trails.",
|
|
206
|
+
"severity": "high"
|
|
207
|
+
},
|
|
208
|
+
{
|
|
209
|
+
"id": "WN12-AD-000002-DC",
|
|
210
|
+
"title": "The Active Directory SYSVOL directory must have the proper access control permissions.",
|
|
211
|
+
"description": "Improper access permissions for directory data files could allow unauthorized users to read, modify, or delete directory data.\n\nThe SYSVOL directory contains public files (to the domain) such as policies and logon scripts. Data in shared subdirectories are replicated to all domain controllers in a domain.",
|
|
212
|
+
"severity": "high"
|
|
213
|
+
},
|
|
214
|
+
{
|
|
215
|
+
"id": "WN12-AD-000003-DC",
|
|
216
|
+
"title": "Active Directory Group Policy objects must have proper access control permissions.",
|
|
217
|
+
"description": "When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems relying on the directory service.\n\nFor Active Directory (AD), the Group Policy objects require special attention. In a distributed administration model (i.e., help desk), Group Policy objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for Group Policy Objects, this could allow an intruder to change the security policy applied to all domain client computers (workstations and servers).",
|
|
218
|
+
"severity": "high"
|
|
219
|
+
},
|
|
220
|
+
{
|
|
221
|
+
"id": "WN12-AD-000004-DC",
|
|
222
|
+
"title": "The Active Directory Domain Controllers Organizational Unit (OU) object must have the proper access control permissions.",
|
|
223
|
+
"description": "When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service.\n\nFor Active Directory (AD), the Organizational Unit (OU) objects require special attention. In a distributed administration model (i.e., help desk), OU objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for OU objects, it could allow an intruder to add or delete users in the OU. This could result in unauthorized access to data or a Denial of Service to authorized users.",
|
|
224
|
+
"severity": "high"
|
|
225
|
+
},
|
|
226
|
+
{
|
|
227
|
+
"id": "WN12-AD-000005-DC",
|
|
228
|
+
"title": "Domain created Active Directory Organizational Unit (OU) objects must have proper access control permissions.",
|
|
229
|
+
"description": "When directory service database objects do not have appropriate access control permissions, it may be possible for malicious users to create, read, update, or delete the objects and degrade or destroy the integrity of the data. When the directory service is used for identification, authentication, or authorization functions, a compromise of the database objects could lead to a compromise of all systems that rely on the directory service.\n\nFor Active Directory (AD), the Organizational Unit (OU) objects require special attention. In a distributed administration model (i.e., help desk), OU objects are more likely to have access permissions changed from the secure defaults. If inappropriate access permissions are defined for OU objects, it could allow an intruder to add or delete users in the OU. This could result in unauthorized access to data or a Denial of Service to authorized users.",
|
|
230
|
+
"severity": "high"
|
|
231
|
+
},
|
|
232
|
+
{
|
|
233
|
+
"id": "WN12-AD-000006-DC",
|
|
234
|
+
"title": "Data files owned by users must be on a different logical partition from the directory server data files.",
|
|
235
|
+
"description": "When directory service data files, especially for directories used for identification, authentication, or authorization, reside on the same logical partition as user-owned files, the directory service data may be more vulnerable to unauthorized access or other availability compromises. Directory service and user-owned data files sharing a partition may be configured with less restrictive permissions in order to allow access to the user data. \n\nThe directory service may be vulnerable to a denial of service attack when user-owned files on a common partition are expanded to an extent preventing the directory service from acquiring more space for directory or audit data.",
|
|
236
|
+
"severity": "medium"
|
|
237
|
+
},
|
|
238
|
+
{
|
|
239
|
+
"id": "WN12-AD-000007-DC",
|
|
240
|
+
"title": "Time synchronization must be enabled on the domain controller.",
|
|
241
|
+
"description": "When a directory service using multi-master replication (such as AD) executes on computers that do not have synchronized time, directory data may be corrupted or updated invalidly.\n\nThe lack of synchronized time could lead to audit log data that is misleading, inconclusive, or unusable. In cases of intrusion this may invalidate the audit data as a source of forensic evidence in an incident investigation.\n\nIn AD, the lack of synchronized time could prevent clients from logging on or accessing server resources as a result of Kerberos requirements related to time variance.",
|
|
242
|
+
"severity": "medium"
|
|
243
|
+
},
|
|
244
|
+
{
|
|
245
|
+
"id": "WN12-AD-000008-DC",
|
|
246
|
+
"title": "The time synchronization tool must be configured to enable logging of time source switching.",
|
|
247
|
+
"description": "When a time synchronization tool executes, it may switch between time sources according to network or server contention. If switches between time sources are not logged, it may be difficult or impossible to detect malicious activity or availability problems.",
|
|
248
|
+
"severity": "low"
|
|
249
|
+
},
|
|
250
|
+
{
|
|
251
|
+
"id": "WN12-AD-000009-DC",
|
|
252
|
+
"title": "The directory server supporting (directly or indirectly) system access or resource authorization must run on a machine dedicated to that function.",
|
|
253
|
+
"description": "Executing application servers on the same host machine with a directory server may substantially weaken the security of the directory server. Web or database server applications usually require the addition of many programs and accounts increasing the attack surface of the computer. \n\nSome applications require the addition of privileged accounts providing potential sources of compromise. Some applications (such as MS Exchange) may require the use of network ports or services conflicting with the directory server. In this case, non-standard ports might be selected and this could interfere with intrusion detection or prevention services.",
|
|
254
|
+
"severity": "medium"
|
|
255
|
+
},
|
|
256
|
+
{
|
|
257
|
+
"id": "WN12-AD-000010-DC",
|
|
258
|
+
"title": "Windows services that are critical for directory server operation must be configured for automatic startup.",
|
|
259
|
+
"description": "Active Directory (AD) is dependent on several Windows services. If one or more of these services is not configured for automatic startup, AD functions may be partially or completely unavailable until the services are manually started. This could result in a failure to replicate data or to support client authentication and authorization requests.",
|
|
260
|
+
"severity": "medium"
|
|
261
|
+
},
|
|
262
|
+
{
|
|
263
|
+
"id": "WN12-AD-000011-DC",
|
|
264
|
+
"title": "Separate, NSA-approved (Type 1) cryptography must be used to protect the directory data-in-transit for directory service implementations at a classified confidentiality level when replication data traverses a network cleared to a lower level than the data.",
|
|
265
|
+
"description": "Commercial-grade encryption does not provide adequate protection when the classification level of directory data in transit is higher than the level of the network or when sources and methods intelligence (SAMI) data is included.",
|
|
266
|
+
"severity": "medium"
|
|
267
|
+
},
|
|
268
|
+
{
|
|
269
|
+
"id": "WN12-AD-000012-DC",
|
|
270
|
+
"title": "Anonymous access to the root DSE of a non-public directory must be disabled.",
|
|
271
|
+
"description": "Allowing anonymous access to the root DSE data on a directory server provides potential attackers with a number of details about the configuration and data contents of a directory. For example, the namingContexts attribute indicates the directory space contained in the directory; the supportedLDAPVersion attribute indicates which versions of the LDAP protocol the server supports; and the supportedSASLMechanisms attribute indicates the names of supported authentication mechanisms. An attacker with this information may be able to select more precisely targeted attack tools or higher value targets.",
|
|
272
|
+
"severity": "low"
|
|
273
|
+
},
|
|
274
|
+
{
|
|
275
|
+
"id": "WN12-AD-000013-DC",
|
|
276
|
+
"title": "Directory data (outside the root DSE) of a non-public directory must be configured to prevent anonymous access.",
|
|
277
|
+
"description": "To the extent that anonymous access to directory data (outside the root DSE) is permitted, read access control of the data is effectively disabled. If other means of controlling access (such as, network restrictions) are compromised, there may be nothing else to protect the confidentiality of sensitive directory data.",
|
|
278
|
+
"severity": "high"
|
|
279
|
+
},
|
|
280
|
+
{
|
|
281
|
+
"id": "WN12-AD-000014-DC",
|
|
282
|
+
"title": "The directory service must be configured to terminate LDAP-based network connections to the directory server after five (5) minutes of inactivity.",
|
|
283
|
+
"description": "The failure to terminate inactive network connections increases the risk of a successful attack on the directory server. The longer an established session is in progress, the more time an attacker has to hijack the session, implement a means to passively intercept data, or compromise any protections on client access. For example, if an attacker gains control of a client computer, an existing (already authenticated) session with the directory server could allow access to the directory. The lack of confidentiality protection in LDAP-based sessions increases exposure to this vulnerability.",
|
|
284
|
+
"severity": "low"
|
|
285
|
+
},
|
|
286
|
+
{
|
|
287
|
+
"id": "WN12-AU-000001",
|
|
288
|
+
"title": "The system must be configured to audit Account Logon - Credential Validation successes.",
|
|
289
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nCredential validation records events related to validation tests on credentials for a user account logon.",
|
|
290
|
+
"severity": "medium"
|
|
291
|
+
},
|
|
292
|
+
{
|
|
293
|
+
"id": "WN12-AU-000002",
|
|
294
|
+
"title": "The system must be configured to audit Account Logon - Credential Validation failures.",
|
|
295
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nCredential validation records events related to validation tests on credentials for a user account logon.",
|
|
296
|
+
"severity": "medium"
|
|
297
|
+
},
|
|
298
|
+
{
|
|
299
|
+
"id": "WN12-AU-000011",
|
|
300
|
+
"title": "The system must be configured to audit Account Logon - Computer Account Management successes.",
|
|
301
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nComputer Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling computer accounts.",
|
|
302
|
+
"severity": "medium"
|
|
303
|
+
},
|
|
304
|
+
{
|
|
305
|
+
"id": "WN12-AU-000012",
|
|
306
|
+
"title": "The system must be configured to audit Account Logon - Computer Account Management failures.",
|
|
307
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nComputer Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling computer accounts.",
|
|
308
|
+
"severity": "medium"
|
|
309
|
+
},
|
|
310
|
+
{
|
|
311
|
+
"id": "WN12-AU-000015",
|
|
312
|
+
"title": "The system must be configured to audit Account Management - Other Account Management Events successes.",
|
|
313
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nOther Account Management Events records events such as the access of a password hash or the Password Policy Checking API being called.",
|
|
314
|
+
"severity": "medium"
|
|
315
|
+
},
|
|
316
|
+
{
|
|
317
|
+
"id": "WN12-AU-000016",
|
|
318
|
+
"title": "The system must be configured to audit Account Management - Other Account Management Events failures.",
|
|
319
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nOther Account Management Events records events such as the access of a password hash or the Password Policy Checking API being called.",
|
|
320
|
+
"severity": "medium"
|
|
321
|
+
},
|
|
322
|
+
{
|
|
323
|
+
"id": "WN12-AU-000017",
|
|
324
|
+
"title": "The system must be configured to audit Account Management - Security Group Management successes.",
|
|
325
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSecurity Group Management records events such as creating, deleting, or changing security groups, including changes in group members.",
|
|
326
|
+
"severity": "medium"
|
|
327
|
+
},
|
|
328
|
+
{
|
|
329
|
+
"id": "WN12-AU-000018",
|
|
330
|
+
"title": "The system must be configured to audit Account Management - Security Group Management failures.",
|
|
331
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSecurity Group Management records events such as creating, deleting, or changing security groups, including changes in group members.",
|
|
332
|
+
"severity": "medium"
|
|
333
|
+
},
|
|
334
|
+
{
|
|
335
|
+
"id": "WN12-AU-000019",
|
|
336
|
+
"title": "The system must be configured to audit Account Management - User Account Management successes.",
|
|
337
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nUser Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts.",
|
|
338
|
+
"severity": "medium"
|
|
339
|
+
},
|
|
340
|
+
{
|
|
341
|
+
"id": "WN12-AU-000020",
|
|
342
|
+
"title": "The system must be configured to audit Account Management - User Account Management failures.",
|
|
343
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nUser Account Management records events such as creating, changing, deleting, renaming, disabling, or enabling user accounts.",
|
|
344
|
+
"severity": "medium"
|
|
345
|
+
},
|
|
346
|
+
{
|
|
347
|
+
"id": "WN12-AU-000023",
|
|
348
|
+
"title": "The system must be configured to audit Detailed Tracking - Process Creation successes.",
|
|
349
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nProcess Creation records events related to the creation of a process and the source.",
|
|
350
|
+
"severity": "medium"
|
|
351
|
+
},
|
|
352
|
+
{
|
|
353
|
+
"id": "WN12-AU-000031-DC",
|
|
354
|
+
"title": "The system must be configured to audit DS Access - Directory Service Access successes.\n",
|
|
355
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detecting attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit directory service access records events related to users accessing an Active Directory object.",
|
|
356
|
+
"severity": "medium"
|
|
357
|
+
},
|
|
358
|
+
{
|
|
359
|
+
"id": "WN12-AU-000032-DC",
|
|
360
|
+
"title": "The system must be configured to audit DS Access - Directory Service Access failures.",
|
|
361
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detecting attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit directory service access records events related to users accessing an Active Directory object.",
|
|
362
|
+
"severity": "medium"
|
|
363
|
+
},
|
|
364
|
+
{
|
|
365
|
+
"id": "WN12-AU-000035-DC",
|
|
366
|
+
"title": "The system must be configured to audit DS Access - Directory Service Changes successes.",
|
|
367
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detecting attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit directory service changes records events related to changes made to objects in Active Directory Domain Services.",
|
|
368
|
+
"severity": "medium"
|
|
369
|
+
},
|
|
370
|
+
{
|
|
371
|
+
"id": "WN12-AU-000036-DC",
|
|
372
|
+
"title": "The system must be configured to audit DS Access - Directory Service Changes failures.",
|
|
373
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detecting attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit directory service changes records events related to changes made to objects in Active Directory Domain Services.",
|
|
374
|
+
"severity": "medium"
|
|
375
|
+
},
|
|
376
|
+
{
|
|
377
|
+
"id": "WN12-AU-000045",
|
|
378
|
+
"title": "The system must be configured to audit Logon/Logoff - Logoff successes.",
|
|
379
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nLogoff records user logoffs. If this is an interactive logoff, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.",
|
|
380
|
+
"severity": "medium"
|
|
381
|
+
},
|
|
382
|
+
{
|
|
383
|
+
"id": "WN12-AU-000047",
|
|
384
|
+
"title": "The system must be configured to audit Logon/Logoff - Logon successes.",
|
|
385
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nLogon records user logons. If this is an interactive logon, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.",
|
|
386
|
+
"severity": "medium"
|
|
387
|
+
},
|
|
388
|
+
{
|
|
389
|
+
"id": "WN12-AU-000048",
|
|
390
|
+
"title": "The system must be configured to audit Logon/Logoff - Logon failures.",
|
|
391
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nLogon records user logons. If this is an interactive logon, it is recorded on the local system. If it is to a network share, it is recorded on the system accessed.",
|
|
392
|
+
"severity": "medium"
|
|
393
|
+
},
|
|
394
|
+
{
|
|
395
|
+
"id": "WN12-AU-000053",
|
|
396
|
+
"title": "The system must be configured to audit Logon/Logoff - Special Logon successes.",
|
|
397
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSpecial Logon records special logons which have administrative privileges and can be used to elevate processes.",
|
|
398
|
+
"severity": "medium"
|
|
399
|
+
},
|
|
400
|
+
{
|
|
401
|
+
"id": "WN12-AU-000059",
|
|
402
|
+
"title": "The system must be configured to audit Object Access - Central Access Policy Staging successes.",
|
|
403
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nCentral Access Policy Staging auditing under Object Access is used to enable the recording of events related to differences in permissions between central access policies and proposed policies.",
|
|
404
|
+
"severity": "medium"
|
|
405
|
+
},
|
|
406
|
+
{
|
|
407
|
+
"id": "WN12-AU-000060",
|
|
408
|
+
"title": "The system must be configured to audit Object Access - Central Access Policy Staging failures.",
|
|
409
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nCentral Access Policy Staging auditing under Object Access is used to enable the recording of events related to differences in permissions between central access policies and proposed policies.",
|
|
410
|
+
"severity": "medium"
|
|
411
|
+
},
|
|
412
|
+
{
|
|
413
|
+
"id": "WN12-AU-000068",
|
|
414
|
+
"title": "The system must be configured to audit Object Access - File System failures.",
|
|
415
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nFile System auditing under Object Access is used to enable the recording of events related to the access and changing of files and directories. Auditing must also be enabled on the specific file system objects to be audited.",
|
|
416
|
+
"severity": "medium"
|
|
417
|
+
},
|
|
418
|
+
{
|
|
419
|
+
"id": "WN12-AU-000074",
|
|
420
|
+
"title": "The system must be configured to audit Object Access - Handle Manipulation failures.",
|
|
421
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nHandle Manipulation auditing under Object Access is needed to correctly enable the recording of events related to the access and changing of files and directories. Auditing must also be enabled on the specific file system objects to be audited.",
|
|
422
|
+
"severity": "medium"
|
|
423
|
+
},
|
|
424
|
+
{
|
|
425
|
+
"id": "WN12-AU-000080",
|
|
426
|
+
"title": "The system must be configured to audit Object Access - Registry failures.",
|
|
427
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nRegistry auditing under Object Access is used to enable the recording of events related to the access and changing of the registry. Auditing must also be enabled on the specific registry objects to be audited.",
|
|
428
|
+
"severity": "medium"
|
|
429
|
+
},
|
|
430
|
+
{
|
|
431
|
+
"id": "WN12-AU-000081",
|
|
432
|
+
"title": "The system must be configured to audit Object Access - Removable Storage successes.",
|
|
433
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nRemovable Storage auditing under Object Access records events related to access attempts on file system objects on removable storage devices.",
|
|
434
|
+
"severity": "medium"
|
|
435
|
+
},
|
|
436
|
+
{
|
|
437
|
+
"id": "WN12-AU-000082",
|
|
438
|
+
"title": "The system must be configured to audit Object Access - Removable Storage failures.",
|
|
439
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nRemovable Storage auditing under Object Access records events related to access attempts on file system objects on removable storage devices.",
|
|
440
|
+
"severity": "medium"
|
|
441
|
+
},
|
|
442
|
+
{
|
|
443
|
+
"id": "WN12-AU-000085",
|
|
444
|
+
"title": "The system must be configured to audit Policy Change - Audit Policy Change successes.",
|
|
445
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit Policy Change records events related to changes in audit policy.",
|
|
446
|
+
"severity": "medium"
|
|
447
|
+
},
|
|
448
|
+
{
|
|
449
|
+
"id": "WN12-AU-000086",
|
|
450
|
+
"title": "The system must be configured to audit Policy Change - Audit Policy Change failures.",
|
|
451
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAudit Policy Change records events related to changes in audit policy.",
|
|
452
|
+
"severity": "medium"
|
|
453
|
+
},
|
|
454
|
+
{
|
|
455
|
+
"id": "WN12-AU-000087",
|
|
456
|
+
"title": "The system must be configured to audit Policy Change - Authentication Policy Change successes.",
|
|
457
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nAuthentication Policy Change records events related to changes in authentication policy, including Kerberos policy and Trust changes.",
|
|
458
|
+
"severity": "medium"
|
|
459
|
+
},
|
|
460
|
+
{
|
|
461
|
+
"id": "WN12-AU-000101",
|
|
462
|
+
"title": "The system must be configured to audit Privilege Use - Sensitive Privilege Use successes.",
|
|
463
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSensitive Privilege Use records events related to use of sensitive privileges, such as \"Act as part of the operating system\" or \"Debug programs\".",
|
|
464
|
+
"severity": "medium"
|
|
465
|
+
},
|
|
466
|
+
{
|
|
467
|
+
"id": "WN12-AU-000102",
|
|
468
|
+
"title": "The system must be configured to audit Privilege Use - Sensitive Privilege Use failures.",
|
|
469
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSensitive Privilege Use records events related to use of sensitive privileges, such as \"Act as part of the operating system\" or \"Debug programs\".",
|
|
470
|
+
"severity": "medium"
|
|
471
|
+
},
|
|
472
|
+
{
|
|
473
|
+
"id": "WN12-AU-000103",
|
|
474
|
+
"title": "The system must be configured to audit System - IPSec Driver successes.",
|
|
475
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nIPSec Driver records events related to the IPSec Driver such as dropped packets.",
|
|
476
|
+
"severity": "medium"
|
|
477
|
+
},
|
|
478
|
+
{
|
|
479
|
+
"id": "WN12-AU-000104",
|
|
480
|
+
"title": "The system must be configured to audit System - IPSec Driver failures.",
|
|
481
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nIPSec Driver records events related to the IPSec Driver such as dropped packets.",
|
|
482
|
+
"severity": "medium"
|
|
483
|
+
},
|
|
484
|
+
{
|
|
485
|
+
"id": "WN12-AU-000107",
|
|
486
|
+
"title": "The system must be configured to audit System - Security State Change successes.",
|
|
487
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSecurity State Change records events related to changes in the security state, such as startup and shutdown of the system.",
|
|
488
|
+
"severity": "medium"
|
|
489
|
+
},
|
|
490
|
+
{
|
|
491
|
+
"id": "WN12-AU-000108",
|
|
492
|
+
"title": "The system must be configured to audit System - Security State Change failures.",
|
|
493
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSecurity State Change records events related to changes in the security state, such as startup and shutdown of the system.",
|
|
494
|
+
"severity": "medium"
|
|
495
|
+
},
|
|
496
|
+
{
|
|
497
|
+
"id": "WN12-AU-000109",
|
|
498
|
+
"title": "The system must be configured to audit System - Security System Extension successes.",
|
|
499
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSecurity System Extension records events related to extension code being loaded by the security subsystem.",
|
|
500
|
+
"severity": "medium"
|
|
501
|
+
},
|
|
502
|
+
{
|
|
503
|
+
"id": "WN12-AU-000110",
|
|
504
|
+
"title": "The system must be configured to audit System - Security System Extension failures.",
|
|
505
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSecurity System Extension records events related to extension code being loaded by the security subsystem.",
|
|
506
|
+
"severity": "medium"
|
|
507
|
+
},
|
|
508
|
+
{
|
|
509
|
+
"id": "WN12-AU-000111",
|
|
510
|
+
"title": "The system must be configured to audit System - System Integrity successes.",
|
|
511
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSystem Integrity records events related to violations of integrity to the security subsystem.",
|
|
512
|
+
"severity": "medium"
|
|
513
|
+
},
|
|
514
|
+
{
|
|
515
|
+
"id": "WN12-AU-000112",
|
|
516
|
+
"title": "The system must be configured to audit System - System Integrity failures.",
|
|
517
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\n\nSystem Integrity records events related to violations of integrity to the security subsystem.",
|
|
518
|
+
"severity": "medium"
|
|
519
|
+
},
|
|
520
|
+
{
|
|
521
|
+
"id": "WN12-AU-000114",
|
|
522
|
+
"title": "Global object access auditing of the file system must be configured to record failures.",
|
|
523
|
+
"description": "Improper modification of system files can have a significant impact on the security configuration of a system, as well as potentially rendering a system inoperable. Failed access attempts may indicate an attack on a system. Auditing for failed access attempts provides an indicator of such attempts and a method of determining responsible parties.",
|
|
524
|
+
"severity": "medium"
|
|
525
|
+
},
|
|
526
|
+
{
|
|
527
|
+
"id": "WN12-AU-000116",
|
|
528
|
+
"title": "Global object access auditing of the registry must be configured to record failures.",
|
|
529
|
+
"description": "Improper modification of the registry can have a significant impact on the security configuration of a system, as well as potentially rendering a system inoperable. Failed access attempts may indicate an attack on a system. Auditing for failed access attempts provides an indicator of such attempts and a method of determining responsible parties.",
|
|
530
|
+
"severity": "medium"
|
|
531
|
+
},
|
|
532
|
+
{
|
|
533
|
+
"id": "WN12-AU-000200",
|
|
534
|
+
"title": "Audit data must be reviewed on a regular basis.",
|
|
535
|
+
"description": "To be of value, audit logs from critical systems must be reviewed on a regular basis. Critical systems should be reviewed on a daily basis to identify security breaches and potential weaknesses in the security structure. This can be done with the use of monitoring software or other utilities for this purpose.",
|
|
536
|
+
"severity": "medium"
|
|
537
|
+
},
|
|
538
|
+
{
|
|
539
|
+
"id": "WN12-AU-000201",
|
|
540
|
+
"title": "Audit data must be retained for at least one year.",
|
|
541
|
+
"description": "Audit records are essential for investigating system activity after the fact. Retention periods for audit data are determined based on the sensitivity of the data handled by the system.",
|
|
542
|
+
"severity": "medium"
|
|
543
|
+
},
|
|
544
|
+
{
|
|
545
|
+
"id": "WN12-AU-000202",
|
|
546
|
+
"title": "Audit data of systems containing sources and methods intelligence (SAMI) must be retained for at least five years.",
|
|
547
|
+
"description": "Audit records are essential for investigating system activity after the fact. Retention periods for audit data are determined based on the sensitivity of the data handled by the system.",
|
|
548
|
+
"severity": "medium"
|
|
549
|
+
},
|
|
550
|
+
{
|
|
551
|
+
"id": "WN12-AU-000203",
|
|
552
|
+
"title": "Audit records must be backed up on an organization defined frequency onto a different system or media than the system being audited.",
|
|
553
|
+
"description": "Protection of log data includes assuring the log data is not accidentally lost or deleted. Backing up audit records to a different system or onto separate media than the system being audited on an organization defined frequency helps to assure in the event of a catastrophic system failure, the audit records will be retained.",
|
|
554
|
+
"severity": "medium"
|
|
555
|
+
},
|
|
556
|
+
{
|
|
557
|
+
"id": "WN12-AU-000204",
|
|
558
|
+
"title": "Permissions for the Application event log must prevent access by nonprivileged accounts.",
|
|
559
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The Application event log may be susceptible to tampering if proper permissions are not applied.",
|
|
560
|
+
"severity": "medium"
|
|
561
|
+
},
|
|
562
|
+
{
|
|
563
|
+
"id": "WN12-AU-000205",
|
|
564
|
+
"title": "Permissions for the Security event log must prevent access by nonprivileged accounts.",
|
|
565
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The Security event log may disclose sensitive information or be susceptible to tampering if proper permissions are not applied.",
|
|
566
|
+
"severity": "medium"
|
|
567
|
+
},
|
|
568
|
+
{
|
|
569
|
+
"id": "WN12-AU-000206",
|
|
570
|
+
"title": "Permissions for the System event log must prevent access by nonprivileged accounts.",
|
|
571
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. The System event log may be susceptible to tampering if proper permissions are not applied.",
|
|
572
|
+
"severity": "medium"
|
|
573
|
+
},
|
|
574
|
+
{
|
|
575
|
+
"id": "WN12-AU-000207-DC",
|
|
576
|
+
"title": "Active Directory Group Policy objects must be configured with proper audit settings.",
|
|
577
|
+
"description": "When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. \n\nFor Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes Group Policy objects. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.",
|
|
578
|
+
"severity": "medium"
|
|
579
|
+
},
|
|
580
|
+
{
|
|
581
|
+
"id": "WN12-AU-000208-DC",
|
|
582
|
+
"title": "The Active Directory Domain object must be configured with proper audit settings.",
|
|
583
|
+
"description": "When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. \n\nFor Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.",
|
|
584
|
+
"severity": "medium"
|
|
585
|
+
},
|
|
586
|
+
{
|
|
587
|
+
"id": "WN12-AU-000209-DC",
|
|
588
|
+
"title": "The Active Directory Infrastructure object must be configured with proper audit settings.",
|
|
589
|
+
"description": "When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. \n\nFor Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Infrastructure object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.",
|
|
590
|
+
"severity": "medium"
|
|
591
|
+
},
|
|
592
|
+
{
|
|
593
|
+
"id": "WN12-AU-000210-DC",
|
|
594
|
+
"title": "The Active Directory Domain Controllers Organizational Unit (OU) object must be configured with proper audit settings.",
|
|
595
|
+
"description": "When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. \n\nFor Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the Domain Controller OU object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.",
|
|
596
|
+
"severity": "medium"
|
|
597
|
+
},
|
|
598
|
+
{
|
|
599
|
+
"id": "WN12-AU-000211-DC",
|
|
600
|
+
"title": "The Active Directory AdminSDHolder object must be configured with proper audit settings.",
|
|
601
|
+
"description": "When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. \n\nFor Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the AdminSDHolder object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.",
|
|
602
|
+
"severity": "medium"
|
|
603
|
+
},
|
|
604
|
+
{
|
|
605
|
+
"id": "WN12-AU-000212-DC",
|
|
606
|
+
"title": "The Active Directory RID Manager$ object must be configured with proper audit settings.",
|
|
607
|
+
"description": "When inappropriate audit settings are configured for directory service database objects, it may be possible for a user or process to update the data without generating any tracking data. The impact of missing audit data is related to the type of object. A failure to capture audit data for objects used by identification, authentication, or authorization functions could degrade or eliminate the ability to track changes to access policy for systems or data. \n\nFor Active Directory (AD), there are a number of critical object types in the domain naming context of the AD database for which auditing is essential. This includes the RID Manager$ object. Because changes to these objects can significantly impact access controls or the availability of systems, the absence of auditing data makes it impossible to identify the source of changes that impact the confidentiality, integrity, and availability of data and systems throughout an AD domain. The lack of proper auditing can result in insufficient forensic evidence needed to investigate an incident and prosecute the intruder.",
|
|
608
|
+
"severity": "medium"
|
|
609
|
+
},
|
|
610
|
+
{
|
|
611
|
+
"id": "WN12-CC-000001",
|
|
612
|
+
"title": "The Mapper I/O network protocol (LLTDIO) driver must be disabled.",
|
|
613
|
+
"description": "The Mapper I/O network protocol (LLTDIO) driver allows the discovery of the connected network and allows various options to be enabled. Disabling this helps protect the system from potentially discovering and connecting to unauthorized devices.",
|
|
614
|
+
"severity": "medium"
|
|
615
|
+
},
|
|
616
|
+
{
|
|
617
|
+
"id": "WN12-CC-000002",
|
|
618
|
+
"title": "The Responder network protocol driver must be disabled.",
|
|
619
|
+
"description": "The Responder network protocol driver allows a computer to be discovered and located on a network. Disabling this helps protect the system from potentially being discovered and connected to by unauthorized devices.",
|
|
620
|
+
"severity": "medium"
|
|
621
|
+
},
|
|
622
|
+
{
|
|
623
|
+
"id": "WN12-CC-000003",
|
|
624
|
+
"title": "Windows Peer-to-Peer Networking Services must be turned off.",
|
|
625
|
+
"description": "Peer-to-Peer applications can allow unauthorized access to a system and exposure of sensitive data. This setting will turn off the Microsoft Peer-to-Peer Networking Service.",
|
|
626
|
+
"severity": "medium"
|
|
627
|
+
},
|
|
628
|
+
{
|
|
629
|
+
"id": "WN12-CC-000004",
|
|
630
|
+
"title": "Network Bridges must be prohibited in Windows.",
|
|
631
|
+
"description": "A Network Bridge can connect two or more network segments, allowing unauthorized access or exposure of sensitive data. This setting prevents a Network Bridge from being installed and configured.",
|
|
632
|
+
"severity": "medium"
|
|
633
|
+
},
|
|
634
|
+
{
|
|
635
|
+
"id": "WN12-CC-000005",
|
|
636
|
+
"title": "Domain users must be required to elevate when setting a network's location.",
|
|
637
|
+
"description": "Selecting an incorrect network location may allow greater exposure of a system. Elevation is required by default on nondomain systems to change network location. This setting configures elevation to also be required on domain-joined systems.",
|
|
638
|
+
"severity": "low"
|
|
639
|
+
},
|
|
640
|
+
{
|
|
641
|
+
"id": "WN12-CC-000006",
|
|
642
|
+
"title": "All Direct Access traffic must be routed through the internal network.",
|
|
643
|
+
"description": "Routing all Direct Access traffic through the internal network allows monitoring and prevents split tunneling.",
|
|
644
|
+
"severity": "low"
|
|
645
|
+
},
|
|
646
|
+
{
|
|
647
|
+
"id": "WN12-CC-000007",
|
|
648
|
+
"title": "The 6to4 IPv6 transition technology must be disabled.",
|
|
649
|
+
"description": "IPv6 transition technologies, which tunnel packets through other protocols, do not provide visibility.",
|
|
650
|
+
"severity": "medium"
|
|
651
|
+
},
|
|
652
|
+
{
|
|
653
|
+
"id": "WN12-CC-000008",
|
|
654
|
+
"title": "The IP-HTTPS IPv6 transition technology must be disabled.",
|
|
655
|
+
"description": "IPv6 transition technologies, which tunnel packets through other protocols, do not provide visibility.",
|
|
656
|
+
"severity": "medium"
|
|
657
|
+
},
|
|
658
|
+
{
|
|
659
|
+
"id": "WN12-CC-000009",
|
|
660
|
+
"title": "The ISATAP IPv6 transition technology must be disabled.",
|
|
661
|
+
"description": "IPv6 transition technologies, which tunnel packets through other protocols, do not provide visibility.",
|
|
662
|
+
"severity": "medium"
|
|
663
|
+
},
|
|
664
|
+
{
|
|
665
|
+
"id": "WN12-CC-000010",
|
|
666
|
+
"title": "The Teredo IPv6 transition technology must be disabled.",
|
|
667
|
+
"description": "IPv6 transition technologies, which tunnel packets through other protocols, do not provide visibility.",
|
|
668
|
+
"severity": "medium"
|
|
669
|
+
},
|
|
670
|
+
{
|
|
671
|
+
"id": "WN12-CC-000011",
|
|
672
|
+
"title": "IP stateless autoconfiguration limits state must be enabled.",
|
|
673
|
+
"description": "IP stateless autoconfiguration could configure routes that circumvent preferred routes if not limited.",
|
|
674
|
+
"severity": "low"
|
|
675
|
+
},
|
|
676
|
+
{
|
|
677
|
+
"id": "WN12-CC-000012",
|
|
678
|
+
"title": "The configuration of wireless devices using Windows Connect Now must be disabled.",
|
|
679
|
+
"description": "Windows Connect Now allows the discovery and configuration of devices over wireless. Wireless devices must be managed. If a rogue device is connected to a system, there is potential for sensitive information to be compromised.",
|
|
680
|
+
"severity": "medium"
|
|
681
|
+
},
|
|
682
|
+
{
|
|
683
|
+
"id": "WN12-CC-000013",
|
|
684
|
+
"title": "The Windows Connect Now wizards must be disabled.",
|
|
685
|
+
"description": "Windows Connect Now provides wizards for tasks such as \"Set up a wireless router or access point\" and must not be available to users. Functions such as these may allow unauthorized connections to a system and the potential for sensitive information to be compromised.",
|
|
686
|
+
"severity": "medium"
|
|
687
|
+
},
|
|
688
|
+
{
|
|
689
|
+
"id": "WN12-CC-000016",
|
|
690
|
+
"title": "Windows Update must be prevented from searching for point and print drivers.",
|
|
691
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting will prevent Windows from searching Windows Update for point and print drivers. Only the local driver store and server driver cache will be searched.",
|
|
692
|
+
"severity": "low"
|
|
693
|
+
},
|
|
694
|
+
{
|
|
695
|
+
"id": "WN12-CC-000018",
|
|
696
|
+
"title": "Optional component installation and component repair must be prevented from using Windows Update.",
|
|
697
|
+
"description": "Uncontrolled system updates can introduce issues to a system. Obtaining update components from an outside source may also potentially provide sensitive information outside of the enterprise. Optional component installation or repair must be obtained from an internal source.",
|
|
698
|
+
"severity": "low"
|
|
699
|
+
},
|
|
700
|
+
{
|
|
701
|
+
"id": "WN12-CC-000019",
|
|
702
|
+
"title": "Remote access to the Plug and Play interface must be disabled for device installation.",
|
|
703
|
+
"description": "Remote access to the Plug and Play interface could potentially allow connections by unauthorized devices. This setting configures remote access to the Plug and Play interface and must be disabled.",
|
|
704
|
+
"severity": "medium"
|
|
705
|
+
},
|
|
706
|
+
{
|
|
707
|
+
"id": "WN12-CC-000020",
|
|
708
|
+
"title": "An error report must not be sent when a generic device driver is installed.",
|
|
709
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents an error report from being sent when a generic device driver is installed.",
|
|
710
|
+
"severity": "low"
|
|
711
|
+
},
|
|
712
|
+
{
|
|
713
|
+
"id": "WN12-CC-000021",
|
|
714
|
+
"title": "A system restore point must be created when a new device driver is installed.",
|
|
715
|
+
"description": "A system restore point allows a rollback if an issue is encountered when a new device driver is installed.",
|
|
716
|
+
"severity": "low"
|
|
717
|
+
},
|
|
718
|
+
{
|
|
719
|
+
"id": "WN12-CC-000022",
|
|
720
|
+
"title": "Device metadata retrieval from the Internet must be prevented.",
|
|
721
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting will prevent Windows from retrieving device metadata from the Internet.",
|
|
722
|
+
"severity": "low"
|
|
723
|
+
},
|
|
724
|
+
{
|
|
725
|
+
"id": "WN12-CC-000023",
|
|
726
|
+
"title": "Windows must be prevented from sending an error report when a device driver requests additional software during installation.",
|
|
727
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting will prevent Windows from sending an error report to Microsoft when a device driver requests additional software during installation.",
|
|
728
|
+
"severity": "low"
|
|
729
|
+
},
|
|
730
|
+
{
|
|
731
|
+
"id": "WN12-CC-000024",
|
|
732
|
+
"title": "Device driver searches using Windows Update must be prevented.",
|
|
733
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting will prevent the system from searching Windows Update for device drivers.",
|
|
734
|
+
"severity": "low"
|
|
735
|
+
},
|
|
736
|
+
{
|
|
737
|
+
"id": "WN12-CC-000025",
|
|
738
|
+
"title": "Device driver updates must only search managed servers, not Windows Update.",
|
|
739
|
+
"description": "Uncontrolled system updates can introduce issues to a system. Obtaining update components from an outside source may also potentially provide sensitive information outside of the enterprise. Device driver updates must be obtained from an internal source.",
|
|
740
|
+
"severity": "low"
|
|
741
|
+
},
|
|
742
|
+
{
|
|
743
|
+
"id": "WN12-CC-000026",
|
|
744
|
+
"title": "Users must not be prompted to search Windows Update for device drivers.",
|
|
745
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents users from being prompted to search Windows Update for device drivers.",
|
|
746
|
+
"severity": "low"
|
|
747
|
+
},
|
|
748
|
+
{
|
|
749
|
+
"id": "WN12-CC-000027",
|
|
750
|
+
"title": "Early Launch Antimalware, Boot-Start Driver Initialization Policy must be enabled and configured to only Good and Unknown.",
|
|
751
|
+
"description": "Compromised boot drivers can introduce malware prior to some protection mechanisms that load after initialization. The Early Launch Antimalware driver can limit allowed drivers based on classifications determined by the malware protection application. At a minimum, drivers determined to be bad must not be allowed.",
|
|
752
|
+
"severity": "medium"
|
|
753
|
+
},
|
|
754
|
+
{
|
|
755
|
+
"id": "WN12-CC-000028",
|
|
756
|
+
"title": "Group Policy objects must be reprocessed even if they have not changed.",
|
|
757
|
+
"description": "Enabling this setting and then selecting the \"Process even if the Group Policy objects have not changed\" option ensures that the policies will be reprocessed even if none have been changed. This way, any unauthorized changes are forced to match the domain-based group policy settings again.",
|
|
758
|
+
"severity": "medium"
|
|
759
|
+
},
|
|
760
|
+
{
|
|
761
|
+
"id": "WN12-CC-000029",
|
|
762
|
+
"title": "Group Policies must be refreshed in the background if the user is logged on.",
|
|
763
|
+
"description": "If this setting is enabled, then Group Policy settings are not refreshed while a user is currently logged on. This could lead to instances when a user does not have the latest changes to a policy applied and is therefore operating in an insecure context.",
|
|
764
|
+
"severity": "medium"
|
|
765
|
+
},
|
|
766
|
+
{
|
|
767
|
+
"id": "WN12-CC-000030",
|
|
768
|
+
"title": "Access to the Windows Store must be turned off.",
|
|
769
|
+
"description": "Uncontrolled installation of applications can introduce various issues, including system instability, and allow access to sensitive information. Installation of applications must be controlled by the enterprise. Turning off access to the Windows Store will limit access to publicly available applications.",
|
|
770
|
+
"severity": "medium"
|
|
771
|
+
},
|
|
772
|
+
{
|
|
773
|
+
"id": "WN12-CC-000031",
|
|
774
|
+
"title": "Root Certificates must not be updated automatically from the Microsoft site.",
|
|
775
|
+
"description": "Root Certificate updates must be controlled in the enterprise to ensure a proper validation chain is maintained. This setting prevents root certificates from being updated automatically from the Microsoft site.",
|
|
776
|
+
"severity": "low"
|
|
777
|
+
},
|
|
778
|
+
{
|
|
779
|
+
"id": "WN12-CC-000032",
|
|
780
|
+
"title": "Downloading print driver packages over HTTP must be prevented.",
|
|
781
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents the computer from downloading print driver packages over HTTP.",
|
|
782
|
+
"severity": "medium"
|
|
783
|
+
},
|
|
784
|
+
{
|
|
785
|
+
"id": "WN12-CC-000033",
|
|
786
|
+
"title": "Event Viewer Events.asp links must be turned off.",
|
|
787
|
+
"description": "Viewing events is a function of administrators, who must not access the Internet with privileged accounts. This setting will disable Events.asp hyperlinks in Event Viewer to prevent links to the Internet from within events.",
|
|
788
|
+
"severity": "low"
|
|
789
|
+
},
|
|
790
|
+
{
|
|
791
|
+
"id": "WN12-CC-000035",
|
|
792
|
+
"title": "Errors in handwriting recognition on tablet PCs must not be reported to Microsoft.",
|
|
793
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents errors in handwriting recognition on tablet PCs from being reported to Microsoft.",
|
|
794
|
+
"severity": "low"
|
|
795
|
+
},
|
|
796
|
+
{
|
|
797
|
+
"id": "WN12-CC-000036",
|
|
798
|
+
"title": "The Internet Connection Wizard must not download a list of Internet Service Providers (ISPs) from Microsoft.",
|
|
799
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.\nThis setting prevents the Internet Connection Wizard from downloading a list of Internet Service Providers (ISPs) from Microsoft.",
|
|
800
|
+
"severity": "low"
|
|
801
|
+
},
|
|
802
|
+
{
|
|
803
|
+
"id": "WN12-CC-000037",
|
|
804
|
+
"title": "Web publishing and online ordering wizards must be prevented from downloading a list of providers.",
|
|
805
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents Windows from downloading a list of providers for the Web publishing and online ordering wizards.",
|
|
806
|
+
"severity": "medium"
|
|
807
|
+
},
|
|
808
|
+
{
|
|
809
|
+
"id": "WN12-CC-000038",
|
|
810
|
+
"title": "The Internet File Association service must be turned off.",
|
|
811
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents unhandled file associations from using the Microsoft Web service to find an application.",
|
|
812
|
+
"severity": "medium"
|
|
813
|
+
},
|
|
814
|
+
{
|
|
815
|
+
"id": "WN12-CC-000039",
|
|
816
|
+
"title": "Printing over HTTP must be prevented.",
|
|
817
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents the client computer from printing over HTTP, which allows the computer to print to printers on the intranet as well as the Internet.",
|
|
818
|
+
"severity": "medium"
|
|
819
|
+
},
|
|
820
|
+
{
|
|
821
|
+
"id": "WN12-CC-000040",
|
|
822
|
+
"title": "Windows Registration Wizard must be turned off.",
|
|
823
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents the Windows Registration Wizard from online registration.",
|
|
824
|
+
"severity": "low"
|
|
825
|
+
},
|
|
826
|
+
{
|
|
827
|
+
"id": "WN12-CC-000041",
|
|
828
|
+
"title": "Search Companion must be prevented from automatically downloading content updates.",
|
|
829
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents the Search Companion from automatically downloading content updates during local and Internet searches.",
|
|
830
|
+
"severity": "medium"
|
|
831
|
+
},
|
|
832
|
+
{
|
|
833
|
+
"id": "WN12-CC-000042",
|
|
834
|
+
"title": "The Order Prints Online wizard must be turned off.",
|
|
835
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting ensures the \"Order Prints Online\" task is not available in File Explorer.",
|
|
836
|
+
"severity": "low"
|
|
837
|
+
},
|
|
838
|
+
{
|
|
839
|
+
"id": "WN12-CC-000043",
|
|
840
|
+
"title": "The file and folder Publish to Web option must be unavailable in Windows folders.",
|
|
841
|
+
"description": "Allowing the option to publish to the web from File and Folder tasks in Windows folders could allow sensitive information to be exposed.",
|
|
842
|
+
"severity": "medium"
|
|
843
|
+
},
|
|
844
|
+
{
|
|
845
|
+
"id": "WN12-CC-000044",
|
|
846
|
+
"title": "Windows Messenger must be prevented from collecting anonymous information about how the service is used.",
|
|
847
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents Windows Messenger from collecting anonymous information about how the Windows Messenger software and service is used.",
|
|
848
|
+
"severity": "medium"
|
|
849
|
+
},
|
|
850
|
+
{
|
|
851
|
+
"id": "WN12-CC-000045",
|
|
852
|
+
"title": "The Windows Customer Experience Improvement Program must be disabled.",
|
|
853
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting ensures the Windows Customer Experience Improvement Program is disabled so information is not passed to the vendor.",
|
|
854
|
+
"severity": "medium"
|
|
855
|
+
},
|
|
856
|
+
{
|
|
857
|
+
"id": "WN12-CC-000046",
|
|
858
|
+
"title": "The system must be configured to prevent automatic forwarding of error information.",
|
|
859
|
+
"description": "This setting controls the reporting of errors to Microsoft and, if defined, a corporate error reporting site. This does not interfere with the reporting of errors to the local user. Since the contents of memory are included in this error report, sensitive information may be transmitted to Microsoft. This feature must be disabled to prevent the release of such information.",
|
|
860
|
+
"severity": "medium"
|
|
861
|
+
},
|
|
862
|
+
{
|
|
863
|
+
"id": "WN12-CC-000047",
|
|
864
|
+
"title": "Windows must be prevented from using Windows Update to search for drivers.",
|
|
865
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents Windows from searching Windows Update for device drivers when no local drivers for a device are present.",
|
|
866
|
+
"severity": "medium"
|
|
867
|
+
},
|
|
868
|
+
{
|
|
869
|
+
"id": "WN12-CC-000048",
|
|
870
|
+
"title": "Copying of user input methods to the system account for sign-in must be prevented.",
|
|
871
|
+
"description": "Allowing different input methods for sign-in could open different avenues of attack. User input methods must be restricted to those enabled for the system account at sign-in.",
|
|
872
|
+
"severity": "medium"
|
|
873
|
+
},
|
|
874
|
+
{
|
|
875
|
+
"id": "WN12-CC-000049",
|
|
876
|
+
"title": "The classic logon screen must be required for user logons.",
|
|
877
|
+
"description": "The classic logon screen requires users to enter a logon name and password to access a system. The simple logon screen or Welcome screen displays usernames for selection, providing part of the necessary logon information.",
|
|
878
|
+
"severity": "low"
|
|
879
|
+
},
|
|
880
|
+
{
|
|
881
|
+
"id": "WN12-CC-000051",
|
|
882
|
+
"title": "Local users on domain-joined computers must not be enumerated.",
|
|
883
|
+
"description": "The username is one part of logon credentials that could be used to gain access to a system. Preventing the enumeration of users limits this information to authorized personnel.",
|
|
884
|
+
"severity": "medium"
|
|
885
|
+
},
|
|
886
|
+
{
|
|
887
|
+
"id": "WN12-CC-000052",
|
|
888
|
+
"title": "App notifications on the lock screen must be turned off.",
|
|
889
|
+
"description": "App notifications that are displayed on the lock screen could display sensitive information to unauthorized personnel. Turning off this feature will limit access to the information to a logged on user.",
|
|
890
|
+
"severity": "medium"
|
|
891
|
+
},
|
|
892
|
+
{
|
|
893
|
+
"id": "WN12-CC-000054",
|
|
894
|
+
"title": "Users must be prompted for a password on resume from sleep (on battery).",
|
|
895
|
+
"description": "Authentication must always be required when accessing a system. This setting ensures the user is prompted for a password on resume from sleep (on battery).",
|
|
896
|
+
"severity": "medium"
|
|
897
|
+
},
|
|
898
|
+
{
|
|
899
|
+
"id": "WN12-CC-000055",
|
|
900
|
+
"title": "The user must be prompted for a password on resume from sleep (plugged in).",
|
|
901
|
+
"description": "Authentication must always be required when accessing a system. This setting ensures the user is prompted for a password on resume from sleep (plugged in).",
|
|
902
|
+
"severity": "medium"
|
|
903
|
+
},
|
|
904
|
+
{
|
|
905
|
+
"id": "WN12-CC-000056",
|
|
906
|
+
"title": "The display must turn off after 20 minutes of inactivity when the system is running on battery.",
|
|
907
|
+
"description": "Turning off an inactive display supports energy saving initiatives. It may also extend availability on systems running on a battery.",
|
|
908
|
+
"severity": "low"
|
|
909
|
+
},
|
|
910
|
+
{
|
|
911
|
+
"id": "WN12-CC-000057",
|
|
912
|
+
"title": "The display must turn off after 20 minutes of inactivity when the system is plugged in.",
|
|
913
|
+
"description": "Turning off an inactive display supports energy saving initiatives.",
|
|
914
|
+
"severity": "low"
|
|
915
|
+
},
|
|
916
|
+
{
|
|
917
|
+
"id": "WN12-CC-000058",
|
|
918
|
+
"title": "The system must be configured to prevent unsolicited remote assistance offers.",
|
|
919
|
+
"description": "Remote assistance allows another user to view or take control of the local session of a user. Unsolicited remote assistance is help that is offered by the remote user. This may allow unauthorized parties access to the resources on the computer.",
|
|
920
|
+
"severity": "medium"
|
|
921
|
+
},
|
|
922
|
+
{
|
|
923
|
+
"id": "WN12-CC-000059",
|
|
924
|
+
"title": "Solicited Remote Assistance must not be allowed.",
|
|
925
|
+
"description": "Remote assistance allows another user to view or take control of the local session of a user. Solicited assistance is help that is specifically requested by the local user. This may allow unauthorized parties access to the resources on the computer.",
|
|
926
|
+
"severity": "high"
|
|
927
|
+
},
|
|
928
|
+
{
|
|
929
|
+
"id": "WN12-CC-000062",
|
|
930
|
+
"title": "Remote Assistance log files must be generated.",
|
|
931
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. This setting will turn on session logging for Remote Assistance connections.",
|
|
932
|
+
"severity": "low"
|
|
933
|
+
},
|
|
934
|
+
{
|
|
935
|
+
"id": "WN12-CC-000063",
|
|
936
|
+
"title": "Client computers must be required to authenticate for RPC communication.",
|
|
937
|
+
"description": "Configuring RPC to require authentication to the RPC Endpoint Mapper will force clients to provide authentication before RPC communication is established.",
|
|
938
|
+
"severity": "medium"
|
|
939
|
+
},
|
|
940
|
+
{
|
|
941
|
+
"id": "WN12-CC-000064",
|
|
942
|
+
"title": "Unauthenticated RPC clients must be restricted from connecting to the RPC server.",
|
|
943
|
+
"description": "Configuring RPC to restrict unauthenticated RPC clients from connecting to the RPC server will prevent anonymous connections.",
|
|
944
|
+
"severity": "medium"
|
|
945
|
+
},
|
|
946
|
+
{
|
|
947
|
+
"id": "WN12-CC-000065",
|
|
948
|
+
"title": "The detection of compatibility issues for applications and drivers must be turned off.",
|
|
949
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system.",
|
|
950
|
+
"severity": "low"
|
|
951
|
+
},
|
|
952
|
+
{
|
|
953
|
+
"id": "WN12-CC-000066",
|
|
954
|
+
"title": "Microsoft Support Diagnostic Tool (MSDT) interactive communication with Microsoft must be prevented.",
|
|
955
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents the MSDT from communicating with and sending collected data to Microsoft, the default support provider.",
|
|
956
|
+
"severity": "low"
|
|
957
|
+
},
|
|
958
|
+
{
|
|
959
|
+
"id": "WN12-CC-000067",
|
|
960
|
+
"title": "Access to Windows Online Troubleshooting Service (WOTS) must be prevented.",
|
|
961
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents users from searching troubleshooting content on Microsoft servers. Only local content will be available.",
|
|
962
|
+
"severity": "low"
|
|
963
|
+
},
|
|
964
|
+
{
|
|
965
|
+
"id": "WN12-CC-000068",
|
|
966
|
+
"title": "Responsiveness events must be prevented from being aggregated and sent to Microsoft.",
|
|
967
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents responsiveness events from being aggregated and sent to Microsoft.",
|
|
968
|
+
"severity": "low"
|
|
969
|
+
},
|
|
970
|
+
{
|
|
971
|
+
"id": "WN12-CC-000069",
|
|
972
|
+
"title": "If the time service is configured, it must use an authorized time server.",
|
|
973
|
+
"description": "The Windows Time Service controls time synchronization settings. Time synchronization is essential for authentication and auditing purposes. If the Windows Time Service is used, it must synchronize with a secure, authorized time source. Domain-joined systems are automatically configured to synchronize with domain controllers. If an NTP server is configured, it must synchronize with a secure, authorized time source.",
|
|
974
|
+
"severity": "low"
|
|
975
|
+
},
|
|
976
|
+
{
|
|
977
|
+
"id": "WN12-CC-000070",
|
|
978
|
+
"title": "Trusted app installation must be enabled to allow for signed enterprise line of business apps.",
|
|
979
|
+
"description": "Enabling trusted app installation allows for enterprise line of business Windows 8 type apps. A trusted app package is one that is signed with a certificate chain that can be successfully validated in the enterprise. Configuring this ensures enterprise line of business apps are accessible.",
|
|
980
|
+
"severity": "low"
|
|
981
|
+
},
|
|
982
|
+
{
|
|
983
|
+
"id": "WN12-CC-000071",
|
|
984
|
+
"title": "The Application Compatibility Program Inventory must be prevented from collecting data and sending the information to Microsoft.",
|
|
985
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting will prevent the Program Inventory from collecting data about a system and sending the information to Microsoft.",
|
|
986
|
+
"severity": "low"
|
|
987
|
+
},
|
|
988
|
+
{
|
|
989
|
+
"id": "WN12-CC-000072",
|
|
990
|
+
"title": "Autoplay must be turned off for non-volume devices.",
|
|
991
|
+
"description": "Allowing autoplay to execute may introduce malicious code to a system. Autoplay begins reading from a drive as soon as media is inserted into the drive. As a result, the setup file of programs or music on audio media may start. This setting will disable autoplay for non-volume devices (such as Media Transfer Protocol (MTP) devices).",
|
|
992
|
+
"severity": "high"
|
|
993
|
+
},
|
|
994
|
+
{
|
|
995
|
+
"id": "WN12-CC-000073",
|
|
996
|
+
"title": "The default autorun behavior must be configured to prevent autorun commands.",
|
|
997
|
+
"description": "Allowing autorun commands to execute may introduce malicious code to a system. Configuring this setting prevents autorun commands from executing.",
|
|
998
|
+
"severity": "high"
|
|
999
|
+
},
|
|
1000
|
+
{
|
|
1001
|
+
"id": "WN12-CC-000074",
|
|
1002
|
+
"title": "Autoplay must be disabled for all drives.",
|
|
1003
|
+
"description": "Allowing autoplay to execute may introduce malicious code to a system. Autoplay begins reading from a drive as soon media is inserted into the drive. As a result, the setup file of programs or music on audio media may start. By default, autoplay is disabled on removable drives, such as the floppy disk drive (but not the CD-ROM drive) and on network drives. Enabling this policy disables autoplay on all drives.",
|
|
1004
|
+
"severity": "high"
|
|
1005
|
+
},
|
|
1006
|
+
{
|
|
1007
|
+
"id": "WN12-CC-000075",
|
|
1008
|
+
"title": "The use of biometrics must be disabled.",
|
|
1009
|
+
"description": "Allowing biometrics may bypass required authentication methods. Biometrics may only be used as an additional authentication factor where an enhanced strength of identity credential is necessary or desirable. Additional factors must be met per DoD policy.",
|
|
1010
|
+
"severity": "medium"
|
|
1011
|
+
},
|
|
1012
|
+
{
|
|
1013
|
+
"id": "WN12-CC-000076",
|
|
1014
|
+
"title": "The password reveal button must not be displayed.",
|
|
1015
|
+
"description": "Visible passwords may be seen by nearby persons, compromising them. The password reveal button can be used to display an entered password and must not be allowed.",
|
|
1016
|
+
"severity": "medium"
|
|
1017
|
+
},
|
|
1018
|
+
{
|
|
1019
|
+
"id": "WN12-CC-000077",
|
|
1020
|
+
"title": "The system must require username and password to elevate a running application.",
|
|
1021
|
+
"description": "Enumeration of administrator accounts when elevating can provide part of the logon information to an unauthorized user. This setting configures the system to always require users to type in a username and password to elevate a running application.",
|
|
1022
|
+
"severity": "medium"
|
|
1023
|
+
},
|
|
1024
|
+
{
|
|
1025
|
+
"id": "WN12-CC-000078",
|
|
1026
|
+
"title": "The Enhanced Mitigation Experience Toolkit (EMET) system-wide Address Space Layout Randomization (ASLR) must be enabled and configured to Application Opt In.",
|
|
1027
|
+
"description": "Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications, adding additional levels of protection.",
|
|
1028
|
+
"severity": "medium"
|
|
1029
|
+
},
|
|
1030
|
+
{
|
|
1031
|
+
"id": "WN12-CC-000079",
|
|
1032
|
+
"title": "The Enhanced Mitigation Experience Toolkit (EMET) Default Protections for Internet Explorer must be enabled.",
|
|
1033
|
+
"description": "Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications, adding additional levels of protection.",
|
|
1034
|
+
"severity": "medium"
|
|
1035
|
+
},
|
|
1036
|
+
{
|
|
1037
|
+
"id": "WN12-CC-000080",
|
|
1038
|
+
"title": "The Enhanced Mitigation Experience Toolkit (EMET) Default Protections for Recommended Software must be enabled.",
|
|
1039
|
+
"description": "Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications, adding additional levels of protection.",
|
|
1040
|
+
"severity": "medium"
|
|
1041
|
+
},
|
|
1042
|
+
{
|
|
1043
|
+
"id": "WN12-CC-000081",
|
|
1044
|
+
"title": "The Enhanced Mitigation Experience Toolkit (EMET) Default Protections for Popular Software must be enabled.",
|
|
1045
|
+
"description": "Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications, adding additional levels of protection.",
|
|
1046
|
+
"severity": "medium"
|
|
1047
|
+
},
|
|
1048
|
+
{
|
|
1049
|
+
"id": "WN12-CC-000082",
|
|
1050
|
+
"title": "The Enhanced Mitigation Experience Toolkit (EMET) system-wide Data Execution Prevention (DEP) must be enabled and configured to at least Application Opt Out.",
|
|
1051
|
+
"description": "Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications, adding additional levels of protection.",
|
|
1052
|
+
"severity": "medium"
|
|
1053
|
+
},
|
|
1054
|
+
{
|
|
1055
|
+
"id": "WN12-CC-000083",
|
|
1056
|
+
"title": "The Enhanced Mitigation Experience Toolkit (EMET) system-wide Structured Exception Handler Overwrite Protection (SEHOP) must be configured to Application Opt Out.",
|
|
1057
|
+
"description": "Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications, adding additional levels of protection.",
|
|
1058
|
+
"severity": "medium"
|
|
1059
|
+
},
|
|
1060
|
+
{
|
|
1061
|
+
"id": "WN12-CC-000084",
|
|
1062
|
+
"title": "The Application event log must be configured to a minimum size requirement.",
|
|
1063
|
+
"description": "Inadequate log size will cause the log to fill up quickly and require frequent clearing by administrative personnel.",
|
|
1064
|
+
"severity": "medium"
|
|
1065
|
+
},
|
|
1066
|
+
{
|
|
1067
|
+
"id": "WN12-CC-000085",
|
|
1068
|
+
"title": "The Security event log must be configured to a minimum size requirement.",
|
|
1069
|
+
"description": "Inadequate log size will cause the log to fill up quickly and require frequent clearing by administrative personnel.",
|
|
1070
|
+
"severity": "medium"
|
|
1071
|
+
},
|
|
1072
|
+
{
|
|
1073
|
+
"id": "WN12-CC-000086",
|
|
1074
|
+
"title": "The Setup event log must be configured to a minimum size requirement.",
|
|
1075
|
+
"description": "Inadequate log size will cause the log to fill up quickly and require frequent clearing by administrative personnel.",
|
|
1076
|
+
"severity": "medium"
|
|
1077
|
+
},
|
|
1078
|
+
{
|
|
1079
|
+
"id": "WN12-CC-000087",
|
|
1080
|
+
"title": "The System event log must be configured to a minimum size requirement.",
|
|
1081
|
+
"description": "Inadequate log size will cause the log to fill up quickly and require frequent clearing by administrative personnel.",
|
|
1082
|
+
"severity": "medium"
|
|
1083
|
+
},
|
|
1084
|
+
{
|
|
1085
|
+
"id": "WN12-CC-000088",
|
|
1086
|
+
"title": "The Windows SmartScreen must be turned off.",
|
|
1087
|
+
"description": "Some features may send system information to the vendor. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise.",
|
|
1088
|
+
"severity": "low"
|
|
1089
|
+
},
|
|
1090
|
+
{
|
|
1091
|
+
"id": "WN12-CC-000089",
|
|
1092
|
+
"title": "Explorer Data Execution Prevention must be enabled.",
|
|
1093
|
+
"description": "Data Execution Prevention (DEP) provides additional protection by performing checks on memory to help prevent malicious code from running. This setting will prevent Data Execution Prevention from being turned off for File Explorer.",
|
|
1094
|
+
"severity": "medium"
|
|
1095
|
+
},
|
|
1096
|
+
{
|
|
1097
|
+
"id": "WN12-CC-000090",
|
|
1098
|
+
"title": "Turning off File Explorer heap termination on corruption must be disabled.",
|
|
1099
|
+
"description": "Legacy plug-in applications may continue to function when a File Explorer session has become corrupt. Disabling this feature will prevent this.",
|
|
1100
|
+
"severity": "low"
|
|
1101
|
+
},
|
|
1102
|
+
{
|
|
1103
|
+
"id": "WN12-CC-000091",
|
|
1104
|
+
"title": "File Explorer shell protocol must run in protected mode.",
|
|
1105
|
+
"description": "The shell protocol will limit the set of folders applications can open when run in protected mode. Restricting files an application can open to a limited set of folders increases the security of Windows.",
|
|
1106
|
+
"severity": "medium"
|
|
1107
|
+
},
|
|
1108
|
+
{
|
|
1109
|
+
"id": "WN12-CC-000095",
|
|
1110
|
+
"title": "The location feature must be turned off.",
|
|
1111
|
+
"description": "The location service on systems may allow sensitive data to be used by applications on the system. This should be turned off unless explicitly allowed for approved systems/applications.",
|
|
1112
|
+
"severity": "medium"
|
|
1113
|
+
},
|
|
1114
|
+
{
|
|
1115
|
+
"id": "WN12-CC-000096",
|
|
1116
|
+
"title": "Passwords must not be saved in the Remote Desktop Client.",
|
|
1117
|
+
"description": "Saving passwords in the Remote Desktop Client could allow an unauthorized user to establish a remote desktop session to another system. The system must be configured to prevent users from saving passwords in the Remote Desktop Client.",
|
|
1118
|
+
"severity": "medium"
|
|
1119
|
+
},
|
|
1120
|
+
{
|
|
1121
|
+
"id": "WN12-CC-000098",
|
|
1122
|
+
"title": "Local drives must be prevented from sharing with Remote Desktop Session Hosts. (Remote Desktop Services Role).",
|
|
1123
|
+
"description": "Preventing users from sharing the local drives on their client computers to Remote Session Hosts that they access helps reduce possible exposure of sensitive data.",
|
|
1124
|
+
"severity": "medium"
|
|
1125
|
+
},
|
|
1126
|
+
{
|
|
1127
|
+
"id": "WN12-CC-000099",
|
|
1128
|
+
"title": "Remote Desktop Services must always prompt a client for passwords upon connection.",
|
|
1129
|
+
"description": "This setting controls the ability of users to supply passwords automatically as part of their remote desktop connection. Disabling this setting would allow anyone to use the stored credentials in a connection item to connect to the terminal server.",
|
|
1130
|
+
"severity": "medium"
|
|
1131
|
+
},
|
|
1132
|
+
{
|
|
1133
|
+
"id": "WN12-CC-000100",
|
|
1134
|
+
"title": "Remote Desktop Services must be configured with the client connection encryption set to the required level.",
|
|
1135
|
+
"description": "Remote connections must be encrypted to prevent interception of data or sensitive information. Selecting \"High Level\" will ensure encryption of Remote Desktop Services sessions in both directions.",
|
|
1136
|
+
"severity": "medium"
|
|
1137
|
+
},
|
|
1138
|
+
{
|
|
1139
|
+
"id": "WN12-CC-000101",
|
|
1140
|
+
"title": "Remote Desktop Services must be configured to disconnect an idle session after the specified time period.",
|
|
1141
|
+
"description": "This setting controls how long a session may be idle before it is automatically disconnected from the server. Users must disconnect if they plan on being away from their terminals for extended periods of time. Idle sessions must be disconnected after 15 minutes.",
|
|
1142
|
+
"severity": "medium"
|
|
1143
|
+
},
|
|
1144
|
+
{
|
|
1145
|
+
"id": "WN12-CC-000102",
|
|
1146
|
+
"title": "Remote Desktop Services must be configured to set a time limit for disconnected sessions.",
|
|
1147
|
+
"description": "This setting controls how long a session will remain open if it is unexpectedly terminated. Such sessions use system resources and must be terminated as soon as possible.",
|
|
1148
|
+
"severity": "medium"
|
|
1149
|
+
},
|
|
1150
|
+
{
|
|
1151
|
+
"id": "WN12-CC-000103",
|
|
1152
|
+
"title": "Remote Desktop Services must delete temporary folders when a session is terminated.",
|
|
1153
|
+
"description": "Remote desktop session temporary folders must always be deleted after a session is over to prevent hard disk clutter and potential leakage of information. This setting controls the deletion of the temporary folders when the session is terminated.",
|
|
1154
|
+
"severity": "medium"
|
|
1155
|
+
},
|
|
1156
|
+
{
|
|
1157
|
+
"id": "WN12-CC-000104",
|
|
1158
|
+
"title": "Remote Desktop Services must be configured to use session-specific temporary folders.",
|
|
1159
|
+
"description": "If a communal temporary folder is used for remote desktop sessions, it might be possible for users to access other users' temporary folders. If this setting is enabled, only one temporary folder is used for all remote desktop sessions. Per session temporary folders must be established.",
|
|
1160
|
+
"severity": "medium"
|
|
1161
|
+
},
|
|
1162
|
+
{
|
|
1163
|
+
"id": "WN12-CC-000105",
|
|
1164
|
+
"title": "Attachments must be prevented from being downloaded from RSS feeds.",
|
|
1165
|
+
"description": "Attachments from RSS feeds may not be secure. This setting will prevent attachments from being downloaded from RSS feeds.",
|
|
1166
|
+
"severity": "medium"
|
|
1167
|
+
},
|
|
1168
|
+
{
|
|
1169
|
+
"id": "WN12-CC-000106",
|
|
1170
|
+
"title": "Basic authentication for RSS feeds over HTTP must be turned off.",
|
|
1171
|
+
"description": "Basic authentication uses plain text passwords that could be used to compromise a system.",
|
|
1172
|
+
"severity": "medium"
|
|
1173
|
+
},
|
|
1174
|
+
{
|
|
1175
|
+
"id": "WN12-CC-000109",
|
|
1176
|
+
"title": "Automatic download of updates from the Windows Store must be turned off.",
|
|
1177
|
+
"description": "Uncontrolled system updates can introduce issues to a system. Obtaining update components from an outside source may also potentially allow sensitive information outside of the enterprise. Application updates must be obtained from an internal source.",
|
|
1178
|
+
"severity": "low"
|
|
1179
|
+
},
|
|
1180
|
+
{
|
|
1181
|
+
"id": "WN12-CC-000110",
|
|
1182
|
+
"title": "The Windows Store application must be turned off.",
|
|
1183
|
+
"description": "Uncontrolled installation of applications can introduce various issues, including system instability, and provide access to sensitive information. Installation of applications must be controlled by the enterprise. Turning off access to the Windows Store will limit access to publicly available applications.",
|
|
1184
|
+
"severity": "medium"
|
|
1185
|
+
},
|
|
1186
|
+
{
|
|
1187
|
+
"id": "WN12-CC-000111",
|
|
1188
|
+
"title": "Microsoft Active Protection Service membership must be disabled.",
|
|
1189
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting disables Microsoft Active Protection Service membership and reporting.",
|
|
1190
|
+
"severity": "medium"
|
|
1191
|
+
},
|
|
1192
|
+
{
|
|
1193
|
+
"id": "WN12-CC-000112",
|
|
1194
|
+
"title": "Error Reporting events must be logged in the system event log.",
|
|
1195
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. This setting ensures that Error Reporting events will be logged in the system event log.",
|
|
1196
|
+
"severity": "low"
|
|
1197
|
+
},
|
|
1198
|
+
{
|
|
1199
|
+
"id": "WN12-CC-000114",
|
|
1200
|
+
"title": "Additional data requests in response to Error Reporting must be declined.",
|
|
1201
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents additional data requests in response to Error Reporting.",
|
|
1202
|
+
"severity": "low"
|
|
1203
|
+
},
|
|
1204
|
+
{
|
|
1205
|
+
"id": "WN12-CC-000115",
|
|
1206
|
+
"title": "Users must be prevented from changing installation options.",
|
|
1207
|
+
"description": "Installation options for applications are typically controlled by administrators. This setting prevents users from changing installation options that may bypass security features.",
|
|
1208
|
+
"severity": "medium"
|
|
1209
|
+
},
|
|
1210
|
+
{
|
|
1211
|
+
"id": "WN12-CC-000116",
|
|
1212
|
+
"title": "The Windows Installer Always install with elevated privileges option must be disabled.",
|
|
1213
|
+
"description": "Standard user accounts must not be granted elevated privileges. Enabling Windows Installer to elevate privileges when installing applications can allow malicious persons and applications to gain full control of a system.",
|
|
1214
|
+
"severity": "high"
|
|
1215
|
+
},
|
|
1216
|
+
{
|
|
1217
|
+
"id": "WN12-CC-000117",
|
|
1218
|
+
"title": "Users must be notified if a web-based program attempts to install software.",
|
|
1219
|
+
"description": "Users must be aware of attempted program installations. This setting ensures users are notified if a web-based program attempts to install software.",
|
|
1220
|
+
"severity": "medium"
|
|
1221
|
+
},
|
|
1222
|
+
{
|
|
1223
|
+
"id": "WN12-CC-000118",
|
|
1224
|
+
"title": "Nonadministrators must be prevented from applying vendor-signed updates.",
|
|
1225
|
+
"description": "Uncontrolled system updates can introduce issues to a system. This setting will prevent users from applying vendor-signed updates (though they may be from a trusted source).",
|
|
1226
|
+
"severity": "low"
|
|
1227
|
+
},
|
|
1228
|
+
{
|
|
1229
|
+
"id": "WN12-CC-000119",
|
|
1230
|
+
"title": "Users must be notified if the logon server was inaccessible and cached credentials were used.",
|
|
1231
|
+
"description": "Notifying a user whether cached credentials were used may make them aware of connection issues.",
|
|
1232
|
+
"severity": "low"
|
|
1233
|
+
},
|
|
1234
|
+
{
|
|
1235
|
+
"id": "WN12-CC-000120",
|
|
1236
|
+
"title": "Windows Media Digital Rights Management (DRM) must be prevented from accessing the Internet.",
|
|
1237
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis check verifies that Windows Media DRM will be prevented from accessing the Internet.",
|
|
1238
|
+
"severity": "medium"
|
|
1239
|
+
},
|
|
1240
|
+
{
|
|
1241
|
+
"id": "WN12-CC-000121",
|
|
1242
|
+
"title": "Users must not be presented with Privacy and Installation options on first use of Windows Media Player.",
|
|
1243
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting prevents users from being presented with Privacy and Installation options on first use of Windows Media Player, which could enable some communication with the vendor.",
|
|
1244
|
+
"severity": "low"
|
|
1245
|
+
},
|
|
1246
|
+
{
|
|
1247
|
+
"id": "WN12-CC-000122",
|
|
1248
|
+
"title": "Windows Media Player must be configured to prevent automatic checking for updates.",
|
|
1249
|
+
"description": "Uncontrolled system updates can introduce issues to a system. The automatic check for updates performed by Windows Media Player must be disabled to ensure a constant platform and to prevent the introduction of unknown\\untested software on the system.",
|
|
1250
|
+
"severity": "medium"
|
|
1251
|
+
},
|
|
1252
|
+
{
|
|
1253
|
+
"id": "WN12-CC-000123",
|
|
1254
|
+
"title": "The Windows Remote Management (WinRM) client must not use Basic authentication.",
|
|
1255
|
+
"description": "Basic authentication uses plain text passwords that could be used to compromise a system.",
|
|
1256
|
+
"severity": "high"
|
|
1257
|
+
},
|
|
1258
|
+
{
|
|
1259
|
+
"id": "WN12-CC-000124",
|
|
1260
|
+
"title": "The Windows Remote Management (WinRM) client must not allow unencrypted traffic.",
|
|
1261
|
+
"description": "Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this.",
|
|
1262
|
+
"severity": "medium"
|
|
1263
|
+
},
|
|
1264
|
+
{
|
|
1265
|
+
"id": "WN12-CC-000125",
|
|
1266
|
+
"title": "The Windows Remote Management (WinRM) client must not use Digest authentication.",
|
|
1267
|
+
"description": "Digest authentication is not as strong as other options and may be subject to man-in-the-middle attacks.",
|
|
1268
|
+
"severity": "medium"
|
|
1269
|
+
},
|
|
1270
|
+
{
|
|
1271
|
+
"id": "WN12-CC-000126",
|
|
1272
|
+
"title": "The Windows Remote Management (WinRM) service must not use Basic authentication.",
|
|
1273
|
+
"description": "Basic authentication uses plain text passwords that could be used to compromise a system.",
|
|
1274
|
+
"severity": "high"
|
|
1275
|
+
},
|
|
1276
|
+
{
|
|
1277
|
+
"id": "WN12-CC-000127",
|
|
1278
|
+
"title": "The Windows Remote Management (WinRM) service must not allow unencrypted traffic.",
|
|
1279
|
+
"description": "Unencrypted remote access to a system can allow sensitive information to be compromised. Windows remote management connections must be encrypted to prevent this.",
|
|
1280
|
+
"severity": "medium"
|
|
1281
|
+
},
|
|
1282
|
+
{
|
|
1283
|
+
"id": "WN12-CC-000128",
|
|
1284
|
+
"title": "The Windows Remote Management (WinRM) service must not store RunAs credentials.",
|
|
1285
|
+
"description": "Storage of administrative credentials could allow unauthorized access. Disallowing the storage of RunAs credentials for Windows Remote Management will prevent them from being used with plug-ins.",
|
|
1286
|
+
"severity": "medium"
|
|
1287
|
+
},
|
|
1288
|
+
{
|
|
1289
|
+
"id": "WN12-CC-000129",
|
|
1290
|
+
"title": "Automatic Updates must not be used (unless configured to point to a DoD server).",
|
|
1291
|
+
"description": "Uncontrolled system updates can introduce issues to a system. The system must be configured to prevent Automatic Updates from being run unless directed to a DoD Windows Server Update Services (WSUS) server.",
|
|
1292
|
+
"severity": "medium"
|
|
1293
|
+
},
|
|
1294
|
+
{
|
|
1295
|
+
"id": "WN12-CC-000130",
|
|
1296
|
+
"title": "The Remote Desktop Session Host must require secure RPC communications.",
|
|
1297
|
+
"description": "Allowing unsecure RPC communication exposes the system to man-in-the-middle attacks and data disclosure attacks. A man-in-the-middle attack occurs when an intruder captures packets between a client and server and modifies them before allowing the packets to be exchanged. Usually the attacker will modify the information in the packets in an attempt to cause either the client or server to reveal sensitive information.",
|
|
1298
|
+
"severity": "medium"
|
|
1299
|
+
},
|
|
1300
|
+
{
|
|
1301
|
+
"id": "WN12-CC-000131",
|
|
1302
|
+
"title": "Remote Desktop Services must limit users to one remote session.",
|
|
1303
|
+
"description": "Allowing multiple Remote Desktop Services sessions could consume resources. There is also potential to make a secondary connection to a system with compromised credentials.",
|
|
1304
|
+
"severity": "medium"
|
|
1305
|
+
},
|
|
1306
|
+
{
|
|
1307
|
+
"id": "WN12-CC-000132",
|
|
1308
|
+
"title": "Users must be prevented from mapping local COM ports and redirecting data from the Remote Desktop Session Host to local COM ports. (Remote Desktop Services Role).",
|
|
1309
|
+
"description": "Preventing the redirection of Remote Desktop session data to a client computer's COM ports helps reduce possible exposure of sensitive data.",
|
|
1310
|
+
"severity": "medium"
|
|
1311
|
+
},
|
|
1312
|
+
{
|
|
1313
|
+
"id": "WN12-CC-000133",
|
|
1314
|
+
"title": "Users must be prevented from mapping local LPT ports and redirecting data from the Remote Desktop Session Host to local LPT ports. (Remote Desktop Services Role).",
|
|
1315
|
+
"description": "Preventing the redirection of Remote Desktop session data to a client computer's LPT ports helps reduce possible exposure of sensitive data.",
|
|
1316
|
+
"severity": "medium"
|
|
1317
|
+
},
|
|
1318
|
+
{
|
|
1319
|
+
"id": "WN12-CC-000134",
|
|
1320
|
+
"title": "The system must be configured to ensure smart card devices can be redirected to the Remote Desktop session. (Remote Desktop Services Role).",
|
|
1321
|
+
"description": "Enabling the redirection of smart card devices allows their use within Remote Desktop sessions.",
|
|
1322
|
+
"severity": "medium"
|
|
1323
|
+
},
|
|
1324
|
+
{
|
|
1325
|
+
"id": "WN12-CC-000135",
|
|
1326
|
+
"title": "Users must be prevented from redirecting Plug and Play devices to the Remote Desktop Session Host. (Remote Desktop Services Role).",
|
|
1327
|
+
"description": "Preventing the redirection of Plug and Play devices in Remote Desktop sessions helps reduce possible exposure of sensitive data.",
|
|
1328
|
+
"severity": "medium"
|
|
1329
|
+
},
|
|
1330
|
+
{
|
|
1331
|
+
"id": "WN12-CC-000136",
|
|
1332
|
+
"title": "Only the default client printer must be redirected to the Remote Desktop Session Host. (Remote Desktop Services Role).",
|
|
1333
|
+
"description": "Allowing the redirection of only the default client printer to a Remote Desktop session helps reduce possible exposure of sensitive data.",
|
|
1334
|
+
"severity": "medium"
|
|
1335
|
+
},
|
|
1336
|
+
{
|
|
1337
|
+
"id": "WN12-CC-000137",
|
|
1338
|
+
"title": "The system must be configured to remove the Disconnect option from the Shut Down dialog box on the Remote Desktop Client. (Remote Desktop Services Role).",
|
|
1339
|
+
"description": "Removing the Disconnect option from the Shut Down dialog box for Remote Desktop sessions helps prevent disconnected but active sessions from continuing to run and using resources.",
|
|
1340
|
+
"severity": "low"
|
|
1341
|
+
},
|
|
1342
|
+
{
|
|
1343
|
+
"id": "WN12-FW-000001",
|
|
1344
|
+
"title": "The Windows Firewall must be enabled for the Domain Profile.",
|
|
1345
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. This setting enables the firewall when connected to the domain.",
|
|
1346
|
+
"severity": "medium"
|
|
1347
|
+
},
|
|
1348
|
+
{
|
|
1349
|
+
"id": "WN12-FW-000002",
|
|
1350
|
+
"title": "The Windows Firewall must block unsolicited inbound connections for the Domain Profile.",
|
|
1351
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unsolicited inbound connections may be malicious attempts to gain access to a system. Unsolicited inbound connections for which there is no rule allowing the connection will be blocked in the domain.",
|
|
1352
|
+
"severity": "high"
|
|
1353
|
+
},
|
|
1354
|
+
{
|
|
1355
|
+
"id": "WN12-FW-000003",
|
|
1356
|
+
"title": "The Windows Firewall must allow outbound connections, unless a rule explicitly blocks the connection for the Domain Profile.",
|
|
1357
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Outbound connections are allowed in the domain, unless a rule explicitly blocks the connection. This allows normal outbound communication, which could be restricted as necessary with additional rules.",
|
|
1358
|
+
"severity": "medium"
|
|
1359
|
+
},
|
|
1360
|
+
{
|
|
1361
|
+
"id": "WN12-FW-000004",
|
|
1362
|
+
"title": "The Windows Firewall must display notifications when a program is blocked from receiving an inbound connection for the Domain Profile.",
|
|
1363
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The display of notifications to the user when a program is blocked from receiving an inbound connection in the domain must be enabled to alert the user of potential issues.",
|
|
1364
|
+
"severity": "low"
|
|
1365
|
+
},
|
|
1366
|
+
{
|
|
1367
|
+
"id": "WN12-FW-000005",
|
|
1368
|
+
"title": "The Windows Firewall must block unicast responses to multicast or broadcast messages for the Domain Profile.",
|
|
1369
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unicast responses to multicast or broadcast messages in the domain will be blocked. This helps minimize the risk of an attacker using broadcast or multicast traffic to deliver malicious payloads.",
|
|
1370
|
+
"severity": "medium"
|
|
1371
|
+
},
|
|
1372
|
+
{
|
|
1373
|
+
"id": "WN12-FW-000006",
|
|
1374
|
+
"title": "The Windows Firewall log file name and location must be configured for the Domain Profile.",
|
|
1375
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The location and file name of the firewall log for a domain connection will be defined to ensure the logs are maintained.",
|
|
1376
|
+
"severity": "low"
|
|
1377
|
+
},
|
|
1378
|
+
{
|
|
1379
|
+
"id": "WN12-FW-000007",
|
|
1380
|
+
"title": "The Windows Firewall log size must be configured for the Domain Profile.",
|
|
1381
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The firewall log file size for a domain connection will be set to ensure enough capacity is allocated for audit data.",
|
|
1382
|
+
"severity": "low"
|
|
1383
|
+
},
|
|
1384
|
+
{
|
|
1385
|
+
"id": "WN12-FW-000008",
|
|
1386
|
+
"title": "The Windows Firewall must log dropped packets for the Domain Profile.",
|
|
1387
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of dropped packets for a domain connection will be enabled to maintain an audit trail of potential issues.",
|
|
1388
|
+
"severity": "low"
|
|
1389
|
+
},
|
|
1390
|
+
{
|
|
1391
|
+
"id": "WN12-FW-000009",
|
|
1392
|
+
"title": "The Windows Firewall must log successful connections for the Domain Profile.",
|
|
1393
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of successful connections for a domain connection will be enabled to maintain an audit trail if issues are discovered.",
|
|
1394
|
+
"severity": "low"
|
|
1395
|
+
},
|
|
1396
|
+
{
|
|
1397
|
+
"id": "WN12-FW-000010",
|
|
1398
|
+
"title": "The Windows Firewall must be enabled for the Private Profile.",
|
|
1399
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. This setting enables the firewall when connected to a private network.",
|
|
1400
|
+
"severity": "medium"
|
|
1401
|
+
},
|
|
1402
|
+
{
|
|
1403
|
+
"id": "WN12-FW-000011",
|
|
1404
|
+
"title": "The Windows Firewall must block unsolicited inbound connections for the Private Profile.",
|
|
1405
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unsolicited inbound connections may be malicious attempts to gain access to a system. Unsolicited inbound connections for which there is no rule allowing the connection will be blocked on a private network.",
|
|
1406
|
+
"severity": "high"
|
|
1407
|
+
},
|
|
1408
|
+
{
|
|
1409
|
+
"id": "WN12-FW-000012",
|
|
1410
|
+
"title": "The Windows Firewall must allow outbound connections, unless a rule explicitly blocks the connection for the Private Profile.",
|
|
1411
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Outbound connections are allowed on a private network, unless a rule explicitly blocks the connection. This allows normal outbound communication, which could be restricted as necessary with additional rules.",
|
|
1412
|
+
"severity": "medium"
|
|
1413
|
+
},
|
|
1414
|
+
{
|
|
1415
|
+
"id": "WN12-FW-000013",
|
|
1416
|
+
"title": "The Windows Firewall must display notifications when a program is blocked from receiving an inbound connection for the Private Profile.",
|
|
1417
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The display of notifications to the user when a program is blocked from receiving an inbound connection on a private network must be enabled to alert the user of potential issues.",
|
|
1418
|
+
"severity": "low"
|
|
1419
|
+
},
|
|
1420
|
+
{
|
|
1421
|
+
"id": "WN12-FW-000014",
|
|
1422
|
+
"title": "The Windows Firewall must block unicast responses to multicast or broadcast messages for the Private Profile.",
|
|
1423
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unicast responses to multicast or broadcast messages for a private connection will be blocked. This helps minimize the risk of an attacker using broadcast or multicast traffic to deliver malicious payloads.",
|
|
1424
|
+
"severity": "medium"
|
|
1425
|
+
},
|
|
1426
|
+
{
|
|
1427
|
+
"id": "WN12-FW-000015",
|
|
1428
|
+
"title": "The Windows Firewall log file name and location must be configured for the Private Profile.",
|
|
1429
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The location and file name of the firewall log for a private connection will be defined to ensure the logs are maintained.",
|
|
1430
|
+
"severity": "low"
|
|
1431
|
+
},
|
|
1432
|
+
{
|
|
1433
|
+
"id": "WN12-FW-000016",
|
|
1434
|
+
"title": "The Windows Firewall log size must be configured for the Private Profile.",
|
|
1435
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The firewall log file size for a private connection will be set to ensure enough capacity is allocated for audit data.",
|
|
1436
|
+
"severity": "low"
|
|
1437
|
+
},
|
|
1438
|
+
{
|
|
1439
|
+
"id": "WN12-FW-000017",
|
|
1440
|
+
"title": "The Windows Firewall must log dropped packets for the Private Profile.",
|
|
1441
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of dropped packets for a private network connection will be enabled to maintain an audit trail of potential issues.",
|
|
1442
|
+
"severity": "low"
|
|
1443
|
+
},
|
|
1444
|
+
{
|
|
1445
|
+
"id": "WN12-FW-000018",
|
|
1446
|
+
"title": "The Windows Firewall must log successful connections for the Private Profile.",
|
|
1447
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of successful connections for a private network connection will be enabled to maintain an audit trail if issues are discovered.",
|
|
1448
|
+
"severity": "low"
|
|
1449
|
+
},
|
|
1450
|
+
{
|
|
1451
|
+
"id": "WN12-FW-000019",
|
|
1452
|
+
"title": "The Windows Firewall must be enabled for the Public Profile.",
|
|
1453
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. This setting enables the firewall when connected to a public network.",
|
|
1454
|
+
"severity": "medium"
|
|
1455
|
+
},
|
|
1456
|
+
{
|
|
1457
|
+
"id": "WN12-FW-000020",
|
|
1458
|
+
"title": "The Windows Firewall must block unsolicited inbound connections for the Public Profile.",
|
|
1459
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unsolicited inbound connections may be malicious attempts to gain access to a system. Unsolicited inbound connections for which there is no rule allowing the connection will be blocked on a public network.",
|
|
1460
|
+
"severity": "high"
|
|
1461
|
+
},
|
|
1462
|
+
{
|
|
1463
|
+
"id": "WN12-FW-000021",
|
|
1464
|
+
"title": "The Windows Firewall must allow outbound connections, unless a rule explicitly blocks the connection for the Public Profile.",
|
|
1465
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Outbound connections are allowed on a public network, unless a rule explicitly blocks the connection. This allows normal outbound communication, which could be restricted as necessary with additional rules.",
|
|
1466
|
+
"severity": "medium"
|
|
1467
|
+
},
|
|
1468
|
+
{
|
|
1469
|
+
"id": "WN12-FW-000022",
|
|
1470
|
+
"title": "The Windows Firewall must display notifications when a program is blocked from receiving an inbound connection for the Public Profile.",
|
|
1471
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The display of notifications to the user when a program is blocked from receiving an inbound connection on a public network must be enabled to alert the user of potential issues.",
|
|
1472
|
+
"severity": "low"
|
|
1473
|
+
},
|
|
1474
|
+
{
|
|
1475
|
+
"id": "WN12-FW-000023",
|
|
1476
|
+
"title": "The Windows Firewall must block unicast responses to multicast or broadcast messages for the Public Profile.",
|
|
1477
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Unicast responses to multicast or broadcast messages for a public network will be blocked. This helps minimize the risk of an attacker using broadcast or multicast traffic to deliver malicious payloads.",
|
|
1478
|
+
"severity": "medium"
|
|
1479
|
+
},
|
|
1480
|
+
{
|
|
1481
|
+
"id": "WN12-FW-000024",
|
|
1482
|
+
"title": "The Windows Firewall local connection rules must not be merged with Group Policy settings for the Public Profile.",
|
|
1483
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Local connection rules will not be merged with Group Policy settings on a public network to prevent Group Policy settings from being changed.",
|
|
1484
|
+
"severity": "medium"
|
|
1485
|
+
},
|
|
1486
|
+
{
|
|
1487
|
+
"id": "WN12-FW-000025",
|
|
1488
|
+
"title": "The Windows Firewall local firewall rules must not be merged with Group Policy settings for the Public Profile.",
|
|
1489
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Local firewall rules will not be merged with Group Policy settings on a public network to prevent Group Policy settings from being changed.",
|
|
1490
|
+
"severity": "medium"
|
|
1491
|
+
},
|
|
1492
|
+
{
|
|
1493
|
+
"id": "WN12-FW-000026",
|
|
1494
|
+
"title": "The Windows Firewall log file name and location must be configured for the Public Profile.",
|
|
1495
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The location and file name of the firewall log for a public network connection will be defined to ensure the logs are maintained.",
|
|
1496
|
+
"severity": "low"
|
|
1497
|
+
},
|
|
1498
|
+
{
|
|
1499
|
+
"id": "WN12-FW-000027",
|
|
1500
|
+
"title": "The Windows Firewall log size must be configured for the Public Profile.",
|
|
1501
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. The firewall log file size for a public network connection will be set to ensure enough capacity is allocated for audit data.",
|
|
1502
|
+
"severity": "low"
|
|
1503
|
+
},
|
|
1504
|
+
{
|
|
1505
|
+
"id": "WN12-FW-000028",
|
|
1506
|
+
"title": "The Windows Firewall must log dropped packets for the Public Profile.",
|
|
1507
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of dropped packets for a public network connection will be enabled to maintain an audit trail of potential issues.",
|
|
1508
|
+
"severity": "low"
|
|
1509
|
+
},
|
|
1510
|
+
{
|
|
1511
|
+
"id": "WN12-FW-000029",
|
|
1512
|
+
"title": "The Windows Firewall must log successful connections for the Public Profile.",
|
|
1513
|
+
"description": "A firewall provides a line of defense against attack. To be effective, it must be enabled and properly configured. Logging of successful connections for a public network connection will be enabled to maintain an audit trail if issues are discovered.",
|
|
1514
|
+
"severity": "low"
|
|
1515
|
+
},
|
|
1516
|
+
{
|
|
1517
|
+
"id": "WN12-GE-000001",
|
|
1518
|
+
"title": "Systems must be maintained at a supported service pack level.",
|
|
1519
|
+
"description": "Systems at unsupported service packs or releases will not receive security updates for new vulnerabilities, which leaves them subject to exploitation. Systems must be maintained at a service pack level supported by the vendor with new security updates.",
|
|
1520
|
+
"severity": "high"
|
|
1521
|
+
},
|
|
1522
|
+
{
|
|
1523
|
+
"id": "WN12-GE-000002",
|
|
1524
|
+
"title": "An approved DoD antivirus program must be installed and used.",
|
|
1525
|
+
"description": "Virus scan programs are a primary line of defense against the introduction of viruses and malicious code that can destroy data and even render a computer inoperable. Utilizing a virus scan program provides the ability to detect malicious code before extensive damage occurs.",
|
|
1526
|
+
"severity": "high"
|
|
1527
|
+
},
|
|
1528
|
+
{
|
|
1529
|
+
"id": "WN12-GE-000003",
|
|
1530
|
+
"title": "The antivirus program signature files must be kept updated.",
|
|
1531
|
+
"description": "Virus scan programs are a primary line of defense against the introduction of viruses and malicious code that can destroy data and even render a computer inoperable. Utilizing the virus scan program provides the ability to detect malicious code before extensive damage occurs. Updated virus scan data files help protect a system, as new malware is identified by the software vendors on a regular basis.",
|
|
1532
|
+
"severity": "high"
|
|
1533
|
+
},
|
|
1534
|
+
{
|
|
1535
|
+
"id": "WN12-GE-000004-DC",
|
|
1536
|
+
"title": "Only administrators responsible for the system must have Administrator rights on the system.",
|
|
1537
|
+
"description": "An account that does not have Administrator duties must not have Administrator rights. Such rights would allow the account to bypass or modify required security restrictions on that machine and make it vulnerable to attack.\n\nSystem administrators must log on to systems only using accounts with the minimum level of authority necessary. \n\nStandard user accounts must not be members of the built-in Administrators group.",
|
|
1538
|
+
"severity": "high"
|
|
1539
|
+
},
|
|
1540
|
+
{
|
|
1541
|
+
"id": "WN12-GE-000005",
|
|
1542
|
+
"title": "Local volumes must be formatted using NTFS.",
|
|
1543
|
+
"description": "The ability to set access permissions and auditing is critical to maintaining the security and proper access controls of a system. To support this, volumes must be formatted using the NTFS file system.",
|
|
1544
|
+
"severity": "high"
|
|
1545
|
+
},
|
|
1546
|
+
{
|
|
1547
|
+
"id": "WN12-GE-000006",
|
|
1548
|
+
"title": "Permissions for system drive root directory (usually C:) must conform to minimum requirements.",
|
|
1549
|
+
"description": "Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications.\n\nThe default permissions are adequate when the Security Option \"Network access: Let everyone permissions apply to anonymous users\" is set to \"Disabled\" (V-3377).",
|
|
1550
|
+
"severity": "medium"
|
|
1551
|
+
},
|
|
1552
|
+
{
|
|
1553
|
+
"id": "WN12-GE-000007",
|
|
1554
|
+
"title": "Permissions for program file directories must conform to minimum requirements.",
|
|
1555
|
+
"description": "Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications.\n\nThe default permissions are adequate when the Security Option \"Network access: Let everyone permissions apply to anonymous users\" is set to \"Disabled\" (V-3377).",
|
|
1556
|
+
"severity": "medium"
|
|
1557
|
+
},
|
|
1558
|
+
{
|
|
1559
|
+
"id": "WN12-GE-000008",
|
|
1560
|
+
"title": "Permissions for Windows installation directory must conform to minimum requirements.",
|
|
1561
|
+
"description": "Changing the system's file and directory permissions allows the possibility of unauthorized and anonymous modification to the operating system and installed applications.\n\nThe default permissions are adequate when the Security Option \"Network access: Let everyone permissions apply to anonymous users\" is set to \"Disabled\" (V-3377).",
|
|
1562
|
+
"severity": "medium"
|
|
1563
|
+
},
|
|
1564
|
+
{
|
|
1565
|
+
"id": "WN12-GE-000009",
|
|
1566
|
+
"title": "Password complexity software that enforces DoD requirements must be implemented.",
|
|
1567
|
+
"description": "Password complexity software (e.g., Password Policy Enforcer) enforces a minimum mix of character types and potentially other options to create strong passwords. \n\nPasswords must contain a case-sensitive character mix with at least one of each of the following: uppercase letters, lowercase letters, numbers, and special characters.\n\nSites are responsible for installing password complexity software that complies with current DoD requirements.",
|
|
1568
|
+
"severity": "medium"
|
|
1569
|
+
},
|
|
1570
|
+
{
|
|
1571
|
+
"id": "WN12-GE-000010",
|
|
1572
|
+
"title": "The system must not boot into multiple operating systems (dual-boot).",
|
|
1573
|
+
"description": "Allowing a system to boot into multiple operating systems (dual-booting) may allow security to be circumvented on a secure system.",
|
|
1574
|
+
"severity": "medium"
|
|
1575
|
+
},
|
|
1576
|
+
{
|
|
1577
|
+
"id": "WN12-GE-000011",
|
|
1578
|
+
"title": "Virtual guest operating systems must be registered in a vulnerability and asset management system.",
|
|
1579
|
+
"description": "Virtual guest operating systems share the same vulnerabilities as operating systems running on dedicated hardware and must be individually assessed for security guidance compliance. The VMS used may be DISA VMS or a similar vulnerability and asset management system.\n",
|
|
1580
|
+
"severity": "medium"
|
|
1581
|
+
},
|
|
1582
|
+
{
|
|
1583
|
+
"id": "WN12-GE-000012",
|
|
1584
|
+
"title": "Nonadministrative user accounts or groups must only have print permissions on printer shares.",
|
|
1585
|
+
"description": "Windows shares are a means by which files, folders, printers, and other resources can be published for network users to access. Improper configuration can permit access to devices and data beyond a user's need.",
|
|
1586
|
+
"severity": "low"
|
|
1587
|
+
},
|
|
1588
|
+
{
|
|
1589
|
+
"id": "WN12-GE-000013",
|
|
1590
|
+
"title": "Local users must not exist on a system in a domain.",
|
|
1591
|
+
"description": "To minimize potential points of attack, local users, other than built-in accounts such as Administrator and Guest accounts, must not exist on a workstation in a domain. Users must log onto workstations in a domain with their domain accounts.",
|
|
1592
|
+
"severity": "low"
|
|
1593
|
+
},
|
|
1594
|
+
{
|
|
1595
|
+
"id": "WN12-GE-000014",
|
|
1596
|
+
"title": "Outdated or unused accounts must be removed from the system.",
|
|
1597
|
+
"description": "Outdated or unused accounts provide penetration points that may go undetected. Inactive accounts must be deleted if no longer necessary or, if still required, disabled until needed.",
|
|
1598
|
+
"severity": "low"
|
|
1599
|
+
},
|
|
1600
|
+
{
|
|
1601
|
+
"id": "WN12-GE-000015",
|
|
1602
|
+
"title": "Accounts must require passwords.",
|
|
1603
|
+
"description": "The lack of password protection enables anyone to gain access to the information system, which opens a backdoor opportunity for intruders to compromise the system as well as other resources. Accounts on a system must require passwords.",
|
|
1604
|
+
"severity": "high"
|
|
1605
|
+
},
|
|
1606
|
+
{
|
|
1607
|
+
"id": "WN12-GE-000016",
|
|
1608
|
+
"title": "System mechanisms must be implemented to enforce automatic expiration of passwords.",
|
|
1609
|
+
"description": "Passwords that do not expire or are reused increase the exposure of a password with greater probability of being discovered or cracked.",
|
|
1610
|
+
"severity": "medium"
|
|
1611
|
+
},
|
|
1612
|
+
{
|
|
1613
|
+
"id": "WN12-GE-000017",
|
|
1614
|
+
"title": "System files must be monitored for unauthorized changes.",
|
|
1615
|
+
"description": "Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code on a system.",
|
|
1616
|
+
"severity": "medium"
|
|
1617
|
+
},
|
|
1618
|
+
{
|
|
1619
|
+
"id": "WN12-GE-000018",
|
|
1620
|
+
"title": "File shares must limit access to data on a system.",
|
|
1621
|
+
"description": "Shares on a system provide network access. To prevent exposing sensitive information, where shares are necessary, permissions must be reconfigured to give the minimum access to those accounts that require it.",
|
|
1622
|
+
"severity": "medium"
|
|
1623
|
+
},
|
|
1624
|
+
{
|
|
1625
|
+
"id": "WN12-GE-000019",
|
|
1626
|
+
"title": "The HBSS McAfee Agent must be installed.",
|
|
1627
|
+
"description": null,
|
|
1628
|
+
"severity": "medium"
|
|
1629
|
+
},
|
|
1630
|
+
{
|
|
1631
|
+
"id": "WN12-GE-000020",
|
|
1632
|
+
"title": "Software certificate installation files must be removed from a system.",
|
|
1633
|
+
"description": "Use of software certificates and their accompanying installation files for end users to access resources is less secure than the use of hardware-based certificates.",
|
|
1634
|
+
"severity": "medium"
|
|
1635
|
+
},
|
|
1636
|
+
{
|
|
1637
|
+
"id": "WN12-GE-000021",
|
|
1638
|
+
"title": "Necessary services must be documented to maintain a baseline to determine if additional, unnecessary services have been added to a system.\n",
|
|
1639
|
+
"description": "Unnecessary services increase the attack surface of a system. Some services may be run under the local System account, which generally has more permissions than required by the service. Compromising a service could allow an intruder to obtain system permissions and open the system to a variety of attacks.",
|
|
1640
|
+
"severity": "medium"
|
|
1641
|
+
},
|
|
1642
|
+
{
|
|
1643
|
+
"id": "WN12-GE-000022",
|
|
1644
|
+
"title": "Servers must have a host-based Intrusion Detection System.",
|
|
1645
|
+
"description": "A properly configured host-based Intrusion Detection System provides another level of defense against unauthorized access to critical servers. With proper configuration and logging enabled, such a system can stop and/or alert for many attempts to gain unauthorized access to resources.",
|
|
1646
|
+
"severity": "medium"
|
|
1647
|
+
},
|
|
1648
|
+
{
|
|
1649
|
+
"id": "WN12-GE-000023",
|
|
1650
|
+
"title": "The system must employ automated mechanisms or must have an application installed that, on an organization defined frequency, determines the state of information system components with regard to flaw remediation.",
|
|
1651
|
+
"description": "Organizations are required to identify information systems containing software affected by recently announced software flaws (and potential vulnerabilities resulting from those flaws) and report this information to designated organizational officials with information security responsibilities (e.g., senior information security officers, information system security managers, information systems security officers). To support this requirement, an automated process or mechanism is required.",
|
|
1652
|
+
"severity": "medium"
|
|
1653
|
+
},
|
|
1654
|
+
{
|
|
1655
|
+
"id": "WN12-GE-000024",
|
|
1656
|
+
"title": "The system must support automated patch management tools to facilitate flaw remediation to organization defined information system components.",
|
|
1657
|
+
"description": "The organization (including any contractor to the organization) must promptly install security-relevant software updates (e.g., patches, service packs, hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed.",
|
|
1658
|
+
"severity": "medium"
|
|
1659
|
+
},
|
|
1660
|
+
{
|
|
1661
|
+
"id": "WN12-GE-000025",
|
|
1662
|
+
"title": "The system must query the certification authority to determine whether a public key certificate has been revoked before accepting the certificate for authentication purposes.",
|
|
1663
|
+
"description": "Failure to verify a certificate's revocation status can result in the system accepting a revoked, and therefore unauthorized, certificate. This could result in the installation of unauthorized software or a connection for rogue networks, depending on the use for which the certificate is intended. Querying for certificate revocation mitigates the risk that the system will accept an unauthorized certificate.",
|
|
1664
|
+
"severity": "medium"
|
|
1665
|
+
},
|
|
1666
|
+
{
|
|
1667
|
+
"id": "WN12-GE-000026",
|
|
1668
|
+
"title": "FTP servers must be configured to prevent anonymous logons.",
|
|
1669
|
+
"description": "The FTP (File Transfer Protocol) service allows remote users to access shared files and directories. Allowing anonymous FTP connections makes user auditing difficult.\n\nUsing accounts that have administrator privileges to log on to FTP risks that the userid and password will be captured on the network and give administrator access to an unauthorized user.",
|
|
1670
|
+
"severity": "medium"
|
|
1671
|
+
},
|
|
1672
|
+
{
|
|
1673
|
+
"id": "WN12-GE-000027",
|
|
1674
|
+
"title": "FTP servers must be configured to prevent access to the system drive.",
|
|
1675
|
+
"description": "The FTP service allows remote users to access shared files and directories which could provide access to system resources and compromise the system, especially if the user can gain access to the root directory of the boot drive.",
|
|
1676
|
+
"severity": "high"
|
|
1677
|
+
},
|
|
1678
|
+
{
|
|
1679
|
+
"id": "WN12-GE-000100",
|
|
1680
|
+
"title": "The Enhanced Mitigation Experience Toolkit (EMET) must be installed on the system.",
|
|
1681
|
+
"description": "Attackers are constantly looking for vulnerabilities in systems and applications. The Enhanced Mitigation Experience Toolkit can enable several mechanisms, such as Data Execution Prevention (DEP), Address Space Layout Randomization (ASLR), and Structured Exception Handler Overwrite Protection (SEHOP) on the system and applications, adding additional levels of protection.",
|
|
1682
|
+
"severity": "medium"
|
|
1683
|
+
},
|
|
1684
|
+
{
|
|
1685
|
+
"id": "WN12-PK-000001",
|
|
1686
|
+
"title": "The DoD root certificate must be installed into the Trusted Root Store.",
|
|
1687
|
+
"description": "To ensure secure DoD websites and DoD signed code are properly validated, the system must trust the DoD Root CA 2. The DoD root certificate will ensure that the trust chain is established for server certificates issued from the DoD CA.",
|
|
1688
|
+
"severity": "medium"
|
|
1689
|
+
},
|
|
1690
|
+
{
|
|
1691
|
+
"id": "WN12-PK-000002",
|
|
1692
|
+
"title": "The External CA root certificate must be installed into the Trusted Root Store.",
|
|
1693
|
+
"description": "To ensure secure websites protected with ECA server certificates are properly validated, the system must trust the ECA Root CA 2. The ECA root certificate will ensure the trust chain is established for server certificates issued from the External CA.",
|
|
1694
|
+
"severity": "medium"
|
|
1695
|
+
},
|
|
1696
|
+
{
|
|
1697
|
+
"id": "WN12-PK-000003",
|
|
1698
|
+
"title": "The DoD Interoperability Root CA to DoD Root CA 2 cross-certificate must be installed into the Untrusted Certificates Store.",
|
|
1699
|
+
"description": "To ensure users do not experience denial of service when performing certificate-based authentication to DoD websites due to the system chaining to a root other than DoD Root CA 2, the DoD Interoperability Root CA to DoD Root CA 2 cross-certificate must be installed in the Untrusted Certificate Store.",
|
|
1700
|
+
"severity": "medium"
|
|
1701
|
+
},
|
|
1702
|
+
{
|
|
1703
|
+
"id": "WN12-PK-000004-DC",
|
|
1704
|
+
"title": "Domain controllers must have a PKI server certificate.",
|
|
1705
|
+
"description": "Domain controller must have a server certificate to establish authenticity as part of PKI authentications in the domain.",
|
|
1706
|
+
"severity": "medium"
|
|
1707
|
+
},
|
|
1708
|
+
{
|
|
1709
|
+
"id": "WN12-PK-000005-DC",
|
|
1710
|
+
"title": "Domain Controller PKI certificates must be issued by the DoD PKI or an approved External Certificate Authority (ECA).",
|
|
1711
|
+
"description": "A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions. The use of multiple CAs from separate PKI implementations results in interoperability issues. If servers and clients do not have a common set of root CA certificates, they are not able to authenticate each other.",
|
|
1712
|
+
"severity": "high"
|
|
1713
|
+
},
|
|
1714
|
+
{
|
|
1715
|
+
"id": "WN12-PK-000006-DC",
|
|
1716
|
+
"title": "PKI certificates associated with user accounts must be issued by the DoD PKI or an approved External Certificate Authority (ECA).",
|
|
1717
|
+
"description": "A PKI implementation depends on the practices established by the Certificate Authority (CA) to ensure the implementation is secure. Without proper practices, the certificates issued by a CA have limited value in authentication functions.",
|
|
1718
|
+
"severity": "high"
|
|
1719
|
+
},
|
|
1720
|
+
{
|
|
1721
|
+
"id": "WN12-PK-000007-DC",
|
|
1722
|
+
"title": "The directory server must be configured to use the CAC, PIV-compliant hardware token, or Alternate Logon Token (ALT) for user authentication.",
|
|
1723
|
+
"description": "PKI is a two-factor authentication technique, thus it provides a higher level of trust in the asserted identity than use of the username/password authentication technique.",
|
|
1724
|
+
"severity": "medium"
|
|
1725
|
+
},
|
|
1726
|
+
{
|
|
1727
|
+
"id": "WN12-RG-000001",
|
|
1728
|
+
"title": "Standard user accounts must only have Read permissions to the Winlogon registry key.",
|
|
1729
|
+
"description": "Permissions on the Winlogon registry key must only allow privileged accounts to change registry values. If standard users have this capability, there is a potential for programs to run with elevated privileges when a privileged user logs on to the system.",
|
|
1730
|
+
"severity": "high"
|
|
1731
|
+
},
|
|
1732
|
+
{
|
|
1733
|
+
"id": "WN12-RG-000002",
|
|
1734
|
+
"title": "Standard user accounts must only have Read permissions to the Active Setup\\Installed Components registry key.",
|
|
1735
|
+
"description": "Permissions on the Active Setup\\Installed Components registry key must only allow privileged accounts to add or change registry values. If standard user accounts have this capability, there is a potential for programs to run with elevated privileges when a privileged user logs on to the system.",
|
|
1736
|
+
"severity": "high"
|
|
1737
|
+
},
|
|
1738
|
+
{
|
|
1739
|
+
"id": "WN12-RG-000003",
|
|
1740
|
+
"title": "Local administrator accounts must have their privileged token filtered to prevent elevated privileges from being used over the network on domain systems.",
|
|
1741
|
+
"description": "A compromised local administrator account can provide means for an attacker to move laterally between domain systems. \n\nWith User Account Control enabled, filtering the privileged token for local administrator accounts will prevent the elevated privileges of these accounts from being used over the network.",
|
|
1742
|
+
"severity": "medium"
|
|
1743
|
+
},
|
|
1744
|
+
{
|
|
1745
|
+
"id": "WN12-RG-000004",
|
|
1746
|
+
"title": "Anonymous access to the registry must be restricted.",
|
|
1747
|
+
"description": "The registry is integral to the function, security, and stability of the Windows system. Some processes may require anonymous access to the registry. This must be limited to properly protect the system.",
|
|
1748
|
+
"severity": "high"
|
|
1749
|
+
},
|
|
1750
|
+
{
|
|
1751
|
+
"id": "WN12-SO-000003",
|
|
1752
|
+
"title": "The built-in guest account must be disabled.",
|
|
1753
|
+
"description": "A system faces an increased vulnerability threat if the built-in guest account is not disabled. This account is a known account that exists on all Windows systems and cannot be deleted. This account is initialized during the installation of the operating system with no password assigned.",
|
|
1754
|
+
"severity": "medium"
|
|
1755
|
+
},
|
|
1756
|
+
{
|
|
1757
|
+
"id": "WN12-SO-000004",
|
|
1758
|
+
"title": "Local accounts with blank passwords must be restricted to prevent access from the network.",
|
|
1759
|
+
"description": "An account without a password can allow unauthorized access to a system as only the username would be required. Password policies should prevent accounts with blank passwords from existing on a system. However, if a local account with a blank password did exist, enabling this setting will prevent network access, limiting the account to local console logon only.",
|
|
1760
|
+
"severity": "high"
|
|
1761
|
+
},
|
|
1762
|
+
{
|
|
1763
|
+
"id": "WN12-SO-000005",
|
|
1764
|
+
"title": "The built-in administrator account must be renamed.",
|
|
1765
|
+
"description": "The built-in administrator account is a well-known account subject to attack. Renaming this account to an unidentified name improves the protection of this account and the system.",
|
|
1766
|
+
"severity": "medium"
|
|
1767
|
+
},
|
|
1768
|
+
{
|
|
1769
|
+
"id": "WN12-SO-000006",
|
|
1770
|
+
"title": "The built-in guest account must be renamed.",
|
|
1771
|
+
"description": "The built-in guest account is a well-known user account on all Windows systems and, as initially installed, does not require a password. This can allow access to system resources by unauthorized users. Renaming this account to an unidentified name improves the protection of this account and the system.",
|
|
1772
|
+
"severity": "medium"
|
|
1773
|
+
},
|
|
1774
|
+
{
|
|
1775
|
+
"id": "WN12-SO-000007",
|
|
1776
|
+
"title": "Auditing the Access to Global System Objects must be turned off.",
|
|
1777
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.\nThis setting prevents the system from setting up a default system access control list for certain system objects, which could create a very large number of security events, filling the security log in Windows and making it difficult to identify actual issues.\n",
|
|
1778
|
+
"severity": "medium"
|
|
1779
|
+
},
|
|
1780
|
+
{
|
|
1781
|
+
"id": "WN12-SO-000008",
|
|
1782
|
+
"title": "Auditing of Backup and Restore Privileges must be turned off.",
|
|
1783
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. \nThis setting prevents the system from generating audit events for every file backed up or restored, which could fill the security log in Windows, making it difficult to identify actual issues.",
|
|
1784
|
+
"severity": "medium"
|
|
1785
|
+
},
|
|
1786
|
+
{
|
|
1787
|
+
"id": "WN12-SO-000009",
|
|
1788
|
+
"title": "Audit policy using subcategories must be enabled.",
|
|
1789
|
+
"description": "Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. \nThis setting allows administrators to enable more precise auditing capabilities.",
|
|
1790
|
+
"severity": "medium"
|
|
1791
|
+
},
|
|
1792
|
+
{
|
|
1793
|
+
"id": "WN12-SO-000011",
|
|
1794
|
+
"title": "Ejection of removable NTFS media must be restricted to Administrators.",
|
|
1795
|
+
"description": "Removable hard drives, if they are not properly configured, can be formatted and ejected by users who are not members of the Administrators Group. Formatting and ejecting removable NTFS media must only be done by administrators.",
|
|
1796
|
+
"severity": "medium"
|
|
1797
|
+
},
|
|
1798
|
+
{
|
|
1799
|
+
"id": "WN12-SO-000012",
|
|
1800
|
+
"title": "Outgoing secure channel traffic must be encrypted or signed.",
|
|
1801
|
+
"description": "Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but not all information is encrypted. If this policy is enabled, outgoing secure channel traffic will be encrypted and signed.",
|
|
1802
|
+
"severity": "medium"
|
|
1803
|
+
},
|
|
1804
|
+
{
|
|
1805
|
+
"id": "WN12-SO-000013",
|
|
1806
|
+
"title": "Outgoing secure channel traffic must be encrypted when possible.",
|
|
1807
|
+
"description": "Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but not all information is encrypted. If this policy is enabled, outgoing secure channel traffic will be encrypted.",
|
|
1808
|
+
"severity": "medium"
|
|
1809
|
+
},
|
|
1810
|
+
{
|
|
1811
|
+
"id": "WN12-SO-000014",
|
|
1812
|
+
"title": "Outgoing secure channel traffic must be signed when possible.",
|
|
1813
|
+
"description": "Requests sent on the secure channel are authenticated, and sensitive information (such as passwords) is encrypted, but the channel is not integrity checked. If this policy is enabled, outgoing secure channel traffic will be signed.",
|
|
1814
|
+
"severity": "medium"
|
|
1815
|
+
},
|
|
1816
|
+
{
|
|
1817
|
+
"id": "WN12-SO-000015",
|
|
1818
|
+
"title": "The computer account password must not be prevented from being reset.",
|
|
1819
|
+
"description": "Computer account passwords are changed automatically on a regular basis. Disabling automatic password changes can make the system more vulnerable to malicious access. Frequent password changes can be a significant safeguard for your system. A new password for the computer account will be generated every 30 days.",
|
|
1820
|
+
"severity": "low"
|
|
1821
|
+
},
|
|
1822
|
+
{
|
|
1823
|
+
"id": "WN12-SO-000016",
|
|
1824
|
+
"title": "The maximum age for machine account passwords must be set to requirements.",
|
|
1825
|
+
"description": "Computer account passwords are changed automatically on a regular basis. This setting controls the maximum password age that a machine account may have. This setting must be set to no more than 30 days, ensuring the machine changes its password monthly.",
|
|
1826
|
+
"severity": "low"
|
|
1827
|
+
},
|
|
1828
|
+
{
|
|
1829
|
+
"id": "WN12-SO-000017",
|
|
1830
|
+
"title": "The system must be configured to require a strong session key.",
|
|
1831
|
+
"description": "A computer connecting to a domain controller will establish a secure channel. Requiring strong session keys enforces 128-bit encryption between systems.",
|
|
1832
|
+
"severity": "medium"
|
|
1833
|
+
},
|
|
1834
|
+
{
|
|
1835
|
+
"id": "WN12-SO-000018",
|
|
1836
|
+
"title": "The system must be configured to prevent the display of the last username on the logon screen.",
|
|
1837
|
+
"description": "Displaying the username of the last logged on user provides half of the userid/password equation that an unauthorized person would need to gain access. The username of the last user to log on to a system must not be displayed.",
|
|
1838
|
+
"severity": "low"
|
|
1839
|
+
},
|
|
1840
|
+
{
|
|
1841
|
+
"id": "WN12-SO-000019",
|
|
1842
|
+
"title": "The Ctrl+Alt+Del security attention sequence for logons must be enabled.",
|
|
1843
|
+
"description": "Disabling the Ctrl+Alt+Del security attention sequence can compromise system security. Because only Windows responds to the Ctrl+Alt+Del security sequence, a user can be assured that any passwords entered following that sequence are sent only to Windows. If the sequence requirement is eliminated, malicious programs can request and receive a user's Windows password. Disabling this sequence also suppresses a custom logon banner.",
|
|
1844
|
+
"severity": "medium"
|
|
1845
|
+
},
|
|
1846
|
+
{
|
|
1847
|
+
"id": "WN12-SO-000020",
|
|
1848
|
+
"title": "The machine account lockout threshold must be set to 10 on systems with BitLocker enabled.",
|
|
1849
|
+
"description": "The account lockout feature, when enabled, prevents brute-force password attacks on the system. The higher this value is, the less effective the account lockout feature will be in protecting the local system. The number of bad logon attempts should be reasonably small to minimize the possibility of a successful password attack, while allowing for honest errors made during a normal user logon.",
|
|
1850
|
+
"severity": "medium"
|
|
1851
|
+
},
|
|
1852
|
+
{
|
|
1853
|
+
"id": "WN12-SO-000021",
|
|
1854
|
+
"title": "The machine inactivity limit must be set to 15 minutes, locking the system with the screensaver.",
|
|
1855
|
+
"description": "Unattended systems are susceptible to unauthorized use and should be locked when unattended. The screen saver should be set at a maximum of 15 minutes and be password protected. This protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.",
|
|
1856
|
+
"severity": "medium"
|
|
1857
|
+
},
|
|
1858
|
+
{
|
|
1859
|
+
"id": "WN12-SO-000022",
|
|
1860
|
+
"title": "The required legal notice must be configured to display before console logon.",
|
|
1861
|
+
"description": "Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.",
|
|
1862
|
+
"severity": "medium"
|
|
1863
|
+
},
|
|
1864
|
+
{
|
|
1865
|
+
"id": "WN12-SO-000023",
|
|
1866
|
+
"title": "The Windows dialog box title for the legal banner must be configured.",
|
|
1867
|
+
"description": "Failure to display the logon banner prior to a logon attempt will negate legal proceedings resulting from unauthorized access to system resources.",
|
|
1868
|
+
"severity": "low"
|
|
1869
|
+
},
|
|
1870
|
+
{
|
|
1871
|
+
"id": "WN12-SO-000024",
|
|
1872
|
+
"title": "Caching of logon credentials must be limited.",
|
|
1873
|
+
"description": "The default Windows configuration caches the last logon credentials for users who log on interactively to a system. This feature is provided for system availability reasons, such as the user's machine being disconnected from the network or domain controllers being unavailable. Even though the credential cache is well protected, storing encrypted copies of users' passwords on workstations does not always have the same physical protection required for domain controllers. If a workstation is attacked, an unauthorized individual may isolate the password to a domain user account using a password-cracking program and gain access to the domain.",
|
|
1874
|
+
"severity": "low"
|
|
1875
|
+
},
|
|
1876
|
+
{
|
|
1877
|
+
"id": "WN12-SO-000025",
|
|
1878
|
+
"title": "Users must be warned in advance of their passwords expiring.",
|
|
1879
|
+
"description": "Creating strong passwords that can be remembered by users requires some thought. By giving the user advance warning, the user has time to construct a sufficiently strong password. This setting configures the system to display a warning to users telling them how many days are left before their password expires.",
|
|
1880
|
+
"severity": "low"
|
|
1881
|
+
},
|
|
1882
|
+
{
|
|
1883
|
+
"id": "WN12-SO-000027",
|
|
1884
|
+
"title": "The Smart Card removal option must be configured to Force Logoff or Lock Workstation.",
|
|
1885
|
+
"description": "Unattended systems are susceptible to unauthorized use and must be locked. Configuring a system to lock when a smart card is removed will ensure the system is inaccessible when unattended.",
|
|
1886
|
+
"severity": "medium"
|
|
1887
|
+
},
|
|
1888
|
+
{
|
|
1889
|
+
"id": "WN12-SO-000028",
|
|
1890
|
+
"title": "The Windows SMB client must be configured to always perform SMB packet signing.",
|
|
1891
|
+
"description": "The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB client will only communicate with an SMB server that performs SMB packet signing.",
|
|
1892
|
+
"severity": "medium"
|
|
1893
|
+
},
|
|
1894
|
+
{
|
|
1895
|
+
"id": "WN12-SO-000029",
|
|
1896
|
+
"title": "The Windows SMB client must be enabled to perform SMB packet signing when possible.",
|
|
1897
|
+
"description": "The server message block (SMB) protocol provides the basis for many network operations. If this policy is enabled, the SMB client will request packet signing when communicating with an SMB server that is enabled or required to perform SMB packet signing.",
|
|
1898
|
+
"severity": "medium"
|
|
1899
|
+
},
|
|
1900
|
+
{
|
|
1901
|
+
"id": "WN12-SO-000030",
|
|
1902
|
+
"title": "Unencrypted passwords must not be sent to a third-party SMB server.",
|
|
1903
|
+
"description": "Some non-Microsoft SMB servers only support unencrypted (plain text) password authentication. Sending plain text passwords across the network, when authenticating to an SMB server, reduces the overall security of the environment. Check with the vendor of the SMB server to see if there is a way to support encrypted password authentication.",
|
|
1904
|
+
"severity": "medium"
|
|
1905
|
+
},
|
|
1906
|
+
{
|
|
1907
|
+
"id": "WN12-SO-000031",
|
|
1908
|
+
"title": "The amount of idle time required before suspending a session must be properly set.",
|
|
1909
|
+
"description": "Open sessions can increase the avenues of attack on a system. This setting is used to control when a computer disconnects an inactive SMB session. If client activity resumes, the session is automatically reestablished. This protects critical and sensitive network data from exposure to unauthorized personnel with physical access to the computer.",
|
|
1910
|
+
"severity": "low"
|
|
1911
|
+
},
|
|
1912
|
+
{
|
|
1913
|
+
"id": "WN12-SO-000032",
|
|
1914
|
+
"title": "The Windows SMB server must be configured to always perform SMB packet signing.",
|
|
1915
|
+
"description": "The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB server will only communicate with an SMB client that performs SMB packet signing.",
|
|
1916
|
+
"severity": "medium"
|
|
1917
|
+
},
|
|
1918
|
+
{
|
|
1919
|
+
"id": "WN12-SO-000033",
|
|
1920
|
+
"title": "The Windows SMB server must perform SMB packet signing when possible.",
|
|
1921
|
+
"description": "The server message block (SMB) protocol provides the basis for many network operations. Digitally signed SMB packets aid in preventing man-in-the-middle attacks. If this policy is enabled, the SMB server will negotiate SMB packet signing as requested by the client.",
|
|
1922
|
+
"severity": "medium"
|
|
1923
|
+
},
|
|
1924
|
+
{
|
|
1925
|
+
"id": "WN12-SO-000034",
|
|
1926
|
+
"title": "Users must be forcibly disconnected when their logon hours expire.",
|
|
1927
|
+
"description": "Users must not be permitted to remain logged on to the network after they have exceeded their permitted logon hours. In many cases, this indicates that a user forgot to log off before leaving for the day. However, it may also indicate that a user is attempting unauthorized access at a time when the system may be less closely monitored. Forcibly disconnecting users when logon hours expire protects critical and sensitive network data from exposure to unauthorized personnel with physical access to the computer.",
|
|
1928
|
+
"severity": "low"
|
|
1929
|
+
},
|
|
1930
|
+
{
|
|
1931
|
+
"id": "WN12-SO-000035",
|
|
1932
|
+
"title": "The service principal name (SPN) target name validation level must be turned off.",
|
|
1933
|
+
"description": "If a service principle name (SPN) is provided by the client, it is validated against the server's list of SPNs. Implementation may disrupt file and print sharing capabilities.",
|
|
1934
|
+
"severity": "medium"
|
|
1935
|
+
},
|
|
1936
|
+
{
|
|
1937
|
+
"id": "WN12-SO-000036",
|
|
1938
|
+
"title": "Automatic logons must be disabled.",
|
|
1939
|
+
"description": "Allowing a system to automatically log on when the machine is booted could give access to any unauthorized individual who restarts the computer. Automatic logon with administrator privileges would give full access to an unauthorized individual.",
|
|
1940
|
+
"severity": "medium"
|
|
1941
|
+
},
|
|
1942
|
+
{
|
|
1943
|
+
"id": "WN12-SO-000037",
|
|
1944
|
+
"title": "IPv6 source routing must be configured to the highest protection level.",
|
|
1945
|
+
"description": "Configuring the system to disable IPv6 source routing protects against spoofing.",
|
|
1946
|
+
"severity": "low"
|
|
1947
|
+
},
|
|
1948
|
+
{
|
|
1949
|
+
"id": "WN12-SO-000038",
|
|
1950
|
+
"title": "The system must be configured to prevent IP source routing.",
|
|
1951
|
+
"description": "Configuring the system to disable IP source routing protects against spoofing.",
|
|
1952
|
+
"severity": "low"
|
|
1953
|
+
},
|
|
1954
|
+
{
|
|
1955
|
+
"id": "WN12-SO-000039",
|
|
1956
|
+
"title": "The system must be configured to prevent Internet Control Message Protocol (ICMP) redirects from overriding Open Shortest Path First (OSPF) generated routes.",
|
|
1957
|
+
"description": "Allowing ICMP redirect of routes can lead to traffic not being routed properly. When disabled, this forces ICMP to be routed via shortest path first.",
|
|
1958
|
+
"severity": "low"
|
|
1959
|
+
},
|
|
1960
|
+
{
|
|
1961
|
+
"id": "WN12-SO-000041",
|
|
1962
|
+
"title": "The system must be configured to limit how often keep-alive packets are sent.",
|
|
1963
|
+
"description": "This setting controls how often TCP sends a keep-alive packet in attempting to verify that an idle connection is still intact. A higher value could allow an attacker to cause a denial of service with numerous connections.",
|
|
1964
|
+
"severity": "low"
|
|
1965
|
+
},
|
|
1966
|
+
{
|
|
1967
|
+
"id": "WN12-SO-000042",
|
|
1968
|
+
"title": "IPSec exemptions must be limited.",
|
|
1969
|
+
"description": "IPSec exemption filters allow specific traffic that may be needed by the system for such things as Kerberos authentication. This setting configures Windows for specific IPSec exemptions.",
|
|
1970
|
+
"severity": "low"
|
|
1971
|
+
},
|
|
1972
|
+
{
|
|
1973
|
+
"id": "WN12-SO-000043",
|
|
1974
|
+
"title": "The system must be configured to ignore NetBIOS name release requests except from WINS servers.",
|
|
1975
|
+
"description": "Configuring the system to ignore name release requests, except from WINS servers, prevents a denial of service (DoS) attack. The DoS consists of sending a NetBIOS name release request to the server for each entry in the server's cache, causing a response delay in the normal operation of the servers WINS resolution capability.",
|
|
1976
|
+
"severity": "low"
|
|
1977
|
+
},
|
|
1978
|
+
{
|
|
1979
|
+
"id": "WN12-SO-000044",
|
|
1980
|
+
"title": "The system must be configured to disable the Internet Router Discovery Protocol (IRDP).",
|
|
1981
|
+
"description": "The Internet Router Discovery Protocol (IRDP) is used to detect and configure default gateway addresses on the computer. If a router is impersonated on a network, traffic could be routed through the compromised system.",
|
|
1982
|
+
"severity": "low"
|
|
1983
|
+
},
|
|
1984
|
+
{
|
|
1985
|
+
"id": "WN12-SO-000045",
|
|
1986
|
+
"title": "The system must be configured to use Safe DLL Search Mode.",
|
|
1987
|
+
"description": "The default search behavior, when an application calls a function in a Dynamic Link Library (DLL), is to search the current directory, followed by the directories contained in the system's path environment variable. An unauthorized DLL, inserted into an application's working directory, could allow malicious code to be run on the system. Setting this policy value forces the system to search the %Systemroot% for the DLL before searching the current directory or the rest of the path.",
|
|
1988
|
+
"severity": "medium"
|
|
1989
|
+
},
|
|
1990
|
+
{
|
|
1991
|
+
"id": "WN12-SO-000046",
|
|
1992
|
+
"title": "The system must be configured to have password protection take effect within a limited time frame when the screen saver becomes active.",
|
|
1993
|
+
"description": "Allowing more than several seconds makes the computer vulnerable to a potential attack from someone walking up to the console to attempt to log on to the system before the lock takes effect.",
|
|
1994
|
+
"severity": "low"
|
|
1995
|
+
},
|
|
1996
|
+
{
|
|
1997
|
+
"id": "WN12-SO-000047",
|
|
1998
|
+
"title": "IPv6 TCP data retransmissions must be configured to prevent resources from becoming exhausted.",
|
|
1999
|
+
"description": "Configuring Windows to limit the number of times that IPv6 TCP retransmits unacknowledged data segments before aborting the attempt helps prevent resources from becoming exhausted.",
|
|
2000
|
+
"severity": "low"
|
|
2001
|
+
},
|
|
2002
|
+
{
|
|
2003
|
+
"id": "WN12-SO-000048",
|
|
2004
|
+
"title": "The system must limit how many times unacknowledged TCP data is retransmitted.",
|
|
2005
|
+
"description": "In a SYN flood attack, the attacker sends a continuous stream of SYN packets to a server, and the server leaves the half-open connections open until it is overwhelmed and is no longer able to respond to legitimate requests.",
|
|
2006
|
+
"severity": "low"
|
|
2007
|
+
},
|
|
2008
|
+
{
|
|
2009
|
+
"id": "WN12-SO-000049",
|
|
2010
|
+
"title": "The system must generate an audit event when the audit log reaches a percentage of full threshold.",
|
|
2011
|
+
"description": "When the audit log reaches a given percent full, an audit event is written to the security log. It is recorded as a successful audit event under the category of System. This option may be especially useful if the audit logs are set to be cleared manually.",
|
|
2012
|
+
"severity": "low"
|
|
2013
|
+
},
|
|
2014
|
+
{
|
|
2015
|
+
"id": "WN12-SO-000050",
|
|
2016
|
+
"title": "Anonymous SID/Name translation must not be allowed.",
|
|
2017
|
+
"description": "Allowing anonymous SID/Name translation can provide sensitive information for accessing a system. Only authorized users must be able to perform such translations.",
|
|
2018
|
+
"severity": "high"
|
|
2019
|
+
},
|
|
2020
|
+
{
|
|
2021
|
+
"id": "WN12-SO-000051",
|
|
2022
|
+
"title": "Anonymous enumeration of SAM accounts must not be allowed.",
|
|
2023
|
+
"description": "Anonymous enumeration of SAM accounts allows anonymous log on users (null session connections) to list all accounts names, thus providing a list of potential points to attack the system.",
|
|
2024
|
+
"severity": "high"
|
|
2025
|
+
},
|
|
2026
|
+
{
|
|
2027
|
+
"id": "WN12-SO-000052",
|
|
2028
|
+
"title": "Anonymous enumeration of shares must be restricted.",
|
|
2029
|
+
"description": "Allowing anonymous logon users (null session connections) to list all account names and enumerate all shared resources can provide a map of potential points to attack the system.",
|
|
2030
|
+
"severity": "high"
|
|
2031
|
+
},
|
|
2032
|
+
{
|
|
2033
|
+
"id": "WN12-SO-000053",
|
|
2034
|
+
"title": "The system must be configured to prevent the storage of passwords and credentials.",
|
|
2035
|
+
"description": "This setting controls the storage of passwords and credentials for network authentication on the local system. Such credentials must not be stored on the local machine, as that may lead to account compromise.",
|
|
2036
|
+
"severity": "medium"
|
|
2037
|
+
},
|
|
2038
|
+
{
|
|
2039
|
+
"id": "WN12-SO-000054",
|
|
2040
|
+
"title": "The system must be configured to prevent anonymous users from having the same rights as the Everyone group.",
|
|
2041
|
+
"description": "Access by anonymous users must be restricted. If this setting is enabled, then anonymous users have the same rights and permissions as the built-in Everyone group. Anonymous users must not have these permissions or rights.",
|
|
2042
|
+
"severity": "medium"
|
|
2043
|
+
},
|
|
2044
|
+
{
|
|
2045
|
+
"id": "WN12-SO-000055-DC",
|
|
2046
|
+
"title": "Named pipes that can be accessed anonymously must be configured with limited values on domain controllers.",
|
|
2047
|
+
"description": "Named pipes that can be accessed anonymously provide the potential for gaining unauthorized system access. Pipes are internal system communications processes. They are identified internally by ID numbers that vary between systems. To make access to these processes easier, these pipes are given names that do not vary between systems. This setting controls which of these pipes anonymous users may access.",
|
|
2048
|
+
"severity": "high"
|
|
2049
|
+
},
|
|
2050
|
+
{
|
|
2051
|
+
"id": "WN12-SO-000056",
|
|
2052
|
+
"title": "Unauthorized remotely accessible registry paths must not be configured.",
|
|
2053
|
+
"description": "The registry is integral to the function, security, and stability of the Windows system. Some processes may require remote access to the registry. This setting controls which registry paths are accessible from a remote computer. These registry paths must be limited, as they could give unauthorized individuals access to the registry.",
|
|
2054
|
+
"severity": "high"
|
|
2055
|
+
},
|
|
2056
|
+
{
|
|
2057
|
+
"id": "WN12-SO-000057",
|
|
2058
|
+
"title": "Unauthorized remotely accessible registry paths and sub-paths must not be configured.",
|
|
2059
|
+
"description": "The registry is integral to the function, security, and stability of the Windows system. Some processes may require remote access to the registry. This setting controls which registry paths and sub-paths are accessible from a remote computer. These registry paths must be limited, as they could give unauthorized individuals access to the registry.",
|
|
2060
|
+
"severity": "high"
|
|
2061
|
+
},
|
|
2062
|
+
{
|
|
2063
|
+
"id": "WN12-SO-000058",
|
|
2064
|
+
"title": "Anonymous access to Named Pipes and Shares must be restricted.",
|
|
2065
|
+
"description": "Allowing anonymous access to named pipes or shares provides the potential for unauthorized system access. This setting restricts access to those defined in \"Network access: Named Pipes that can be accessed anonymously\" and \"Network access: Shares that can be accessed anonymously\", both of which must be blank under other requirements.",
|
|
2066
|
+
"severity": "high"
|
|
2067
|
+
},
|
|
2068
|
+
{
|
|
2069
|
+
"id": "WN12-SO-000059",
|
|
2070
|
+
"title": "Network shares that can be accessed anonymously must not be allowed.",
|
|
2071
|
+
"description": "Anonymous access to network shares provides the potential for gaining unauthorized system access by network users. This could lead to the exposure or corruption of sensitive data.",
|
|
2072
|
+
"severity": "high"
|
|
2073
|
+
},
|
|
2074
|
+
{
|
|
2075
|
+
"id": "WN12-SO-000060",
|
|
2076
|
+
"title": "The system must be configured to use the Classic security model.",
|
|
2077
|
+
"description": "Windows includes two network-sharing security models - Classic and Guest only. With the Classic model, local accounts must be password protected; otherwise, anyone can use guest user accounts to access shared system resources.",
|
|
2078
|
+
"severity": "medium"
|
|
2079
|
+
},
|
|
2080
|
+
{
|
|
2081
|
+
"id": "WN12-SO-000061",
|
|
2082
|
+
"title": "Services using Local System that use Negotiate when reverting to NTLM authentication must use the computer identity vs. authenticating anonymously.",
|
|
2083
|
+
"description": "Services using Local System that use Negotiate when reverting to NTLM authentication may gain unauthorized access if allowed to authenticate anonymously vs. using the computer identity.",
|
|
2084
|
+
"severity": "medium"
|
|
2085
|
+
},
|
|
2086
|
+
{
|
|
2087
|
+
"id": "WN12-SO-000062",
|
|
2088
|
+
"title": "NTLM must be prevented from falling back to a Null session.",
|
|
2089
|
+
"description": "NTLM sessions that are allowed to fall back to Null (unauthenticated) sessions may gain unauthorized access.",
|
|
2090
|
+
"severity": "medium"
|
|
2091
|
+
},
|
|
2092
|
+
{
|
|
2093
|
+
"id": "WN12-SO-000063",
|
|
2094
|
+
"title": "PKU2U authentication using online identities must be prevented.",
|
|
2095
|
+
"description": "PKU2U is a peer-to-peer authentication protocol. This setting prevents online identities from authenticating to domain-joined systems. Authentication will be centrally managed with Windows user accounts.",
|
|
2096
|
+
"severity": "medium"
|
|
2097
|
+
},
|
|
2098
|
+
{
|
|
2099
|
+
"id": "WN12-SO-000064",
|
|
2100
|
+
"title": "Kerberos encryption types must be configured to prevent the use of DES encryption suites.",
|
|
2101
|
+
"description": "Certain encryption types are no longer considered secure. This setting configures a minimum encryption type for Kerberos, preventing the use of the DES encryption suites.",
|
|
2102
|
+
"severity": "medium"
|
|
2103
|
+
},
|
|
2104
|
+
{
|
|
2105
|
+
"id": "WN12-SO-000065",
|
|
2106
|
+
"title": "The system must be configured to prevent the storage of the LAN Manager hash of passwords.",
|
|
2107
|
+
"description": "The LAN Manager hash uses a weak encryption algorithm and there are several tools available that use this hash to retrieve account passwords. This setting controls whether or not a LAN Manager hash of the password is stored in the SAM the next time the password is changed.",
|
|
2108
|
+
"severity": "high"
|
|
2109
|
+
},
|
|
2110
|
+
{
|
|
2111
|
+
"id": "WN12-SO-000066",
|
|
2112
|
+
"title": "The system must be configured to force users to log off when their allowed logon hours expire.",
|
|
2113
|
+
"description": "Limiting logon hours can help protect data by only allowing access during specified times. This setting controls whether or not users are forced to log off when their allowed logon hours expire. If logon hours are set for users, this must be enforced.",
|
|
2114
|
+
"severity": "medium"
|
|
2115
|
+
},
|
|
2116
|
+
{
|
|
2117
|
+
"id": "WN12-SO-000067",
|
|
2118
|
+
"title": "The LanMan authentication level must be set to send NTLMv2 response only, and to refuse LM and NTLM.",
|
|
2119
|
+
"description": "The Kerberos v5 authentication protocol is the default for authentication of users who are logging on to domain accounts. NTLM, which is less secure, is retained in later Windows versions for compatibility with clients and servers that are running earlier versions of Windows or applications that still use it. It is also used to authenticate logons to stand-alone computers that are running later versions.",
|
|
2120
|
+
"severity": "high"
|
|
2121
|
+
},
|
|
2122
|
+
{
|
|
2123
|
+
"id": "WN12-SO-000068",
|
|
2124
|
+
"title": "The system must be configured to the required LDAP client signing level.",
|
|
2125
|
+
"description": "This setting controls the signing requirements for LDAP clients. This setting must be set to Negotiate signing or Require signing, depending on the environment and type of LDAP server in use.",
|
|
2126
|
+
"severity": "medium"
|
|
2127
|
+
},
|
|
2128
|
+
{
|
|
2129
|
+
"id": "WN12-SO-000069",
|
|
2130
|
+
"title": "The system must be configured to meet the minimum session security requirement for NTLM SSP-based clients.",
|
|
2131
|
+
"description": "Microsoft has implemented a variety of security support providers for use with RPC sessions. All of the options must be enabled to ensure the maximum security level.",
|
|
2132
|
+
"severity": "medium"
|
|
2133
|
+
},
|
|
2134
|
+
{
|
|
2135
|
+
"id": "WN12-SO-000070",
|
|
2136
|
+
"title": "The system must be configured to meet the minimum session security requirement for NTLM SSP-based servers.",
|
|
2137
|
+
"description": "Microsoft has implemented a variety of security support providers for use with RPC sessions. All of the options must be enabled to ensure the maximum security level.",
|
|
2138
|
+
"severity": "medium"
|
|
2139
|
+
},
|
|
2140
|
+
{
|
|
2141
|
+
"id": "WN12-SO-000071",
|
|
2142
|
+
"title": "The Recovery Console option must be set to prevent automatic logon to the system.",
|
|
2143
|
+
"description": "If this option is enabled, the Recovery Console does not require a password and automatically logs on to the system. This could allow unauthorized administrative access to the system.",
|
|
2144
|
+
"severity": "high"
|
|
2145
|
+
},
|
|
2146
|
+
{
|
|
2147
|
+
"id": "WN12-SO-000072",
|
|
2148
|
+
"title": "The Recovery Console SET command must be disabled.",
|
|
2149
|
+
"description": "The Recovery Console SET command allows environment variables to be set in the Recovery Console. This permits access to all drives and folders and the copying of files to removable media, which could expose sensitive information.",
|
|
2150
|
+
"severity": "low"
|
|
2151
|
+
},
|
|
2152
|
+
{
|
|
2153
|
+
"id": "WN12-SO-000073",
|
|
2154
|
+
"title": "The shutdown option must not be available from the logon dialog box.",
|
|
2155
|
+
"description": "Displaying the shutdown button may allow individuals to shut down a system anonymously. Only authenticated users should be allowed to shut down the system. Preventing display of this button in the logon dialog box ensures that individuals who shut down the system are authorized and tracked in the system's Security event log.",
|
|
2156
|
+
"severity": "low"
|
|
2157
|
+
},
|
|
2158
|
+
{
|
|
2159
|
+
"id": "WN12-SO-000074",
|
|
2160
|
+
"title": "The system must be configured to use FIPS-compliant algorithms for encryption, hashing, and signing.",
|
|
2161
|
+
"description": "This setting ensures that the system uses algorithms that are FIPS-compliant for encryption, hashing, and signing. FIPS-compliant algorithms meet specific standards established by the U.S. Government and must be the algorithms used for all OS encryption functions.",
|
|
2162
|
+
"severity": "medium"
|
|
2163
|
+
},
|
|
2164
|
+
{
|
|
2165
|
+
"id": "WN12-SO-000075",
|
|
2166
|
+
"title": "The system must be configured to require case insensitivity for non-Windows subsystems.",
|
|
2167
|
+
"description": "This setting controls the behavior of non-Windows subsystems when dealing with the case of arguments or commands. Case sensitivity could lead to the access of files or commands that must be restricted. To prevent this from happening, case insensitivity restrictions must be required.",
|
|
2168
|
+
"severity": "medium"
|
|
2169
|
+
},
|
|
2170
|
+
{
|
|
2171
|
+
"id": "WN12-SO-000076",
|
|
2172
|
+
"title": "The default permissions of global system objects must be increased.",
|
|
2173
|
+
"description": "Windows systems maintain a global list of shared system resources such as DOS device names, mutexes, and semaphores. Each type of object is created with a default DACL that specifies who can access the objects with what permissions. If this policy is enabled, the default DACL is stronger, allowing nonadministrative users to read shared objects, but not modify shared objects that they did not create.",
|
|
2174
|
+
"severity": "low"
|
|
2175
|
+
},
|
|
2176
|
+
{
|
|
2177
|
+
"id": "WN12-SO-000077",
|
|
2178
|
+
"title": "User Account Control approval mode for the built-in Administrator must be enabled.",
|
|
2179
|
+
"description": "User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures the built-in Administrator account so that it runs in Admin Approval Mode.",
|
|
2180
|
+
"severity": "medium"
|
|
2181
|
+
},
|
|
2182
|
+
{
|
|
2183
|
+
"id": "WN12-SO-000078",
|
|
2184
|
+
"title": "User Account Control must, at minimum, prompt administrators for consent.",
|
|
2185
|
+
"description": "User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures the elevation requirements for logged on administrators to complete a task that requires raised privileges.",
|
|
2186
|
+
"severity": "medium"
|
|
2187
|
+
},
|
|
2188
|
+
{
|
|
2189
|
+
"id": "WN12-SO-000079",
|
|
2190
|
+
"title": "User Account Control must automatically deny standard user requests for elevation.",
|
|
2191
|
+
"description": "User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting controls the behavior of elevation when requested by a standard user account.",
|
|
2192
|
+
"severity": "medium"
|
|
2193
|
+
},
|
|
2194
|
+
{
|
|
2195
|
+
"id": "WN12-SO-000080",
|
|
2196
|
+
"title": "User Account Control must be configured to detect application installations and prompt for elevation.",
|
|
2197
|
+
"description": "User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting requires Windows to respond to application installation requests by prompting for credentials.",
|
|
2198
|
+
"severity": "medium"
|
|
2199
|
+
},
|
|
2200
|
+
{
|
|
2201
|
+
"id": "WN12-SO-000081",
|
|
2202
|
+
"title": "Windows must elevate all applications in User Account Control, not just signed ones.",
|
|
2203
|
+
"description": "User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures whether Windows elevates all applications, or only signed ones.",
|
|
2204
|
+
"severity": "medium"
|
|
2205
|
+
},
|
|
2206
|
+
{
|
|
2207
|
+
"id": "WN12-SO-000082",
|
|
2208
|
+
"title": "User Account Control must only elevate UIAccess applications that are installed in secure locations.",
|
|
2209
|
+
"description": "User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures Windows to only allow applications installed in a secure location on the file system, such as the Program Files or the Windows\\System32 folders, to run with elevated privileges.",
|
|
2210
|
+
"severity": "medium"
|
|
2211
|
+
},
|
|
2212
|
+
{
|
|
2213
|
+
"id": "WN12-SO-000083",
|
|
2214
|
+
"title": "User Account Control must run all administrators in Admin Approval Mode, enabling UAC.",
|
|
2215
|
+
"description": "User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting enables UAC.",
|
|
2216
|
+
"severity": "medium"
|
|
2217
|
+
},
|
|
2218
|
+
{
|
|
2219
|
+
"id": "WN12-SO-000084",
|
|
2220
|
+
"title": "User Account Control must switch to the secure desktop when prompting for elevation.",
|
|
2221
|
+
"description": "User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting ensures that the elevation prompt is only used in secure desktop mode.",
|
|
2222
|
+
"severity": "medium"
|
|
2223
|
+
},
|
|
2224
|
+
{
|
|
2225
|
+
"id": "WN12-SO-000085",
|
|
2226
|
+
"title": "User Account Control must virtualize file and registry write failures to per-user locations.",
|
|
2227
|
+
"description": "User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting configures non-UAC-compliant applications to run in virtualized file and registry entries in per-user locations, allowing them to run.",
|
|
2228
|
+
"severity": "medium"
|
|
2229
|
+
},
|
|
2230
|
+
{
|
|
2231
|
+
"id": "WN12-SO-000086",
|
|
2232
|
+
"title": "UIAccess applications must not be allowed to prompt for elevation without using the secure desktop.",
|
|
2233
|
+
"description": "User Account Control (UAC) is a security mechanism for limiting the elevation of privileges, including administrative accounts, unless authorized. This setting prevents User Interface Accessibility programs from disabling the secure desktop for elevation prompts.",
|
|
2234
|
+
"severity": "medium"
|
|
2235
|
+
},
|
|
2236
|
+
{
|
|
2237
|
+
"id": "WN12-SO-000087",
|
|
2238
|
+
"title": "Software certificate restriction policies must be enforced.",
|
|
2239
|
+
"description": "Software restriction policies help to protect users and computers from executing unauthorized code such as viruses and Trojans horses. This setting must be enabled to enforce certificate rules in software restriction policies.",
|
|
2240
|
+
"severity": "medium"
|
|
2241
|
+
},
|
|
2242
|
+
{
|
|
2243
|
+
"id": "WN12-SO-000088",
|
|
2244
|
+
"title": "Optional Subsystems must not be permitted to operate on the system.",
|
|
2245
|
+
"description": "The POSIX subsystem is an Institute of Electrical and Electronic Engineers (IEEE) standard that defines a set of operating system services. The POSIX Subsystem is required if the server supports applications that use that subsystem. The subsystem introduces a security risk relating to processes that can potentially persist across logins. That is, if a user starts a process and then logs out, there is a potential that the next user who logs in to the system could access the previous users process. This is dangerous because the process started by the first user may retain that users system privileges, and anything the second user does with that process will be performed with the privileges of the first user.",
|
|
2246
|
+
"severity": "low"
|
|
2247
|
+
},
|
|
2248
|
+
{
|
|
2249
|
+
"id": "WN12-SO-000089",
|
|
2250
|
+
"title": "The print driver installation privilege must be restricted to administrators.",
|
|
2251
|
+
"description": "Allowing users to install drivers can introduce malware or cause the instability of a system. This capability should be restricted to administrators.",
|
|
2252
|
+
"severity": "low"
|
|
2253
|
+
},
|
|
2254
|
+
{
|
|
2255
|
+
"id": "WN12-SO-000090-DC",
|
|
2256
|
+
"title": "Domain controllers must require LDAP access signing.",
|
|
2257
|
+
"description": "Unsigned network traffic is susceptible to man in the middle attacks where an intruder captures packets between the server and the client and modifies them before forwarding them to the client. In the case of an LDAP server, this means that an attacker could cause a client to make decisions based on false records from the LDAP directory. You can lower the risk of an attacker pulling this off in a corporate network by implementing strong physical security measures to protect the network infrastructure. Furthermore, implementing Internet Protocol security (IPSec) authentication header mode (AH), which performs mutual authentication and packet integrity for Internet Protocol (IP) traffic, can make all types of man in the middle attacks extremely difficult.",
|
|
2258
|
+
"severity": "medium"
|
|
2259
|
+
},
|
|
2260
|
+
{
|
|
2261
|
+
"id": "WN12-SO-000091-DC",
|
|
2262
|
+
"title": "Domain controllers must be configured to allow reset of machine account passwords.",
|
|
2263
|
+
"description": "Enabling this setting on all domain controllers in a domain prevents domain members from changing their computer account passwords. If these passwords are weak or compromised, the inability to change them may leave these computers vulnerable.",
|
|
2264
|
+
"severity": "low"
|
|
2265
|
+
},
|
|
2266
|
+
{
|
|
2267
|
+
"id": "WN12-SV-000100",
|
|
2268
|
+
"title": "The Fax service must be disabled if installed.",
|
|
2269
|
+
"description": "Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.",
|
|
2270
|
+
"severity": "medium"
|
|
2271
|
+
},
|
|
2272
|
+
{
|
|
2273
|
+
"id": "WN12-SV-000101",
|
|
2274
|
+
"title": "The Microsoft FTP service must not be installed.",
|
|
2275
|
+
"description": "Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.",
|
|
2276
|
+
"severity": "medium"
|
|
2277
|
+
},
|
|
2278
|
+
{
|
|
2279
|
+
"id": "WN12-SV-000103",
|
|
2280
|
+
"title": "The Peer Networking Identity Manager service must be disabled if installed.",
|
|
2281
|
+
"description": "Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.",
|
|
2282
|
+
"severity": "medium"
|
|
2283
|
+
},
|
|
2284
|
+
{
|
|
2285
|
+
"id": "WN12-SV-000104",
|
|
2286
|
+
"title": "The Simple TCP/IP Services service must be disabled if installed.",
|
|
2287
|
+
"description": "Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.",
|
|
2288
|
+
"severity": "medium"
|
|
2289
|
+
},
|
|
2290
|
+
{
|
|
2291
|
+
"id": "WN12-SV-000105",
|
|
2292
|
+
"title": "The Telnet service must be disabled if installed.",
|
|
2293
|
+
"description": "Unnecessary services increase the attack surface of a system. Some of these services may not support required levels of authentication or encryption.",
|
|
2294
|
+
"severity": "medium"
|
|
2295
|
+
},
|
|
2296
|
+
{
|
|
2297
|
+
"id": "WN12-SV-000106",
|
|
2298
|
+
"title": "The Smart Card Removal Policy service must be configured to automatic.",
|
|
2299
|
+
"description": "The automatic start of the Smart Card Removal Policy service is required to support the smart card removal behavior requirement.",
|
|
2300
|
+
"severity": "medium"
|
|
2301
|
+
},
|
|
2302
|
+
{
|
|
2303
|
+
"id": "WN12-UC-000001",
|
|
2304
|
+
"title": "A screen saver must be enabled on the system.",
|
|
2305
|
+
"description": "Unattended systems are susceptible to unauthorized use and must be locked when unattended. Enabling a password-protected screen saver to engage after a specified period of time helps protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.",
|
|
2306
|
+
"severity": "medium"
|
|
2307
|
+
},
|
|
2308
|
+
{
|
|
2309
|
+
"id": "WN12-UC-000002",
|
|
2310
|
+
"title": "A screen saver must be defined.",
|
|
2311
|
+
"description": "Unattended systems are susceptible to unauthorized use and must be locked. Specifying a screen saver ensures the screen saver timeout lock is initiated properly. This protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.",
|
|
2312
|
+
"severity": "low"
|
|
2313
|
+
},
|
|
2314
|
+
{
|
|
2315
|
+
"id": "WN12-UC-000003",
|
|
2316
|
+
"title": "The screen saver must be password protected.",
|
|
2317
|
+
"description": "Unattended systems are susceptible to unauthorized use and must be locked when unattended. Enabling a password-protected screen saver to engage after a specified period of time helps protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.",
|
|
2318
|
+
"severity": "medium"
|
|
2319
|
+
},
|
|
2320
|
+
{
|
|
2321
|
+
"id": "WN12-UC-000004",
|
|
2322
|
+
"title": "Changing the screen saver must be prevented.",
|
|
2323
|
+
"description": "Unattended systems are susceptible to unauthorized use and must be locked. Preventing users from changing the screen saver ensures an approved screen saver is used. This protects critical and sensitive data from exposure to unauthorized personnel with physical access to the computer.",
|
|
2324
|
+
"severity": "low"
|
|
2325
|
+
},
|
|
2326
|
+
{
|
|
2327
|
+
"id": "WN12-UC-000005",
|
|
2328
|
+
"title": "Notifications from Windows Push Network Service must be turned off.",
|
|
2329
|
+
"description": "The Windows Push Notification Service (WNS) allows third-party vendors to send updates for toasts, tiles, and badges.",
|
|
2330
|
+
"severity": "low"
|
|
2331
|
+
},
|
|
2332
|
+
{
|
|
2333
|
+
"id": "WN12-UC-000006",
|
|
2334
|
+
"title": "Toast notifications to the lock screen must be turned off.",
|
|
2335
|
+
"description": "Toast notifications that are displayed on the lock screen could display sensitive information to unauthorized personnel. Turning off this feature will limit access to the information to a logged on user.",
|
|
2336
|
+
"severity": "low"
|
|
2337
|
+
},
|
|
2338
|
+
{
|
|
2339
|
+
"id": "WN12-UC-000007",
|
|
2340
|
+
"title": "The Windows Help Experience Improvement Program must be disabled.",
|
|
2341
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting ensures the Windows Help Experience Improvement Program is disabled to prevent information from being passed to the vendor.",
|
|
2342
|
+
"severity": "medium"
|
|
2343
|
+
},
|
|
2344
|
+
{
|
|
2345
|
+
"id": "WN12-UC-000008",
|
|
2346
|
+
"title": "Windows Help Ratings feedback must be turned off.",
|
|
2347
|
+
"description": "Some features may communicate with the vendor, sending system information or downloading data or components for the feature. Turning off this capability will prevent potentially sensitive information from being sent outside the enterprise and uncontrolled updates to the system. \nThis setting ensures users cannot provide ratings feedback to Microsoft for Help content.",
|
|
2348
|
+
"severity": "medium"
|
|
2349
|
+
},
|
|
2350
|
+
{
|
|
2351
|
+
"id": "WN12-UC-000009",
|
|
2352
|
+
"title": "Zone information must be preserved when saving attachments.",
|
|
2353
|
+
"description": "Preserving zone of origin (Internet, intranet, local, restricted) information on file attachments allows Windows to determine risk.",
|
|
2354
|
+
"severity": "medium"
|
|
2355
|
+
},
|
|
2356
|
+
{
|
|
2357
|
+
"id": "WN12-UC-000010",
|
|
2358
|
+
"title": "Mechanisms for removing zone information from file attachments must be hidden.",
|
|
2359
|
+
"description": "Preserving zone of origin (Internet, intranet, local, restricted) information on file attachments allows Windows to determine risk. This setting prevents users from manually removing zone information from saved file attachments.",
|
|
2360
|
+
"severity": "medium"
|
|
2361
|
+
},
|
|
2362
|
+
{
|
|
2363
|
+
"id": "WN12-UC-000011",
|
|
2364
|
+
"title": "The system must notify antivirus when file attachments are opened.",
|
|
2365
|
+
"description": "Attaching malicious files is a known avenue of attack. This setting configures the system to notify antivirus programs when a user opens a file attachment.",
|
|
2366
|
+
"severity": "medium"
|
|
2367
|
+
},
|
|
2368
|
+
{
|
|
2369
|
+
"id": "WN12-UC-000012",
|
|
2370
|
+
"title": "Users must be prevented from sharing files in their profiles.",
|
|
2371
|
+
"description": "Allowing users to share files in their profiles may provide unauthorized access or result in the exposure of sensitive data.",
|
|
2372
|
+
"severity": "medium"
|
|
2373
|
+
},
|
|
2374
|
+
{
|
|
2375
|
+
"id": "WN12-UC-000013",
|
|
2376
|
+
"title": "Media Player must be configured to prevent automatic Codec downloads.",
|
|
2377
|
+
"description": "The Windows Media Player uses software components, referred to as Codecs, to play back media files. By default, when an unknown file type is opened with the Media Player, it will search the Internet for the appropriate Codec and automatically download it. To ensure platform consistency and to protect against new vulnerabilities associated with media types, all Codecs must be installed by the System Administrator.",
|
|
2378
|
+
"severity": "medium"
|
|
2379
|
+
},
|
|
2380
|
+
{
|
|
2381
|
+
"id": "WN12-UR-000001",
|
|
2382
|
+
"title": "Unauthorized accounts must not have the Access Credential Manager as a trusted caller user right.",
|
|
2383
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Access Credential Manager as a trusted caller\" user right may be able to retrieve the credentials of other accounts from Credential Manager.",
|
|
2384
|
+
"severity": "medium"
|
|
2385
|
+
},
|
|
2386
|
+
{
|
|
2387
|
+
"id": "WN12-UR-000002-DC",
|
|
2388
|
+
"title": "Unauthorized accounts must not have the Access this computer from the network user right.",
|
|
2389
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Access this computer from the network\" right may access resources on the system and should be limited to those requiring it.",
|
|
2390
|
+
"severity": "medium"
|
|
2391
|
+
},
|
|
2392
|
+
{
|
|
2393
|
+
"id": "WN12-UR-000003",
|
|
2394
|
+
"title": "Unauthorized accounts must not have the Act as part of the operating system user right.",
|
|
2395
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Act as part of the operating system\" user right can assume the identity of any user and gain access to resources that user is authorized to access. Any accounts with this right can take complete control of a system.",
|
|
2396
|
+
"severity": "high"
|
|
2397
|
+
},
|
|
2398
|
+
{
|
|
2399
|
+
"id": "WN12-UR-000004",
|
|
2400
|
+
"title": "Unauthorized accounts must not have the Adjust memory quotas for a process user right.",
|
|
2401
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Adjust memory quotas for a process\" user right can adjust memory that is available to processes, and could be used in a denial of service (DoS) attack.",
|
|
2402
|
+
"severity": "medium"
|
|
2403
|
+
},
|
|
2404
|
+
{
|
|
2405
|
+
"id": "WN12-UR-000005",
|
|
2406
|
+
"title": "Unauthorized accounts must not have the Allow log on locally user right.",
|
|
2407
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Allow log on locally\" user right can log on interactively to a system.",
|
|
2408
|
+
"severity": "medium"
|
|
2409
|
+
},
|
|
2410
|
+
{
|
|
2411
|
+
"id": "WN12-UR-000006",
|
|
2412
|
+
"title": "Unauthorized accounts must not have the Allow log on through Remote Desktop Services user right.",
|
|
2413
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Allow log on through Remote Desktop Services\" user right can access a system through Remote Desktop.",
|
|
2414
|
+
"severity": "medium"
|
|
2415
|
+
},
|
|
2416
|
+
{
|
|
2417
|
+
"id": "WN12-UR-000007",
|
|
2418
|
+
"title": "Unauthorized accounts must not have the Back up files and directories user right.",
|
|
2419
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Back up files and directories\" user right can circumvent file and directory permissions and could allow access to sensitive data.",
|
|
2420
|
+
"severity": "medium"
|
|
2421
|
+
},
|
|
2422
|
+
{
|
|
2423
|
+
"id": "WN12-UR-000008",
|
|
2424
|
+
"title": "Unauthorized accounts must not have the Bypass traverse checking user right.",
|
|
2425
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Bypass traverse checking\" user right can pass through folders when browsing even if they do not have the \"Traverse Folder\" access permission. They could potentially view sensitive file and folder names. They would not have additional access to the files and folders unless it is granted through permissions.",
|
|
2426
|
+
"severity": "low"
|
|
2427
|
+
},
|
|
2428
|
+
{
|
|
2429
|
+
"id": "WN12-UR-000009",
|
|
2430
|
+
"title": "Unauthorized accounts must not have the Change the system time user right.",
|
|
2431
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Change the system time\" user right can change the system time, which can impact authentication, as well as affect time stamps on event log entries.",
|
|
2432
|
+
"severity": "medium"
|
|
2433
|
+
},
|
|
2434
|
+
{
|
|
2435
|
+
"id": "WN12-UR-000010",
|
|
2436
|
+
"title": "Unauthorized accounts must not have the Change the time zone user right.",
|
|
2437
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Change the time zone\" user right can change the time zone of a system.",
|
|
2438
|
+
"severity": "low"
|
|
2439
|
+
},
|
|
2440
|
+
{
|
|
2441
|
+
"id": "WN12-UR-000011",
|
|
2442
|
+
"title": "Unauthorized accounts must not have the Create a pagefile user right.",
|
|
2443
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Create a pagefile\" user right can change the size of a pagefile, which could affect system performance.",
|
|
2444
|
+
"severity": "medium"
|
|
2445
|
+
},
|
|
2446
|
+
{
|
|
2447
|
+
"id": "WN12-UR-000012",
|
|
2448
|
+
"title": "Unauthorized accounts must not have the Create a token object user right.",
|
|
2449
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Create a token object\" user right allows a process to create an access token. This could be used to provide elevated rights and compromise a system.",
|
|
2450
|
+
"severity": "high"
|
|
2451
|
+
},
|
|
2452
|
+
{
|
|
2453
|
+
"id": "WN12-UR-000013",
|
|
2454
|
+
"title": "Unauthorized accounts must not have the Create global objects user right.",
|
|
2455
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Create global objects\" user right can create objects that are available to all sessions, which could affect processes in other users' sessions.",
|
|
2456
|
+
"severity": "medium"
|
|
2457
|
+
},
|
|
2458
|
+
{
|
|
2459
|
+
"id": "WN12-UR-000014",
|
|
2460
|
+
"title": "Unauthorized accounts must not have the Create permanent shared objects user right.",
|
|
2461
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Create permanent shared objects\" user right could expose sensitive data by creating shared objects.",
|
|
2462
|
+
"severity": "medium"
|
|
2463
|
+
},
|
|
2464
|
+
{
|
|
2465
|
+
"id": "WN12-UR-000015",
|
|
2466
|
+
"title": "Unauthorized accounts must not have the Create symbolic links user right.",
|
|
2467
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Create symbolic links\" user right can create pointers to other objects, which could potentially expose the system to attack.",
|
|
2468
|
+
"severity": "medium"
|
|
2469
|
+
},
|
|
2470
|
+
{
|
|
2471
|
+
"id": "WN12-UR-000016",
|
|
2472
|
+
"title": "Unauthorized accounts must not have the Debug programs user right.",
|
|
2473
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Debug programs\" user right can attach a debugger to any process or to the kernel, providing complete access to sensitive and critical operating system components. This right is given to Administrators in the default configuration.",
|
|
2474
|
+
"severity": "high"
|
|
2475
|
+
},
|
|
2476
|
+
{
|
|
2477
|
+
"id": "WN12-UR-000017-DC",
|
|
2478
|
+
"title": "The Deny access to this computer from the network user right on domain controllers must be configured to prevent unauthenticated access.",
|
|
2479
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Deny access to this computer from the network\" user right defines the accounts that are prevented from logging on from the network. \n\nThe Guests group must be assigned this right to prevent unauthenticated access.",
|
|
2480
|
+
"severity": "medium"
|
|
2481
|
+
},
|
|
2482
|
+
{
|
|
2483
|
+
"id": "WN12-UR-000018-DC",
|
|
2484
|
+
"title": "The Deny log on as a batch job user right on domain controllers must be configured to prevent unauthenticated access.",
|
|
2485
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Deny log on as a batch job\" user right defines accounts that are prevented from logging on to the system as a batch job, such as Task Scheduler. \n\nThe Guests group must be assigned to prevent unauthenticated access.",
|
|
2486
|
+
"severity": "medium"
|
|
2487
|
+
},
|
|
2488
|
+
{
|
|
2489
|
+
"id": "WN12-UR-000019-DC",
|
|
2490
|
+
"title": "The Deny log on as a service user right must be configured to include no accounts or groups (blank).",
|
|
2491
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Deny log on as a service\" user right defines accounts that are denied log on as a service. \n\nIncorrect configurations could prevent services from starting and result in a DoS.",
|
|
2492
|
+
"severity": "medium"
|
|
2493
|
+
},
|
|
2494
|
+
{
|
|
2495
|
+
"id": "WN12-UR-000020-DC",
|
|
2496
|
+
"title": "The Deny log on locally user right on domain controllers must be configured to prevent unauthenticated access.",
|
|
2497
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Deny log on locally\" user right defines accounts that are prevented from logging on interactively. \n\nThe Guests group must be assigned this right to prevent unauthenticated access.",
|
|
2498
|
+
"severity": "medium"
|
|
2499
|
+
},
|
|
2500
|
+
{
|
|
2501
|
+
"id": "WN12-UR-000021-DC",
|
|
2502
|
+
"title": "The Deny log on through Remote Desktop Services user right on domain controllers must be configured to prevent unauthenticated access.",
|
|
2503
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Deny log on through Remote Desktop Services\" user right defines the accounts that are prevented from logging on using Remote Desktop Services.\n\nThe Guests group must be assigned this right to prevent unauthenticated access.",
|
|
2504
|
+
"severity": "medium"
|
|
2505
|
+
},
|
|
2506
|
+
{
|
|
2507
|
+
"id": "WN12-UR-000022-DC",
|
|
2508
|
+
"title": "Unauthorized accounts must not have the Enable computer and user accounts to be trusted for delegation user right.",
|
|
2509
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Enable computer and user accounts to be trusted for delegation\" user right allows the \"Trusted for Delegation\" setting to be changed. This could potentially allow unauthorized users to impersonate other users.",
|
|
2510
|
+
"severity": "medium"
|
|
2511
|
+
},
|
|
2512
|
+
{
|
|
2513
|
+
"id": "WN12-UR-000023",
|
|
2514
|
+
"title": "Unauthorized accounts must not have the Force shutdown from a remote system user right.",
|
|
2515
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Force shutdown from a remote system\" user right can remotely shut down a system, which could result in a DoS.",
|
|
2516
|
+
"severity": "medium"
|
|
2517
|
+
},
|
|
2518
|
+
{
|
|
2519
|
+
"id": "WN12-UR-000024",
|
|
2520
|
+
"title": "Unauthorized accounts must not have the Generate security audits user right.",
|
|
2521
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Generate security audits\" user right specifies users and processes that can generate Security Log audit records, which must only be the system service accounts defined.",
|
|
2522
|
+
"severity": "medium"
|
|
2523
|
+
},
|
|
2524
|
+
{
|
|
2525
|
+
"id": "WN12-UR-000025",
|
|
2526
|
+
"title": "Unauthorized accounts must not have the Impersonate a client after authentication user right.",
|
|
2527
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Impersonate a client after authentication\" user right allows a program to impersonate another user or account to run on their behalf. An attacker could potentially use this to elevate privileges.",
|
|
2528
|
+
"severity": "medium"
|
|
2529
|
+
},
|
|
2530
|
+
{
|
|
2531
|
+
"id": "WN12-UR-000026",
|
|
2532
|
+
"title": "Unauthorized accounts must not have the Increase a process working set user right.",
|
|
2533
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Increase a process working set\" user right can change the size of a process's working set, potentially causing performance issues or a DoS.",
|
|
2534
|
+
"severity": "medium"
|
|
2535
|
+
},
|
|
2536
|
+
{
|
|
2537
|
+
"id": "WN12-UR-000027",
|
|
2538
|
+
"title": "Unauthorized accounts must not have the Increase scheduling priority user right.",
|
|
2539
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Increase scheduling priority\" user right can change a scheduling priority causing performance issues or a DoS.",
|
|
2540
|
+
"severity": "medium"
|
|
2541
|
+
},
|
|
2542
|
+
{
|
|
2543
|
+
"id": "WN12-UR-000028",
|
|
2544
|
+
"title": "Unauthorized accounts must not have the Load and unload device drivers user right.",
|
|
2545
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Load and unload device drivers\" user right allows device drivers to dynamically be loaded on a system by a user. This could potentially be used to install malicious code by an attacker.",
|
|
2546
|
+
"severity": "medium"
|
|
2547
|
+
},
|
|
2548
|
+
{
|
|
2549
|
+
"id": "WN12-UR-000029",
|
|
2550
|
+
"title": "Unauthorized accounts must not have the Lock pages in memory user right.",
|
|
2551
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Lock pages in memory\" user right allows physical memory to be assigned to processes, which could cause performance issues or a DoS.",
|
|
2552
|
+
"severity": "medium"
|
|
2553
|
+
},
|
|
2554
|
+
{
|
|
2555
|
+
"id": "WN12-UR-000030",
|
|
2556
|
+
"title": "Unauthorized accounts must not have the Log on as a batch job user right.",
|
|
2557
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Log on as a batch job\" user right allows accounts to log on using the task scheduler service, which must be restricted.",
|
|
2558
|
+
"severity": "medium"
|
|
2559
|
+
},
|
|
2560
|
+
{
|
|
2561
|
+
"id": "WN12-UR-000032",
|
|
2562
|
+
"title": "Unauthorized accounts must not have the Manage auditing and security log user right.",
|
|
2563
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Manage auditing and security log\" user right can manage the security log and change auditing configurations. This could be used to clear evidence of tampering.",
|
|
2564
|
+
"severity": "medium"
|
|
2565
|
+
},
|
|
2566
|
+
{
|
|
2567
|
+
"id": "WN12-UR-000033",
|
|
2568
|
+
"title": "Unauthorized accounts must not have the Modify an object label user right.",
|
|
2569
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Modify an object label\" user right can change the integrity label of an object. This could potentially be used to execute code at a higher privilege.",
|
|
2570
|
+
"severity": "medium"
|
|
2571
|
+
},
|
|
2572
|
+
{
|
|
2573
|
+
"id": "WN12-UR-000034",
|
|
2574
|
+
"title": "Unauthorized accounts must not have the Modify firmware environment values user right.",
|
|
2575
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Modify firmware environment values\" user right can change hardware configuration environment variables. This could result in hardware failures or a DoS.",
|
|
2576
|
+
"severity": "medium"
|
|
2577
|
+
},
|
|
2578
|
+
{
|
|
2579
|
+
"id": "WN12-UR-000035",
|
|
2580
|
+
"title": "Unauthorized accounts must not have the Perform volume maintenance tasks user right.",
|
|
2581
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Perform volume maintenance tasks\" user right can manage volume and disk configurations. They could potentially delete volumes, resulting in data loss or a DoS.",
|
|
2582
|
+
"severity": "medium"
|
|
2583
|
+
},
|
|
2584
|
+
{
|
|
2585
|
+
"id": "WN12-UR-000036",
|
|
2586
|
+
"title": "Unauthorized accounts must not have the Profile single process user right.",
|
|
2587
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Profile single process\" user right can monitor nonsystem processes performance. An attacker could potentially use this to identify processes to attack.",
|
|
2588
|
+
"severity": "medium"
|
|
2589
|
+
},
|
|
2590
|
+
{
|
|
2591
|
+
"id": "WN12-UR-000037",
|
|
2592
|
+
"title": "Unauthorized accounts must not have the Profile system performance user right.",
|
|
2593
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Profile system performance\" user right can monitor system processes performance. An attacker could potentially use this to identify processes to attack.",
|
|
2594
|
+
"severity": "medium"
|
|
2595
|
+
},
|
|
2596
|
+
{
|
|
2597
|
+
"id": "WN12-UR-000039",
|
|
2598
|
+
"title": "Unauthorized accounts must not have the Replace a process level token user right.",
|
|
2599
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nThe \"Replace a process level token\" user right allows one process or service to start another process or service with a different security access token. A user with this right could use this to impersonate another account.",
|
|
2600
|
+
"severity": "medium"
|
|
2601
|
+
},
|
|
2602
|
+
{
|
|
2603
|
+
"id": "WN12-UR-000040",
|
|
2604
|
+
"title": "Unauthorized accounts must not have the Restore files and directories user right.",
|
|
2605
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Restore files and directories\" user right can circumvent file and directory permissions and could allow access to sensitive data. It could also be used to overwrite more current data.",
|
|
2606
|
+
"severity": "medium"
|
|
2607
|
+
},
|
|
2608
|
+
{
|
|
2609
|
+
"id": "WN12-UR-000041",
|
|
2610
|
+
"title": "Unauthorized accounts must not have the Shut down the system user right.",
|
|
2611
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Shut down the system\" user right can interactively shut down a system, which could result in a DoS.",
|
|
2612
|
+
"severity": "medium"
|
|
2613
|
+
},
|
|
2614
|
+
{
|
|
2615
|
+
"id": "WN12-UR-000042",
|
|
2616
|
+
"title": "Unauthorized accounts must not have the Take ownership of files or other objects user right.",
|
|
2617
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Take ownership of files or other objects\" user right can take ownership of objects and make changes.\n",
|
|
2618
|
+
"severity": "medium"
|
|
2619
|
+
},
|
|
2620
|
+
{
|
|
2621
|
+
"id": "WN12-UR-000043-DC",
|
|
2622
|
+
"title": "The Synchronize directory service data user right must be configured to include no accounts or groups (blank).",
|
|
2623
|
+
"description": "A Windows account with the \"Synchronize directory service data\" right has the ability to read all information in the AD database. This bypasses the object access permissions that would otherwise restrict access to the data. The scope of access granted by this right is too broad for secure usage. Specific object permissions or other group membership assignments could be used to provide access on an appropriate scale.",
|
|
2624
|
+
"severity": "high"
|
|
2625
|
+
},
|
|
2626
|
+
{
|
|
2627
|
+
"id": "WN12-UR-000044-DC",
|
|
2628
|
+
"title": "Unauthorized accounts must not have the Add workstations to domain user right.",
|
|
2629
|
+
"description": "Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.\n\nAccounts with the \"Add workstations to domain\" right may add computers to a domain. This could result in unapproved or incorrectly configured systems being added to a domain.",
|
|
2630
|
+
"severity": "medium"
|
|
2631
|
+
}
|
|
2632
|
+
]
|
|
2633
|
+
}
|