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,119 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "stig_mobile_device_integrity_scanning_mdis_server",
|
|
3
|
+
"date": "2013-05-08",
|
|
4
|
+
"description": "This STIG provides technical security controls required for the use of a mobile MDIS server to audit the integrity of mobile devices in the DoD environment. The requirements listed in this benchmark apply to any DoD iOS implementation when iOS devices process sensitive DoD information, connect to a DoD network or network connected PC, or provide service to a DoD email system. The requirements can be implemented in an application server separate from the MDM server or included in the MDM server. 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": "Mobile Device Integrity Scanning (MDIS) Server Security Technical Implementation Guide (STIG)",
|
|
6
|
+
"version": "1",
|
|
7
|
+
"item_syntax": "^\\w-\\d+$",
|
|
8
|
+
"section_separator": null,
|
|
9
|
+
"items": [
|
|
10
|
+
{
|
|
11
|
+
"id": "V-24972",
|
|
12
|
+
"title": "The required mobile device management server version (or later) must be used. ",
|
|
13
|
+
"description": "Earlier versions of the MDM server may have security vulnerabilities or not have required security features implemented. Therefore, sensitive DoD data could be exposed if required security features are not implemented on site-managed mobile devices.",
|
|
14
|
+
"severity": "medium"
|
|
15
|
+
},
|
|
16
|
+
{
|
|
17
|
+
"id": "V-24973",
|
|
18
|
+
"title": "The host server where the mobile management server is installed must be hardened according to the appropriate Application STIG (SQL, Apache Tomcat, IIS, etc.). ",
|
|
19
|
+
"description": "The host server where the mobile management server is installed must be compliant with the Windows STIG and applicable application STIGs to ensure the system is not vulnerable to attack resulting in a Denial of Service or compromise of the management server.",
|
|
20
|
+
"severity": "medium"
|
|
21
|
+
},
|
|
22
|
+
{
|
|
23
|
+
"id": "V-24975",
|
|
24
|
+
"title": "The host server where the mobile management server is installed must have a host-based or appliance firewall, which must be configured as required.\n",
|
|
25
|
+
"description": "A mobile device user could get access to unauthorized network resources (application and content servers, etc.) via the communications link between the mobile device and mobile management server if the server host firewall is not set up as required. HBSS is usually used to satisfy this requirement.",
|
|
26
|
+
"severity": "high"
|
|
27
|
+
},
|
|
28
|
+
{
|
|
29
|
+
"id": "V-25754",
|
|
30
|
+
"title": "The PKI digital certificate installed on mobile management servers for server authentication must be a DoD PKI-issued certificate.",
|
|
31
|
+
"description": "When a self-signed PKI certificate is used, a rogue mobile management server can impersonate the DoD mobile management server. DoDI 8520-02 requires PKI certificates come from a trusted DoD PKI.",
|
|
32
|
+
"severity": "low"
|
|
33
|
+
},
|
|
34
|
+
{
|
|
35
|
+
"id": "V-26564",
|
|
36
|
+
"title": "Authentication on system administration accounts for mobile management servers must be configured to support CTO 07-15 Rev 1 requirements.\n",
|
|
37
|
+
"description": "CTO 07-15 Rev 1 requires administrator accounts use either CAC authentication or use complex passwords to ensure strong access control is enforced. This is best enforced by requiring the server support AD authentication.",
|
|
38
|
+
"severity": "high"
|
|
39
|
+
},
|
|
40
|
+
{
|
|
41
|
+
"id": "V-32748",
|
|
42
|
+
"title": "The results and mitigation actions from MDIS server on site managed mobile OS devices must be maintained by the site for at least 6 months (1 year recommended). ",
|
|
43
|
+
"description": "Scan results must be maintained so auditors can verify mitigation actions have been completed, so a scan can be compared to a previous scan, and to determine if there are any security vulnerability trends for site-managed mobile OS devices.",
|
|
44
|
+
"severity": "medium"
|
|
45
|
+
},
|
|
46
|
+
{
|
|
47
|
+
"id": "V-32749",
|
|
48
|
+
"title": "Mitigation actions must be implemented based on integrity validation scan findings. ",
|
|
49
|
+
"description": "If mitigation actions are not implemented after a scan finding, DoD data and the enclave could be at risk of being compromised because the security baseline of the device has been compromised. The IAO should determine the appropriate mitigation action based on the scan finding report and any other analysis performed by site Information Assurance (IA) staff. It is expected that the system administrator or IAO will approve all mitigation actions before they are implemented, including those implemented by the server (for example, device wipe).",
|
|
50
|
+
"severity": "high"
|
|
51
|
+
},
|
|
52
|
+
{
|
|
53
|
+
"id": "V-32753",
|
|
54
|
+
"title": "The MDIS server must alert when it identifies malicious code on managed mobile devices. ",
|
|
55
|
+
"description": "Detection of possible compromise of a DoD mobile device is a key security control to insure the compromise does not result in the exposure of sensitive DoD data or lead to a successful attack on the DoD network. Alerting is required to ensure proper management oversight is provided to timely mitigation actions to reduce the effect of the compromise.\n",
|
|
56
|
+
"severity": "high"
|
|
57
|
+
},
|
|
58
|
+
{
|
|
59
|
+
"id": "V-32754",
|
|
60
|
+
"title": "The MDIS server must provide a near real-time alert when any compromise or potential compromise indicators occurs. ",
|
|
61
|
+
"description": "Detection of possible compromise of a DoD mobile device is a key security control to insure the compromise does not result in the exposure of sensitive DoD data or lead to a successful attack on the DoD network. Timely alerting is required to ensure proper management oversight is provided to mitigation actions to reduce the effect of the compromise. Compromise indicators include the following:\n-Unauthorized software on the device.\n-Jailbroken or rooted device.\n-Changes in file structure or files on the device.\n-Unexpected changes in applications installed on the device.\n-Integrity check failure of all operating system files, device drivers, and security enforcement mechanisms at device startup.",
|
|
62
|
+
"severity": "high"
|
|
63
|
+
},
|
|
64
|
+
{
|
|
65
|
+
"id": "V-32755",
|
|
66
|
+
"title": "The MDIS server must provide notifications regarding suspicious events to an organization defined list of response personnel, including the IAO and system administrator, who are identified by name and/or by role.",
|
|
67
|
+
"description": "Detection of possible compromise of a DoD mobile device is a key security control to insure the compromise does not result in the exposure of sensitive DoD data or lead to a successful attack on the DoD network. Timely alerting is required to ensure proper management oversight is provided to mitigation actions to reduce the effect of the compromise.\n",
|
|
68
|
+
"severity": "medium"
|
|
69
|
+
},
|
|
70
|
+
{
|
|
71
|
+
"id": "V-32758",
|
|
72
|
+
"title": "The MDIS server must verify the integrity of all operating system files, device drivers, and security enforcement mechanisms at startup and at least every six hours thereafter, using one or more DoD-approved cryptographic mechanisms that compare attributes of the operating system configuration to a known good baseline.",
|
|
73
|
+
"description": "Detection of possible compromise of a DoD mobile device is a key security control to insure the compromise does not result in the exposure of sensitive DoD data or lead to a successful attack on the DoD network. Analysis has determined scans must be performed at least every 6 hours.\n",
|
|
74
|
+
"severity": "high"
|
|
75
|
+
},
|
|
76
|
+
{
|
|
77
|
+
"id": "V-32759",
|
|
78
|
+
"title": "The MDIS agent must not be capable of being disabled or controlled by the user or other mobile device application. \n",
|
|
79
|
+
"description": "The integrity of the device security baseline would be compromised if the MDIS agent could be disabled by the user or an application.\n\n",
|
|
80
|
+
"severity": "high"
|
|
81
|
+
},
|
|
82
|
+
{
|
|
83
|
+
"id": "V-32761",
|
|
84
|
+
"title": "The MDIS server must base recommended mitigations for findings on the identified risk level of the finding. ",
|
|
85
|
+
"description": "Detection of possible compromise of a DoD mobile device is a key security control to insure the compromise does not result in the exposure of sensitive DoD data or lead to a successful attack on the DoD network. Since the MDIS is an automated capability, the server must be able to determine the severity of the finding and provide a recommended mitigation to ensure timely action to mitigate the finding.",
|
|
86
|
+
"severity": "medium"
|
|
87
|
+
},
|
|
88
|
+
{
|
|
89
|
+
"id": "V-32762",
|
|
90
|
+
"title": "The MDIS agent must operate separate and independent of the management of the mobile devices security policy. \n",
|
|
91
|
+
"description": "One of the key capabilities of the MDIS feature is the capability to determine if the device has been compromised. To ensure integrity of the feature, the MDIS must not be modified by any device management feature, and must be able to monitor the compliance of device management.",
|
|
92
|
+
"severity": "high"
|
|
93
|
+
},
|
|
94
|
+
{
|
|
95
|
+
"id": "V-32763",
|
|
96
|
+
"title": "The MDIS server must identify changes in file structure and files on the mobile device. ",
|
|
97
|
+
"description": "Detection of possible compromise of a DoD mobile device is a key security control to insure the compromise does not result in the exposure of sensitive DoD data or lead to a successful attack on the DoD network. File structure changes are a key indicator of possible device compromise.\n",
|
|
98
|
+
"severity": "high"
|
|
99
|
+
},
|
|
100
|
+
{
|
|
101
|
+
"id": "V-32764",
|
|
102
|
+
"title": "The MDIS server must identify unexpected changes in applications installed on the mobile device. ",
|
|
103
|
+
"description": "Detection of possible compromise of a DoD mobile device is a key security control to insure the compromise does not result in the exposure of sensitive DoD data or lead to a successful attack on the DoD network. Application changes are a key indicator of possible device compromise.\n",
|
|
104
|
+
"severity": "high"
|
|
105
|
+
},
|
|
106
|
+
{
|
|
107
|
+
"id": "V-32765",
|
|
108
|
+
"title": "The MDIS server must have the capability to maintain change history of individual devices.",
|
|
109
|
+
"description": "Scan results must be maintained so auditors can verify mitigation actions have been completed, so a scan can be compared to a previous scan, and to determine if there are any security vulnerability trends for site managed mobile OS devices.",
|
|
110
|
+
"severity": "medium"
|
|
111
|
+
},
|
|
112
|
+
{
|
|
113
|
+
"id": "V-33231",
|
|
114
|
+
"title": "The master AES encryption key used to encrypt data between the management server and the agent on the mobile device must be changed every 30 days or less. ",
|
|
115
|
+
"description": "There are two primary methods for generating the encryption key used to encrypt data between the management server and the server agent installed on the mobile device. The first method is to use a shared secret and the second is to generate the master encryption key based on PKI key generation. When a shared secret is used, if the master encryption key is not rotated periodically, and it is compromised, all future data sent between the mobile management server and the agent located on the mobile device would be compromised. Limiting the compromise to no more than a specific period of data is a security best practice.",
|
|
116
|
+
"severity": "low"
|
|
117
|
+
}
|
|
118
|
+
]
|
|
119
|
+
}
|
|
@@ -0,0 +1,125 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "stig_mobile_device_management_mdm_server",
|
|
3
|
+
"date": "2013-05-08",
|
|
4
|
+
"description": "This STIG provides technical security controls required for the use of a MDM server to manage mobile devices in the DoD environment. 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": "Mobile Device Management (MDM) Server Security Technical Implementation Guide (STIG)",
|
|
6
|
+
"version": "1",
|
|
7
|
+
"item_syntax": "^\\w-\\d+$",
|
|
8
|
+
"section_separator": null,
|
|
9
|
+
"items": [
|
|
10
|
+
{
|
|
11
|
+
"id": "V-24972",
|
|
12
|
+
"title": "The required mobile device management server version (or later) must be used. ",
|
|
13
|
+
"description": "Earlier versions of the MDM server may have security vulnerabilities or not have required security features implemented. Therefore, sensitive DoD data could be exposed if required security features are not implemented on site-managed mobile devices.",
|
|
14
|
+
"severity": "medium"
|
|
15
|
+
},
|
|
16
|
+
{
|
|
17
|
+
"id": "V-24973",
|
|
18
|
+
"title": "The host server where the mobile management server is installed must be hardened according to the appropriate Application STIG (SQL, Apache Tomcat, IIS, etc.). ",
|
|
19
|
+
"description": "The host server where the mobile management server is installed must be compliant with the Windows STIG and applicable application STIGs to ensure the system is not vulnerable to attack resulting in a Denial of Service or compromise of the management server.",
|
|
20
|
+
"severity": "medium"
|
|
21
|
+
},
|
|
22
|
+
{
|
|
23
|
+
"id": "V-24975",
|
|
24
|
+
"title": "The host server where the mobile management server is installed must have a host-based or appliance firewall, which must be configured as required.\n",
|
|
25
|
+
"description": "A mobile device user could get access to unauthorized network resources (application and content servers, etc.) via the communications link between the mobile device and mobile management server if the server host firewall is not set up as required. HBSS is usually used to satisfy this requirement.",
|
|
26
|
+
"severity": "high"
|
|
27
|
+
},
|
|
28
|
+
{
|
|
29
|
+
"id": "V-24976",
|
|
30
|
+
"title": "Security controls must be implemented on the MDM server for connections to back-office servers and applications by managed mobile devices.\n",
|
|
31
|
+
"description": "The secure connection from the smartphone to the MDM server can be used by the mobile device to allow a user to connect to back-office servers and applications located on the enclave network. These connections bypass network authentication controls setup on the enclave. Strong access controls to back-office servers are required to ensure DoD data is not exposed to users of the smartphone system that are not authorized to access the back-office servers and applications. Many MDM servers have the capability to proxy the authentication credentials for the mobile device user to the network. (The network views the connection request as if it is coming from the MDM server, not the mobile device user, therefore the server must proxy network authentication on behalf of the user.) In the DoD environment where CAC authentication to the network is required, the MDM server must have the capability to proxy (pass to Active Directory) the user’s CAC authentication, but most MDM servers cannot support this capability; therefore connections to back-office servers via the MDM server must be disabled.",
|
|
32
|
+
"severity": "high"
|
|
33
|
+
},
|
|
34
|
+
{
|
|
35
|
+
"id": "V-24978",
|
|
36
|
+
"title": "Mobile device accounts must not be assigned default and non-STIG compliant security/IT policies. ",
|
|
37
|
+
"description": "The mobile device default security/IT policy on the MDM does not include most DoD-required security policies for data encryption, authentication, and access control. Also, non-STIG compliant policy may not meet critical (CAT I and CAT II) security requirements. DoD enclaves are at risk of data exposure and hacker attack if devices are assigned default or other non-STIG compliant security/IT policies.",
|
|
38
|
+
"severity": "high"
|
|
39
|
+
},
|
|
40
|
+
{
|
|
41
|
+
"id": "V-24987",
|
|
42
|
+
"title": "The timeout for the PKI certificate PIN cache must be set at 120 minutes or less. (Note: 15 minutes or less is the recommended setting.)",
|
|
43
|
+
"description": "Most mobile devices have the capability to cache the digital certificate PIN so that it does not need to be entered every time the user’s digital certificate has to be accessed when a PKI encryption or authentication operation takes place. The PIN should only be cached for a limited time period; otherwise the user’s digital certificates could be exposed to unauthorized individuals if the mobile device is lost or stolen.",
|
|
44
|
+
"severity": "low"
|
|
45
|
+
},
|
|
46
|
+
{
|
|
47
|
+
"id": "V-24998",
|
|
48
|
+
"title": "The Over-The-Air (OTA) device provisioning password must have expiration set. ",
|
|
49
|
+
"description": "The time period that a device can be provisioned via Over-The-Air (OTA) provisioning needs to be controlled to ensure unauthorized individuals do not have the capability to set up rogue devices on the network. Note Active Directory credentials should not be utilized for the OTA provisioning password.\n",
|
|
50
|
+
"severity": "medium"
|
|
51
|
+
},
|
|
52
|
+
{
|
|
53
|
+
"id": "V-24999",
|
|
54
|
+
"title": "OTA Provisioning PIN reuse must not be allowed.",
|
|
55
|
+
"description": "The reuse of the OTA PIN can allow a hacker to provision an unauthorized device on the system.",
|
|
56
|
+
"severity": "low"
|
|
57
|
+
},
|
|
58
|
+
{
|
|
59
|
+
"id": "V-25000",
|
|
60
|
+
"title": "The MDM server must enable an MDM security profile on each managed iOS device.\n",
|
|
61
|
+
"description": "Sensitive DoD data could be compromised if an MDM security profile is not installed on DoD iOS devices. Other iOS profiles do not have access to all security APIs on the iOS device. If the iOS MDM security profile is removed access to the protected Government data inside the security container will not be allowed. The user must be forced to re-install the MDM security profile before gaining access. The mobile device will report the removal and implementation of the MDM security profile to the MDM management server.",
|
|
62
|
+
"severity": "medium"
|
|
63
|
+
},
|
|
64
|
+
{
|
|
65
|
+
"id": "V-25002",
|
|
66
|
+
"title": "The MDM server must define the required mobile device hardware versions.\n ",
|
|
67
|
+
"description": "Older devices do not support required security features. Therefore, sensitive data could be at risk of being exposed if required security features are not available.",
|
|
68
|
+
"severity": "low"
|
|
69
|
+
},
|
|
70
|
+
{
|
|
71
|
+
"id": "V-25004",
|
|
72
|
+
"title": "The MDM server must implement jailbreak detection on managed mobile devices.",
|
|
73
|
+
"description": "If a device is jailbroken, the user may have the ability to install unauthorized software that might disclose sensitive DoD information or attack other systems. The MDM should alert if there are indicators that the device has been jailbroken so actions, such as wiping the device, can be implemented to protect device data. For iOS, jailbreak detection by a third-party application is limited; therefore, this requirement is a defense-in-depth control to supplement iOS jailbreak controls. ",
|
|
74
|
+
"severity": "low"
|
|
75
|
+
},
|
|
76
|
+
{
|
|
77
|
+
"id": "V-25754",
|
|
78
|
+
"title": "The PKI digital certificate installed on mobile management servers for server authentication must be a DoD PKI-issued certificate.",
|
|
79
|
+
"description": "When a self-signed PKI certificate is used, a rogue mobile management server can impersonate the DoD mobile management server. DoDI 8520-02 requires PKI certificates come from a trusted DoD PKI.",
|
|
80
|
+
"severity": "low"
|
|
81
|
+
},
|
|
82
|
+
{
|
|
83
|
+
"id": "V-26152",
|
|
84
|
+
"title": "S/MIME must be enabled on the server. ",
|
|
85
|
+
"description": "Sensitive DoD data could be exposed if the required setting is not configured on the Good server. If S/MIME support is not configured on the server, the user will not be able to view critical encrypted email or be able to encrypt email with sensitive DoD information.",
|
|
86
|
+
"severity": "medium"
|
|
87
|
+
},
|
|
88
|
+
{
|
|
89
|
+
"id": "V-26564",
|
|
90
|
+
"title": "Authentication on system administration accounts for mobile management servers must be configured to support CTO 07-15 Rev 1 requirements.\n",
|
|
91
|
+
"description": "CTO 07-15 Rev 1 requires administrator accounts use either CAC authentication or use complex passwords to ensure strong access control is enforced. This is best enforced by requiring the server support AD authentication.",
|
|
92
|
+
"severity": "high"
|
|
93
|
+
},
|
|
94
|
+
{
|
|
95
|
+
"id": "V-26728",
|
|
96
|
+
"title": "The MDM server must define the required MDM agent version.",
|
|
97
|
+
"description": "Older software versions do not support required security features.",
|
|
98
|
+
"severity": "low"
|
|
99
|
+
},
|
|
100
|
+
{
|
|
101
|
+
"id": "V-32745",
|
|
102
|
+
"title": "The MDM agent must wipe a managed mobile device if the MDM agent does not connect to the MDM server in 90 days or less.\n",
|
|
103
|
+
"description": "If a mobile device has not connected to the management server within the specified time period, this is an indication that the device is no longer being used, has been lost, or has been stolen. To protect possible sensitive data on the device from being compromised, the device should be wiped.\n",
|
|
104
|
+
"severity": "low"
|
|
105
|
+
},
|
|
106
|
+
{
|
|
107
|
+
"id": "V-33231",
|
|
108
|
+
"title": "The master AES encryption key used to encrypt data between the management server and the agent on the mobile device must be changed every 30 days or less. ",
|
|
109
|
+
"description": "There are two primary methods for generating the encryption key used to encrypt data between the management server and the server agent installed on the mobile device. The first method is to use a shared secret and the second is to generate the master encryption key based on PKI key generation. When a shared secret is used, if the master encryption key is not rotated periodically, and it is compromised, all future data sent between the mobile management server and the agent located on the mobile device would be compromised. Limiting the compromise to no more than a specific period of data is a security best practice.",
|
|
110
|
+
"severity": "low"
|
|
111
|
+
},
|
|
112
|
+
{
|
|
113
|
+
"id": "V-33996",
|
|
114
|
+
"title": "The MDM server must be configured to display an alert to the administrator when handhelds have been inactive after a defined period of time. ",
|
|
115
|
+
"description": "An inactive mobile device is an indication that the device may have been lost or stolen. In addition, provisioned devices have monthly fees associated with them and management should consider reallocating inactive devices.",
|
|
116
|
+
"severity": "low"
|
|
117
|
+
},
|
|
118
|
+
{
|
|
119
|
+
"id": "V-33999",
|
|
120
|
+
"title": "A valid Apple MDM certificate must be installed on the MDM server. ",
|
|
121
|
+
"description": "Without the Apple MDM certificate, the MDM server will not be able to manage a security policy on the iOS mobile device and DoD data will be at risk of compromise.",
|
|
122
|
+
"severity": "medium"
|
|
123
|
+
}
|
|
124
|
+
]
|
|
125
|
+
}
|
|
@@ -0,0 +1,2555 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "stig_mobile_device_manager_security_requirements_guide",
|
|
3
|
+
"date": "2013-01-24",
|
|
4
|
+
"description": "The MDM Security Requirements Guide (SRG) is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the NIST 800-53 and related documents. 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": "Mobile Device Manager Security Requirements Guide",
|
|
6
|
+
"version": "1",
|
|
7
|
+
"item_syntax": "^\\w-\\d+$",
|
|
8
|
+
"section_separator": null,
|
|
9
|
+
"items": [
|
|
10
|
+
{
|
|
11
|
+
"id": "V-36006",
|
|
12
|
+
"title": "The MDM server must provide automated support for account management functions.",
|
|
13
|
+
"description": "A comprehensive account management process that includes automation helps to ensure the accounts designated as requiring attention are consistently and promptly addressed. If an attacker compromises an account, the entire MDM server infrastructure is at risk. Providing automated support functions for the management of accounts will ensure only active accounts will be granted access with the proper authorization levels.\n\nAs accounts are created or terminated and privilege levels are updated, the MDM server implementation must be configured so it automatically recognizes and supports this activity and immediately enforces the current account policy.",
|
|
14
|
+
"severity": "high"
|
|
15
|
+
},
|
|
16
|
+
{
|
|
17
|
+
"id": "V-36007",
|
|
18
|
+
"title": "The MDM server must automatically disable inactive administrator accounts after an organization defined time period.\n",
|
|
19
|
+
"description": "Users are often the first line of defense within an application. Account management and distribution is vital to the security of the application. If an attacker compromises an account, the entire MDM server infrastructure, including the mobile devices on the network, are at risk. Authentication for user or administrative access to the system is required at all times. Inactive accounts could be reactivated or compromised by unauthorized users allowing them to exploit vulnerabilities and maintain undetected access to the system. \n\nThere is always a risk for inactive accounts to be reactivated or compromised by unauthorized users who could then gain full control of the device; thereby enabling them to trigger a Denial of Service, intercept sensitive information, or disrupt the MDM server.",
|
|
20
|
+
"severity": "high"
|
|
21
|
+
},
|
|
22
|
+
{
|
|
23
|
+
"id": "V-36008",
|
|
24
|
+
"title": "The MDM server must implement separation of administrator duties by requiring a specific role be assigned to each administrator account.\n",
|
|
25
|
+
"description": "Separation of duties supports the management of individual accountability and reduces the power of one individual or administrative account. Employing a separation of duties model reduces the threat that one individual has the authority to make changes to a system, and the authority to delete any record of those changes. \nThis requirement is intended to limit exposure due to operating from within a privileged account or role. The inclusion of a role is intended to address those situations where an access control policy, such as Role Based Access Control (RBAC), is being implemented and where a change of role provides the same degree of assurance in the change of access authorizations for both the user and all processes acting on behalf of the user as would be provided by a change between a privileged and non-privileged account. \n It is recommended that the following or similar roles be supported: \n- MDM server administrative account administrator: responsible for server installation, initial configuration, and maintenance functions.\n- Security configuration policy administrator (IA technical professional): responsible for security configuration of the server and setting up and maintenance of mobile device security policies.\n- Device management administrator (Technical operator): responsible for maintenance of mobile device accounts, including setup, change of account configurations, and account deletion.\n- Auditor (internal auditor or reviewer): responsible for reviewing and maintaining server and mobile device audit logs.",
|
|
26
|
+
"severity": "high"
|
|
27
|
+
},
|
|
28
|
+
{
|
|
29
|
+
"id": "V-36009",
|
|
30
|
+
"title": "The MDM server must enforce the organization defined limit of consecutive invalid access attempts by an administrator during the organization defined time period.\n",
|
|
31
|
+
"description": "Anytime an authentication method is exposed so as to allow for the utilization of an application, there is a risk that attempts will be made to obtain unauthorized access. \nOne of the most prevalent ways an attacker tries to gain access to a system is by repeatedly trying to access an account and guessing a password. \n\nTo reduce the risk of malicious access attempts being successful, the MDM server must define and limit the number of times a user account may consecutively fail a login attempt within a defined time period.\n\nBy limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attack, is reduced. ",
|
|
32
|
+
"severity": "high"
|
|
33
|
+
},
|
|
34
|
+
{
|
|
35
|
+
"id": "V-36010",
|
|
36
|
+
"title": "The MDM server, when the maximum number of unsuccessful attempts is exceeded, must automatically lock the account for an organization defined time period or must lock the account until released by an administrator IAW organizational policy.\n",
|
|
37
|
+
"description": "One of the most prevalent ways an attacker tries to gain access to a system is by repeatedly trying to access an account and guessing a password. \n\nTo reduce the risk of malicious access attempts being successful, the MDM server must define and limit the number of times a user account may consecutively fail a login attempt within a defined time period, and subsequently lock that account when the maximum numbers have been reached. \n\nBy limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attack, is reduced. ",
|
|
38
|
+
"severity": "high"
|
|
39
|
+
},
|
|
40
|
+
{
|
|
41
|
+
"id": "V-36011",
|
|
42
|
+
"title": "The MDM server must display an approved system use notification message or banner before granting access to the system.\n",
|
|
43
|
+
"description": "Applications are required to display an approved system use notification message or banner before granting access to the system providing privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance and states that: \n\n(i) users are accessing a U.S. Government information system; \n(ii) system usage may be monitored, recorded, and subject to audit; \n(iii) unauthorized use of the system is prohibited and subject to criminal and civil penalties; and \n(iv) the use of the system indicates consent to monitoring and recording.\n\nSystem use notification messages can be implemented in the form of warning banners displayed when individuals log in to the information system. \n\nSystem use notification is intended only for information system access including an interactive login interface with a human user and is not intended to require notification when an interactive interface does not exist. \n\nUse this banner for desktops, laptops, and other devices accommodating banners of 1300 characters. The banner shall be implemented as a click-through banner at logon (to the extent permitted by the MDM server), meaning it prevents further activity on the information system unless and until the user executes a positive action to manifest agreement by clicking on a box indicating “OK”.\n\n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.\n-At any time, the USG may inspect and seize data stored on this IS.\n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.\"\n \n\nFor BlackBerry and other PDAs/PEDs with severe character limitations use the following:\n\n\"I've read & consent to terms in IS user agreement.\"",
|
|
44
|
+
"severity": "low"
|
|
45
|
+
},
|
|
46
|
+
{
|
|
47
|
+
"id": "V-36012",
|
|
48
|
+
"title": "The MDM server must retain the logon banner on the screen unless the administrator takes explicit actions to logon to the server.\n",
|
|
49
|
+
"description": "To establish acceptance of system usage policy, a click-through banner at application logon is required. The banner shall prevent further activity on the application unless and until the user executes a positive action to manifest agreement by clicking on a box indicating \"OK\". The text of this banner should be customizable in the event of future user agreement changes. Failure to display the required login warning banner prior to log on attempts will limit the ability to prosecute unauthorized access and also presents the potential to give rise to criminal and civil liability for systems administrators and information systems managers. In addition, DoD's ability to monitor the device's usage is limited unless a proper warning banner is displayed.\n",
|
|
50
|
+
"severity": "low"
|
|
51
|
+
},
|
|
52
|
+
{
|
|
53
|
+
"id": "V-36013",
|
|
54
|
+
"title": "The MDM server, upon successful logon, must display to the administrator the date and time of the last logon (access).\n",
|
|
55
|
+
"description": "MDM server users need to be very vigilant in maintaining situational awareness of activity that occurs regarding their accounts. Providing them with information regarding the date and time of their last successful login allows them to determine if any unauthorized activity has occurred, gives them an opportunity to notify appropriate security personnel if necessary, and ensure other systems have not been affected. If administrators are not aware of potential attacks against a system, they cannot perform due diligence to ensure access is not granted to unauthorized users.",
|
|
56
|
+
"severity": "low"
|
|
57
|
+
},
|
|
58
|
+
{
|
|
59
|
+
"id": "V-36014",
|
|
60
|
+
"title": "The MDM server, before or upon successful unlock, must display to the administrator the number of unsuccessful unlock attempts since the last successful unlock.\n",
|
|
61
|
+
"description": "MDM server users need to be very vigilant in maintaining situational awareness of activity that occurs regarding their accounts. Providing them with information regarding the date and time of unsuccessful login allows them to determine if any unauthorized activity has occurred, gives them an opportunity to notify appropriate security personnel if necessary, and ensure other systems have not been affected. If administrators are not aware of potential attacks against a system, they cannot perform due diligence to ensure access is not granted to unauthorized users.\n",
|
|
62
|
+
"severity": "low"
|
|
63
|
+
},
|
|
64
|
+
{
|
|
65
|
+
"id": "V-36015",
|
|
66
|
+
"title": "The MDM server must limit the number of concurrent sessions for each account to an organization defined number of sessions.\n",
|
|
67
|
+
"description": "Limiting the number of concurrent sessions reduces the risk of Denial of Service (DoS) to the MDM server from overburdening the system from a potential attacker.",
|
|
68
|
+
"severity": "medium"
|
|
69
|
+
},
|
|
70
|
+
{
|
|
71
|
+
"id": "V-36016",
|
|
72
|
+
"title": "The MDM server must have the ability to retain a session lock remaining in effect until the user re-authenticates using established identification and authentication procedures.\n",
|
|
73
|
+
"description": "If the MDM server does not support a lock feature, then anyone who gains access to the application may be able to access sensitive DoD information or perform other authorized functions. The lock features mitigates the risk of unauthorized access.\n",
|
|
74
|
+
"severity": "high"
|
|
75
|
+
},
|
|
76
|
+
{
|
|
77
|
+
"id": "V-36017",
|
|
78
|
+
"title": "The MDM server must lock the application after an organization defined time period.\n",
|
|
79
|
+
"description": "If the MDM server does not support a lock feature, then anyone who gains access to the application may be able to access sensitive DoD information or perform other authorized functions. The lock feature mitigates the risk of unauthorized access.\n",
|
|
80
|
+
"severity": "high"
|
|
81
|
+
},
|
|
82
|
+
{
|
|
83
|
+
"id": "V-36018",
|
|
84
|
+
"title": "The MDM server must provide the capability for an administrator to lock the application console.\n",
|
|
85
|
+
"description": "If the MDM server does not support a lock feature, then anyone who gains access to the application may be able to access sensitive DoD information or perform other authorized functions. The lock features mitigates the risk of unauthorized access.\n",
|
|
86
|
+
"severity": "high"
|
|
87
|
+
},
|
|
88
|
+
{
|
|
89
|
+
"id": "V-36019",
|
|
90
|
+
"title": "The MDM server session lock mechanism, when activated on the server, must place a publicly viewable pattern onto the associated display, hiding what was previously visible on the screen.\n",
|
|
91
|
+
"description": "A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. \n\nThe session lock is implemented at the point where session activity can be determined. This is typically at the operating system-level, but may be at the application-level. \n\nWhen the application design specifies the application rather than the operating system will determine when to lock the session, the application session lock event must include an obfuscation of the display screen so as to prevent other users from reading what was previously displayed. \n\nAn example of obfuscation is a screensaver creating a viewable pattern that overwrites the entire screen rendering the screen contents unreadable. ",
|
|
92
|
+
"severity": "high"
|
|
93
|
+
},
|
|
94
|
+
{
|
|
95
|
+
"id": "V-36020",
|
|
96
|
+
"title": "The MDM server must enforce requirements for remote connections to the information system.\n",
|
|
97
|
+
"description": "The organization will define the requirements for connection of remote connections. In order to ensure the connection provides adequate integrity and confidentiality of the connection, the MDM server must enforce these requirements.\n\nThis rule requires explicit authorization prior to allowing remote access to an information system without specifying a specific format for that authorization. For example, while the organization may deem it appropriate to use a system interconnection agreement to authorize a given remote access, such agreements are not required by this rule.",
|
|
98
|
+
"severity": "high"
|
|
99
|
+
},
|
|
100
|
+
{
|
|
101
|
+
"id": "V-36021",
|
|
102
|
+
"title": "The MDM server must monitor for unauthorized connections of mobile devices to the MDM server application.\n",
|
|
103
|
+
"description": "Mobile devices include portable storage media (e.g., USB memory sticks, external hard disk drives) and portable computing and communications devices with information storage capability (e.g., notebook/laptop computers, personal digital assistants, cellular telephones, digital cameras, audio recording devices). \n\nUnapproved or unrecognized devices connected to the network and being served by an MDM server as well can lead to malware possibly gaining control over the MDM server. ",
|
|
104
|
+
"severity": "medium"
|
|
105
|
+
},
|
|
106
|
+
{
|
|
107
|
+
"id": "V-36022",
|
|
108
|
+
"title": "The MDM server must protect against an individual falsely denying having performed a particular action.\n",
|
|
109
|
+
"description": "Non-repudiation of actions taken is required in order to maintain application integrity. Examples of particular actions taken by individuals include creating information, sending a message, approving information (e.g., indicating concurrence or signing a contract), and receiving a message. \n\nWhen non-repudiation techniques are not employed, high assurance that an individual performed a specific action cannot be guaranteed and the individual can falsely deny having performed such action and therefore, be held unaccountable. Non-repudiation protects individuals against later claims by an author of not having authored a particular document, a sender of not having transmitted a message, a receiver of not having received a message, or a signatory of not having signed a document.",
|
|
110
|
+
"severity": "medium"
|
|
111
|
+
},
|
|
112
|
+
{
|
|
113
|
+
"id": "V-36023",
|
|
114
|
+
"title": "The MDM server must require a password to access the servers private keys saved in the key certificate store that meets organizationally defined network administrator password requirements.\n",
|
|
115
|
+
"description": "The cornerstone of the PKI is the private key used to encrypt or digitally sign information. Allowing unauthenticated access to private keys can enable an adversary in possession of the device to decrypt messages encrypted with the public-key and to digitally sign data, thereby potentially enabling an adversary to impersonate the user in any application that uses that private key for user authentication. Requiring a password to access keys saved in the certificate store mitigates the risk of unauthorized access.\n",
|
|
116
|
+
"severity": "medium"
|
|
117
|
+
},
|
|
118
|
+
{
|
|
119
|
+
"id": "V-36024",
|
|
120
|
+
"title": "The MDM server must support administrator authentication to the server via the Enterprise Authentication Mechanisms authentication. \n",
|
|
121
|
+
"description": "In the DoD, Administrator credential requirements for authentication are defined by CTO 07-115 Rev 1, which is usually enforced by the Enterprise Authentication Mechanism. Non-complaint credential enforcement mechanisms make the DoD IS vulnerable to attack.\n",
|
|
122
|
+
"severity": "medium"
|
|
123
|
+
},
|
|
124
|
+
{
|
|
125
|
+
"id": "V-36025",
|
|
126
|
+
"title": "The MDM server must not transmit passwords in clear text.\n",
|
|
127
|
+
"description": "Transmission of passwords in clear text reveals the password to any adversary who can successfully eavesdrop on the communication. In the case of wireless communication, the ability to eavesdrop is available to anyone within the range of the device’s radio signal, which in some cases can be miles. Once an adversary has obtained a password, the adversary may be able to use it to compromise sensitive DoD information or other DoD information systems. Using methods that avoid the transmission of passwords in clear text mitigates the risk of this attack.",
|
|
128
|
+
"severity": "high"
|
|
129
|
+
},
|
|
130
|
+
{
|
|
131
|
+
"id": "V-36026",
|
|
132
|
+
"title": "The MDM server must obscure a password when it is entered on the server. \n",
|
|
133
|
+
"description": "To prevent the compromise of authentication information, such as passwords during the authentication process, the feedback from the MDM server shall not provide any information that would allow an unauthorized user to compromise the authentication mechanism. During the authentication process, malicious users can gain knowledge of passwords by simply walking by a user logging on, and viewing what had been input. Obfuscation of user provided information when typed into the system is a method used in addressing this risk. \n",
|
|
134
|
+
"severity": "low"
|
|
135
|
+
},
|
|
136
|
+
{
|
|
137
|
+
"id": "V-36027",
|
|
138
|
+
"title": "The MDM server must enforce approved authorizations for logical access to the system in accordance with applicable policy.\n",
|
|
139
|
+
"description": "Strong access controls are critical to securing the MDM server. Access control policies (e.g., identity-based policies, role-based policies, attribute-based policies) and access enforcement mechanisms (e.g., access control lists, access control matrices, cryptography) must be employed by the MDM server when applicable to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, domains) in the MDM server.\n\nWithout stringent logical access and authorization controls to the MDM server, an adversary may have the ability, with very little effort, to compromise the MDM server and associated supporting infrastructure. ",
|
|
140
|
+
"severity": "high"
|
|
141
|
+
},
|
|
142
|
+
{
|
|
143
|
+
"id": "V-36028",
|
|
144
|
+
"title": "The MDM server must utilize only approved versions of components, including the mobile device integrity scanning component and mobile email management component (if used).\n",
|
|
145
|
+
"description": "Approved versions of components have gone though all required phases of testing, approval, etc. Using non-approved versions of server components could compromise the functionality of the MDM server environment.\n",
|
|
146
|
+
"severity": "high"
|
|
147
|
+
},
|
|
148
|
+
{
|
|
149
|
+
"id": "V-36029",
|
|
150
|
+
"title": "The MDM server must be capable of scanning the hardware version of managed mobile devices and alert if unsupported versions are found.\n",
|
|
151
|
+
"description": "Approved versions of devices have gone though all required phases of testing, approval, etc., and are able to support required security features. Using non-approved versions of mobile device hardware could compromise the security baseline of the mobile system, since some required security features may not be supported.\n",
|
|
152
|
+
"severity": "high"
|
|
153
|
+
},
|
|
154
|
+
{
|
|
155
|
+
"id": "V-36030",
|
|
156
|
+
"title": "The host server where the MDM server components are installed must be hardened according to the appropriate Application and OS STIGs (Windows, SQL, Apache Web Server, Apache Tomcat, IIS, etc.).\n",
|
|
157
|
+
"description": "The host server where the MDM server components are installed must be compliant with the Windows STIG and applicable application STIGs to ensure the system is not vulnerable to attack resulting in a Denial of Service or compromise of the MDM server environment.",
|
|
158
|
+
"severity": "medium"
|
|
159
|
+
},
|
|
160
|
+
{
|
|
161
|
+
"id": "V-36031",
|
|
162
|
+
"title": "The MDM server must employ automated mechanisms to enforce access restrictions.\n",
|
|
163
|
+
"description": "When dealing with access restrictions pertaining to change control, it should be noted that, any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have significant effects on the overall security of the system. \n\nAny changes to the hardware, software, and/or firmware components of the MDM server can potentially have significant effects on the overall security of the system. Therefore, only qualified and authorized individuals should be allowed to obtain access to the MDM server components for the purposes of implementing any changes or upgrades.",
|
|
164
|
+
"severity": "medium"
|
|
165
|
+
},
|
|
166
|
+
{
|
|
167
|
+
"id": "V-36032",
|
|
168
|
+
"title": "The MDM server must configure the information system to specifically prohibit or restrict the use of organization defined functions, ports, protocols, and/or services on the server.\n\n\n",
|
|
169
|
+
"description": "Most information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations. Unneeded services and processes provide additional threat vectors and avenues of attack to the information system. The MDM server is a critical component of the mobility architecture and it must be configured to only those ports, protocols, and services (PPS) necessary to support functionality, all others must be expressly disabled or removed. The DoD Category Assurance List (CAL) should be referenced for compliance.",
|
|
170
|
+
"severity": "high"
|
|
171
|
+
},
|
|
172
|
+
{
|
|
173
|
+
"id": "V-36033",
|
|
174
|
+
"title": "The MDM server host based firewall must be configured to Deny All except when explicitly authorized and block all incoming and outgoing ports, protocols, and IP address ranges except for those required to support the MDM server functions.\n",
|
|
175
|
+
"description": "Most information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations. Since the MDM server is a critical component of the mobility architecture and it must be configured to only those ports, protocols, and services (PPS) necessary to support functionality, all others must be expressly disabled or removed. A host firewall installed on the MDM server provides a protection mechanism to ensure unwanted service requests do not reach the MDM server and outbound traffic is limited to only MDM server functionality. By not allowing only known good traffic into the MDM server, the MDM server could be vulnerability to denial of service attacks, as well as brute-force attacks by intruders.\n",
|
|
176
|
+
"severity": "high"
|
|
177
|
+
},
|
|
178
|
+
{
|
|
179
|
+
"id": "V-36034",
|
|
180
|
+
"title": "The MDM server must disable network access by unauthorized server components or notify designated organizational officials.\n",
|
|
181
|
+
"description": "Maintaining system and network integrity requires all systems on the network are identified and accounted for. Without an accurate accounting of systems utilizing the network, the opportunity exists for the introduction of rogue systems. The significance of this manner of security compromise increases exponentially over time and could become a persistent threat. Therefore, organizations must employ automated mechanisms to detect the addition unauthorized devices. Eliminating unauthorized access to the network is vital to maintaining a secured network. For an MDM server, this accounting extends to the allowance of specific mobile devices to access the network via the MDM server.",
|
|
182
|
+
"severity": "medium"
|
|
183
|
+
},
|
|
184
|
+
{
|
|
185
|
+
"id": "V-36035",
|
|
186
|
+
"title": "The MDM server data must be backed up per a defined frequency.\n",
|
|
187
|
+
"description": "Information 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. In order to assure availability of this data in the event of a system failure, DoD organizations are required to ensure user generated data is backed up at a defined frequency. This includes data stored on file systems, within databases or within any other storage media.\n\nApplications performing backups must be capable of backing up user-level information per the DoD defined frequency.",
|
|
188
|
+
"severity": "medium"
|
|
189
|
+
},
|
|
190
|
+
{
|
|
191
|
+
"id": "V-36036",
|
|
192
|
+
"title": "The MDM server must conduct backups of system-level information contained in the information system per organization defined frequency to conduct backups that are consistent with recovery time and recovery point objectives.\n",
|
|
193
|
+
"description": "MDM server backup is a critical step in maintaining data assurance and availability. Without available back up data to restore a system in the event of a system failure, the system may be rendered useless. If the MDM server fails and there is no backup of the MDM server information, a denial of service condition is possible for all who utilize this critical network component. ",
|
|
194
|
+
"severity": "medium"
|
|
195
|
+
},
|
|
196
|
+
{
|
|
197
|
+
"id": "V-36037",
|
|
198
|
+
"title": "The MDM server must use multifactor authentication via an Enterprise Authentication Mechanism for network access to privileged accounts.\n",
|
|
199
|
+
"description": "Single factor authentication poses much unnecessary risk upon any information system as most single factor authentication methods use only a userid and password. Passwords are, in most cases, easily hacked with the right tools. Multifactor authentication utilizes multiple levels of identification and authorization criteria and provides a much stronger level of security than single factor. As privileged users have access to most of the files on the platform, using a single factor authentication approach provides an easy avenue of attack for a malicious user. \n\nMultifactor authentication includes: \n\n(i) something a user knows (e.g., password/PIN); \n(ii) something a user has (e.g., cryptographic identification device, token); or \n(iii) something a user is (e.g., biometric). ",
|
|
200
|
+
"severity": "high"
|
|
201
|
+
},
|
|
202
|
+
{
|
|
203
|
+
"id": "V-36038",
|
|
204
|
+
"title": "The MDM server must use multifactor authentication via an Enterprise Authentication Mechanism for local access to privileged accounts.\n",
|
|
205
|
+
"description": "Single factor authentication poses much unnecessary risk upon any information system as most single factor authentication methods use only a userid and password. Passwords are, in most cases, easily hacked with the right tools. Multifactor authentication utilizes multiple levels of identification and authorization criteria and provides a much stronger level of security than single factor. As privileged users have access to most of the files on the platform, using a single factor authentication approach provides an easy avenue of attack for a malicious user. \n\nMultifactor authentication includes: \n\n(i) something a user knows (e.g., password/PIN); \n(ii) something a user has (e.g., cryptographic identification device, token); or \n(iii) something a user is (e.g., biometric). ",
|
|
206
|
+
"severity": "high"
|
|
207
|
+
},
|
|
208
|
+
{
|
|
209
|
+
"id": "V-36039",
|
|
210
|
+
"title": "The MDM server must require administrators to be authenticated with an individual authenticator prior to using a group authenticator.\n",
|
|
211
|
+
"description": "To assure individual accountability and prevent unauthorized access, MDM server administrators and users (and any processes acting on behalf of users) must be individually identified and authenticated. Without individual accountability, there can be no traceability back to an individual if there were a security incident on the system. In addition, group accounts can be shared with individuals who do not have authorized access. \n",
|
|
212
|
+
"severity": "high"
|
|
213
|
+
},
|
|
214
|
+
{
|
|
215
|
+
"id": "V-36040",
|
|
216
|
+
"title": "The MDM server must use organization defined replay-resistant authentication mechanisms for network access to privileged accounts.\n",
|
|
217
|
+
"description": "An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. Replay attacks, if successfully used against a MDM server account could result in unfettered access to the MDM server settings and data records. ",
|
|
218
|
+
"severity": "high"
|
|
219
|
+
},
|
|
220
|
+
{
|
|
221
|
+
"id": "V-36041",
|
|
222
|
+
"title": "The MDM server must disable administrative accounts after an organization defined time period of inactivity.\n",
|
|
223
|
+
"description": "Users are often the first line of defense within an application. Active users take notice of system and data conditions and are usually the first to notify systems administrators when they notice a system or application related anomaly, particularly if the anomaly is related to their own account. \n\nInactive user accounts pose a risk to systems and applications. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. Attackers that are able to exploit an inactive account can potentially obtain and maintain undetected access to the system. Systems need to track periods of user inactivity and disable accounts after an organization defined period of inactivity. Such a process greatly reduces the risk that accounts will be misused, hijacked, or will have data compromised.",
|
|
224
|
+
"severity": "high"
|
|
225
|
+
},
|
|
226
|
+
{
|
|
227
|
+
"id": "V-36042",
|
|
228
|
+
"title": "The MDM server must use mechanisms for authentication to a cryptographic module meeting the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication.\n",
|
|
229
|
+
"description": "MDM server applications utilizing encryption are required to use approved encryption modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. Encryption is only as good as the encryption modules utilized. Unapproved cryptographic module algorithms cannot be verified, and cannot be relied upon to provide confidentiality or integrity and DoD data may be compromised due to weak algorithms. ",
|
|
230
|
+
"severity": "high"
|
|
231
|
+
},
|
|
232
|
+
{
|
|
233
|
+
"id": "V-36043",
|
|
234
|
+
"title": "The PKI key store of the MDM server must be FIPS validated.\n",
|
|
235
|
+
"description": " MDM server applications utilizing encryption are required to use approved encryption modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. Encryption is only as good as the encryption modules utilized. Unapproved cryptographic module algorithms cannot be verified, and cannot be relied upon to provide confidentiality or integrity and DoD data may be compromised due to weak algorithms. FIPS validation ensures the encryption algorithm is suitable for the DoD environment.\n",
|
|
236
|
+
"severity": "medium"
|
|
237
|
+
},
|
|
238
|
+
{
|
|
239
|
+
"id": "V-36044",
|
|
240
|
+
"title": "The MDM server must employ strong identification and authentication techniques in the establishment of non-local maintenance and diagnostic sessions.\n",
|
|
241
|
+
"description": "Lack of authentication enables anyone to gain access to the MDM server. Network access control mechanisms interoperate to prevent unauthorized access and to enforce the organization's security policy. Authorization for access to the MDM server to perform maintenance and diagnostics requires an individual account identifier that has been approved, assigned, and configured. Authentication of non-local maintenance and diagnostics sessions must be accomplished through two-factor authentication via the combination of passwords, tokens, and biometrics.",
|
|
242
|
+
"severity": "high"
|
|
243
|
+
},
|
|
244
|
+
{
|
|
245
|
+
"id": "V-36045",
|
|
246
|
+
"title": "The MDM server must terminate all sessions and network connections when non-local maintenance is completed.\n",
|
|
247
|
+
"description": "In the event the remote node has abnormally terminated or an upstream link from the MDM server is down, the management session will be terminated; thereby, freeing device resources and eliminating any possibility of an unauthorized user being orphaned to an open idle session of the MDM server.\n",
|
|
248
|
+
"severity": "medium"
|
|
249
|
+
},
|
|
250
|
+
{
|
|
251
|
+
"id": "V-36046",
|
|
252
|
+
"title": "The MDM server must use organizational requirements to employ cryptographic mechanisms to protect information in storage.\n",
|
|
253
|
+
"description": "When data is written to digital media, there is risk of loss of data along with integrity and data confidentiality. An organizational assessment of risk guides the selection of media and associated information contained on the media requiring physical protection. Fewer protection measures are needed for media containing information determined by the organization to be in the public domain, to be publicly releasable, or to have limited or no adverse impact on the organization or individuals if accessed by other than authorized personnel. In these situations, it is assumed the physical access controls to the facility where the media resides provide adequate protection. \n\nAs part of a defense-in-depth strategy, the organization considers routinely encrypting information at rest on selected secondary storage devices. The employment of cryptography is at the discretion of the information owner/steward. The selection of the cryptographic mechanisms used is based upon maintaining the confidentiality and integrity of the information. The strength of mechanisms is commensurate with the classification and sensitivity of the information.",
|
|
254
|
+
"severity": "medium"
|
|
255
|
+
},
|
|
256
|
+
{
|
|
257
|
+
"id": "V-36047",
|
|
258
|
+
"title": "The MDM server must prevent unauthorized and unintended access to shared system resources by applications on managed mobile devices.\n",
|
|
259
|
+
"description": "The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current user/role (or current process) that obtains access to a shared system resource (e.g., registers, main memory, secondary storage) after the resource has been released back to the information system. Control of information in shared resources is also referred to as object reuse. This prevents inadvertent data disclosure from one process to another.\n",
|
|
260
|
+
"severity": "low"
|
|
261
|
+
},
|
|
262
|
+
{
|
|
263
|
+
"id": "V-36048",
|
|
264
|
+
"title": "The MDM server must be able to filter both inbound and outbound traffic based on IP address and UDP/TCP port.\n",
|
|
265
|
+
"description": "A host-based boundary protection mechanism is a host-based firewall. Host-based boundary protection mechanisms are employed on mobile devices, such as notebook/laptop computers, and other types of mobile devices where such boundary protection mechanisms are available. This helps mitigate attacks at the network interface.\n",
|
|
266
|
+
"severity": "high"
|
|
267
|
+
},
|
|
268
|
+
{
|
|
269
|
+
"id": "V-36049",
|
|
270
|
+
"title": "The MDM server must be configured so the connection between the MDM server and the mobile device is initiated based on an out-bound connection request from the MDM server only.\n",
|
|
271
|
+
"description": "By configuring the MDM server to connect to the mobile device on an out-bound connection, the traffic is segregated which made it more difficult for an intruder to compromise the device management session.\n",
|
|
272
|
+
"severity": "low"
|
|
273
|
+
},
|
|
274
|
+
{
|
|
275
|
+
"id": "V-36050",
|
|
276
|
+
"title": "The MDM server must maintain the confidentiality of information during aggregation, packaging, and transformation in preparation for transmission. When transmitting data, applications need to leverage transmission protection mechanisms, such as TLS, SSL VPN, or IPSEC tunnel. \n",
|
|
277
|
+
"description": "Preventing the disclosure of transmitted information requires that applications take measures to employ some form of cryptographic mechanism in order to protect the information during transmission. This is usually achieved through the use of Transport Layer Security (TLS), SSL VPN, or IPSEC tunnel. Without these cryptographic mechanisms, the data could be disclosed to unauthorized users or processes during aggregation, packaging, and transformation in preparation for transmission.\n",
|
|
278
|
+
"severity": "medium"
|
|
279
|
+
},
|
|
280
|
+
{
|
|
281
|
+
"id": "V-36051",
|
|
282
|
+
"title": "The MDM server must terminate the network connection associated with a communications session at the end of the session or after an organization defined time period of inactivity.\n",
|
|
283
|
+
"description": "If communications sessions remain open for extended periods of time even when unused, there is the potential for an adversary to highjack the session and use it to gain access to the device or networks to which it is attached. Terminating sessions after a certain period of inactivity is a method for mitigating the risk of this vulnerability.\n",
|
|
284
|
+
"severity": "low"
|
|
285
|
+
},
|
|
286
|
+
{
|
|
287
|
+
"id": "V-36052",
|
|
288
|
+
"title": "The cryptographic module supporting encryption of the certificate store must be FIPS 140-2 validated.\n",
|
|
289
|
+
"description": "The most common vulnerabilities with cryptographic modules are those associated with poor implementation. FIPS 140 validation provides assurance that the relevant cryptography has been implemented correctly to ensure confidentiality of the data store. FIPS validation is also a strict requirement for use of cryptography in the Federal Government.\n",
|
|
290
|
+
"severity": "medium"
|
|
291
|
+
},
|
|
292
|
+
{
|
|
293
|
+
"id": "V-36053",
|
|
294
|
+
"title": "The cryptographic module supporting encryption of data at rest must be FIPS 140-2 validated.\n",
|
|
295
|
+
"description": "The most common vulnerabilities with cryptographic modules are those associated with poor implementation. FIPS 140 validation provides assurance that the relevant cryptography has been implemented correctly to ensure confidentiality of the data at rest. FIPS validation is also a strict requirement for use of cryptography in the Federal Government.\n",
|
|
296
|
+
"severity": "medium"
|
|
297
|
+
},
|
|
298
|
+
{
|
|
299
|
+
"id": "V-36054",
|
|
300
|
+
"title": "The MDM server must employ NSA approved cryptography when cryptography is required to protect classified information.",
|
|
301
|
+
"description": "The most common vulnerabilities with cryptographic modules are those associated with poor implementation. NSA approval is required for cryptography for classified data and applications when such data is not adequately protected through local physical security controls. NSA approval provides assurance that the implementation is not vulnerable to attacks that might impact the confidentiality, integrity, or availability of the information.",
|
|
302
|
+
"severity": "high"
|
|
303
|
+
},
|
|
304
|
+
{
|
|
305
|
+
"id": "V-36055",
|
|
306
|
+
"title": "The MDM server must protect the integrity and availability of publicly available information and applications.\n",
|
|
307
|
+
"description": "The MDM server may provide information that has to be made publicly available, therefore security of the MDM server system is paramount to protect the integrity and availability of the MDM server structure and the information that it provides to the network and public. The purpose of this control is to ensure organizations explicitly address the protection needs for public information and applications with such protection likely being implemented as part of other security controls. \n",
|
|
308
|
+
"severity": "low"
|
|
309
|
+
},
|
|
310
|
+
{
|
|
311
|
+
"id": "V-36056",
|
|
312
|
+
"title": "The MDM server must terminate administrator sessions upon administrator logout or any other organization or policy defined session termination events such as idle time limit exceeded.\n",
|
|
313
|
+
"description": "If communications sessions remain open for extended periods of time even when unused, there is the potential for an adversary to highjack the session and use it to gain access to the device or networks to which it is attached. Terminating sessions after a certain period of inactivity is a method for mitigating the risk of this vulnerability.\n",
|
|
314
|
+
"severity": "medium"
|
|
315
|
+
},
|
|
316
|
+
{
|
|
317
|
+
"id": "V-36057",
|
|
318
|
+
"title": "The MDM server must provide a logout functionality to allow the user to manually terminate the session.\n",
|
|
319
|
+
"description": "Manually terminating an application session allows users to immediately depart the physical vicinity of the system they are logged into without the risk of subsequent system users reactivating or continuing their application session. Users who log into the MDM server application must have the ability to manually terminate their application session. \n",
|
|
320
|
+
"severity": "medium"
|
|
321
|
+
},
|
|
322
|
+
{
|
|
323
|
+
"id": "V-36058",
|
|
324
|
+
"title": "The MDM server must fail to an organization defined known-state for organization defined types of failures.\n",
|
|
325
|
+
"description": "Failure in a known state can address safety or security in accordance with the mission/business needs of the organization. It helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. Preserving system state information facilitates system restart and return to the operational mode of the organization with less disruption of mission/business processes.\n",
|
|
326
|
+
"severity": "high"
|
|
327
|
+
},
|
|
328
|
+
{
|
|
329
|
+
"id": "V-36059",
|
|
330
|
+
"title": "The MDM server must protect the confidentiality and integrity of information at rest.\n",
|
|
331
|
+
"description": "This control is intended to address the confidentiality and integrity of information at rest in non-mobile devices and covers user information and system information. Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive, tape drive). The MDM server must ensure the data being written to these devices is protected. In most cases, this is done via encryption. Without encryption, data while at rest can be copied from secondary storage by an attacker.\n",
|
|
332
|
+
"severity": "medium"
|
|
333
|
+
},
|
|
334
|
+
{
|
|
335
|
+
"id": "V-36060",
|
|
336
|
+
"title": "The MDM server must protect the integrity of information during the processes of data aggregation, packaging, and transformation in preparation for transmission.\n",
|
|
337
|
+
"description": "Information can be subjected to unauthorized changes (e.g., malicious and/or unintentional modification) at information aggregation or protocol transformation points. It is therefore imperative the application take steps to validate and assure the integrity of data while at these stages of processing. \n",
|
|
338
|
+
"severity": "low"
|
|
339
|
+
},
|
|
340
|
+
{
|
|
341
|
+
"id": "V-36061",
|
|
342
|
+
"title": "The MDM server must support automated patch management tools to facilitate flaw remediation of all software components on the server.\n",
|
|
343
|
+
"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. Left un-patched, software may be vulnerable to a variety of exploits that could disclose sensitive information or lead to subsequent security breaches. An automated patch management tool can mitigate this risk.\n",
|
|
344
|
+
"severity": "medium"
|
|
345
|
+
},
|
|
346
|
+
{
|
|
347
|
+
"id": "V-36062",
|
|
348
|
+
"title": "The MDM server must periodically verify the correct operation of security functions in the server.\n",
|
|
349
|
+
"description": "Security functional testing involves testing the operating system for conformance to the operating system security function specifications, as well as, for the underlying security model. The need to verify security functionality applies to all security functions. The conformance criteria state the conditions necessary for the MDM server to exhibit the desired security behavior or satisfy a security property for example, successful login triggers an audit entry. If tests are not provided and periodically run, the integrity of the system state cannot be verified. \n",
|
|
350
|
+
"severity": "medium"
|
|
351
|
+
},
|
|
352
|
+
{
|
|
353
|
+
"id": "V-36063",
|
|
354
|
+
"title": "The MDM server must provide notification to an external device of failed automated security tests on the server.\n",
|
|
355
|
+
"description": "Automated security tests are critical in the detection of IA attacks. Such checks include verification of the integrity of system files, device drivers, and security enforcement mechanisms. However, users and systems administrators can only benefit from the security tests of they are notified in case of failure. A notification mechanism reduces the risk that a security breach will go undetected.\n",
|
|
356
|
+
"severity": "high"
|
|
357
|
+
},
|
|
358
|
+
{
|
|
359
|
+
"id": "V-36064",
|
|
360
|
+
"title": "The MDM server must check the validity of information inputs.\n",
|
|
361
|
+
"description": "Invalid user input occurs when a user inserts data or characters into an applications data entry fields and the application is unprepared to process that data. This results in unanticipated application behavior potentially leading to an application or information system compromise. Invalid user input is one of the primary methods employed when attempting to compromise an application. \n",
|
|
362
|
+
"severity": "medium"
|
|
363
|
+
},
|
|
364
|
+
{
|
|
365
|
+
"id": "V-36065",
|
|
366
|
+
"title": "The MDM server must identify potentially security relevant error conditions on the server.\n",
|
|
367
|
+
"description": "Error messages generated by the MDM server can indicate a possible security violation or breach. The MDM server system must be configured to be able to recognize those error messages that can be a symptom of a compromise and to provide notification. If security-relevant error conditions are not identified by the MDM server they may be overlooked by the personnel responsible for addressing them.\n",
|
|
368
|
+
"severity": "low"
|
|
369
|
+
},
|
|
370
|
+
{
|
|
371
|
+
"id": "V-36066",
|
|
372
|
+
"title": "The MDM server must reveal error messages only to authorized personnel.\n",
|
|
373
|
+
"description": "If the MDM server provides too much information in error logs and administrative messages to the screen it could lead to compromise. The structure and content of error messages need to be carefully considered by the organization.\n",
|
|
374
|
+
"severity": "low"
|
|
375
|
+
},
|
|
376
|
+
{
|
|
377
|
+
"id": "V-36067",
|
|
378
|
+
"title": "The MDM server must activate an organization defined alarm and/or automatically shut down the server, if a server component failure is detected.\n",
|
|
379
|
+
"description": "Predictable failure prevention requires organizational planning to address system failure issues. Since the MDM server is key to maintaining security, if it fails to function, the system could continue operating in an insecure state. The MDM server must alarm for such conditions and/or automatically shuts down.\n",
|
|
380
|
+
"severity": "low"
|
|
381
|
+
},
|
|
382
|
+
{
|
|
383
|
+
"id": "V-36068",
|
|
384
|
+
"title": "The MDM server must validate the binding of the information producers identity to the information.\n",
|
|
385
|
+
"description": "Non-repudiation protects individuals against later claims by an author of not having authored a particular document, a sender of not having transmitted a message, a receiver of not having received a message, or a signatory of not having signed a document. For the MDM server, this requirement applies for software updates or applications pushed from the server to managed devices. The MDM server must validate the origin of software updates and applications.\n",
|
|
386
|
+
"severity": "medium"
|
|
387
|
+
},
|
|
388
|
+
{
|
|
389
|
+
"id": "V-36069",
|
|
390
|
+
"title": "The MDM server must display an approved system use notification message or banner before granting access to the system.\n",
|
|
391
|
+
"description": "If the MDM server does not display an appropriate warning display, the organization may not be able to take appropriate legal action in the case of a system compromise.\n",
|
|
392
|
+
"severity": "low"
|
|
393
|
+
},
|
|
394
|
+
{
|
|
395
|
+
"id": "V-36070",
|
|
396
|
+
"title": "The MDM server must automatically audit administrator account disabling actions.\n",
|
|
397
|
+
"description": "When accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying processes themselves. In order to detect and respond to events the MDM server must audit account disabling actions and, as required, notify the appropriate individuals, so they can investigate the event. Such a capability greatly reduces the risk that accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.\n",
|
|
398
|
+
"severity": "medium"
|
|
399
|
+
},
|
|
400
|
+
{
|
|
401
|
+
"id": "V-36071",
|
|
402
|
+
"title": "The MDM server must only allow authorized entities to change security attributes.\n",
|
|
403
|
+
"description": "Security attributes are abstractions representing the basic properties or characteristics of an entity (e.g., subjects, objects) with respect to safeguarding information. These attributes are typically associated with internal data structures (e.g., records, buffers, files, registry keys) within the system and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. If unauthorized entities were able to change them, the integrity and/or confidentiality of the MDM server could be compromised.\n",
|
|
404
|
+
"severity": "low"
|
|
405
|
+
},
|
|
406
|
+
{
|
|
407
|
+
"id": "V-36072",
|
|
408
|
+
"title": "The MDM server must display to the administrator the identity of the entity that signed the downloaded software before installing the software.\n",
|
|
409
|
+
"description": "The user provides an important line of defense in protecting the system against the installation of malicious software. It is more likely that software will be installed from unknown sources if the user is unaware of the transactions. Revealing the signatory of downloaded software to the user enables the user to identify rogue or suspect sources prior to installation, and possibly abort the transaction or report the concern to the IAO. \n",
|
|
410
|
+
"severity": "low"
|
|
411
|
+
},
|
|
412
|
+
{
|
|
413
|
+
"id": "V-36073",
|
|
414
|
+
"title": "The MDM server must disable the use of organization defined networking protocols within the operating system deemed to be non-secure except for explicitly identified components in support of specific operational requirements.\n",
|
|
415
|
+
"description": "Some networking protocols may not meet security requirements to protect data and components. The organization can either make a determination as to the relative security of the networking protocol or base the security decision on the assessment of other entities. Based on that assessment some may be deemed to be non-secure except for explicitly identified components in support of specific operational requirements. Networking protocols used may be complaint with the DoD The Category Assurance List (CAL).\n",
|
|
416
|
+
"severity": "medium"
|
|
417
|
+
},
|
|
418
|
+
{
|
|
419
|
+
"id": "V-36074",
|
|
420
|
+
"title": "The MDM server must enforce the organization defined time period during which the limit of consecutive invalid access attempts by an administrator is counted.\n",
|
|
421
|
+
"description": "By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account.\n",
|
|
422
|
+
"severity": "medium"
|
|
423
|
+
},
|
|
424
|
+
{
|
|
425
|
+
"id": "V-36075",
|
|
426
|
+
"title": "The MDM server must limit privileges to change software resident within software libraries (including privileged programs).\n",
|
|
427
|
+
"description": "Any changes to the MDM server software can potentially have significant effects on the overall security and functionality of the system. Therefore, only qualified and authorized individuals should be allowed to obtain access to the MDM server software resident within the software libraries. If non-authorized users were to make changes to software libraries, those changes could be implemented without undergoing the appropriate testing, validation, and approval, as well as lead to system degradation and denial of service. \n",
|
|
428
|
+
"severity": "low"
|
|
429
|
+
},
|
|
430
|
+
{
|
|
431
|
+
"id": "V-36076",
|
|
432
|
+
"title": "The MDM server must ensure unauthorized, security relevant configuration changes are tracked if detected.\n",
|
|
433
|
+
"description": "Uncoordinated or incorrect configuration changes to MDM server can potentially lead to outages and possibly compromises. Configuration changes must be tracked and detected to prevent these outages and compromises.\n",
|
|
434
|
+
"severity": "low"
|
|
435
|
+
},
|
|
436
|
+
{
|
|
437
|
+
"id": "V-36077",
|
|
438
|
+
"title": "The MDM server must preserve organization defined system state information in the event of a system failure.\n",
|
|
439
|
+
"description": "Failure in a known state can address safety or security in accordance with the mission/business needs of the organization. Failure in a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the operating system or a component of the system. \n",
|
|
440
|
+
"severity": "medium"
|
|
441
|
+
},
|
|
442
|
+
{
|
|
443
|
+
"id": "V-36078",
|
|
444
|
+
"title": "The MDM server must notify appropriate individuals when administrator accounts are created.\n",
|
|
445
|
+
"description": "Once an attacker establishes initial access to a system, they often attempt to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account. By notifying personnel when an account is created, action can be taken immediately to terminate the access.\n",
|
|
446
|
+
"severity": "medium"
|
|
447
|
+
},
|
|
448
|
+
{
|
|
449
|
+
"id": "V-36079",
|
|
450
|
+
"title": "The MDM server must notify, as required, appropriate individuals when administrator accounts are modified.\n",
|
|
451
|
+
"description": "Monitoring account modification is critical to ensure only appropriate personnel have access to the MDM server. This reduces the possibility that an account will be given more access than is intended. In order to facilitate the monitoring, the MDM server must notify designated personnel when an account is modified.\n",
|
|
452
|
+
"severity": "medium"
|
|
453
|
+
},
|
|
454
|
+
{
|
|
455
|
+
"id": "V-36080",
|
|
456
|
+
"title": "The MDM server must notify, as required, appropriate individuals when administrator accounts are disabled.\n",
|
|
457
|
+
"description": "Monitoring account disabling is critical to ensure a denial of service situation does not exist on the operating system. An unexpected account deletion can also be a sign that there is a rogue administrator account that may be deleting traces of activity. In order to facilitate the monitoring, the MDM server must notify designated personnel when an account is disabled.\n",
|
|
458
|
+
"severity": "medium"
|
|
459
|
+
},
|
|
460
|
+
{
|
|
461
|
+
"id": "V-36081",
|
|
462
|
+
"title": "The MDM server must notify appropriate individuals when administrator accounts are terminated.\n",
|
|
463
|
+
"description": "When MDM server accounts are terminated, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events that affect user accessibility and application processing, applications must notify the appropriate individuals when an account is terminated, so they can investigate the event. Such a capability greatly reduces the risk that application accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes. \n",
|
|
464
|
+
"severity": "medium"
|
|
465
|
+
},
|
|
466
|
+
{
|
|
467
|
+
"id": "V-36082",
|
|
468
|
+
"title": "The MDM server must accept alerts of certificate failures related to digital signatures on software applications or components on managed mobile devices.\n",
|
|
469
|
+
"description": "A certificate failure related to a digital signature on software applications or components is strong evidence of a system breach. Notifying the MDM server of such an occurrence allows the enterprise to assess the situation, contain the breach if there is one, and possibly invoke incident response procedures.\n",
|
|
470
|
+
"severity": "medium"
|
|
471
|
+
},
|
|
472
|
+
{
|
|
473
|
+
"id": "V-36083",
|
|
474
|
+
"title": "The MDM server must provide mutual authentication between the MDM server and the provisioned device during a trusted over-the-air (OTA) provisioning session.\n",
|
|
475
|
+
"description": "If mutual authentication is not performed between the MDM server and the provisioned devices during the provisioning, rogue devices could connect to the MDM server or a rogue MDM server could connect to the device. In either case, an integrity issue would exist within the mobility infrastructure. The mutual authentication ensures that the MDM server and the device are known entities before provisioning.\n",
|
|
476
|
+
"severity": "high"
|
|
477
|
+
},
|
|
478
|
+
{
|
|
479
|
+
"id": "V-36084",
|
|
480
|
+
"title": "The MDM server must deploy operating system and application updates via over-the-air (OTA) provisioning for managed mobile devices.\n",
|
|
481
|
+
"description": "Without the MDM server capability to deploy operating systems and application updates OTA, it is possible for the mobile devices under the MDM server's control to be susceptible to a zero day attack. The ability to apply updates OTA allows for rapid response to patching.\n",
|
|
482
|
+
"severity": "medium"
|
|
483
|
+
},
|
|
484
|
+
{
|
|
485
|
+
"id": "V-36085",
|
|
486
|
+
"title": "The MDM server must prevent the installation of applications that are not digitally signed with an organizationally accepted private key.\n",
|
|
487
|
+
"description": "Any additions of applications can potentially have significant effects on the overall security of the system. Digital signatures on code provide assurance that the code comes from a known source and has not been modified. This feature is a key malware control on mobile devices.\n",
|
|
488
|
+
"severity": "high"
|
|
489
|
+
},
|
|
490
|
+
{
|
|
491
|
+
"id": "V-36086",
|
|
492
|
+
"title": "The MDM server must be configured to provide the administrative functionality to transmit a remote Data Wipe command, including removable media cards, to a managed mobile device.\n",
|
|
493
|
+
"description": "Without a Data Wipe capability, the data on the mobile device can be compromised in the event of a lost or stolen device.\n",
|
|
494
|
+
"severity": "medium"
|
|
495
|
+
},
|
|
496
|
+
{
|
|
497
|
+
"id": "V-36087",
|
|
498
|
+
"title": "The MDM server must be configured to have the administrative functionality to centrally manage configuration settings, including security policies, on managed mobile devices.\n",
|
|
499
|
+
"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 server 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. ",
|
|
500
|
+
"severity": "medium"
|
|
501
|
+
},
|
|
502
|
+
{
|
|
503
|
+
"id": "V-36088",
|
|
504
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Perform a Data Wipe function whereby all data stored in user addressable memory on the mobile device and the removable memory card is erased when the maximum number of incorrect passwords for device unlock has been reached. \n",
|
|
505
|
+
"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 server 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. Data wipe could be accomplished by deleting the data-at-rest encryption key (data obfuscation). ",
|
|
506
|
+
"severity": "medium"
|
|
507
|
+
},
|
|
508
|
+
{
|
|
509
|
+
"id": "V-36089",
|
|
510
|
+
"title": "The MDM server must be configured to have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Removable storage media cards are bound to the mobile device so data stored on them can only be read by that mobile device.\n",
|
|
511
|
+
"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 server 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. ",
|
|
512
|
+
"severity": "medium"
|
|
513
|
+
},
|
|
514
|
+
{
|
|
515
|
+
"id": "V-36090",
|
|
516
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable data-at-rest encryption on the mobile device. \n",
|
|
517
|
+
"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 server 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. ",
|
|
518
|
+
"severity": "medium"
|
|
519
|
+
},
|
|
520
|
+
{
|
|
521
|
+
"id": "V-36091",
|
|
522
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable device unlock password.\n",
|
|
523
|
+
"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 server 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. ",
|
|
524
|
+
"severity": "medium"
|
|
525
|
+
},
|
|
526
|
+
{
|
|
527
|
+
"id": "V-36092",
|
|
528
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Maximum password age (e.g., 30 days, 90 days, 180 days).\n",
|
|
529
|
+
"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 server 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. ",
|
|
530
|
+
"severity": "medium"
|
|
531
|
+
},
|
|
532
|
+
{
|
|
533
|
+
"id": "V-36093",
|
|
534
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Minimum password length for the device unlock password is configured to the organizationally defined value when DoD sensitive data is being protected.\n",
|
|
535
|
+
"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 server 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. ",
|
|
536
|
+
"severity": "medium"
|
|
537
|
+
},
|
|
538
|
+
{
|
|
539
|
+
"id": "V-36094",
|
|
540
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Maximum password history.\n",
|
|
541
|
+
"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 server 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\nThis security setting determines the number of unique new passwords that have to be associated with a user account before an old password can be reused. This policy enables administrators to enhance security by ensuring that old passwords are not reused continually.",
|
|
542
|
+
"severity": "medium"
|
|
543
|
+
},
|
|
544
|
+
{
|
|
545
|
+
"id": "V-36095",
|
|
546
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Device inactivity timeout whereby the user must reenter their user password or Smart Card PIN to unlock the device. \n",
|
|
547
|
+
"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 server 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. ",
|
|
548
|
+
"severity": "medium"
|
|
549
|
+
},
|
|
550
|
+
{
|
|
551
|
+
"id": "V-36096",
|
|
552
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set the device inactivity timeout (the following settings must be available, at a minimum: Disable (no timeout), 15 minutes, and 60 minutes).\n",
|
|
553
|
+
"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 server 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. ",
|
|
554
|
+
"severity": "medium"
|
|
555
|
+
},
|
|
556
|
+
{
|
|
557
|
+
"id": "V-36097",
|
|
558
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the mobile device Bluetooth stack.\n",
|
|
559
|
+
"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 server 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. ",
|
|
560
|
+
"severity": "medium"
|
|
561
|
+
},
|
|
562
|
+
{
|
|
563
|
+
"id": "V-36098",
|
|
564
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable any supported Bluetooth profile. \n",
|
|
565
|
+
"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 server 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. ",
|
|
566
|
+
"severity": "medium"
|
|
567
|
+
},
|
|
568
|
+
{
|
|
569
|
+
"id": "V-36099",
|
|
570
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable Bluetooth.\n",
|
|
571
|
+
"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 server 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. ",
|
|
572
|
+
"severity": "medium"
|
|
573
|
+
},
|
|
574
|
+
{
|
|
575
|
+
"id": "V-36100",
|
|
576
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the Bluetooth discoverable mode.\n",
|
|
577
|
+
"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 server 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. ",
|
|
578
|
+
"severity": "medium"
|
|
579
|
+
},
|
|
580
|
+
{
|
|
581
|
+
"id": "V-36101",
|
|
582
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Bluetooth pairing using a randomly generated passkey size of at least 8 digits.\n",
|
|
583
|
+
"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 server 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. ",
|
|
584
|
+
"severity": "medium"
|
|
585
|
+
},
|
|
586
|
+
{
|
|
587
|
+
"id": "V-36102",
|
|
588
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Bluetooth mutual authentication immediately after the initial establishment of any Bluetooth connection between the mobile device and the smart card reader or hands free headset.\n",
|
|
589
|
+
"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 server 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. ",
|
|
590
|
+
"severity": "medium"
|
|
591
|
+
},
|
|
592
|
+
{
|
|
593
|
+
"id": "V-36103",
|
|
594
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Bluetooth 128 bit encryption.\n",
|
|
595
|
+
"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 server 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. ",
|
|
596
|
+
"severity": "medium"
|
|
597
|
+
},
|
|
598
|
+
{
|
|
599
|
+
"id": "V-36104",
|
|
600
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set up a white list of Bluetooth devices that are authorized to pair to the mobile device (white list filters based on device Friendly Name).\n",
|
|
601
|
+
"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 server 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. ",
|
|
602
|
+
"severity": "medium"
|
|
603
|
+
},
|
|
604
|
+
{
|
|
605
|
+
"id": "V-36105",
|
|
606
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable MMS messaging.\n",
|
|
607
|
+
"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 server 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. ",
|
|
608
|
+
"severity": "medium"
|
|
609
|
+
},
|
|
610
|
+
{
|
|
611
|
+
"id": "V-36106",
|
|
612
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the IR port.\n",
|
|
613
|
+
"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 server 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. ",
|
|
614
|
+
"severity": "medium"
|
|
615
|
+
},
|
|
616
|
+
{
|
|
617
|
+
"id": "V-36107",
|
|
618
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable Wi-Fi.\n",
|
|
619
|
+
"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 server 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. ",
|
|
620
|
+
"severity": "medium"
|
|
621
|
+
},
|
|
622
|
+
{
|
|
623
|
+
"id": "V-36108",
|
|
624
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the Voice recorder.\n",
|
|
625
|
+
"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 server 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. ",
|
|
626
|
+
"severity": "medium"
|
|
627
|
+
},
|
|
628
|
+
{
|
|
629
|
+
"id": "V-36109",
|
|
630
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the Microphone.\n",
|
|
631
|
+
"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 server 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. ",
|
|
632
|
+
"severity": "medium"
|
|
633
|
+
},
|
|
634
|
+
{
|
|
635
|
+
"id": "V-36110",
|
|
636
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the GPS receiver.\n",
|
|
637
|
+
"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 server 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. ",
|
|
638
|
+
"severity": "medium"
|
|
639
|
+
},
|
|
640
|
+
{
|
|
641
|
+
"id": "V-36111",
|
|
642
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the near-field communications (NFC) radio.\n",
|
|
643
|
+
"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 server 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. ",
|
|
644
|
+
"severity": "medium"
|
|
645
|
+
},
|
|
646
|
+
{
|
|
647
|
+
"id": "V-36112",
|
|
648
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the all cameras.\n",
|
|
649
|
+
"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 server 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. ",
|
|
650
|
+
"severity": "medium"
|
|
651
|
+
},
|
|
652
|
+
{
|
|
653
|
+
"id": "V-36113",
|
|
654
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the memory card port.\n",
|
|
655
|
+
"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 server 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. ",
|
|
656
|
+
"severity": "medium"
|
|
657
|
+
},
|
|
658
|
+
{
|
|
659
|
+
"id": "V-36114",
|
|
660
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the user's ability to switch devices.\n",
|
|
661
|
+
"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 server 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. ",
|
|
662
|
+
"severity": "medium"
|
|
663
|
+
},
|
|
664
|
+
{
|
|
665
|
+
"id": "V-36115",
|
|
666
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the mobile device users access to an application store or repository.\n",
|
|
667
|
+
"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 server 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. ",
|
|
668
|
+
"severity": "medium"
|
|
669
|
+
},
|
|
670
|
+
{
|
|
671
|
+
"id": "V-36116",
|
|
672
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Block access to specific web sites.\n",
|
|
673
|
+
"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 server 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. ",
|
|
674
|
+
"severity": "medium"
|
|
675
|
+
},
|
|
676
|
+
{
|
|
677
|
+
"id": "V-36117",
|
|
678
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the mobile device user modification of the security configuration file, policy, or profile on the mobile device. \n",
|
|
679
|
+
"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 server 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. ",
|
|
680
|
+
"severity": "medium"
|
|
681
|
+
},
|
|
682
|
+
{
|
|
683
|
+
"id": "V-36118",
|
|
684
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set security policy refresh interval (at least every 1, 6, 12, 24 hours should be supported).\n",
|
|
685
|
+
"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 server 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. ",
|
|
686
|
+
"severity": "medium"
|
|
687
|
+
},
|
|
688
|
+
{
|
|
689
|
+
"id": "V-36119",
|
|
690
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable location services. \n",
|
|
691
|
+
"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 server 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. ",
|
|
692
|
+
"severity": "medium"
|
|
693
|
+
},
|
|
694
|
+
{
|
|
695
|
+
"id": "V-36120",
|
|
696
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the video recorder.\n",
|
|
697
|
+
"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 server 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. ",
|
|
698
|
+
"severity": "medium"
|
|
699
|
+
},
|
|
700
|
+
{
|
|
701
|
+
"id": "V-36121",
|
|
702
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable the USB Port mass storage mode.\n",
|
|
703
|
+
"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 server 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. ",
|
|
704
|
+
"severity": "medium"
|
|
705
|
+
},
|
|
706
|
+
{
|
|
707
|
+
"id": "V-36122",
|
|
708
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable or disable tethering (Wi-Fi, Bluetooth, or USB).\n",
|
|
709
|
+
"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 server 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. ",
|
|
710
|
+
"severity": "medium"
|
|
711
|
+
},
|
|
712
|
+
{
|
|
713
|
+
"id": "V-36123",
|
|
714
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Force the display of a warning banner on the mobile device. \n",
|
|
715
|
+
"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 server 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. \nThe warning banner must be displayed before or immediately after the user successfully unlocks the mobile device or unlocks a secure application where sensitive DoD data is stored: “I’ve read & consent to terms in IS user agreement.” (Wording must be exactly as specified.)",
|
|
716
|
+
"severity": "medium"
|
|
717
|
+
},
|
|
718
|
+
{
|
|
719
|
+
"id": "V-36124",
|
|
720
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Disable any mobile OS service that connects to a non-DoD server.\n",
|
|
721
|
+
"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 server 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. ",
|
|
722
|
+
"severity": "medium"
|
|
723
|
+
},
|
|
724
|
+
{
|
|
725
|
+
"id": "V-36125",
|
|
726
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set the number of allowed repeated characters in the mobile device unlock password.\n",
|
|
727
|
+
"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 server 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. ",
|
|
728
|
+
"severity": "medium"
|
|
729
|
+
},
|
|
730
|
+
{
|
|
731
|
+
"id": "V-36126",
|
|
732
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Disallow sequential numbers in the mobile device unlock password.\n",
|
|
733
|
+
"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 server 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. ",
|
|
734
|
+
"severity": "medium"
|
|
735
|
+
},
|
|
736
|
+
{
|
|
737
|
+
"id": "V-36127",
|
|
738
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set the number of upper case letters in the device unlock password.\n",
|
|
739
|
+
"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 server 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. ",
|
|
740
|
+
"severity": "medium"
|
|
741
|
+
},
|
|
742
|
+
{
|
|
743
|
+
"id": "V-36128",
|
|
744
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set the number of special characters in the device unlock password.\n",
|
|
745
|
+
"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 server 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. ",
|
|
746
|
+
"severity": "medium"
|
|
747
|
+
},
|
|
748
|
+
{
|
|
749
|
+
"id": "V-36129",
|
|
750
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set the number of lower case letters in the device unlock password.\n",
|
|
751
|
+
"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 server 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. ",
|
|
752
|
+
"severity": "medium"
|
|
753
|
+
},
|
|
754
|
+
{
|
|
755
|
+
"id": "V-36130",
|
|
756
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set the number of numbers in the device unlock password.\n",
|
|
757
|
+
"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 server 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. ",
|
|
758
|
+
"severity": "medium"
|
|
759
|
+
},
|
|
760
|
+
{
|
|
761
|
+
"id": "V-36131",
|
|
762
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Perform a Data Wipe function whereby all data stored in the security container is erased when the maximum number of incorrect passwords for the security container application has been reached.\n",
|
|
763
|
+
"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 server 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. ",
|
|
764
|
+
"severity": "medium"
|
|
765
|
+
},
|
|
766
|
+
{
|
|
767
|
+
"id": "V-36132",
|
|
768
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set the number of incorrect password attempts before a data wipe procedure is initiated (minimum requirement is 3-10).\n",
|
|
769
|
+
"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 server 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. ",
|
|
770
|
+
"severity": "medium"
|
|
771
|
+
},
|
|
772
|
+
{
|
|
773
|
+
"id": "V-36133",
|
|
774
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: When a mobile device lock occurs (user initiated or due to an inactivity timeout) all data must be re-encrypted.\n",
|
|
775
|
+
"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 server 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. ",
|
|
776
|
+
"severity": "medium"
|
|
777
|
+
},
|
|
778
|
+
{
|
|
779
|
+
"id": "V-36134",
|
|
780
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: All data-at-rest inside the MDM server agent must be encrypted. \n",
|
|
781
|
+
"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 server 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. ",
|
|
782
|
+
"severity": "medium"
|
|
783
|
+
},
|
|
784
|
+
{
|
|
785
|
+
"id": "V-36135",
|
|
786
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Enable an MDM server agent password.\n",
|
|
787
|
+
"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 server 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. ",
|
|
788
|
+
"severity": "medium"
|
|
789
|
+
},
|
|
790
|
+
{
|
|
791
|
+
"id": "V-36136",
|
|
792
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Disallow sequential numbers in the MDM server agent password.\n",
|
|
793
|
+
"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 server 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. ",
|
|
794
|
+
"severity": "medium"
|
|
795
|
+
},
|
|
796
|
+
{
|
|
797
|
+
"id": "V-36137",
|
|
798
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Disallow common password patterns for the MDM server agent password (e.g., letters in order from the top row of the keypad).\n",
|
|
799
|
+
"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 server 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. ",
|
|
800
|
+
"severity": "medium"
|
|
801
|
+
},
|
|
802
|
+
{
|
|
803
|
+
"id": "V-36138",
|
|
804
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set the number of upper case letters in the MDM server agent password.\n",
|
|
805
|
+
"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 server 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",
|
|
806
|
+
"severity": "medium"
|
|
807
|
+
},
|
|
808
|
+
{
|
|
809
|
+
"id": "V-36139",
|
|
810
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set the number of numbers in the MDM server agent password.\n",
|
|
811
|
+
"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 server 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. ",
|
|
812
|
+
"severity": "medium"
|
|
813
|
+
},
|
|
814
|
+
{
|
|
815
|
+
"id": "V-36140",
|
|
816
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set the number of special characters in the MDM server agent password.\n",
|
|
817
|
+
"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 server 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",
|
|
818
|
+
"severity": "medium"
|
|
819
|
+
},
|
|
820
|
+
{
|
|
821
|
+
"id": "V-36141",
|
|
822
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Maximum MDM server agent password age (e.g., 30 days, 90 days, 180 days).\n",
|
|
823
|
+
"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 server 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. ",
|
|
824
|
+
"severity": "medium"
|
|
825
|
+
},
|
|
826
|
+
{
|
|
827
|
+
"id": "V-36142",
|
|
828
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Minimum MDM server agent password length of eight or more characters.\n",
|
|
829
|
+
"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 server 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. ",
|
|
830
|
+
"severity": "medium"
|
|
831
|
+
},
|
|
832
|
+
{
|
|
833
|
+
"id": "V-36143",
|
|
834
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Maximum MDM server agent password history (3 previous passwords checked is the recommended setting).\n",
|
|
835
|
+
"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 server 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. ",
|
|
836
|
+
"severity": "medium"
|
|
837
|
+
},
|
|
838
|
+
{
|
|
839
|
+
"id": "V-36144",
|
|
840
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set the MDM server agent inactivity timeout (the following settings must be available, at a minimum: Disable (no timeout), 15 minutes, and 60 minutes).\n",
|
|
841
|
+
"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 server 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. ",
|
|
842
|
+
"severity": "medium"
|
|
843
|
+
},
|
|
844
|
+
{
|
|
845
|
+
"id": "V-36145",
|
|
846
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Set approved IP address ranges, ports, and protocols on a managed mobile device firewall.\n",
|
|
847
|
+
"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 server 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",
|
|
848
|
+
"severity": "medium"
|
|
849
|
+
},
|
|
850
|
+
{
|
|
851
|
+
"id": "V-36146",
|
|
852
|
+
"title": "The MDM server must configure the mobile device agent to prohibit the download of applications on mobile operating system devices without system administrator control (i.e., the SA either downloads and installs the application or enables the user to download/install the application).\n",
|
|
853
|
+
"description": "The installation and execution of unauthorized software on an operating system may allow the application to obtain sensitive information or further compromise the system. If the system administrator has control over what applications are downloaded, then the system administrator can check that only known good programs are installed, which significantly mitigates the risk posed by malicious software.\n",
|
|
854
|
+
"severity": "medium"
|
|
855
|
+
},
|
|
856
|
+
{
|
|
857
|
+
"id": "V-36147",
|
|
858
|
+
"title": "The MDM server application white list for managed mobile devices must be set to Deny All by default when no applications are listed.\n",
|
|
859
|
+
"description": "The installation and execution of unauthorized software on an operating system may allow the application to obtain sensitive information or further compromise the system. If the system administrator has control over what applications are downloaded, then the system administrator can check that only known good programs are installed, which significantly mitigates the risk posed by malicious software.\n",
|
|
860
|
+
"severity": "high"
|
|
861
|
+
},
|
|
862
|
+
{
|
|
863
|
+
"id": "V-36148",
|
|
864
|
+
"title": "The MDM server must configure the mobile device to prohibit the mobile device user from installing unapproved applications.\n",
|
|
865
|
+
"description": "The operating system must enforce software installation by users based upon what types of software installations are permitted (e.g., updates and security patches to existing software) and what types of installations are prohibited (e.g., software whose pedigree with regard to being potentially malicious is unknown or suspect) by the organization. The installation and execution of unauthorized software on an operating system may allow the application to obtain sensitive information or further compromise the system. Preventing a user from installing unapproved applications mitigates this risk. All OS core applications, third-party applications, and carrier installed applications must be approved. In this case, applications include any applets, browse channel apps, and icon apps.\n",
|
|
866
|
+
"severity": "medium"
|
|
867
|
+
},
|
|
868
|
+
{
|
|
869
|
+
"id": "V-36149",
|
|
870
|
+
"title": "The MDM server must configure the mobile device agent to prohibit the download of software from a DoD non-approved source (e.g., DoD operated mobile device application store or MDM server).\n",
|
|
871
|
+
"description": "DoD can perform due diligence on sources of software to mitigate the risk that malicious software is introduced to those sources. Therefore, if software is downloaded from a DoD approved source, then it is less likely to be malicious than if it is downloaded from an unapproved source. To prevent access to unapproved sources, the operating system in most cases can be configured to disable user access to public application stores.\n",
|
|
872
|
+
"severity": "medium"
|
|
873
|
+
},
|
|
874
|
+
{
|
|
875
|
+
"id": "V-36150",
|
|
876
|
+
"title": "The MDM server must provide the administrative functionality to specify a list of approved applications that must be installed on the mobile device and cannot be removed by the user.\n",
|
|
877
|
+
"description": "DoD can perform due diligence on sources of software to mitigate the risk that malicious software is introduced to those sources. Therefore, if software is downloaded from a DoD approved source, then it is less likely to be malicious than if it is downloaded from an unapproved source. To prevent access to unapproved sources, the operating system in most cases can be configured to disable user access to public application stores. In some cases, some applications are required for secure operation of the mobile devices controlled by the MDM server. In these cases, the ability for users to remove the application is needed as to ensure proper secure operations of the device.\n",
|
|
878
|
+
"severity": "medium"
|
|
879
|
+
},
|
|
880
|
+
{
|
|
881
|
+
"id": "V-36151",
|
|
882
|
+
"title": "The MDM server must have the administrative functionality to centrally manage the following security policy rule on managed mobile devices: Disable copying data from inside a security container to a non-secure data area on a mobile device. \n",
|
|
883
|
+
"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 server 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. If this control is not available, sensitive DoD data stored inside the security container could be exposed if it is copied to a non-secure area on the device.",
|
|
884
|
+
"severity": "medium"
|
|
885
|
+
},
|
|
886
|
+
{
|
|
887
|
+
"id": "V-36152",
|
|
888
|
+
"title": "The MDM server must be able to detect if the security policy has been modified, disabled, or bypassed on managed mobile devices. \n",
|
|
889
|
+
"description": "If the security policy has been modified in an unauthorized manner, IA is severely degraded and a variety of further attacks are possible. Detecting whether the security policy has been modified or disabled mitigates these risks.\n",
|
|
890
|
+
"severity": "high"
|
|
891
|
+
},
|
|
892
|
+
{
|
|
893
|
+
"id": "V-36153",
|
|
894
|
+
"title": "The MDM server must employ automated mechanisms to respond to unauthorized changes to the security policy or MDM server agent on managed mobile devices.",
|
|
895
|
+
"description": "Uncoordinated or incorrect configuration changes to the MDM server managed components can potentially lead to compromises. Without automated mechanisms to respond to changes, changes can go unnoticed for a significant amount of time which could result in compromise. \n",
|
|
896
|
+
"severity": "medium"
|
|
897
|
+
},
|
|
898
|
+
{
|
|
899
|
+
"id": "V-36154",
|
|
900
|
+
"title": "The MDM server must uniquely identify mobile devices managed by the server prior to connecting to the device.\n",
|
|
901
|
+
"description": "When managed mobile devices connect to the MDM server the security policy and possible sensitive DoD data will be pushed to the device. In addition, the device may be provided access to application and web servers on the DoD network. Therefore, strong authentication of the user on the device is required to ensure sensitive DoD data is not exposed and unauthorized access to the DoD network is not granted, exposing the network to malware and attack.\n",
|
|
902
|
+
"severity": "medium"
|
|
903
|
+
},
|
|
904
|
+
{
|
|
905
|
+
"id": "V-36155",
|
|
906
|
+
"title": "The MDM server must authenticate devices before establishing remote network connections using bidirectional cryptographically based authentication between devices.\n",
|
|
907
|
+
"description": "Device authentication is a solution enabling an organization to manage devices. Without the authentication, there is risk of a rogue device being serviced by an MDM server.\n",
|
|
908
|
+
"severity": "medium"
|
|
909
|
+
},
|
|
910
|
+
{
|
|
911
|
+
"id": "V-36156",
|
|
912
|
+
"title": "The MDM server must deny all connections to DoD network servers by managed mobile devices except for network servers that have the capability to support PKI based mutual authentication between the network server and the mobile device user.\n",
|
|
913
|
+
"description": "Device authentication is a solution enabling an organization to manage both users and devices. This requirement applies to MDM servers that provide mobile device and user access to network shares, web servers, and other network resources located on the internal enclave (back-office servers, etc.). This connection bypasses user network authentication mechanisms (i.e., CAC authentication). Therefore, the MDM server must allow connections to only back-office network resources that support CAC authentication with the mobile device user.\n",
|
|
914
|
+
"severity": "high"
|
|
915
|
+
},
|
|
916
|
+
{
|
|
917
|
+
"id": "V-36157",
|
|
918
|
+
"title": "When the MDM server is configured to allow connections from managed mobile devices to back-office servers and network shares, the server must be configured to accept only trusted connections to those resources.\n",
|
|
919
|
+
"description": "Device authentication is a solution enabling an organization to manage both users and devices. This requirement applies to MDM servers that provide mobile device and user access to network shares, web servers, and other network resources located on the internal enclave (back-office servers, etc.). This connection bypasses user network authentication mechanisms (i.e., CAC authentication). Therefore, the MDM server must allow connections to only back-office network resources that support CAC authentication with the mobile device user. In this case, a trusted connection refers to mutual PKI based authentication between the MDM server and the network server.\n",
|
|
920
|
+
"severity": "medium"
|
|
921
|
+
},
|
|
922
|
+
{
|
|
923
|
+
"id": "V-36158",
|
|
924
|
+
"title": "The MDM server must deny all connections to DoD network servers by managed mobile devices unless the MDM server can support PKI based mutual authentication between the network server and the mobile device user.\n",
|
|
925
|
+
"description": "Device authentication is a solution enabling an organization to manage both users and devices. This requirement applies to MDM servers that provide mobile device and user access to network shares, web servers, and other network resources located on the internal enclave (back-office servers, etc.). This connection bypasses user network authentication mechanisms (i.e., CAC authentication). Therefore, the MDM server must support CAC authentication of the user to back-office network resources, or disable access.\n",
|
|
926
|
+
"severity": "medium"
|
|
927
|
+
},
|
|
928
|
+
{
|
|
929
|
+
"id": "V-36159",
|
|
930
|
+
"title": "The cryptographic module supporting encryption of data in transit (including email and attachments) must be FIPS 140-2 validated.\n",
|
|
931
|
+
"description": "The most common vulnerabilities with cryptographic modules are those associated with poor implementation. FIPS 140 validation provides assurance that the relevant cryptography has been implemented correctly. FIPS validation is also a strict requirement for use of cryptography in the Federal Government. This requirement applies to any secure connection between the server and other IT resource, including the secure communications tunnel between the MDM server and managed mobile devices.\n",
|
|
932
|
+
"severity": "medium"
|
|
933
|
+
},
|
|
934
|
+
{
|
|
935
|
+
"id": "V-36160",
|
|
936
|
+
"title": "Applications providing remote access capabilities must utilize approved cryptography to protect the confidentiality of remote access sessions.",
|
|
937
|
+
"description": "Remote access is any access to an organizational information system by a user (or an information system) communicating through an external, non-organization-controlled network (e.g., the Internet). Examples of remote access methods include dial-up, broadband, and wireless. \n\nRemote network access is accomplished by leveraging common communication protocols and establishing a remote connection. These connections will typically occur over either the public Internet or the Public Switched Telephone Network (PSTN). Since neither of these internetworking mechanisms are private nor secure, if cryptography is not used, then the session data traversing the remote connection could be intercepted and compromised. Cryptography provides a means to secure the remote connection so as to prevent unauthorized access to the data traversing the remote access connection thereby providing a degree of confidentiality. The encryption strength of mechanism is selected based on the security categorization of the information traversing the remote connection.\n\nRationale for non-applicability: Remote access into the server is controlled at the network or OS level.",
|
|
938
|
+
"severity": "medium"
|
|
939
|
+
},
|
|
940
|
+
{
|
|
941
|
+
"id": "V-36161",
|
|
942
|
+
"title": "The MDM server must ensure authentication of both mobile device MDM server agent and server during the entire session. \n",
|
|
943
|
+
"description": "MDM server can be prone to man-in-the middle attacks. If communication sessions are not provided appropriate validity protections, such as the employment of SSL Mutual Authentication authenticity of the data cannot be guaranteed. \n",
|
|
944
|
+
"severity": "medium"
|
|
945
|
+
},
|
|
946
|
+
{
|
|
947
|
+
"id": "V-36162",
|
|
948
|
+
"title": "The MDM server must support organizational requirements to install software updates automatically on managed mobile devices.\n",
|
|
949
|
+
"description": "Security faults with software applications and operating systems are discovered daily and vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling, must also be addressed expeditiously. By having the MDM server installing software updates automatically, devices stay current and are less prone to zero day attacks.\n\nAutomatic software installation could be performed during a wired or over-the-air (OTA) session.",
|
|
950
|
+
"severity": "medium"
|
|
951
|
+
},
|
|
952
|
+
{
|
|
953
|
+
"id": "V-36163",
|
|
954
|
+
"title": "The application must employ automated mechanisms to facilitate the monitoring and control of remote access methods.",
|
|
955
|
+
"description": "Remote network access is accomplished by leveraging common communication protocols and establishing a remote connection. These connections will occur over the public Internet. \n\nRemote access is any access to an organizational information system by a user (or an information system) communicating through an external, non-organization-controlled network (e.g., the Internet). Examples of remote access methods include dial-up, broadband, and wireless. \n\nAutomated monitoring of remote access sessions allows organizations to audit user activities on a variety of information system components (e.g., servers, workstations, notebook/laptop computers) and to ensure compliance with remote access policy.\n\nRemote access applications such as those providing remote access to network devices and information systems and are individually configured with no monitoring or automation capabilities increase risk and makes remote user access management difficult at best.\n\nApplications providing remote access capability need to provide the ability to automatically monitor and control remote user sessions. This includes the capability to directly trigger actions based on user activity or pass information and or data to a separate application or entity that can then perform automated tasks based on the information. \n\nRationale for non-applicability: Remote access into the server is controlled at the network or OS level.",
|
|
956
|
+
"severity": "medium"
|
|
957
|
+
},
|
|
958
|
+
{
|
|
959
|
+
"id": "V-36164",
|
|
960
|
+
"title": "The MDM server must detect and report the version of the operating system, device drivers, and application software for managed mobile devices. \n",
|
|
961
|
+
"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. This mechanism also ensures the network configuration is known for risk mitigation when known issues are found with certain versions of the operating system or applications.\n",
|
|
962
|
+
"severity": "high"
|
|
963
|
+
},
|
|
964
|
+
{
|
|
965
|
+
"id": "V-36165",
|
|
966
|
+
"title": "The MDM server must notify when it detects unauthorized changes to security configuration of managed mobile devices.\n",
|
|
967
|
+
"description": "Incident response functions are intended to monitor, detect, and alarm on defined events occurring on the system or on the network. A large part of their functionality is accurate and timely notification of events. Notifications can be made more efficient by the creation of notification groups containing members who would be responding to a particular alarm or event. \n",
|
|
968
|
+
"severity": "high"
|
|
969
|
+
},
|
|
970
|
+
{
|
|
971
|
+
"id": "V-36166",
|
|
972
|
+
"title": "The MDM server must perform required actions when a security related alert is received.\n",
|
|
973
|
+
"description": "Incident response functions are intended to monitor, detect, and alarm on defined events occurring on the system or on the network. A large part of their functionality is accurate and timely notification of events. Notifications can be made more efficient by the creation of notification groups containing members who would be responding to a particular alarm or event. Types of actions the MDM server must be able to perform after a security alert include: log the alert, send email to a system administrator, wipe the managed mobile device, lock the mobile device account on the MDM server, disable the security container, wipe the security container, and delete an unapproved application. Security alerts include any alert from the MDIS or MAM component of the MDM server.\n",
|
|
974
|
+
"severity": "high"
|
|
975
|
+
},
|
|
976
|
+
{
|
|
977
|
+
"id": "V-36167",
|
|
978
|
+
"title": "The MDM server must provide automated support for the management of distributed security testing on managed mobile devices.\n",
|
|
979
|
+
"description": "The need to verify security functionality is necessary to ensure the MDM server is behaving as expected and the defenses are enabled. To scale the deployment of the verification process, the MDM server systems must provide automated support for the management of distributed security testing. Without testing of the security controls across the architecture, the MDM server infrastructure could be compromised without knowledge of the administrators. \n",
|
|
980
|
+
"severity": "medium"
|
|
981
|
+
},
|
|
982
|
+
{
|
|
983
|
+
"id": "V-36168",
|
|
984
|
+
"title": "The MDM server must use cryptography to protect the integrity of remote access sessions with managed mobile devices.\n",
|
|
985
|
+
"description": "Encryption is critical for the protection of the remote access sessions. If the encryption is not being used for integrity, malicious users may gain the ability to modify the MDM server. The use of cryptography for integrity of remote access session to the MDM server mitigates that risk.\n",
|
|
986
|
+
"severity": "medium"
|
|
987
|
+
},
|
|
988
|
+
{
|
|
989
|
+
"id": "V-36169",
|
|
990
|
+
"title": "Applications managing network connectivity must have the capability to authenticate devices before establishing network connections by using bidirectional authentication that is cryptographically based.",
|
|
991
|
+
"description": "Device authentication is a solution enabling an organization to manage both users and devices. \n\nRationale for non-applicability: This requirement is included in SRG-APP-197-MDM server-159-MDM server\n",
|
|
992
|
+
"severity": "medium"
|
|
993
|
+
},
|
|
994
|
+
{
|
|
995
|
+
"id": "V-36170",
|
|
996
|
+
"title": "The MDM server must have the capability to enable and disable a managed mobile device.\n",
|
|
997
|
+
"description": "Under some conditions, a compromised device represents a threat to other computing resources on the network. For example, a compromised device may attempt to conduct a denial of service attack on other devices, or may be executing a mechanism to spread malware before a countermeasure has been put in place. In these situations, it is critical that an MDM server be able to disable the device to protect other network resources.\n",
|
|
998
|
+
"severity": "high"
|
|
999
|
+
},
|
|
1000
|
+
{
|
|
1001
|
+
"id": "V-36171",
|
|
1002
|
+
"title": "The MDM server must record an event in the server audit log if a success acknowledgement is not received from the MDM server agent after a device security policy has been pushed to a managed mobile device.\n",
|
|
1003
|
+
"description": "When the MDM server transfers policies, there is the chance an error or problem with the data transfer may occur. The MDM server needs to track failures and any problems encountered when performing data transfers, so problems can be identified and remediated. Since policies are the enforcement mechanism that so many of the mobile device operating system security controls depend upon, this tracking is critical to remediate the situation quickly.",
|
|
1004
|
+
"severity": "medium"
|
|
1005
|
+
},
|
|
1006
|
+
{
|
|
1007
|
+
"id": "V-36172",
|
|
1008
|
+
"title": "The MDM server device integrity validation component must employ automated mechanisms to detect the presence of unauthorized software on managed mobile devices and notify designated organizational officials in accordance with the organization defined frequency.\n",
|
|
1009
|
+
"description": "Unauthorized software poses a risk to the device because it could potentially perform malicious functions, including but not limited to gathering sensitive information, searching for other system vulnerabilities, or modifying log entries. A mechanism to detect unauthorized software and notify officials of its presence assists in the task of removing such software to eliminate the risks it poses to the device and the networks to which the device attaches. \n",
|
|
1010
|
+
"severity": "high"
|
|
1011
|
+
},
|
|
1012
|
+
{
|
|
1013
|
+
"id": "V-36173",
|
|
1014
|
+
"title": "The MDM server device integrity scanning component must implement detection and inspection mechanisms to identify unauthorized mobile code on managed mobile devices.\n",
|
|
1015
|
+
"description": "Decisions regarding the employment of mobile code within organizational information systems are based on the potential for the code to cause damage to the system if used maliciously. Mobile code can contain malicious code and be executed without the user's consent. When the MDM server scans and detects mobile code, this risk can be mitigated.\n",
|
|
1016
|
+
"severity": "high"
|
|
1017
|
+
},
|
|
1018
|
+
{
|
|
1019
|
+
"id": "V-36174",
|
|
1020
|
+
"title": "The MDM server device integrity validation component must scan for malicious code on managed mobile devices on an organization defined frequency.\n",
|
|
1021
|
+
"description": "Malicious code protection mechanisms include but are not limited to anti-virus and malware detection software. In order to minimize potential negative impact to the organization that can be caused by malicious code, it is imperative that malicious code is identified and eradicated. \n",
|
|
1022
|
+
"severity": "high"
|
|
1023
|
+
},
|
|
1024
|
+
{
|
|
1025
|
+
"id": "V-36175",
|
|
1026
|
+
"title": "The MDM server device integrity validation component must alert when it identifies malicious code on managed mobile devices.\n",
|
|
1027
|
+
"description": "Malicious code protection mechanisms include but are not limited to anti-virus and malware detection software. In order to minimize potential negative impact to the organization that can be caused by malicious code, it is imperative that malicious code is identified and eradicated. \n",
|
|
1028
|
+
"severity": "high"
|
|
1029
|
+
},
|
|
1030
|
+
{
|
|
1031
|
+
"id": "V-36176",
|
|
1032
|
+
"title": "The application must prevent the execution of prohibited mobile code.",
|
|
1033
|
+
"description": "Decisions regarding the utilization of mobile code within organizational information systems needs to include evaluations which help determine the potential for the code to cause damage to the system if used maliciously. \n\nRationale for non-applicability: An MDM server does not enforce mobile code policies.",
|
|
1034
|
+
"severity": "medium"
|
|
1035
|
+
},
|
|
1036
|
+
{
|
|
1037
|
+
"id": "V-36177",
|
|
1038
|
+
"title": "The MDM server device integrity validation component must support organizational requirements to address the receipt of false positives during malicious code detection.\n",
|
|
1039
|
+
"description": "In order to minimize potential negative impact to the organization that can be caused by malicious code, it is imperative that malicious code is identified and eradicated. Malicious code includes viruses, worms, Trojan horses, and Spyware. The MDM server must have an ability to address the issue of false alerts. False alerts can overwhelm reporting and administrative interfaces making it difficult to identify the true threat. A filtering capability that serves to identify and remove false positives is often employed to address this issue.\n",
|
|
1040
|
+
"severity": "medium"
|
|
1041
|
+
},
|
|
1042
|
+
{
|
|
1043
|
+
"id": "V-36178",
|
|
1044
|
+
"title": "The MDM server device integrity validation component must provide a near real-time alert when any of the organization defined list of compromise or potential compromise indicators occurs. \n",
|
|
1045
|
+
"description": "When an intrusion detection security event occurs it is imperative the operating system that has detected the event immediately notify the appropriate support personnel so they can respond accordingly. The ability of an MDM server to alert on compromises to the managed mobile devices mitigates the potential for these compromises to have further consequences to the enterprise.\n",
|
|
1046
|
+
"severity": "high"
|
|
1047
|
+
},
|
|
1048
|
+
{
|
|
1049
|
+
"id": "V-36179",
|
|
1050
|
+
"title": "The MDM server device integrity validation component must include the capability to notify an organization defined list of response personnel who are identified by name and/or by role notifications of suspicious events.\n",
|
|
1051
|
+
"description": "Integrity checking applications are by their nature designed to monitor and detect defined events occurring on the system. When the integrity checking mechanism finds an anomaly, it must notify personnel in order to ensure the proper action is taken based upon the integrity issues found. If notification is not performed, the issue may continue or worsen to allow intruders into the system.\n",
|
|
1052
|
+
"severity": "high"
|
|
1053
|
+
},
|
|
1054
|
+
{
|
|
1055
|
+
"id": "V-36180",
|
|
1056
|
+
"title": "Applications that utilize Discretionary Access Control (DAC) must enforce a policy that Includes or excludes access to the granularity of a single user.",
|
|
1057
|
+
"description": "DAC is based on the notion that individual users are \"owners\" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment.\nRationale for non-applicability: This control primarily applies to the discretionary sharing of information resources by data owners. This type of service is unrelated to MDM server functionality.",
|
|
1058
|
+
"severity": "medium"
|
|
1059
|
+
},
|
|
1060
|
+
{
|
|
1061
|
+
"id": "V-36181",
|
|
1062
|
+
"title": "The MDM server device integrity validation component must use automated mechanisms to alert security personnel when the device has been jailbroken or rooted.",
|
|
1063
|
+
"description": "Successful incident response and auditing relies on timely, accurate system information and analysis in order to allow the organization to identify and respond to potential incidents in a proficient manner. The ability of an MDM server to detect \"jailbreaking\" or rooting of the device mitigates the potential for these breaches to have further consequences to the enterprise.\n\nJailbroken/rooting refers to a mobile device where the security mechanisms of the hardware and OS of the device have been bypassed so the user has root access.",
|
|
1064
|
+
"severity": "high"
|
|
1065
|
+
},
|
|
1066
|
+
{
|
|
1067
|
+
"id": "V-36182",
|
|
1068
|
+
"title": "The MDM server must accept alerts from the mobile operating system when the mobile OS has detected integrity check failures. \n",
|
|
1069
|
+
"description": "Successful incident response and auditing relies on timely, accurate system information and analysis in order to allow the organization to identify and respond to potential incidents in a proficient manner. Alerting an MDM server mitigates the potential for attacks triggering integrity failures to have further consequences to the enterprise.\n",
|
|
1070
|
+
"severity": "high"
|
|
1071
|
+
},
|
|
1072
|
+
{
|
|
1073
|
+
"id": "V-36183",
|
|
1074
|
+
"title": "Applications utilizing Discretionary Access Control (DAC) must enforce a policy that limits propagation of access rights.",
|
|
1075
|
+
"description": "Discretionary Access Control (DAC) is based on the premise that individual users are \"owners\" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment.\nRationale for non-applicability: This control primarily applies to the discretionary sharing of information resources by data owners. This type of service is unrelated to MDM server functionality.",
|
|
1076
|
+
"severity": "medium"
|
|
1077
|
+
},
|
|
1078
|
+
{
|
|
1079
|
+
"id": "V-36184",
|
|
1080
|
+
"title": "The MDM server device integrity validation component device integrity validation scan interval must be configurable (desired setting is 6 hours or less). \n",
|
|
1081
|
+
"description": "Unauthorized changes to the operating system software or information on the system can possibly result in integrity or availability concerns. In order to quickly react to this situation, the operating system must detect these changes. One aspect of detection is the frequency at which the scans occur. The ability to set an appropriate frequency mitigates the risk that an attack will go without detection longer than the scanning interval.\n",
|
|
1082
|
+
"severity": "high"
|
|
1083
|
+
},
|
|
1084
|
+
{
|
|
1085
|
+
"id": "V-36185",
|
|
1086
|
+
"title": "Applications utilizing mobile code must meet DoD-defined mobile code requirements.",
|
|
1087
|
+
"description": "Decisions regarding the deployment of mobile code within organizational information systems are based on the potential for the code to cause damage to the system if used maliciously. \nRationale for non-applicability: The MDM server has no mobile code protection features.",
|
|
1088
|
+
"severity": "medium"
|
|
1089
|
+
},
|
|
1090
|
+
{
|
|
1091
|
+
"id": "V-36186",
|
|
1092
|
+
"title": "The MDM server device integrity validation component must verify the integrity of all operating system files, device drivers, and security enforcement mechanisms at startup and at least every six hours thereafter using one or more DoD approved cryptographic mechanisms that compare attributes of the operating system configuration to a known good baseline. \n",
|
|
1093
|
+
"description": "One of the most significant indicators of an IA attack is modification of operating system files, device drivers, or security enforcement mechanisms. An integrity verification capability or tool detects unauthorized modifications to files or permissions and either prevents further operation or reports its findings so an appropriate response can occur. ",
|
|
1094
|
+
"severity": "high"
|
|
1095
|
+
},
|
|
1096
|
+
{
|
|
1097
|
+
"id": "V-36187",
|
|
1098
|
+
"title": "The MDM server device integrity validation component must not be capable of being disabled or controlled by the user or a mobile device application.\n",
|
|
1099
|
+
"description": "One of the most significant indicators of an IA attack is modification of operating system files, device drivers, or security enforcement mechanisms. An integrity verification capability or tool detects unauthorized modifications to files or permissions and either prevents further operation or reports its findings so an appropriate response can occur. \n",
|
|
1100
|
+
"severity": "high"
|
|
1101
|
+
},
|
|
1102
|
+
{
|
|
1103
|
+
"id": "V-36188",
|
|
1104
|
+
"title": "The information system automatically terminates emergency accounts after an organization defined time period for each type of account.",
|
|
1105
|
+
"description": "Emergency application accounts are typically created due to an unforeseen operational event or could ostensibly be used in the event of a vendor support visit where a support representative requires a temporary unique account in order to perform diagnostic testing or conduct some other support related activity. When these types of accounts are created, there is a risk that the temporary account may remain in place and active after the support representative has left. \nRationale for non-applicability: The MDM server will leverage Enterprise Authentication Mechanism accounts. Therefore, the Enterprise Authentication Mechanism is expected to implement this control in lieu of local monitoring.",
|
|
1106
|
+
"severity": "medium"
|
|
1107
|
+
},
|
|
1108
|
+
{
|
|
1109
|
+
"id": "V-36189",
|
|
1110
|
+
"title": "The MDM server device integrity validation component must identify the affected mobile device, severity of the finding, and provide a recommended mitigation.\n",
|
|
1111
|
+
"description": "One of the most significant indicators of an IA attack is modification of operating system files, device drivers, or security enforcement mechanisms. An integrity verification capability or tool detects unauthorized modifications to files or permissions and either prevents further operation or reports its findings so an appropriate response can occur. \n",
|
|
1112
|
+
"severity": "high"
|
|
1113
|
+
},
|
|
1114
|
+
{
|
|
1115
|
+
"id": "V-36190",
|
|
1116
|
+
"title": "The MDM server device integrity validation component must base recommended mitigations for findings on the identified risk level of the finding.\n",
|
|
1117
|
+
"description": "One of the most significant indicators of an IA attack is modification of operating system files, device drivers, or security enforcement mechanisms. An integrity verification capability or tool detects unauthorized modifications to files or permissions and either prevents further operation or reports its findings so an appropriate response can occur. \n",
|
|
1118
|
+
"severity": "high"
|
|
1119
|
+
},
|
|
1120
|
+
{
|
|
1121
|
+
"id": "V-36191",
|
|
1122
|
+
"title": "The application must perform data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources when requested by client systems.",
|
|
1123
|
+
"description": "A recursive resolving or caching Domain Name System (DNS) server is an example of an information system providing name/address resolution service for local clients. \nRationale for non-applicability: The MDM server does not support name/address resolution queries.",
|
|
1124
|
+
"severity": "medium"
|
|
1125
|
+
},
|
|
1126
|
+
{
|
|
1127
|
+
"id": "V-36192",
|
|
1128
|
+
"title": "The MDM server device integrity validation component must operate separate and independent of the management of the mobile devices security policy.\n",
|
|
1129
|
+
"description": "One of the most significant indicators of an IA attack is modification of operating system files, device drivers, or security enforcement mechanisms. An integrity verification capability or tool detects unauthorized modifications to files or permissions and either prevents further operation or reports its findings so an appropriate response can occur. \n",
|
|
1130
|
+
"severity": "high"
|
|
1131
|
+
},
|
|
1132
|
+
{
|
|
1133
|
+
"id": "V-36193",
|
|
1134
|
+
"title": "Applications designed to address malware issues and/or enforce policy pertaining to organizational use of mobile code must take corrective actions, when unauthorized mobile code is identified.",
|
|
1135
|
+
"description": "Decisions regarding the employment of mobile code within organizational information systems are based on the potential for the code to cause damage to the system if used maliciously. \nRationale for non-applicability: An MDM server is not designed to enforce policy pertaining to use of mobile code.",
|
|
1136
|
+
"severity": "medium"
|
|
1137
|
+
},
|
|
1138
|
+
{
|
|
1139
|
+
"id": "V-36194",
|
|
1140
|
+
"title": "The MDM server device integrity validation component must identify changes in file structure and files on the mobile device.\n",
|
|
1141
|
+
"description": "One of the most significant indicators of an IA attack is modification of operating system files, device drivers, or security enforcement mechanisms. An integrity verification capability or tool detects unauthorized modifications to files or permissions and either prevents further operation or reports its findings so an appropriate response can occur. \n",
|
|
1142
|
+
"severity": "high"
|
|
1143
|
+
},
|
|
1144
|
+
{
|
|
1145
|
+
"id": "V-36195",
|
|
1146
|
+
"title": "The MDM server device integrity validation component must identify unexpected changes in applications installed on the mobile device.\n",
|
|
1147
|
+
"description": "One of the most significant indicators of an IA attack is modification of operating system files, device drivers, or security enforcement mechanisms. An integrity verification capability or tool detects unauthorized modifications to files or permissions and either prevents further operation or reports its findings so an appropriate response can occur. \n",
|
|
1148
|
+
"severity": "high"
|
|
1149
|
+
},
|
|
1150
|
+
{
|
|
1151
|
+
"id": "V-36196",
|
|
1152
|
+
"title": "The MDM server device integrity validation component must have the capability to maintain change history of individual devices.\n",
|
|
1153
|
+
"description": "One of the most significant indicators of an IA attack is modification of operating system files, device drivers, or security enforcement mechanisms. An integrity verification capability or tool detects unauthorized modifications to files or permissions and either prevents further operation or reports its findings so an appropriate response can occur. \n",
|
|
1154
|
+
"severity": "high"
|
|
1155
|
+
},
|
|
1156
|
+
{
|
|
1157
|
+
"id": "V-36197",
|
|
1158
|
+
"title": "The application must support organizational requirements to enforce password complexity by the number of special characters used.",
|
|
1159
|
+
"description": "Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. \nRationale for non-applicability: The MDM server will leverage Enterprise Authentication Mechanism accounts. Therefore, the Enterprise Authentication Mechanism is expected to implement this control in lieu of local monitoring.",
|
|
1160
|
+
"severity": "medium"
|
|
1161
|
+
},
|
|
1162
|
+
{
|
|
1163
|
+
"id": "V-36198",
|
|
1164
|
+
"title": "The MDM server device integrity validation component must provide the capability for the site administrator to amend information on mitigation actions that have taken place (e.g., wipe the device) to the scan report before the report is archived.\n",
|
|
1165
|
+
"description": "One of the most significant indicators of an IA attack is modification of operating system files, device drivers, or security enforcement mechanisms. An integrity verification capability or tool detects unauthorized modifications to files or permissions and either prevents further operation or reports its findings so an appropriate response can occur. \n",
|
|
1166
|
+
"severity": "high"
|
|
1167
|
+
},
|
|
1168
|
+
{
|
|
1169
|
+
"id": "V-36199",
|
|
1170
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must notify the user if it cannot verify the revocation status of the certificate.\n",
|
|
1171
|
+
"description": "If the user is aware that the revocation status of a certificate could not be verified, the user is better prepared to identify suspicious behavior that indicates an IA incident is in progress. Failure to notify the user of this occurrence makes it more likely that an adversary can use revoked certificates without detection. \n",
|
|
1172
|
+
"severity": "low"
|
|
1173
|
+
},
|
|
1174
|
+
{
|
|
1175
|
+
"id": "V-36200",
|
|
1176
|
+
"title": "The application must reject or delay, as defined by the organization, network traffic generated above configurable traffic volume thresholds.\n",
|
|
1177
|
+
"description": "It is critical when a system is at risk of failing to process audit logs as required; actions are automatically taken to mitigate the failure or risk of failure. \n\nOne method used to thwart the auditing system is for an attacker to attempt to overwhelm the auditing system with large amounts of irrelevant data. The end result being audit logs that are either overwritten and activity thereby erased or disk space that is exhausted and any future activity is no longer logged. \n\nIn many system configurations, the disk space allocated to the auditing system is separate from the disks allocated for the operating system; therefore, this may not result in a system outage.\nRationale for non-applicability: MDM server functionality involves the transfer of small policy and configuration files and other commands, none of which are expected to trigger network volume thresholds. If such protection is desired, it is better performed by the operating system or a network firewall.",
|
|
1178
|
+
"severity": "medium"
|
|
1179
|
+
},
|
|
1180
|
+
{
|
|
1181
|
+
"id": "V-36201",
|
|
1182
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must give the user the option to deny acceptance of a certificate if it cannot verify the certificates revocation status.\n",
|
|
1183
|
+
"description": "When additional assurance is required, the system should deny acceptance of a certificate if it cannot verify its revocation status. Otherwise, there is the potential that it is accepting the credentials of an unauthorized system. Allowing the operating system or user to deny certificates with unverified revocation status mitigates the risk associated with the acceptance of such certificates. \n",
|
|
1184
|
+
"severity": "low"
|
|
1185
|
+
},
|
|
1186
|
+
{
|
|
1187
|
+
"id": "V-36202",
|
|
1188
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must alert the user if it receives a public-key certificate issued from an untrusted certificate authority. \n",
|
|
1189
|
+
"description": "If the user is aware that a certificate has been issued from an untrusted certificate authority, the user can opt not to proceed or, alternatively, is better prepared to identify suspicious behavior that indicates an IA incident is in progress. Failure to notify the user of this occurrence makes it more likely that an adversary can launch an attack from an untrusted system.\n",
|
|
1190
|
+
"severity": "medium"
|
|
1191
|
+
},
|
|
1192
|
+
{
|
|
1193
|
+
"id": "V-36203",
|
|
1194
|
+
"title": "Applications providing information flow control must uniquely authenticate destination domains when transferring information.",
|
|
1195
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: Information flow control only applies to a CDS. The MDM server is not a CDS.",
|
|
1196
|
+
"severity": "medium"
|
|
1197
|
+
},
|
|
1198
|
+
{
|
|
1199
|
+
"id": "V-36204",
|
|
1200
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must give the user the option to deny acceptance of a certificate if the certificate was issued by an untrusted certificate authority.\n",
|
|
1201
|
+
"description": "When the operating system accepts the use of certificates issued from untrusted certificate authorities, there is the potential that the system or object presenting the certificate is malicious, and can compromise sensitive information or system integrity. When additional assurance is required, the system must deny acceptance of a certificate if it was issued by an untrusted certificate authority. \n",
|
|
1202
|
+
"severity": "medium"
|
|
1203
|
+
},
|
|
1204
|
+
{
|
|
1205
|
+
"id": "V-36205",
|
|
1206
|
+
"title": "Applications must uniquely identify destination domains for information transfer.",
|
|
1207
|
+
"description": "The application enforces approved authorizations for controlling the flow of information within the system and between interconnected systems in accordance with applicable policy. \nRationale for non-applicability: There is only one domain on the MDM server.",
|
|
1208
|
+
"severity": "medium"
|
|
1209
|
+
},
|
|
1210
|
+
{
|
|
1211
|
+
"id": "V-36206",
|
|
1212
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must alert the user if it receives an invalid public-key certificate. \n",
|
|
1213
|
+
"description": "If the user is aware that a certificate is invalid, the user can opt not to proceed or, alternatively, is better prepared to identify suspicious behavior that indicates an IA incident is in progress. Failure to notify the user of this occurrence makes it more likely that an adversary can launch an attack from an untrusted system.\n",
|
|
1214
|
+
"severity": "medium"
|
|
1215
|
+
},
|
|
1216
|
+
{
|
|
1217
|
+
"id": "V-36207",
|
|
1218
|
+
"title": "The application must provide the capability to remotely view/hear all content related to an established user session in real time.",
|
|
1219
|
+
"description": "While a great deal of effort is made to secure applications so as to prevent unauthorized access, in certain instances there can be valid requirements to listen/hear or view all content related to a particular user's application session in real time as it occurs. \nRationale for non-applicability: All user sessions are administrative whether local or remote.",
|
|
1220
|
+
"severity": "medium"
|
|
1221
|
+
},
|
|
1222
|
+
{
|
|
1223
|
+
"id": "V-36208",
|
|
1224
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must give the user the option to deny acceptance of a certificate if the mobile email client determines that the certificate is invalid.\n",
|
|
1225
|
+
"description": "When the operating system accepts the use of invalid certificates, there is the potential that the system or object presenting the certificate is malicious, and can compromise sensitive information or system integrity. When additional assurance is required, the system must deny acceptance of invalid certificates. \n",
|
|
1226
|
+
"severity": "medium"
|
|
1227
|
+
},
|
|
1228
|
+
{
|
|
1229
|
+
"id": "V-36209",
|
|
1230
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must not accept certificate revocation information without verifying its authenticity. \n",
|
|
1231
|
+
"description": "If the operating system does not verify the authenticity of revocation information, there is the potential that an authorized system is providing false information. Acceptance of the false information could result in the installation of unauthorized software or connection to rogue networks, depending on the use for which the certificate is intended. Verifying the authenticity of revocation information mitigates this risk.\n",
|
|
1232
|
+
"severity": "low"
|
|
1233
|
+
},
|
|
1234
|
+
{
|
|
1235
|
+
"id": "V-36210",
|
|
1236
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must verify all digital certificates in the certificate chain when performing PKI transactions.\n",
|
|
1237
|
+
"description": "If an adversary is able to compromise one of the certificates in the certificate chain, the adversary may be able to sign lower level certificates in the chain. This would enable the adversary to masquerade as other users or systems. By providing the mobile user with such false assurance, the adversary may be able obtain DoD information, capture authentication credentials, and perform other unauthorized functions. Verifying all digital certificates in the chain mitigates this risk.\n",
|
|
1238
|
+
"severity": "low"
|
|
1239
|
+
},
|
|
1240
|
+
{
|
|
1241
|
+
"id": "V-36211",
|
|
1242
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must give the user the option to deny acceptance of a certificate if the mobile email client determines that the certificate is unverified.\n",
|
|
1243
|
+
"description": "When the operating system accepts the use of invalid certificates, there is the potential that the system or object presenting the certificate is malicious, and can compromise sensitive information or system integrity. When additional assurance is required, the system must deny acceptance of invalid certificates. \n",
|
|
1244
|
+
"severity": "medium"
|
|
1245
|
+
},
|
|
1246
|
+
{
|
|
1247
|
+
"id": "V-36212",
|
|
1248
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must alert the user if it receives a public-key certificate with a non-FIPS approved algorithm. \n",
|
|
1249
|
+
"description": "If the user is aware that a certificate is invalid, the user can opt not to proceed or, alternatively, is better prepared to identify suspicious behavior that indicates an IA incident is in progress. Failure to notify the user of this occurrence makes it more likely that an adversary can launch an attack from an untrusted system.\n",
|
|
1250
|
+
"severity": "medium"
|
|
1251
|
+
},
|
|
1252
|
+
{
|
|
1253
|
+
"id": "V-36213",
|
|
1254
|
+
"title": "The application must dynamically reconfigure security attributes in accordance with an identified security policy as information is created and combined.",
|
|
1255
|
+
"description": "Security attributes are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. \nRationale for non-applicability: The only security attribute managed by the system is digital signatures.",
|
|
1256
|
+
"severity": "medium"
|
|
1257
|
+
},
|
|
1258
|
+
{
|
|
1259
|
+
"id": "V-36214",
|
|
1260
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must give the user the option to deny acceptance of a certificate if the mobile email client determines that the certificate uses a non-FIPS approved algorithm. \n",
|
|
1261
|
+
"description": "When the operating system accepts the use of invalid certificates, there is the potential that the system or object presenting the certificate is malicious, and can compromise sensitive information or system integrity. When additional assurance is required, the system must deny acceptance of invalid certificates. \n",
|
|
1262
|
+
"severity": "medium"
|
|
1263
|
+
},
|
|
1264
|
+
{
|
|
1265
|
+
"id": "V-36215",
|
|
1266
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must alert the user if the certificate uses an unverified CRL. \n",
|
|
1267
|
+
"description": "If the user is aware that a certificate is invalid, the user can opt not to proceed or, alternatively, is better prepared to identify suspicious behavior that indicates an IA incident is in progress. Failure to notify the user of this occurrence makes it more likely that an adversary can launch an attack from an untrusted system.\n",
|
|
1268
|
+
"severity": "medium"
|
|
1269
|
+
},
|
|
1270
|
+
{
|
|
1271
|
+
"id": "V-36216",
|
|
1272
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must give the user the option to deny acceptance of a certificate if the mobile email client determines the CRL of the certificate is unverified.\n",
|
|
1273
|
+
"description": "If the user is aware that a certificate is invalid, the user can opt not to proceed or, alternatively, is better prepared to identify suspicious behavior that indicates an IA incident is in progress. Failure to notify the user of this occurrence makes it more likely that an adversary can launch an attack from an untrusted system. \n",
|
|
1274
|
+
"severity": "medium"
|
|
1275
|
+
},
|
|
1276
|
+
{
|
|
1277
|
+
"id": "V-36217",
|
|
1278
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must alert the user if it receives an unverified public-key certificate. \n",
|
|
1279
|
+
"description": "If the user is aware that a certificate is invalid, the user can opt not to proceed or, alternatively, is better prepared to identify suspicious behavior that indicates an IA incident is in progress. Failure to notify the user of this occurrence makes it more likely that an adversary can launch an attack from an untrusted system.\n",
|
|
1280
|
+
"severity": "medium"
|
|
1281
|
+
},
|
|
1282
|
+
{
|
|
1283
|
+
"id": "V-36218",
|
|
1284
|
+
"title": "If the MDM server includes a mobile email management capability, all email (including email attachments) sent over the wireless link from the mobile email client MDM server mobile email management component located on the DoD network must be encrypted using AES. AES 128 bit encryption key length is the minimum requirement; AES 256 desired. \n",
|
|
1285
|
+
"description": "If an adversary can access the key store, it may be able to use the keys to perform a variety of unauthorized transactions. It may also be able to modify public-keys in a way that it can trick the operating system into accepting invalid certificates. Encrypting the key store protects the integrity and confidentiality of keys. AES encryption with adequate key lengths provides assurance that the protection is strong.\n",
|
|
1286
|
+
"severity": "medium"
|
|
1287
|
+
},
|
|
1288
|
+
{
|
|
1289
|
+
"id": "V-36219",
|
|
1290
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must encrypt all email using a FIPS 140-2 validated encryption algorithm. \n",
|
|
1291
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case the requirement is that the email client must utilize FIPS 140-2 encryption.\n",
|
|
1292
|
+
"severity": "medium"
|
|
1293
|
+
},
|
|
1294
|
+
{
|
|
1295
|
+
"id": "V-36220",
|
|
1296
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must be capable of providing S/MIME v3 (or later version) encryption of email. \n",
|
|
1297
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case S/MIME is the required mechanism for encryption of email.\n",
|
|
1298
|
+
"severity": "medium"
|
|
1299
|
+
},
|
|
1300
|
+
{
|
|
1301
|
+
"id": "V-36221",
|
|
1302
|
+
"title": "Applications providing information flow control must enforce approved authorizations for controlling the flow of information between interconnected systems in accordance with applicable policy.",
|
|
1303
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: This control maps to NIST SP 800-53 AC-4, which has been determined to apply to cross-domain solutions not within the scope of this SRG.\n",
|
|
1304
|
+
"severity": "medium"
|
|
1305
|
+
},
|
|
1306
|
+
{
|
|
1307
|
+
"id": "V-36222",
|
|
1308
|
+
"title": "Applications must notify users of organization defined security-related changes to the user's account occurring during the organization defined time period.\n",
|
|
1309
|
+
"description": "Some organizations may define certain security events as events requiring user notification. An organization may define an event such as a password change to a user's account occurring outside of normal business hours as a security-related event requiring that the application user be notified. In those instances, where organizations define such events, the application must notify the affected user or users.\nRationale for non-applicability: The MDM server has no user accounts, only administrators.",
|
|
1310
|
+
"severity": "medium"
|
|
1311
|
+
},
|
|
1312
|
+
{
|
|
1313
|
+
"id": "V-36223",
|
|
1314
|
+
"title": "If the MDM server includes a mobile email management capability, the email client S/MIME must be fully interoperable with DoD PKI and CAC/PIV. CAC/PIV (hard token) and PKCS#12 (soft token) certificate stores must be supported. \n",
|
|
1315
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case the CAC is the required mechanism for that protection.\n",
|
|
1316
|
+
"severity": "low"
|
|
1317
|
+
},
|
|
1318
|
+
{
|
|
1319
|
+
"id": "V-36224",
|
|
1320
|
+
"title": "If the MDM server includes a mobile email management capability, the email client S/MIME encryption algorithm must be 3DES or AES. When AES is used, AES 128 bit encryption key length is the minimum requirement; AES 256 desired.\n",
|
|
1321
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case the requirement states that S/MIME must utilize a 3DES or AES encryption algorithm.\n",
|
|
1322
|
+
"severity": "medium"
|
|
1323
|
+
},
|
|
1324
|
+
{
|
|
1325
|
+
"id": "V-36225",
|
|
1326
|
+
"title": "If the MDM server includes a mobile email management capability, the email client S/MIME cryptographic module must be FIPS 140-2 validated.\n",
|
|
1327
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case the requirement states that the S/MIME cryptographic module must be FIPS 140-2 validated.\n",
|
|
1328
|
+
"severity": "medium"
|
|
1329
|
+
},
|
|
1330
|
+
{
|
|
1331
|
+
"id": "V-36226",
|
|
1332
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must provide the mobile device user the capability to save public certificates of contacts in the contact object.\n",
|
|
1333
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case the requirement states that the user must be given the capability to save public certificates of contacts.",
|
|
1334
|
+
"severity": "low"
|
|
1335
|
+
},
|
|
1336
|
+
{
|
|
1337
|
+
"id": "V-36227",
|
|
1338
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must cache the certificate status of signed emails that have been received on the handheld device for a period not extending beyond the expiration period of the revocation data. \n",
|
|
1339
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case the requirement is to cache the certificate status of signed emails on the mobile device.\n",
|
|
1340
|
+
"severity": "low"
|
|
1341
|
+
},
|
|
1342
|
+
{
|
|
1343
|
+
"id": "V-36228",
|
|
1344
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must set the Smart Card or Certificate Store Password caching timeout period from at least 15 to 120 minutes, if Smart Card or Certificate Store Password caching is available.\n",
|
|
1345
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case the requirement states that Smart Card/Certificate Store password caching must time out.\n",
|
|
1346
|
+
"severity": "medium"
|
|
1347
|
+
},
|
|
1348
|
+
{
|
|
1349
|
+
"id": "V-36229",
|
|
1350
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must provide the mobile device user the capability to digitally sign and/or encrypt outgoing email messages using software or hardware based digital certificates. \n",
|
|
1351
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case the requirement states that the email client must be able to sign and/or encrypt outgoing messages.",
|
|
1352
|
+
"severity": "medium"
|
|
1353
|
+
},
|
|
1354
|
+
{
|
|
1355
|
+
"id": "V-36230",
|
|
1356
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must provide the mobile device user the capability to decrypt incoming email messages using software or hardware based digital certificates. \n",
|
|
1357
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case the requirement states that the email client must be able to decrypt incoming email messages.\n",
|
|
1358
|
+
"severity": "medium"
|
|
1359
|
+
},
|
|
1360
|
+
{
|
|
1361
|
+
"id": "V-36231",
|
|
1362
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must provide a mechanism to provide certificate validation through a trusted OCSP, CRL, or SCVP.\n",
|
|
1363
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case the requirement states that the email client must validate certificates through a trusted OCSP, CRL, or SCVP.",
|
|
1364
|
+
"severity": "medium"
|
|
1365
|
+
},
|
|
1366
|
+
{
|
|
1367
|
+
"id": "V-36232",
|
|
1368
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must provide a noticeable warning to the user if the CRL, SCVP, or OCSP server cannot be contacted or the revocation data provided cannot be verified \n",
|
|
1369
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case the requirement states that the user must be notified if the CRL/SCVP/OCSP server cannot be contacted.",
|
|
1370
|
+
"severity": "low"
|
|
1371
|
+
},
|
|
1372
|
+
{
|
|
1373
|
+
"id": "V-36233",
|
|
1374
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must support retrieving encryption certificates not stored in the local trust anchor store for S/MIME purposes.\n",
|
|
1375
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case the requirement stated that the email client must support retrieving certificates not stored in the local trust anchor store.\n",
|
|
1376
|
+
"severity": "low"
|
|
1377
|
+
},
|
|
1378
|
+
{
|
|
1379
|
+
"id": "V-36234",
|
|
1380
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must support SHA2 signing operations.\n",
|
|
1381
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. In this case the requirement states the email client must support SHA2 signing.\n",
|
|
1382
|
+
"severity": "medium"
|
|
1383
|
+
},
|
|
1384
|
+
{
|
|
1385
|
+
"id": "V-36235",
|
|
1386
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must either block or convert all active content in email (HTML, RTF, etc.) to text before the email is forwarded to the mobile device.\n",
|
|
1387
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. Requiring that all emails are viewed in plain text helps remediate phishing attempts.\n",
|
|
1388
|
+
"severity": "low"
|
|
1389
|
+
},
|
|
1390
|
+
{
|
|
1391
|
+
"id": "V-36236",
|
|
1392
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must support SHA2 signature verification.\n",
|
|
1393
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data and must be supported on signature verification. In this case the requirement is that the email client must support SHA2 signature verification.\n",
|
|
1394
|
+
"severity": "low"
|
|
1395
|
+
},
|
|
1396
|
+
{
|
|
1397
|
+
"id": "V-36237",
|
|
1398
|
+
"title": "If the MDM server includes a mobile email management capability, all email sent to the mobile device must be managed by the MDM server mobile email component. Desktop or Internet controlled email redirection are not authorized.\n",
|
|
1399
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data and must be supported on signature verification. In this case the requirement is that the email client must interface directly with the MDM server.",
|
|
1400
|
+
"severity": "low"
|
|
1401
|
+
},
|
|
1402
|
+
{
|
|
1403
|
+
"id": "V-36238",
|
|
1404
|
+
"title": "The MDM server must prevent modification of key material except during secure, non-operable system states.\n",
|
|
1405
|
+
"description": "Secure, non-operable system states are states in which the information system is not performing mission/business-related processing (e.g., the system is off-line for maintenance, troubleshooting, boot-up, shutdown). If an adversary is able to modify key material, then the adversary may be able to compromise sensitive DoD information. The adversary may also be able to bypass authentication controls on downloaded applications, websites, and network access points depending on the keys modified. This attack could enable the adversary to install unauthorized applications and stage subsequent attacks on other systems. Preventing modification of key material mitigates the risk of this attack.\n\nKey material general refers to cryptographic keys and algorithms. There are operations were key material must be modified for proper operation of the cryptographic system.",
|
|
1406
|
+
"severity": "high"
|
|
1407
|
+
},
|
|
1408
|
+
{
|
|
1409
|
+
"id": "V-36239",
|
|
1410
|
+
"title": "The MDM server must query the certification authority to determine whether a public-key certificate has been revoked before accepting the certificate for authentication purposes.\n",
|
|
1411
|
+
"description": "Failure to verify a certificate’s revocation status can result in the system accepting a revoked and therefore authorized certificate. This could result in the installation of unauthorized software or 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.\n",
|
|
1412
|
+
"severity": "low"
|
|
1413
|
+
},
|
|
1414
|
+
{
|
|
1415
|
+
"id": "V-36240",
|
|
1416
|
+
"title": "The MDM server must verify all digital certificates in the certificate chain when performing PKI transactions.\n",
|
|
1417
|
+
"description": "If an adversary is able to compromise one of the certificates in the certificate chain, the adversary may be able to sign lower level certificates in the chain. This would enable the adversary to masquerade as other users or systems. By providing the mobile user with such false assurance, the adversary may be able obtain DoD information, capture authentication credentials, and perform other unauthorized functions. Verifying all digital certificates in the chain mitigates this risk.\n",
|
|
1418
|
+
"severity": "low"
|
|
1419
|
+
},
|
|
1420
|
+
{
|
|
1421
|
+
"id": "V-36241",
|
|
1422
|
+
"title": "The MDM server must ensure that PKI-based authentication maps the authenticated identity to the user account.\n",
|
|
1423
|
+
"description": "The cornerstone of the PKI is the private key used to encrypt or digitally sign information. The key by itself is a cryptographic value that does not contain specific user information. The authenticated identity must be mapped to an account for access and authorization decisions. This capability strengthens authentication to remote information systems and thus makes it less likely that such systems will be compromised.\n",
|
|
1424
|
+
"severity": "low"
|
|
1425
|
+
},
|
|
1426
|
+
{
|
|
1427
|
+
"id": "V-36242",
|
|
1428
|
+
"title": "The MDM server must encrypt all data in transit (e.g., mobile device encryption keys, server PKI certificates, mobile device data bases) using AES encryption (AES 128 bit encryption key length is the minimum requirement; AES 256 desired). \n",
|
|
1429
|
+
"description": "If data in transit is unencrypted, it is vulnerable to disclosure. Even if the operating system enforces permissions on data access, an adversary can remove non-volatile memory and read it directly, thereby circumventing operating system controls. Encrypting the data ensures that confidentiality is protected even when the operating system is not running. AES encryption with appropriate key lengths provides assurance that the cryptography is adequate. This requirement applies to data transmitted to managed mobile devices and to another enterprise network management application.\n",
|
|
1430
|
+
"severity": "medium"
|
|
1431
|
+
},
|
|
1432
|
+
{
|
|
1433
|
+
"id": "V-36243",
|
|
1434
|
+
"title": "The MDM server must produce, control, and distribute symmetric cryptographic keys using NIST-approved or NSA approved key management technology and processes.\n",
|
|
1435
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data.\n",
|
|
1436
|
+
"severity": "medium"
|
|
1437
|
+
},
|
|
1438
|
+
{
|
|
1439
|
+
"id": "V-36244",
|
|
1440
|
+
"title": "The MDM server must produce, control, and distribute asymmetric cryptographic keys using NSA-approved or NIST-approved key management technology and processes.\n",
|
|
1441
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data.\n",
|
|
1442
|
+
"severity": "medium"
|
|
1443
|
+
},
|
|
1444
|
+
{
|
|
1445
|
+
"id": "V-36245",
|
|
1446
|
+
"title": "The MDM server must have access to DoD root and intermediate PKI certificates when performing DoD PKI related transactions.\n",
|
|
1447
|
+
"description": "DoD root and intermediate PKI certificates are used to verify the authenticity of PKI certificates of users and web services. If the root and intermediate certificates are not available, an adversary could falsely sign a certificate in such a way that it could not be detected. Providing access to the DoD root and intermediate PKI certificates greatly diminishes the risk of this attack.\n",
|
|
1448
|
+
"severity": "medium"
|
|
1449
|
+
},
|
|
1450
|
+
{
|
|
1451
|
+
"id": "V-36246",
|
|
1452
|
+
"title": "The application must notify the user of the number of unsuccessful login/access attempts occurring during an organization defined time period.",
|
|
1453
|
+
"description": "Users need to be aware of activity that occurs regarding their application account. Providing users with information regarding the number of unsuccessful attempts made to login to their account allows the user to determine if any unauthorized activity has occurred and gives them an opportunity to notify administrators.\nRationale for non-applicability: The MDM server will leverage Enterprise Authentication Mechanism accounts. Therefore, the Enterprise Authentication Mechanism is expected to implement this control in lieu of local monitoring.",
|
|
1454
|
+
"severity": "medium"
|
|
1455
|
+
},
|
|
1456
|
+
{
|
|
1457
|
+
"id": "V-36247",
|
|
1458
|
+
"title": "The MDM server PKI certificate store must encrypt contents using AES encryption (AES 128 bit encryption key length is the minimum requirement; AES 256 desired).\n",
|
|
1459
|
+
"description": "If an adversary can access the key store, it may be able to use the keys to perform a variety of unauthorized transactions. It may also be able to modify public-keys in a way that it can trick the operating system into accepting invalid certificates. Encrypting the key store protects the integrity and confidentiality of keys. AES encryption with adequate key lengths provides assurance that the protection is strong.\n",
|
|
1460
|
+
"severity": "medium"
|
|
1461
|
+
},
|
|
1462
|
+
{
|
|
1463
|
+
"id": "V-36248",
|
|
1464
|
+
"title": "In order to inform the user of the number of successful login attempts made with the user's account, the application must notify the user of the number of successful logins/accesses occurring during an organization defined time period.",
|
|
1465
|
+
"description": "Users need to be aware of activity that occurs regarding their application account. Providing users with information regarding the number of successful attempts made to login to their account allows the user to determine if any unauthorized activity has occurred and gives them an opportunity to notify administrators. \nRationale for non-applicability: The MDM server will leverage Enterprise Authentication Mechanism accounts. Therefore, the Enterprise Authentication Mechanism is expected to implement this control in lieu of local monitoring.",
|
|
1466
|
+
"severity": "medium"
|
|
1467
|
+
},
|
|
1468
|
+
{
|
|
1469
|
+
"id": "V-36249",
|
|
1470
|
+
"title": "The MDM server must implement required cryptographic protections using cryptographic modules that comply with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n",
|
|
1471
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. Strong encryption must be used to protect the integrity and confidentiality of the data. Data at rest on the phone and memory storage devices, data in transit, and critical data in memory could be applicable.",
|
|
1472
|
+
"severity": "low"
|
|
1473
|
+
},
|
|
1474
|
+
{
|
|
1475
|
+
"id": "V-36250",
|
|
1476
|
+
"title": "If the MDM server includes a mobile email management capability, the email client must support the capability to enable or disable contact list data elements transferred to the phone application.\n",
|
|
1477
|
+
"description": "The contact list data elements may contain sensitive or PII information, therefore, the data elements accessed outside the security container must be limited so sensitive data is not exposed.\n",
|
|
1478
|
+
"severity": "low"
|
|
1479
|
+
},
|
|
1480
|
+
{
|
|
1481
|
+
"id": "V-36251",
|
|
1482
|
+
"title": "Applications must uniquely authenticate source domains for information transfer.",
|
|
1483
|
+
"description": "The information system enforces approved authorizations for controlling the flow of information within the system and between interconnected systems in accordance with applicable policy. \nRationale for non-applicability: Information flow control only applies to a CDS. An MDM server is not a cross domain solution.",
|
|
1484
|
+
"severity": "medium"
|
|
1485
|
+
},
|
|
1486
|
+
{
|
|
1487
|
+
"id": "V-36252",
|
|
1488
|
+
"title": "The MDM server must associate digital certificates used to sign applications, security policies, etc., with information exchanged between information systems.\n",
|
|
1489
|
+
"description": "When data is exchanged between information systems, the security attributes associated with said data needs to be maintained. If the associated keys are disrupted application integrity is lost.\n",
|
|
1490
|
+
"severity": "low"
|
|
1491
|
+
},
|
|
1492
|
+
{
|
|
1493
|
+
"id": "V-36253",
|
|
1494
|
+
"title": "Applications must uniquely identify source domains for information transfer.",
|
|
1495
|
+
"description": "The application enforces approved authorizations for controlling the flow of information within the system and between interconnected systems in accordance with applicable policy. \nRationale for non-applicability: The MDM server does not support multiple security domains.",
|
|
1496
|
+
"severity": "medium"
|
|
1497
|
+
},
|
|
1498
|
+
{
|
|
1499
|
+
"id": "V-36254",
|
|
1500
|
+
"title": "The MDM server must validate the integrity of digital certificates exchanged between systems.\n",
|
|
1501
|
+
"description": "When data is exchanged between information systems, the security attributes associated with said data needs to be maintained. If the associated keys are disrupted application integrity is lost.\n",
|
|
1502
|
+
"severity": "low"
|
|
1503
|
+
},
|
|
1504
|
+
{
|
|
1505
|
+
"id": "V-36255",
|
|
1506
|
+
"title": "The MDM server must support organizational requirements to issue public-key certificates under an appropriate certificate policy or obtain public-key certificates under an appropriate certificate policy from an approved service provider.\n",
|
|
1507
|
+
"description": "Only DoD PKI issued or approved software authentication certificates must be installed on DoD mobile operating system devices. Without this trust paths would be broken which could lead to unapproved certificates being used.\n",
|
|
1508
|
+
"severity": "medium"
|
|
1509
|
+
},
|
|
1510
|
+
{
|
|
1511
|
+
"id": "V-36256",
|
|
1512
|
+
"title": "The MDM server must encrypt all key data items (e.g., mobile device encryption keys, server PKI certificates, mobile device data bases) saved in memory using AES encryption (AES 128 bit encryption key length is the minimum requirement; AES 256 desired). \n",
|
|
1513
|
+
"description": "If data at rest is unencrypted, it is vulnerable to disclosure. Even if the operating system enforces permissions on data access, an adversary can remove non-volatile memory and read it directly, thereby circumventing operating system controls. Encrypting the data ensures that confidentiality is protected even when the operating system is not running. AES encryption with appropriate key lengths provides assurance that the cryptography is adequate.\n",
|
|
1514
|
+
"severity": "medium"
|
|
1515
|
+
},
|
|
1516
|
+
{
|
|
1517
|
+
"id": "V-36257",
|
|
1518
|
+
"title": "Applications must provide the ability to prohibit the transfer of unsanctioned information in accordance with security policy.",
|
|
1519
|
+
"description": "The application enforces approved authorizations for controlling the flow of information within the system and between interconnected systems in accordance with applicable policy. \nRationale for non-applicability: The MDM server does not support the concept of sanctioned or unsanctioned information.",
|
|
1520
|
+
"severity": "medium"
|
|
1521
|
+
},
|
|
1522
|
+
{
|
|
1523
|
+
"id": "V-36258",
|
|
1524
|
+
"title": "The MDM server must support and maintain the binding of digital signatures on software components and applications in storage.\n",
|
|
1525
|
+
"description": "Digital signatures enable the system to verify the integrity of the signed object and authenticate the object’s signatory. Failure to maintain the binding of digital signatures on software components and applications in storage makes it more likely that an adversary could modify or replace those objects. Conversely, the bindings enable the operating system to verify the software’s integrity and source with a high degree of assurance whenever necessary. \n",
|
|
1526
|
+
"severity": "high"
|
|
1527
|
+
},
|
|
1528
|
+
{
|
|
1529
|
+
"id": "V-36259",
|
|
1530
|
+
"title": "Applications designed to control information flow must provide the ability to detect unsanctioned information being transmitted across security domains.",
|
|
1531
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: The scope of this SRG concerns MDM server systems that support a single security domain.",
|
|
1532
|
+
"severity": "medium"
|
|
1533
|
+
},
|
|
1534
|
+
{
|
|
1535
|
+
"id": "V-36260",
|
|
1536
|
+
"title": "Applications, when transferring information between different security domains, must implement or incorporate policy filters that constrain data object and structure attributes according to organizational security policy requirements.",
|
|
1537
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: The MDM server does not support multiple security domains.",
|
|
1538
|
+
"severity": "medium"
|
|
1539
|
+
},
|
|
1540
|
+
{
|
|
1541
|
+
"id": "V-36261",
|
|
1542
|
+
"title": "Applications providing information flow control must enforce approved authorizations for controlling the flow of information within the system in accordance with applicable policy.",
|
|
1543
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system, and between information systems (as opposed to who is allowed to access the information), and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: This control maps to NIST SP 800-53 AC-4, which has been determined to apply to cross-domain solutions not within the scope of this SRG.\n",
|
|
1544
|
+
"severity": "medium"
|
|
1545
|
+
},
|
|
1546
|
+
{
|
|
1547
|
+
"id": "V-36262",
|
|
1548
|
+
"title": "The MDM server must support and maintain the binding of digital signatures on software components and applications in process.\n",
|
|
1549
|
+
"description": "Digital signatures enable the system to verify the integrity of the signed object and authenticate the object’s signatory. Failure to maintain the binding of digital signatures on software components and applications in process makes it more likely that an adversary could modify or replace those objects when the software is executed. The bindings enable the operating system to verify the software’s integrity and source just before the execution process. \n",
|
|
1550
|
+
"severity": "high"
|
|
1551
|
+
},
|
|
1552
|
+
{
|
|
1553
|
+
"id": "V-36263",
|
|
1554
|
+
"title": "The application must enforce Discretionary Access Control (DAC) policy allowing users to specify and control sharing by named individuals, groups of individuals, or by both, limiting propagation of access rights and includes or excludes access to the granularity of a single user.",
|
|
1555
|
+
"description": "Access control policies (e.g., identity-based policies, role-based policies, attribute-based policies) and access enforcement mechanisms (e.g., access control lists, access control matrices, cryptography) are employed by organizations to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, domains). \nRationale for non-applicability: This control primarily applies to the discretionary sharing of information resources by data owners. This type of service is unrelated to MDM server functionality.",
|
|
1556
|
+
"severity": "medium"
|
|
1557
|
+
},
|
|
1558
|
+
{
|
|
1559
|
+
"id": "V-36264",
|
|
1560
|
+
"title": "The MDM server must support and maintain the binding of digital signatures on information in transmission.\n",
|
|
1561
|
+
"description": "Digital signatures enable the system to verify the integrity of the signed object and authenticate the object’s signatory. Failure to maintain the binding of digital signatures on software components and applications in process makes it more likely that an adversary could modify or replace those objects when the software is executed. The bindings enable the operating system to verify the software’s integrity and source just before the execution process. In order for the signature to be present at execution, it must be bound during transmission.",
|
|
1562
|
+
"severity": "high"
|
|
1563
|
+
},
|
|
1564
|
+
{
|
|
1565
|
+
"id": "V-36265",
|
|
1566
|
+
"title": "Applications must support the organizational requirement to automatically monitor on atypical usage of accounts.",
|
|
1567
|
+
"description": "Atypical account usage is behavior that is not part of normal usage cycles. For example, user account activity occurring after hours or on weekends. \nRationale for non-applicability: The MDM server will leverage Enterprise Authentication Mechanism accounts. Therefore, the Enterprise Authentication Mechanism is expected to implement this control in lieu of local monitoring.",
|
|
1568
|
+
"severity": "medium"
|
|
1569
|
+
},
|
|
1570
|
+
{
|
|
1571
|
+
"id": "V-36266",
|
|
1572
|
+
"title": "The MDM server must maintain the binding of digital credentials to information with sufficient assurance that the information/credential association can be used as the basis for automated policy actions.\n",
|
|
1573
|
+
"description": "Without the assurance of credential association with the information, policy decisions based on that association become faulty and potentially allow for authorization decisions that are applied incorrectly.\n\nSufficient assurance: assurance that the digital credential has not been removed, replaced or modified.",
|
|
1574
|
+
"severity": "high"
|
|
1575
|
+
},
|
|
1576
|
+
{
|
|
1577
|
+
"id": "V-36267",
|
|
1578
|
+
"title": "The application must protect audit data records and integrity by using cryptographic mechanisms.",
|
|
1579
|
+
"description": "Protection of audit records and audit data is of critical importance. Cryptographic mechanisms are the industry established standard used to protect the integrity of audit data. An example of a cryptographic mechanism is the computation and application of a cryptographic-signed hash using asymmetric cryptography. \nRationale for non-applicability: This requirement is better allocated to a central audit management system.",
|
|
1580
|
+
"severity": "medium"
|
|
1581
|
+
},
|
|
1582
|
+
{
|
|
1583
|
+
"id": "V-36268",
|
|
1584
|
+
"title": "The MDM server must only allow authorized administrators to associate PKI credentials with information.\n",
|
|
1585
|
+
"description": "Without the assurance of credential association with the information, policy decisions based on that association become faulty and potentially allow for authorization decisions that are applied incorrectly. \n",
|
|
1586
|
+
"severity": "high"
|
|
1587
|
+
},
|
|
1588
|
+
{
|
|
1589
|
+
"id": "V-36269",
|
|
1590
|
+
"title": "The application must invoke a system shutdown in the event of an audit failure, unless an alternative audit capability exists.",
|
|
1591
|
+
"description": "It is critical when a system is at risk of failing to process audit logs as required; it takes action to mitigate the failure. If the system were to continue processing without auditing enabled, actions can be taken on the system that cannot be tracked and recorded for later forensic analysis. \nRationale for non-applicability: This requirement is better handled by the operating system or the audit system handling this capability.",
|
|
1592
|
+
"severity": "medium"
|
|
1593
|
+
},
|
|
1594
|
+
{
|
|
1595
|
+
"id": "V-36270",
|
|
1596
|
+
"title": "The MDM server must automatically audit on administrator account creation.\n",
|
|
1597
|
+
"description": "Auditing of account creation is a method and best practice for mitigating the risk of an attacker creating a persistent method of re-establishing access. A comprehensive account management process will ensure an audit trail which documents the creation of accounts and, if required, notifies administrators. Such a process greatly reduces the risk of accounts being created outside the normal approval process and provides logging that can be used for forensic purposes. Additionally, the audit records of account creation can be compared to the known approved account creation list.",
|
|
1598
|
+
"severity": "medium"
|
|
1599
|
+
},
|
|
1600
|
+
{
|
|
1601
|
+
"id": "V-36271",
|
|
1602
|
+
"title": "The MDM server must audit any use of privileged accounts, or roles, with access to organization defined security functions or security relevant information, when accessing other system functions.\n",
|
|
1603
|
+
"description": "This requirement is intended to address those situations where an access control policy, such as Role Based Access Control (RBAC), is being implemented and where a change of role provides the same degree of assurance in the change of access authorizations for both the user and all processes acting on behalf of the user as would be provided by a change between a privileged and non-privileged account. An audit trail pertaining to the access of security functions or security relevant information is imperative for forensic analysis in the event a non-privileged account becomes a part of a role it should not be a part of.",
|
|
1604
|
+
"severity": "medium"
|
|
1605
|
+
},
|
|
1606
|
+
{
|
|
1607
|
+
"id": "V-36272",
|
|
1608
|
+
"title": "The application must validate the binding of the reviewers identity to the information at the transfer/release point prior to release/transfer from one security domain to another security domain.",
|
|
1609
|
+
"description": "This non-repudiation control enhancement is intended to mitigate the risk that information could be modified between review and transfer/release particularly when transfer is occurring between security domains. \nRationale for non-applicability: The MDM server is not intended to store user data and therefore would not employ notions of chain of custody.",
|
|
1610
|
+
"severity": "medium"
|
|
1611
|
+
},
|
|
1612
|
+
{
|
|
1613
|
+
"id": "V-36273",
|
|
1614
|
+
"title": "The MDM server must produce audit records containing the severity level of each recorded event.\n",
|
|
1615
|
+
"description": "MDM server auditing capability is critical for accurate forensic analysis. Event severity levels allow system administrators and IA personnel to more easily identify critical system issues and debug software.\n",
|
|
1616
|
+
"severity": "low"
|
|
1617
|
+
},
|
|
1618
|
+
{
|
|
1619
|
+
"id": "V-36274",
|
|
1620
|
+
"title": "Applications must maintain reviewer/releaser identity and credentials within the established chain of custody for all information reviewed or released.",
|
|
1621
|
+
"description": "Non-repudiation protects individuals against later claims by an author of not having authored a particular document, a sender of not having transmitted a message, a receiver of not having received a message, or a signatory of not having signed a document. Non-repudiation services can be used to determine if information originated from an individual, or if an individual took specific actions (e.g., sending an email, signing a contract, approving a procurement request) or received specific information. Non-repudiation services are obtained by employing various techniques or mechanisms (e.g., digital signatures, digital message receipts).\nRationale for non-applicability: The MDM server is not intended to store user data and therefore would not employ notions of chain of custody.",
|
|
1622
|
+
"severity": "medium"
|
|
1623
|
+
},
|
|
1624
|
+
{
|
|
1625
|
+
"id": "V-36275",
|
|
1626
|
+
"title": "The MDM server must include date and timestamps in each event recorded in audit logs.\n",
|
|
1627
|
+
"description": "MDM server auditing capability is critical for accurate forensic analysis. The inclusion of timestamps better enables for correlation of events across disparate systems, which can be critical to isolating IA incidents and developing appropriate countermeasures. \n",
|
|
1628
|
+
"severity": "low"
|
|
1629
|
+
},
|
|
1630
|
+
{
|
|
1631
|
+
"id": "V-36276",
|
|
1632
|
+
"title": "The MDM server must include the software component (e.g., administration module, mobile device security policy module, etc.) that generated each event recorded in audit logs.\n",
|
|
1633
|
+
"description": "MDM server auditing capability is critical for accurate forensic analysis. The inclusion of software component that generated each event in the audit logs enables system administrators and IA personnel to identify the source of problems and incidents. Without this data, the component information may not be known.\n",
|
|
1634
|
+
"severity": "low"
|
|
1635
|
+
},
|
|
1636
|
+
{
|
|
1637
|
+
"id": "V-36277",
|
|
1638
|
+
"title": "The application must associate the identity of the information producer with the information.",
|
|
1639
|
+
"description": "Non-repudiation supports audit requirements to provide the appropriate organizational officials the means to identify who produced specific information in the event of an information transfer. \nRationale for non-applicability: This requirement is better allocated to the operating system.",
|
|
1640
|
+
"severity": "medium"
|
|
1641
|
+
},
|
|
1642
|
+
{
|
|
1643
|
+
"id": "V-36278",
|
|
1644
|
+
"title": "The MDM server must produce audit records containing sufficient information to establish the sources of the events.\n",
|
|
1645
|
+
"description": "MDM server auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, for example, timestamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, IP addresses, and access control or flow control rules invoked.",
|
|
1646
|
+
"severity": "low"
|
|
1647
|
+
},
|
|
1648
|
+
{
|
|
1649
|
+
"id": "V-36279",
|
|
1650
|
+
"title": "The application must only generate error messages that provide information necessary for corrective actions without revealing organization defined sensitive or potentially harmful information in error logs and administrative messages that could be exploited.",
|
|
1651
|
+
"description": "Any application providing too much information in error logs and in administrative messages to the screen risks compromising the data and security of the application and system. The structure and content of error messages needs to be carefully considered by the organization and development team. \nRationale for non-applicability: This requirement is better specified by other audit related CCIs. CCI-001314 ensures that only the MDM server Administrator has access to error messages.",
|
|
1652
|
+
"severity": "medium"
|
|
1653
|
+
},
|
|
1654
|
+
{
|
|
1655
|
+
"id": "V-36280",
|
|
1656
|
+
"title": "The MDM server must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.\n",
|
|
1657
|
+
"description": "MDM server auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, for example, timestamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked. Success or failure indicators allow recreation of the processes that led up to events in question.",
|
|
1658
|
+
"severity": "low"
|
|
1659
|
+
},
|
|
1660
|
+
{
|
|
1661
|
+
"id": "V-36281",
|
|
1662
|
+
"title": "Applications that are utilized to address the issue of SPAM and provide protection from SPAM must automatically update any and all SPAM protection measures including signature definitions.",
|
|
1663
|
+
"description": "Originators of SPAM emails are constantly changing their source email addresses in order to defeat SPAM countermeasures; therefore, SPAM software must be constantly updated to address the changing threat. A manual update procedure is labor intensive and does not scale well in an enterprise environment which necessitates an automatic update capability.\nRationale for non-applicability: The MDM server does not perform SPAM protection.",
|
|
1664
|
+
"severity": "medium"
|
|
1665
|
+
},
|
|
1666
|
+
{
|
|
1667
|
+
"id": "V-36282",
|
|
1668
|
+
"title": "The MDM server must support the transfer of audit logs to remote log or management servers.\n",
|
|
1669
|
+
"description": "MDM server auditing capability is critical for accurate forensic analysis. The ability to transfer audit logs often is necessary to quickly isolate them, protect their integrity, and analyze their contents. An important aspect of security is maintaining awareness of what users have tried to do to with their devices.\n",
|
|
1670
|
+
"severity": "high"
|
|
1671
|
+
},
|
|
1672
|
+
{
|
|
1673
|
+
"id": "V-36283",
|
|
1674
|
+
"title": "Applications that serve to protect organizations and individuals from SPAM messages must incorporate update mechanisms updating protection mechanisms and signature updates when new application releases are available in accordance with organizational configuration management policy and procedures.\n",
|
|
1675
|
+
"description": "Senders of SPAM messages are continually modifying their tactics and source email addresses in order to elude protection mechanisms. To stay up-to-date with the changing threat and to identify SPAM messages, it is critical that SPAM protection mechanisms are kept current.\nRationale for non-applicability: The MDM server does not perform SPAM protection.",
|
|
1676
|
+
"severity": "medium"
|
|
1677
|
+
},
|
|
1678
|
+
{
|
|
1679
|
+
"id": "V-36284",
|
|
1680
|
+
"title": "The MDM server must transfer audit logs from managed mobile devices to the MDM server.\n",
|
|
1681
|
+
"description": "MDM server auditing capability is critical for accurate forensic analysis. The ability to transfer audit logs often is necessary to quickly isolate them, protect their integrity, and analyze their contents.\n",
|
|
1682
|
+
"severity": "high"
|
|
1683
|
+
},
|
|
1684
|
+
{
|
|
1685
|
+
"id": "V-36285",
|
|
1686
|
+
"title": "The MDM server must provide designated alerts to another enterprise network management application using SNMPv3.\n",
|
|
1687
|
+
"description": "Distributing designated alerts via SNMP will ensure appropriate management personnel and/or management applications receive the alerts.\n",
|
|
1688
|
+
"severity": "high"
|
|
1689
|
+
},
|
|
1690
|
+
{
|
|
1691
|
+
"id": "V-36286",
|
|
1692
|
+
"title": "For those instances where the organization requires encrypted traffic to be visible to information system monitoring tools, the application transmitting the encrypted traffic must make provisions to allow that traffic to be visible to specific system monitoring.",
|
|
1693
|
+
"description": "There is a recognized need to balance encrypting traffic versus the need to have insight into the traffic from a monitoring perspective. \nRationale for non-applicability: The MDM server traffic between the server and mobile device cannot be monitored. This is a feature of an MDM server.",
|
|
1694
|
+
"severity": "medium"
|
|
1695
|
+
},
|
|
1696
|
+
{
|
|
1697
|
+
"id": "V-36287",
|
|
1698
|
+
"title": "The application must enforce organizational requirements to protect information obtained from intrusion monitoring tools from unauthorized access, modification, and deletion.",
|
|
1699
|
+
"description": "Intrusion monitoring applications are by their nature designed to monitor and record network and system traffic and activity. They can accumulate a significant amount of sensitive data, examples of which could include user account information and application data not related to the intrusion monitoring application itself. \nRationale for non-applicability: The MDM server is not an IDS.",
|
|
1700
|
+
"severity": "medium"
|
|
1701
|
+
},
|
|
1702
|
+
{
|
|
1703
|
+
"id": "V-36288",
|
|
1704
|
+
"title": "The MDM server must provide designated alerts to another enterprise network management application using an IPSec, TLS, or SSL encrypted secure connection.",
|
|
1705
|
+
"description": "Auditing and logging are key components of any security architecture. Centrally managing audit data provides for easier management of mobility events and is an effective facility for monitoring and the automatic generation of alert notification. The repository of audit data can facilitate troubleshooting when problems are encountered and can assist in performing root cause analysis. A repository of audit data can also be correlated in real time to identify suspicious behavior or be archived for review at a later time for research and analysis.\n",
|
|
1706
|
+
"severity": "high"
|
|
1707
|
+
},
|
|
1708
|
+
{
|
|
1709
|
+
"id": "V-36289",
|
|
1710
|
+
"title": "The MDM server must allocate sufficient audit record storage capacity for 7 days of operation.\n",
|
|
1711
|
+
"description": "Centralized management of audit records and logs provides for efficiency in maintenance and management of records, as well as the backup and archiving of those records. If auditing is not comprehensive and managed effectively, including adequate capacity, it will not be useful for intrusion monitoring, security investigations, and forensic analysis. \n",
|
|
1712
|
+
"severity": "medium"
|
|
1713
|
+
},
|
|
1714
|
+
{
|
|
1715
|
+
"id": "V-36290",
|
|
1716
|
+
"title": "The MDM server must send alerts to the administrator or organizations central audit management system when the audit log size reaches an organization defined critical percentage of capacity and full capacity.\n",
|
|
1717
|
+
"description": "MDM server auditing capability is critical for accurate forensic analysis. Alerting administrators when audit log size thresholds are exceeded helps ensure the administrators can respond to heavy activity in a timely manner. Failure to alert increases the probability that an adversary’s actions will go undetected.\n",
|
|
1718
|
+
"severity": "low"
|
|
1719
|
+
},
|
|
1720
|
+
{
|
|
1721
|
+
"id": "V-36291",
|
|
1722
|
+
"title": "Applications providing IDS and prevention capabilities must prevent non-privileged users from circumventing intrusion detection and prevention capabilities.",
|
|
1723
|
+
"description": "Any application providing intrusion detection and prevention capabilities must be architected and implemented so as to prevent non-privileged users from circumventing such protections. This can be accomplished through the use of user roles, use of proper systems permissions, auditing, logging, etc.\nRationale for non-applicability: The MDM server is not an IDS.",
|
|
1724
|
+
"severity": "medium"
|
|
1725
|
+
},
|
|
1726
|
+
{
|
|
1727
|
+
"id": "V-36292",
|
|
1728
|
+
"title": "The MDM server Sever must alert designated organizational officials in the event of an audit processing failure.\n",
|
|
1729
|
+
"description": "It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Audit processing failures include, software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. If audit processing failure occurs, forensic analysis or detection may not be possible. ",
|
|
1730
|
+
"severity": "low"
|
|
1731
|
+
},
|
|
1732
|
+
{
|
|
1733
|
+
"id": "V-36293",
|
|
1734
|
+
"title": "Applications providing malware and/or firewall protection must monitor inbound and outbound communications for unauthorized activities or conditions.",
|
|
1735
|
+
"description": "Unusual/unauthorized activities or conditions include internal traffic indicating the presence of malicious code within an information system or propagating among system components, the unauthorized export of information, or signaling to an external information system. \nRationale for non-applicability: The MDM server is not a firewall.",
|
|
1736
|
+
"severity": "medium"
|
|
1737
|
+
},
|
|
1738
|
+
{
|
|
1739
|
+
"id": "V-36294",
|
|
1740
|
+
"title": "The MDM server must overwrite the oldest audit log entries when audit logs reach capacity.\n",
|
|
1741
|
+
"description": "It is critical that when a system is at risk of failing to process audit logs as required, it detects and takes action to mitigate the failure. Overwriting the oldest audit log entries is the safest course of action in the context of the limited resources available on a mobile device that may not have network connectivity.\n",
|
|
1742
|
+
"severity": "low"
|
|
1743
|
+
},
|
|
1744
|
+
{
|
|
1745
|
+
"id": "V-36295",
|
|
1746
|
+
"title": "Intrusion detection software must be able to interconnect using standard protocols to create a system wide intrusion detection system.",
|
|
1747
|
+
"description": "When utilizing intrusion detection software, monitoring components are usually dispersed throughout the network, such as, when utilizing HIDS and multiple NIDS sensors. In order to leverage the capabilities of intrusion detection systems to get a complete overall view of network and host activity, these separate components must be able to report and react to activity they detect. \nRationale for non-applicability: The MDM server is not an IDS.",
|
|
1748
|
+
"severity": "medium"
|
|
1749
|
+
},
|
|
1750
|
+
{
|
|
1751
|
+
"id": "V-36296",
|
|
1752
|
+
"title": "The MDM server must provide a warning when allocated audit record storage volume reaches an organization defined percentage of maximum audit record storage capacity.\n",
|
|
1753
|
+
"description": "It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs when storage capacity is reached. Notification of the storage condition will allow administrators to take actions so that logs are not lost.",
|
|
1754
|
+
"severity": "low"
|
|
1755
|
+
},
|
|
1756
|
+
{
|
|
1757
|
+
"id": "V-36297",
|
|
1758
|
+
"title": "Malicious code protection applications must update malicious code protection mechanisms only when directed by a privileged user.",
|
|
1759
|
+
"description": "Malicious code protection software must be protected to prevent a non-privileged user or malicious piece of software from manipulating the protection update mechanism. \nRationale for non-applicability: The MDM server does not perform traditional signature based malware scanning.",
|
|
1760
|
+
"severity": "medium"
|
|
1761
|
+
},
|
|
1762
|
+
{
|
|
1763
|
+
"id": "V-36298",
|
|
1764
|
+
"title": "The application must prevent non-privileged users from circumventing malicious code protection capabilities.",
|
|
1765
|
+
"description": "Malicious code protection software must be protected so as to prevent a non-privileged user or malicious piece of software from disabling the protection mechanism. A common tactic of malware is to identify the type of malicious code protection software running on the system and deactivate it. Malicious code includes viruses, worms, Trojan horses, and Spyware. \nRationale for non-applicability: The MDM server should only be accessed by authorized administrators, which means that non-privileged accounts will not be present.",
|
|
1766
|
+
"severity": "medium"
|
|
1767
|
+
},
|
|
1768
|
+
{
|
|
1769
|
+
"id": "V-36299",
|
|
1770
|
+
"title": "The MDM server must provide a real-time alert when organization defined audit failure events occur.\n",
|
|
1771
|
+
"description": "It is critical for the appropriate personnel to be aware if a system is at risk of failing due to an audit failure event. Notification of the event will allow administrators to take actions so logs are not lost.",
|
|
1772
|
+
"severity": "low"
|
|
1773
|
+
},
|
|
1774
|
+
{
|
|
1775
|
+
"id": "V-36300",
|
|
1776
|
+
"title": "The application must automatically update malicious code protection mechanisms, including signature definitions. Examples include anti-virus signatures and malware data files employed to identify and/or block malicious software from executing.",
|
|
1777
|
+
"description": "Anti-virus and malicious software detection applications utilize signature definitions in order to identify viruses and other malicious software. These signature definitions need to be constantly updated in order to identify the new threats that are discovered every day. All anti-virus and malware software shall come with an update mechanism that automatically updates these signatures. The organization (including any contractor to the organization) is required to promptly install security-relevant malicious code protection software updates (e.g., anti-virus signature updates and hot fixes). Malicious code includes, viruses, worms, Trojan horses, and Spyware. \nRationale for non-applicability: The MDM server does not perform traditional signature based malware scanning.",
|
|
1778
|
+
"severity": "medium"
|
|
1779
|
+
},
|
|
1780
|
+
{
|
|
1781
|
+
"id": "V-36301",
|
|
1782
|
+
"title": "Applications providing malicious code protection must support organizational requirements to configure malicious code protection mechanisms to perform real-time scans of files from external sources as the files are downloaded, opened, or executed in accordance with organizational security policy.\n",
|
|
1783
|
+
"description": "Malicious code protection mechanisms include but are not limited to anti-virus and malware detection software. In order to minimize potential negative impact to the organization that can be caused by malicious code, it is imperative that malicious code is identified and eradicated. \nRationale for non-applicability: The MDM server does not perform malware scanning of downloaded files on managed mobile devices.",
|
|
1784
|
+
"severity": "medium"
|
|
1785
|
+
},
|
|
1786
|
+
{
|
|
1787
|
+
"id": "V-36302",
|
|
1788
|
+
"title": "The MDM server must utilize the integration of audit review, analysis, and reporting processes by an organizations central audit management system to support organizational processes for investigation and response to suspicious activities.\n",
|
|
1789
|
+
"description": "Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is being done, what attempted to be done, where it was done, when it was done, and by whom in order to compile an accurate collection of data for troubleshooting, forensics, etc. Logging the actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or to simply identify an improperly configured network element. In order to determine what is happening within the network infrastructure or to resolve and trace an attack, it is imperative to correlate the log data from multiple network elements to acquire a clear understanding as to what happened or is happening. Collecting log data and presenting that data in a single, consolidated view achieves this objective.",
|
|
1790
|
+
"severity": "low"
|
|
1791
|
+
},
|
|
1792
|
+
{
|
|
1793
|
+
"id": "V-36303",
|
|
1794
|
+
"title": "The MDM server must centralize the review and analysis of audit records from multiple components within the server.\n",
|
|
1795
|
+
"description": "Due to the numerous functions a MDM server implementation processes, log files can become extremely large because of the volume of data. The more processes that are logged, more log data is collected. This can become very difficult to analyze manually; therefore, it is important to process them automatically and tailor the views of the data to only those events of interest based upon selectable criteria. Without the automation of log processing, based upon events of interest to security personnel, log files will not be viewed accurately and actions will not be taken when a significant event occurs on the system because it can be too overwhelming. Significant or meaningful events may be missed due to the sheer volume of data if logs are reviewed manually. Reducing the auditing capability to only those events that are significant aids in supporting near real-time audit review and analysis requirements and after-the-fact investigations of security incidents. ",
|
|
1796
|
+
"severity": "medium"
|
|
1797
|
+
},
|
|
1798
|
+
{
|
|
1799
|
+
"id": "V-36304",
|
|
1800
|
+
"title": "Applications providing malicious code protection must support organizational requirements to update malicious code protection mechanisms (including signature definitions) whenever new releases are available in accordance with organizational configuration management policy and procedures.",
|
|
1801
|
+
"description": "Malicious code protection mechanisms include, but are not limited to, anti-virus and malware detection software. In order to minimize potential negative impact to the organization caused by malicious code, it is imperative that malicious code is identified and eradicated. \nRationale for non-applicability: The MDM server does not perform traditional signature based malware scanning.",
|
|
1802
|
+
"severity": "medium"
|
|
1803
|
+
},
|
|
1804
|
+
{
|
|
1805
|
+
"id": "V-36305",
|
|
1806
|
+
"title": "The MDM server must support an audit reduction capability.\n",
|
|
1807
|
+
"description": "Audit reduction is used to reduce the volume of audit records in order to facilitate manual review. Before a security review information systems and/or applications with an audit reduction capability may remove many audit records known to have little security significance. \n",
|
|
1808
|
+
"severity": "low"
|
|
1809
|
+
},
|
|
1810
|
+
{
|
|
1811
|
+
"id": "V-36306",
|
|
1812
|
+
"title": "Applications required to be non-modifiable must support organizational requirements to provide components that contain no writeable storage capability. These components must be persistent across restart and/or power on/off.",
|
|
1813
|
+
"description": "Organizations may require applications or application components to be non-modifiable or to be stored and executed on non-writeable storage. Use of non-modifiable storage ensures the integrity of the software program from the point of creation of the read-only image and eliminates the possibility of malicious code insertion. \nRationale for non-applicability: The MDM server must be capable of being updated with patches at any time, and therefore must be modifiable.",
|
|
1814
|
+
"severity": "medium"
|
|
1815
|
+
},
|
|
1816
|
+
{
|
|
1817
|
+
"id": "V-36307",
|
|
1818
|
+
"title": "The MDM server audit records must be able to be used by a report generation capability.\n",
|
|
1819
|
+
"description": "Due to the numerous functions a MDM server implementation processes, log files can become extremely large because of the volume of data. The more processes that are logged, more log data is collected. This can become very difficult to analyze manually; therefore, it is important to process them automatically, tailor the views of the data to only those events of interest based upon selectable criteria, and provide a report generation capability. Without the automation of log processing, based upon events of interest to security personnel, log files will not be viewed accurately and actions will not be taken when a significant event occurs on the system because it can be too overwhelming. Significant or meaningful events may be missed due to the sheer volume of data if logs are reviewed or generated manually. Reducing the auditing capability to only those events that are significant and providing a report generation capability, aids in supporting near real-time audit review and analysis requirements and after-the-fact investigations of security incidents. \n\nIn order to identify and report on what (repetitive) data has been removed via the use of audit reduction, the MDM server implementation must provide a capability to generate reports containing what values were removed by the audit reduction. This capability within the MDM server implementation may utilize a component outside of the MDM server itself.",
|
|
1820
|
+
"severity": "low"
|
|
1821
|
+
},
|
|
1822
|
+
{
|
|
1823
|
+
"id": "V-36308",
|
|
1824
|
+
"title": "The MDM server must automatically process audit records for events of interest based upon selectable, event criteria.\n",
|
|
1825
|
+
"description": "Due to the numerous functions a MDM server implementation processes, log files can become extremely large because of the volume of data. The more processes that are logged, more log data is collected. This can become very difficult to analyze manually; therefore, it is important to process them automatically and tailor the views of the data to only those events of interest based upon selectable criteria. Without the automation of log processing, based upon events of interest to security personnel, log files will not be viewed accurately and actions will not be taken when a significant event occurs on the system because it can be too overwhelming. Significant or meaningful events may be missed due to the sheer volume of data if logs are reviewed manually.",
|
|
1826
|
+
"severity": "low"
|
|
1827
|
+
},
|
|
1828
|
+
{
|
|
1829
|
+
"id": "V-36309",
|
|
1830
|
+
"title": "Applications must support organizationally-defined requirements to load and execute from hardware-enforced, read-only media.",
|
|
1831
|
+
"description": "Use of non-modifiable storage ensures the integrity of the software program from the point of creation of the read-only image. Organizations may require the information system to load specified applications from hardware enforced read-only media. Hardware-enforced, read-only media include, CD-R/DVD-R disk drives. \nRationale for non-applicability: This requirement is better covered by the operating system.",
|
|
1832
|
+
"severity": "medium"
|
|
1833
|
+
},
|
|
1834
|
+
{
|
|
1835
|
+
"id": "V-36310",
|
|
1836
|
+
"title": "The MDM server must use internal system clocks to generate timestamps for audit records.\n",
|
|
1837
|
+
"description": "Determining the correct time a particular event occurred within the MDM server architecture is critical when conducting forensic analysis and investigating system events. Without the use of an approved and synchronized time source, configured on the systems, events cannot be accurately correlated and analyzed to determine what is transpiring within the MDM server. If an event has been triggered on the network, and the MDM server is not configured with the correct time, the event may be seen as insignificant, when in reality the events are related and may have a larger impact across the network. Synchronization of system clocks is needed in order to correctly correlate the timing of events that occur across multiple systems. Determining the correct time a particular event occurred on a system, via timestamps, is critical when conducting forensic analysis and investigating system events. ",
|
|
1838
|
+
"severity": "low"
|
|
1839
|
+
},
|
|
1840
|
+
{
|
|
1841
|
+
"id": "V-36311",
|
|
1842
|
+
"title": "Applications must, for organization defined information system components, load and execute the operating environment from hardware-enforced, read-only media.",
|
|
1843
|
+
"description": "Organizations may require the information system to load the operating environment from hardware enforced read-only media. The term operating environment is defined as the code upon which applications are hosted, for example, a monitor, executive, operating system, or application running directly on the hardware platform. \nRationale for non-applicability: This requirement is better covered by the operating system.",
|
|
1844
|
+
"severity": "medium"
|
|
1845
|
+
},
|
|
1846
|
+
{
|
|
1847
|
+
"id": "V-36312",
|
|
1848
|
+
"title": "The MDM server must synchronize internal information system clocks with United States Naval Observatory (USNO or other DoD-approved) time servers at least once every 24 hours.\n",
|
|
1849
|
+
"description": "Determining the correct time a particular application event occurred on a system is critical when conducting forensic analysis and investigating system events. Periodically synchronizing internal clocks with an authoritative time source helps ensure time is synchronized across the enterprise. The USNO time servers provide accurate time and are recommended. This synchronization facilitates event correlation and increases the likelihood that the scope and severity of an IA incident will be fully understood, thereby enabling an effective response to the incident. \n",
|
|
1850
|
+
"severity": "low"
|
|
1851
|
+
},
|
|
1852
|
+
{
|
|
1853
|
+
"id": "V-36313",
|
|
1854
|
+
"title": "The MDM server must protect audit information from unauthorized read access.\n",
|
|
1855
|
+
"description": "Audit data is considered sensitive, and is intended to be read by the System Administrator only. Allowing non-administrators access to this data could expose vulnerabilities in the system.",
|
|
1856
|
+
"severity": "low"
|
|
1857
|
+
},
|
|
1858
|
+
{
|
|
1859
|
+
"id": "V-36314",
|
|
1860
|
+
"title": "The MDM server must protect audit information from unauthorized modification.\n",
|
|
1861
|
+
"description": "If audit data were to become compromised then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. \n",
|
|
1862
|
+
"severity": "medium"
|
|
1863
|
+
},
|
|
1864
|
+
{
|
|
1865
|
+
"id": "V-36315",
|
|
1866
|
+
"title": "Only a Honey Pot information system and/or application must include components that proactively seek to identify web-based malicious code. Honey Pot systems must be not be shared or used for any other purpose other than described.",
|
|
1867
|
+
"description": "A Honey Pot is an organization designated information system and/or application that includes components specifically designed to be the target of malicious attacks for the purpose of detecting, deflecting, and analyzing such attacks. \nRationale for non-applicability: The MDM server is not a Honey Pot.",
|
|
1868
|
+
"severity": "medium"
|
|
1869
|
+
},
|
|
1870
|
+
{
|
|
1871
|
+
"id": "V-36316",
|
|
1872
|
+
"title": "The MDM server must protect audit information from unauthorized deletion.\n",
|
|
1873
|
+
"description": "If audit data were to become compromised then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. \n",
|
|
1874
|
+
"severity": "medium"
|
|
1875
|
+
},
|
|
1876
|
+
{
|
|
1877
|
+
"id": "V-36317",
|
|
1878
|
+
"title": "The MDM server must provide audit record generation capability for the auditable events defined at the organizational level for defined information system components.\n",
|
|
1879
|
+
"description": "The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records (i.e., auditable events) for example, timestamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked. ",
|
|
1880
|
+
"severity": "low"
|
|
1881
|
+
},
|
|
1882
|
+
{
|
|
1883
|
+
"id": "V-36318",
|
|
1884
|
+
"title": "Applications that collectively provide name/address resolution service for an organization must implement internal/external role separation.",
|
|
1885
|
+
"description": "A Domain Name System (DNS) server is an example of an information system providing name/address resolution service. To eliminate single points of failure and to enhance redundancy, there are typically at least two authoritative domain name system DNS servers, one configured as primary and the other as secondary. \nRationale for non-applicability: The MDM server does not support name/address resolution queries.",
|
|
1886
|
+
"severity": "medium"
|
|
1887
|
+
},
|
|
1888
|
+
{
|
|
1889
|
+
"id": "V-36319",
|
|
1890
|
+
"title": "The MDM server must allow designated administrators to select which auditable events are to be audited by the server.\n",
|
|
1891
|
+
"description": "The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records (i.e., auditable events). Allowing an administrator to choose the events allows for better coverage of logs for specific activities of interest at a specific time.",
|
|
1892
|
+
"severity": "low"
|
|
1893
|
+
},
|
|
1894
|
+
{
|
|
1895
|
+
"id": "V-36320",
|
|
1896
|
+
"title": "The MDM server must generate audit records for the DoD-required auditable events.\n",
|
|
1897
|
+
"description": "The DoD-required auditable events are events that assist in intrusion detection and forensic analysis. Failure to capture them increases the likelihood that an adversary can breach the system without detection.\n",
|
|
1898
|
+
"severity": "low"
|
|
1899
|
+
},
|
|
1900
|
+
{
|
|
1901
|
+
"id": "V-36321",
|
|
1902
|
+
"title": "The application must perform data origin authentication and data integrity verification on all resolution responses received whether or not local client systems explicitly request this service.",
|
|
1903
|
+
"description": "A recursive resolving or caching Domain Name System (DNS) server is an example of an information system providing name/address resolution service for local clients. \nRationale for non-applicability: The MDM server does not support name/address resolution queries.",
|
|
1904
|
+
"severity": "medium"
|
|
1905
|
+
},
|
|
1906
|
+
{
|
|
1907
|
+
"id": "V-36322",
|
|
1908
|
+
"title": "The MDM server must support the capability to compile audit records from multiple components within the server into a system-wide (logical or physical) audit trail that is time-correlated to within an organization defined level of tolerance for the relationship between time stamps of individual records in the audit trail.\n",
|
|
1909
|
+
"description": "Audit generation and audit records can be generated from various components within the MDM server. The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records (i.e., auditable events). \n",
|
|
1910
|
+
"severity": "low"
|
|
1911
|
+
},
|
|
1912
|
+
{
|
|
1913
|
+
"id": "V-36323",
|
|
1914
|
+
"title": "The MDM server must record an event in the device audit log each time the server is started.\n",
|
|
1915
|
+
"description": "Some MDM server system features, including security enforcement, may only be modified when the MDM server applications not running. Logging startup events provides valuable information on system problems and potential MDM server integrity issues.\n",
|
|
1916
|
+
"severity": "low"
|
|
1917
|
+
},
|
|
1918
|
+
{
|
|
1919
|
+
"id": "V-36324",
|
|
1920
|
+
"title": "The application must perform data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources when requested by client systems.\n",
|
|
1921
|
+
"description": "A recursive resolving or caching Domain Name System (DNS) server is an example of an information system providing name/address resolution service for local clients. ",
|
|
1922
|
+
"severity": "medium"
|
|
1923
|
+
},
|
|
1924
|
+
{
|
|
1925
|
+
"id": "V-36325",
|
|
1926
|
+
"title": "The MDM server must record an event in audit log each time the server makes a security relevant configuration change on a managed mobile device.\n",
|
|
1927
|
+
"description": "Any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have significant effects on the overall security of the system. Security-relevant configuration changes, if not authorized, are a breach of system security and might indicate a broader attack is occurring. Recording security-relevant changes in the audit logs mitigates the risk that unauthorized changes will go undetected.\n",
|
|
1928
|
+
"severity": "medium"
|
|
1929
|
+
},
|
|
1930
|
+
{
|
|
1931
|
+
"id": "V-36326",
|
|
1932
|
+
"title": "Applications, when operating as part of a distributed, hierarchical namespace, must provide the means to indicate the security status of child subspaces and (if the child supports secure resolution services) enable verification of a chain of trust among parent and child domains.\n",
|
|
1933
|
+
"description": "This control enables remote clients to obtain origin authentication and integrity verification assurances for the host/service name to network address resolution information obtained through the service.\nRationale for non-applicability: The MDM server does not operate as part of a distributed, hierarchical namespace.",
|
|
1934
|
+
"severity": "medium"
|
|
1935
|
+
},
|
|
1936
|
+
{
|
|
1937
|
+
"id": "V-36327",
|
|
1938
|
+
"title": "The application must provide additional data origin and integrity artifacts along with the authoritative data the system returns in response to name/address resolution queries.",
|
|
1939
|
+
"description": "This control enables remote clients to obtain origin authentication and integrity verification assurances for the host/service name to network address resolution information obtained through the service. \nRationale for non-applicability: The MDM server does not support name/address resolution queries.",
|
|
1940
|
+
"severity": "medium"
|
|
1941
|
+
},
|
|
1942
|
+
{
|
|
1943
|
+
"id": "V-36328",
|
|
1944
|
+
"title": "The MDM server must employ cryptographic mechanisms to protect the integrity and confidentiality for all audit logs managed by the server.\n",
|
|
1945
|
+
"description": "The integrity of server audit logs and managed device audit logs is vital to the security baseline of the server and network. Otherwise, critical audit event information could be compromised.\n",
|
|
1946
|
+
"severity": "medium"
|
|
1947
|
+
},
|
|
1948
|
+
{
|
|
1949
|
+
"id": "V-36329",
|
|
1950
|
+
"title": "Applications designed to enforce policy pertaining to the use of mobile code must prevent the automatic execution of mobile code in organization defined software applications and require organization defined actions prior to executing the code.",
|
|
1951
|
+
"description": "Decisions regarding the employment of mobile code within organizational information systems are based on the potential for the code to cause damage to the system if used maliciously. \nRationale for non-applicability: An MDM server is not designed to enforce policy pertaining to use of mobile code.",
|
|
1952
|
+
"severity": "medium"
|
|
1953
|
+
},
|
|
1954
|
+
{
|
|
1955
|
+
"id": "V-36330",
|
|
1956
|
+
"title": "The MDM server must back up audit records on an organization defined frequency onto a different system or media than the system being audited.\n",
|
|
1957
|
+
"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 organizationally defined frequency helps to assure in the event of a catastrophic system failure, the audit records will be retained.\n",
|
|
1958
|
+
"severity": "medium"
|
|
1959
|
+
},
|
|
1960
|
+
{
|
|
1961
|
+
"id": "V-36331",
|
|
1962
|
+
"title": "The MDM server must protect the audit records resulting from non-local accesses to privileged accounts and the execution of privileged functions.\n",
|
|
1963
|
+
"description": "Protection of audit records and audit data is of critical importance. Care must be taken to ensure privileged users cannot circumvent audit protections put in place. Auditing might not be reliable when performed by an operating system which the user being audited has privileged access to. The privileged user could inhibit auditing or directly modify audit records. To prevent this from occurring, privileged access shall be further defined between audit-related privileges and other privileges, thus, limiting the users with audit-related privileges.",
|
|
1964
|
+
"severity": "medium"
|
|
1965
|
+
},
|
|
1966
|
+
{
|
|
1967
|
+
"id": "V-36332",
|
|
1968
|
+
"title": "Applications designed to enforce policy pertaining to organizational use of mobile code must prevent the download and execution of prohibited mobile code.",
|
|
1969
|
+
"description": "Decisions regarding the employment of mobile code within organizational information systems are based on the potential for the code to cause damage to the system if used maliciously. \nRationale for non-applicability: An MDM server is not designed to enforce policy pertaining to use of mobile code.",
|
|
1970
|
+
"severity": "medium"
|
|
1971
|
+
},
|
|
1972
|
+
{
|
|
1973
|
+
"id": "V-36333",
|
|
1974
|
+
"title": "The MDM server must produce a system-wide (logical or physical) audit trail composed of audit records in a standardized format.\n",
|
|
1975
|
+
"description": "Audits records can be generated from various components within the MDM server. The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records (i.e., auditable events).",
|
|
1976
|
+
"severity": "low"
|
|
1977
|
+
},
|
|
1978
|
+
{
|
|
1979
|
+
"id": "V-36334",
|
|
1980
|
+
"title": "The MDM server must automatically audit administrator account modification.\n",
|
|
1981
|
+
"description": "Once an attacker establishes initial access to a system, they often attempt to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply modify an existing account. Auditing administrator account modification ensures forensic information is available to track these instances.",
|
|
1982
|
+
"severity": "medium"
|
|
1983
|
+
},
|
|
1984
|
+
{
|
|
1985
|
+
"id": "V-36335",
|
|
1986
|
+
"title": "Applications utilizing mobile code must meet policy requirements regarding the acquisition, development, and/or use of mobile code.",
|
|
1987
|
+
"description": "Decisions regarding the employment of mobile code within organizational information systems are based on the potential for the code to cause damage to the system if used maliciously. \nRationale for non-applicability: An MDM server is not designed to enforce policy pertaining to use of mobile code.",
|
|
1988
|
+
"severity": "medium"
|
|
1989
|
+
},
|
|
1990
|
+
{
|
|
1991
|
+
"id": "V-36336",
|
|
1992
|
+
"title": "Software and/or firmware used for collaborative computing devices must prohibit remote activation excluding the organization defined exceptions where remote activation is to be allowed.",
|
|
1993
|
+
"description": "Collaborative computing devices include, networked white boards, cameras, and microphones. Collaborative software examples include instant messaging or chat clients. \nRationale for non-applicability: The MDM server is not a collaborative computing device.",
|
|
1994
|
+
"severity": "medium"
|
|
1995
|
+
},
|
|
1996
|
+
{
|
|
1997
|
+
"id": "V-36337",
|
|
1998
|
+
"title": "The MDM server must automatically audit administrator account termination.\n",
|
|
1999
|
+
"description": "Accounts are utilized for identifying individual application users or for identifying the application processes themselves. When accounts are deleted, a myriad of side effects could occur. The MDM server must audit and notify, as required, to provide a forensic audit trail.\n",
|
|
2000
|
+
"severity": "medium"
|
|
2001
|
+
},
|
|
2002
|
+
{
|
|
2003
|
+
"id": "V-36338",
|
|
2004
|
+
"title": "Applications must employ FIPS-validated cryptography to protect unclassified information when such information must be separated from individuals who have the necessary clearances yet lack the necessary access approvals.",
|
|
2005
|
+
"description": "Cryptography is only as strong as the encryption modules/algorithms employed to encrypt the data. Use of weak or un-tested encryption algorithms undermines the purposes of utilizing encryption to protect data. FIPS 140-2 Security Requirements for Cryptographic Modules can be found at the following web site: http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf.\nRationale for non-applicability: The MDM server does not manage access to data by clearances of administrators.",
|
|
2006
|
+
"severity": "medium"
|
|
2007
|
+
},
|
|
2008
|
+
{
|
|
2009
|
+
"id": "V-36339",
|
|
2010
|
+
"title": "The MDM server must ensure remote sessions for accessing the server by an administrator are audited.\n",
|
|
2011
|
+
"description": "Session auditing activities are developed, integrated, and used in consultation with legal counsel in accordance with applicable federal laws, Executive Orders, directives, policies, or regulations. This allows all aspects of a session to be recreated.\n",
|
|
2012
|
+
"severity": "high"
|
|
2013
|
+
},
|
|
2014
|
+
{
|
|
2015
|
+
"id": "V-36340",
|
|
2016
|
+
"title": "Applications involved in the production, control, and distribution of asymmetric cryptographic keys must use approved PKI Class 3 or class 4 certificates and hardware tokens that protect the users private key.",
|
|
2017
|
+
"description": "Cryptographic key management and establishment can be performed using manual procedures or automated mechanisms with supporting manual procedures. \nRationale for non-applicability: The MDM server is not involved in the production, control, and distribution of asymmetric cryptographic keys.",
|
|
2018
|
+
"severity": "medium"
|
|
2019
|
+
},
|
|
2020
|
+
{
|
|
2021
|
+
"id": "V-36341",
|
|
2022
|
+
"title": "The MDM server must capture/record and log all content related to an administrator session.\n",
|
|
2023
|
+
"description": "Session auditing activities are developed, integrated, and used in consultation with legal counsel in accordance with applicable federal laws, Executive Orders, directives, policies, or regulations. This allows all aspects of a session to be recreated.\n",
|
|
2024
|
+
"severity": "high"
|
|
2025
|
+
},
|
|
2026
|
+
{
|
|
2027
|
+
"id": "V-36342",
|
|
2028
|
+
"title": "The MDM server must initiate session auditing upon start up.\n",
|
|
2029
|
+
"description": "Without session-level auditing, IA and IT professionals do not have the complete picture, in detail, of what is transpiring on their systems. Without the session-level auditing capability, it is difficult to determine when a specific action was taken on the system and perform forensic analysis if there is an attack, or troubleshoot a problem. \n",
|
|
2030
|
+
"severity": "high"
|
|
2031
|
+
},
|
|
2032
|
+
{
|
|
2033
|
+
"id": "V-36343",
|
|
2034
|
+
"title": "The MDM server must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event.\n",
|
|
2035
|
+
"description": "MDM server auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes: timestamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked. \n\nMDM server is capable of a range of actions on data stored within the database. It is important, for accurate forensic analysis, to know exactly who performed a given action. If user identification information is not recorded and stored with the audit record, the record itself is of very limited use.",
|
|
2036
|
+
"severity": "high"
|
|
2037
|
+
},
|
|
2038
|
+
{
|
|
2039
|
+
"id": "V-36344",
|
|
2040
|
+
"title": "The MDM server must protect audit tools from unauthorized access.\n",
|
|
2041
|
+
"description": "Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Depending upon the log format and application, system and application log tools may provide the only means to manipulate and manage application and system log data. It is, therefore, imperative that access to audit tools be controlled and protected from unauthorized access. If an attacker were to access audit tools he could analyze audit logs for system weaknesses or weaknesses in the auditing itself. An attacker could also manipulate logs to hide evidence of malicious activity.\n",
|
|
2042
|
+
"severity": "high"
|
|
2043
|
+
},
|
|
2044
|
+
{
|
|
2045
|
+
"id": "V-36345",
|
|
2046
|
+
"title": "Boundary protection applications must fail securely in the event of an operational failure.",
|
|
2047
|
+
"description": "Fail secure is a condition achieved by the application of a set of information system mechanisms to ensure that in the event of an operational failure of a boundary protection device at a managed interface (e.g., router, firewall, guard, application gateway residing on a protected sub network commonly referred to as a demilitarized zone), the system does not enter into an unsecure state where intended security properties no longer hold. A failure of a boundary protection device cannot lead to, or cause information external to the boundary protection device to enter the device, nor can a failure permit unauthorized information release.\nRationale for non-applicability: The MDM server is not a boundary protection application.",
|
|
2048
|
+
"severity": "medium"
|
|
2049
|
+
},
|
|
2050
|
+
{
|
|
2051
|
+
"id": "V-36346",
|
|
2052
|
+
"title": "The MDM server must protect audit tools from unauthorized modification.\n",
|
|
2053
|
+
"description": "Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Depending upon the log format and application, system and application log tools may provide the only means to manipulate and manage application and system log data. It is, therefore, imperative that access to audit tools be controlled and protected from unauthorized modification. If an attacker were to modify audit tools he could analyze audit logs for system weaknesses or weaknesses in the auditing itself. An attacker could also manipulate logs to hide evidence of malicious activity.\n",
|
|
2054
|
+
"severity": "high"
|
|
2055
|
+
},
|
|
2056
|
+
{
|
|
2057
|
+
"id": "V-36347",
|
|
2058
|
+
"title": "The MDM server must protect audit tools from unauthorized deletion.\n",
|
|
2059
|
+
"description": "Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Depending upon the log format and application, system and application log tools may provide the only means to manipulate and manage application and system log data. It is, therefore, imperative that access to audit tools be controlled and protected from unauthorized deletion. If an attacker were to delete audit tools MDM server administrator may have no way of managing or viewing the logs.",
|
|
2060
|
+
"severity": "high"
|
|
2061
|
+
},
|
|
2062
|
+
{
|
|
2063
|
+
"id": "V-36348",
|
|
2064
|
+
"title": "Applications designed to enforce protocol formats must employ automated mechanisms to enforce strict adherence to protocol format.",
|
|
2065
|
+
"description": "Automated mechanisms used to enforce protocol formats include, deep packet inspection firewalls and XML gateways. These devices verify adherence to the protocol specification (e.g., IEEE) at the application layer and serve to identify significant vulnerabilities that cannot be detected by devices operating at the network or transport layer. It is impractical to expect protocol format inspection to be conducted manually.\nRationale for non-applicability: The MDM server is not designed to enforce protocol formats. ",
|
|
2066
|
+
"severity": "medium"
|
|
2067
|
+
},
|
|
2068
|
+
{
|
|
2069
|
+
"id": "V-36349",
|
|
2070
|
+
"title": "The MDM server must use cryptographic mechanisms to protect the integrity of audit tools.\n",
|
|
2071
|
+
"description": "Auditing and logging are key components of any security architecture. It is essential security personnel know what is being done, what attempted to be done, where it was done, when it was done, and by whom in order to compile an accurate risk assessment. Cryptographic mechanisms must be used to protect the integrity of the audit tools used for audit reduction and reporting.\n",
|
|
2072
|
+
"severity": "high"
|
|
2073
|
+
},
|
|
2074
|
+
{
|
|
2075
|
+
"id": "V-36350",
|
|
2076
|
+
"title": "The MDM server must provide transaction recovery to avoid disabling the CMD in the event of an incomplete policy push.\n",
|
|
2077
|
+
"description": "Since the MDM server controls many mobile devices as well as serving as a gateway into the network infrastructure, the absence of this feature could also enable an adversary to launch an enterprise-wide DoS attack.\n",
|
|
2078
|
+
"severity": "high"
|
|
2079
|
+
},
|
|
2080
|
+
{
|
|
2081
|
+
"id": "V-36351",
|
|
2082
|
+
"title": "Boundary protection applications must prevent discovery of specific system components (or devices) composing a managed interface.",
|
|
2083
|
+
"description": "Firewall control requirement for isolating and preventing the discovery of management interfaces. This control enhancement is intended to protect the network addresses of information system components that are part of the managed interface from discovery through common tools and techniques used to identify devices on a network.\nRationale for non-applicability: The MDM server is not a boundary protection application.",
|
|
2084
|
+
"severity": "medium"
|
|
2085
|
+
},
|
|
2086
|
+
{
|
|
2087
|
+
"id": "V-36352",
|
|
2088
|
+
"title": "The MDM server must separate the security functions between the management of the server itself, and the management of the mobile device.\n",
|
|
2089
|
+
"description": "Security functions are defined as \"the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based.\" If the security functions were to be undermined, the MDM server could be compromised. \n\nMDM server administrators can increase the assurance in security functions by employing well-defined security policy models, structured, disciplined, and rigorous hardware and software development techniques, and sound system/security engineering principles. The MDM server element must isolate security functions from non-security functions by means of an isolation boundary (implemented via partitions and domains) controlling access to and protecting the integrity of, the hardware, software, and firmware performing those security functions. The MDM server must maintain a separate execution domain (e.g., address space) for each executing process. ",
|
|
2090
|
+
"severity": "low"
|
|
2091
|
+
},
|
|
2092
|
+
{
|
|
2093
|
+
"id": "V-36353",
|
|
2094
|
+
"title": "Applications functioning in the capacity of a firewall must check incoming communications to ensure the communications are coming from an authorized source and routed to an authorized destination.",
|
|
2095
|
+
"description": "In regards to boundary controls such as routers and firewalls, examples of restricting and prohibiting communications are: restricting external web traffic only to organizational web servers within managed interfaces and prohibiting external traffic that appears to be spoofing an internal address as the source. \nRationale for non-applicability: The MDM server is not a firewall.",
|
|
2096
|
+
"severity": "medium"
|
|
2097
|
+
},
|
|
2098
|
+
{
|
|
2099
|
+
"id": "V-36354",
|
|
2100
|
+
"title": "The MDM server must establish a trusted communications path between the Administrator and the systems authentication mechanism.\n",
|
|
2101
|
+
"description": "Without a trusted communication path, the MDM server is vulnerable to a man in the middle attack.\n",
|
|
2102
|
+
"severity": "medium"
|
|
2103
|
+
},
|
|
2104
|
+
{
|
|
2105
|
+
"id": "V-36355",
|
|
2106
|
+
"title": "The MDM server application must generate a unique session identifier for each session.\n",
|
|
2107
|
+
"description": "This requirement focuses on communications protection at the application session, versus network packet level. The intent of this control is to establish grounds for confidence at each end of a communications session in the ongoing identity of the other party and in the validity of the information being transmitted. This helps prevent a session hijacking attack.\n",
|
|
2108
|
+
"severity": "low"
|
|
2109
|
+
},
|
|
2110
|
+
{
|
|
2111
|
+
"id": "V-36356",
|
|
2112
|
+
"title": "The MDM server application must generate unique session identifiers with organization defined randomness requirements.\n",
|
|
2113
|
+
"description": "This requirement focuses on communications protection at the application session, versus network packet level. The intent of this control is to establish grounds for confidence at each end of a communications session in the ongoing identity of the other party and in the validity of the information being transmitted. This helps prevent a session hijacking attack.\n",
|
|
2114
|
+
"severity": "low"
|
|
2115
|
+
},
|
|
2116
|
+
{
|
|
2117
|
+
"id": "V-36357",
|
|
2118
|
+
"title": "The MDM server must respond to security function anomalies in accordance with organization defined responses and alternative action(s).\n",
|
|
2119
|
+
"description": "The MDM server is the collection point for many of the security function anomalies both for the mobile devices it manages, as well as the MDM server application itself. Without response to anomalies, would be attackers would not be noticed once in the MDM server.\n",
|
|
2120
|
+
"severity": "low"
|
|
2121
|
+
},
|
|
2122
|
+
{
|
|
2123
|
+
"id": "V-36358",
|
|
2124
|
+
"title": "Applications performing extrusion detection must be capable of denying network traffic and auditing internal users (or malicious code) posing a threat to external information systems.",
|
|
2125
|
+
"description": "Detecting internal actions that may pose a security threat to external information systems is sometimes termed extrusion detection. Extrusion detection at the information system boundary includes the analysis of network traffic (incoming as well as, outgoing) looking for indications of an internal threat to the security of external systems.\nRationale for non-applicability: The MDM server is not an IDS.",
|
|
2126
|
+
"severity": "medium"
|
|
2127
|
+
},
|
|
2128
|
+
{
|
|
2129
|
+
"id": "V-36359",
|
|
2130
|
+
"title": "The MDM server application must recognize only system-generated session identifiers.\n",
|
|
2131
|
+
"description": "This requirement focuses on communications protection at the application session, versus network packet level. The intent of this control is to establish grounds for confidence at each end of a communications session in the ongoing identity of the other party and in the validity of the information being transmitted. Without this, session hijacking attacks could be possible.\n",
|
|
2132
|
+
"severity": "low"
|
|
2133
|
+
},
|
|
2134
|
+
{
|
|
2135
|
+
"id": "V-36360",
|
|
2136
|
+
"title": "Proxy applications must support logging individual Transmission Control Protocol (TCP) sessions and blocking specific Uniform Resource Locators (URLs), domain names, and Internet Protocol (IP) addresses. Proxy applications must also be configurable with organization defined lists of authorized and unauthorized websites.\n",
|
|
2137
|
+
"description": "External networks are networks outside the control of the organization. Proxy servers support logging individual Transmission Control Protocol (TCP) sessions and blocking specific Uniform Resource Locators (URLs), domain names, and Internet Protocol (IP) addresses. Proxy servers are also configurable with organization defined lists of authorized and unauthorized websites.\nRationale for non-applicability: The MDM server is not an Internet proxy application.",
|
|
2138
|
+
"severity": "medium"
|
|
2139
|
+
},
|
|
2140
|
+
{
|
|
2141
|
+
"id": "V-36361",
|
|
2142
|
+
"title": "The MDM server must not enable information system functionality providing the capability for automatic execution of code on mobile devices without user direction.\n",
|
|
2143
|
+
"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 server 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. Allowing automatic execution of code without user interaction could result in malware executing itself on a CMD.\n",
|
|
2144
|
+
"severity": "medium"
|
|
2145
|
+
},
|
|
2146
|
+
{
|
|
2147
|
+
"id": "V-36362",
|
|
2148
|
+
"title": "Applications providing remote connectivity must prevent remote devices that have established a non-remote connection with the system from communicating outside of the communications path with resources in external networks.",
|
|
2149
|
+
"description": "This control enhancement is implemented within the remote device (e.g., notebook/laptop computer) via configuration settings that are not configurable by the user of that device. An example of a non-remote communications path from a remote device is a virtual private network. When a non-remote connection is established using a virtual private network, the configuration settings prevent split-tunneling. Split-tunneling might otherwise be used by remote users to communicate with the information system as an extension of that system and to communicate with local resources such as, a printer or file server. Since the remote device, when connected by a non-remote connection, becomes an extension of the information system, allowing dual communications paths such as split-tunneling would be, in effect, allowing unauthorized external connections into the system.\nRationale for non-applicability: The MDM server does not allow remote connecting mobile devices to establish non-remote connections.",
|
|
2150
|
+
"severity": "medium"
|
|
2151
|
+
},
|
|
2152
|
+
{
|
|
2153
|
+
"id": "V-36363",
|
|
2154
|
+
"title": "The MDM server must be able to disable services that are not required by site-defined functions.\n",
|
|
2155
|
+
"description": "Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). Unneeded services and processes provide additional threat vectors and avenues of attack to the information system.",
|
|
2156
|
+
"severity": "medium"
|
|
2157
|
+
},
|
|
2158
|
+
{
|
|
2159
|
+
"id": "V-36364",
|
|
2160
|
+
"title": "Any software application designed to function as a firewall must be capable employing a default deny all configuration.",
|
|
2161
|
+
"description": "A firewall default deny is a firewall configuration setting that will force the administrator to explicitly allow network or application traffic rather than allowing all traffic by default. The purpose is to prevent unmanaged access into the internal network or in the case of an application firewall, to application content, features, or functionality. \nRationale for non-applicability: The MDM server is not a firewall.",
|
|
2162
|
+
"severity": "medium"
|
|
2163
|
+
},
|
|
2164
|
+
{
|
|
2165
|
+
"id": "V-36365",
|
|
2166
|
+
"title": "The master AES encryption key used to encrypt data between the MDM server and the agent on the mobile device must be rotated. \n",
|
|
2167
|
+
"description": "There are two primary methods for generating the encryption key used to encrypt data between the management server and the server agent installed on the mobile device. The first method is to use a shared secret and the second is to generate the master encryption key based on PKI key generation. When a shared secret is used, if the master encryption key is not rotated periodically, and it is compromised, all future data sent between the mobile management server and the agent located on the mobile device would be compromised. Limit the compromise to an organizationally defined period is a security best practice. This is typically 30 days or less.\n",
|
|
2168
|
+
"severity": "medium"
|
|
2169
|
+
},
|
|
2170
|
+
{
|
|
2171
|
+
"id": "V-36366",
|
|
2172
|
+
"title": "The MDM server, when used for non-local maintenance sessions, must protect those sessions through the use of a strong authenticator tightly bound to the user.\n",
|
|
2173
|
+
"description": "Non-local maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal network.\n",
|
|
2174
|
+
"severity": "medium"
|
|
2175
|
+
},
|
|
2176
|
+
{
|
|
2177
|
+
"id": "V-36367",
|
|
2178
|
+
"title": "Boundary protection applications must be capable of preventing public access into the organizations internal networks except as appropriately mediated by managed interfaces.",
|
|
2179
|
+
"description": "Access into an organization's internal network and to key internal boundaries must be tightly controlled and managed. Applications monitoring and/or controlling communications at the external boundary of the system and at key internal boundaries must be capable of preventing public access into the organization’s internal networks except as appropriately mediated by managed interfaces. \nRationale for non-applicability: The MDM server is not a boundary protection application.",
|
|
2180
|
+
"severity": "medium"
|
|
2181
|
+
},
|
|
2182
|
+
{
|
|
2183
|
+
"id": "V-36368",
|
|
2184
|
+
"title": "Applications must limit the use of resources by priority and not impede the host from servicing processes designated as a higher-priority.",
|
|
2185
|
+
"description": "Priority protection helps prevent a lower-priority process from delaying or interfering with the information system servicing any higher-priority process. This control does not apply to components in the information system for which there is only a single user/role. The application must limit the use of resources by priority.\nRationale for non-applicability: This is better addressed through infrastructure design (multiple load balancing servers) rather than SRG application design.",
|
|
2186
|
+
"severity": "medium"
|
|
2187
|
+
},
|
|
2188
|
+
{
|
|
2189
|
+
"id": "V-36370",
|
|
2190
|
+
"title": "Applications must manage excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of Denial of Service (DoS) attacks.",
|
|
2191
|
+
"description": "In the case of application DoS attacks, care must be taken when designing the application so as to ensure that the application makes the best use of system resources. SQL queries have the potential to consume large amounts of CPU cycles if they are not tuned for optimal performance. Web services containing complex calculations requiring large amounts of time to complete can bog down if too many requests for the service are encountered within a short period of time. \nRationale for non-applicability: The MDM server is not responsible for actively protecting against traditional DoS attacks.",
|
|
2192
|
+
"severity": "medium"
|
|
2193
|
+
},
|
|
2194
|
+
{
|
|
2195
|
+
"id": "V-36371",
|
|
2196
|
+
"title": "Web services applications establishing identities at run-time for previously unknown entities must dynamically manage identifiers, attributes, and associated access authorizations.\n",
|
|
2197
|
+
"description": "Web services are web applications providing a method of communication between two or more different electronic devices. They are normally used by applications to provide each other with data. \nRationale for non-applicability: The MDM server is not an SOA based application.",
|
|
2198
|
+
"severity": "medium"
|
|
2199
|
+
},
|
|
2200
|
+
{
|
|
2201
|
+
"id": "V-36372",
|
|
2202
|
+
"title": "Applications must restrict the ability of users to launch Denial of Service (DoS) attacks against other information systems or networks.",
|
|
2203
|
+
"description": "When it comes to DoS attacks most of the attention is paid to ensuring that systems and applications are not victims of these attacks. \nRationale for non-applicability: This function is better allocated to the operating system.",
|
|
2204
|
+
"severity": "medium"
|
|
2205
|
+
},
|
|
2206
|
+
{
|
|
2207
|
+
"id": "V-36373",
|
|
2208
|
+
"title": "The application must provide a mechanism to automatically terminate accounts designated as temporary or emergency accounts after an organization defined time period.\n",
|
|
2209
|
+
"description": "Temporary application accounts could ostensibly be used in the event of a vendor support visit where a support representative requires a temporary unique account in order to perform diagnostic testing or conduct some other support related activity. When these types of accounts are created, there is a risk that the temporary account may remain in place and active after the support representative has left. \nRationale for non-applicability: There are no temporary administrator accounts on an MDM server. This feature is handled by the operating system.",
|
|
2210
|
+
"severity": "medium"
|
|
2211
|
+
},
|
|
2212
|
+
{
|
|
2213
|
+
"id": "V-36374",
|
|
2214
|
+
"title": "Service Oriented Architecture (SOA) based applications must dynamically manage user privileges and associated access authorizations.\n",
|
|
2215
|
+
"description": "Web services are web applications providing a method of communication between two or more different electronic devices. They are normally used by applications to provide each other with data. \nRationale for non-applicability: The MDM server is not an SOA based application.",
|
|
2216
|
+
"severity": "medium"
|
|
2217
|
+
},
|
|
2218
|
+
{
|
|
2219
|
+
"id": "V-36375",
|
|
2220
|
+
"title": "Applications must protect against or limit the effects of the organization defined or referenced types of Denial of Service (DoS) attacks.",
|
|
2221
|
+
"description": "A variety of technologies exist to limit, or in some cases, eliminate the effects of DoS attacks. For example, boundary protection devices can filter certain types of packets to protect devices on an organization’s internal network from being directly affected by DoS attacks. \nRationale for non-applicability: This function is better allocated to the operating system.",
|
|
2222
|
+
"severity": "medium"
|
|
2223
|
+
},
|
|
2224
|
+
{
|
|
2225
|
+
"id": "V-36376",
|
|
2226
|
+
"title": "The application must enforce dual authorization, based on organizational policies and procedures for organization defined privileged commands.\n",
|
|
2227
|
+
"description": "Dual authorization requires 2 distinct approving authorities to approve the use of an application command prior to it being invoked. This capability is typically reserved for specific application functionality where the application owner, data owner or organization requires an additional assurance that certain application commands are only invoked under the utmost authority. When a policy is defined stating that certain commands contained within an application require dual-authorization before they may be invoked, or when an organization defines a set of application related privileged commands requiring dual authorization, the application must support those requirements. \nRationale for non-applicability: The IA posture of the MDM server does not warrant dual authorization, and is therefore out of scope for this version of the MDM SRG.",
|
|
2228
|
+
"severity": "medium"
|
|
2229
|
+
},
|
|
2230
|
+
{
|
|
2231
|
+
"id": "V-36377",
|
|
2232
|
+
"title": "Applications must not share resources used to interface with systems operating at different security levels.",
|
|
2233
|
+
"description": "The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current user/role (or current process) that obtains access to a shared system resource (e.g., registers, main memory, secondary storage) after the resource has been released back to the information system. Shared resources include, memory, input/output queues, and network interface cards. \nRationale for non-applicability: Multi-level security is out of the scope of this SRG.",
|
|
2234
|
+
"severity": "medium"
|
|
2235
|
+
},
|
|
2236
|
+
{
|
|
2237
|
+
"id": "V-36378",
|
|
2238
|
+
"title": "Applications must enforce non-discretionary access control policies over users and resources where the policy rule set for each policy specifies: access control information (i.e., attributes) employed by the policy rule set (e.g., position, nationality, age, project, time of day).\n",
|
|
2239
|
+
"description": "Access control policies (e.g., identity-based policies, role-based policies, attribute-based policies) and access enforcement mechanisms (e.g., access control lists, access control matrices, cryptography) are employed to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, domains). \nRationale for non-applicability: This control primarily applies to the discretionary sharing of information resources by data owners. This type of service is unrelated to MDM server functionality.",
|
|
2240
|
+
"severity": "medium"
|
|
2241
|
+
},
|
|
2242
|
+
{
|
|
2243
|
+
"id": "V-36379",
|
|
2244
|
+
"title": "Applications must meet organizational requirements to implement an information system isolation boundary that minimizes the number of non-security functions included within the boundary containing security functions.",
|
|
2245
|
+
"description": "The information system isolates security functions from non-security functions by means of an isolation boundary (implemented via partitions and domains) controlling access to and protecting the integrity of, the hardware, software, and firmware that perform those security functions. The information system maintains a separate execution domain (e.g., address space) for each executing process.\nRationale for non-applicability: The MDM server does not have different classes of security functions.",
|
|
2246
|
+
"severity": "medium"
|
|
2247
|
+
},
|
|
2248
|
+
{
|
|
2249
|
+
"id": "V-36380",
|
|
2250
|
+
"title": "Applications providing information flow control must use explicit security attributes on information, source, and destination objects as a basis for flow control decisions.\n",
|
|
2251
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: Information flow control only applies to a CDS. An MDM server is not a cross domain solution.",
|
|
2252
|
+
"severity": "medium"
|
|
2253
|
+
},
|
|
2254
|
+
{
|
|
2255
|
+
"id": "V-36381",
|
|
2256
|
+
"title": "Applications must isolate security functions enforcing access and information flow control from both non-security functions and from other security functions.",
|
|
2257
|
+
"description": "Application functionality is typically broken down into modules that perform various tasks or roles. Examples of non-privileged application functionality include, but are not limited to, application modules written for displaying data or printing reports. \nRationale for non-applicability: The MDM server does not support non-privileged functions.",
|
|
2258
|
+
"severity": "medium"
|
|
2259
|
+
},
|
|
2260
|
+
{
|
|
2261
|
+
"id": "V-36382",
|
|
2262
|
+
"title": "Applications must enforce information flow control using protected processing domains (e.g., domain type-enforcement) as a basis for flow control decisions.\n",
|
|
2263
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: Information flow control only applies to a CDS. An MDM server is not a cross domain solution.",
|
|
2264
|
+
"severity": "medium"
|
|
2265
|
+
},
|
|
2266
|
+
{
|
|
2267
|
+
"id": "V-36383",
|
|
2268
|
+
"title": "Applications must enforce information flow using dynamic control based on policy that allows or disallows information flow based on changing conditions or operational considerations.\n",
|
|
2269
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: Information flow control only applies to a CDS. An MDM server is not a cross domain solution.",
|
|
2270
|
+
"severity": "medium"
|
|
2271
|
+
},
|
|
2272
|
+
{
|
|
2273
|
+
"id": "V-36384",
|
|
2274
|
+
"title": "Applications must prevent encrypted data from bypassing content-checking mechanisms.\n",
|
|
2275
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \n\nRationale for non-applicability: The MDM server must protect data from being content checked by network mechanisms to comply with requirement SRG-APP-196-MDM server-212-MEM to protect confidentiality of communications.",
|
|
2276
|
+
"severity": "medium"
|
|
2277
|
+
},
|
|
2278
|
+
{
|
|
2279
|
+
"id": "V-36385",
|
|
2280
|
+
"title": "Applications must enforce organization defined limitations on the embedding of data types within other data types.\n",
|
|
2281
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: The MDM server does not manage data content.",
|
|
2282
|
+
"severity": "medium"
|
|
2283
|
+
},
|
|
2284
|
+
{
|
|
2285
|
+
"id": "V-36386",
|
|
2286
|
+
"title": "Applications must isolate security functions from non-security functions by means of an isolation boundary (implemented via partitions and domains) controlling access to and protecting the integrity of, the hardware, software, and firmware that perform those security functions. The application must isolate security functions from non-security functions.",
|
|
2287
|
+
"description": "Security functions are defined as \"the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based\". \nRationale for non-applicability: The MDM server does not support multiple domains.",
|
|
2288
|
+
"severity": "medium"
|
|
2289
|
+
},
|
|
2290
|
+
{
|
|
2291
|
+
"id": "V-36387",
|
|
2292
|
+
"title": "Applications providing remote access must have capabilities that allow all remote access to be routed through managed access control points.\n",
|
|
2293
|
+
"description": "Remote network access is accomplished by leveraging common communication protocols and establishing a remote connection. These connections will occur over the public Internet. \n\nRemote access is any access to an organizational information system by a user (or an information system) communicating through an external, non-organization-controlled network (e.g., the Internet). Examples of remote access methods include dial-up, broadband, and wireless. \n\nAutomated monitoring of remote access sessions allows organizations to audit user activities on a variety of information system components (e.g., servers, workstations, notebook/laptop computers) and to ensure compliance with remote access policy.\n\nRemote access applications such as those providing remote access to network devices and information systems and are individually configured with no monitoring or automation capabilities increase risk and makes remote user access management difficult at best.\n\nApplications providing remote access capability need to provide the ability to automatically monitor and control remote user sessions. This includes the capability to directly trigger actions based on user activity or pass information and or data to a separate application or entity that can then perform automated tasks based on the information.\n\nRationale for non-applicability: The MDM server application is not directly administered remotely.",
|
|
2294
|
+
"severity": "medium"
|
|
2295
|
+
},
|
|
2296
|
+
{
|
|
2297
|
+
"id": "V-36388",
|
|
2298
|
+
"title": "Applications must enforce information flow control on metadata.\n",
|
|
2299
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: Information flow control only applies to a CDS. An MDM server is not a cross domain solution.",
|
|
2300
|
+
"severity": "medium"
|
|
2301
|
+
},
|
|
2302
|
+
{
|
|
2303
|
+
"id": "V-36389",
|
|
2304
|
+
"title": "The application must prevent the presentation of information system management-related functionality at an interface utilized by general (i.e., non-privileged) users.",
|
|
2305
|
+
"description": "Information system management functionality includes, functions necessary to administer databases, network components, workstations, or servers, and typically requires privileged user access. \nRationale for non-applicability: The MDM server should only be accessed by authorized administrators, which means that non-privileged accounts will not be present.",
|
|
2306
|
+
"severity": "medium"
|
|
2307
|
+
},
|
|
2308
|
+
{
|
|
2309
|
+
"id": "V-36390",
|
|
2310
|
+
"title": "Applications must use security policy filters as a basis for making information flow control decisions.\n",
|
|
2311
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: Information flow control only applies to a CDS. An MDM server is not a cross domain solution.",
|
|
2312
|
+
"severity": "medium"
|
|
2313
|
+
},
|
|
2314
|
+
{
|
|
2315
|
+
"id": "V-36391",
|
|
2316
|
+
"title": "The application must separate user functionality (including user interface services) from information system management functionality.",
|
|
2317
|
+
"description": "Information system management functionality includes, functions necessary to administer databases, network components, workstations, or servers, and typically requires privileged user access. \nRationale for non-applicability: There are no users on an MDM server, only administrators.",
|
|
2318
|
+
"severity": "medium"
|
|
2319
|
+
},
|
|
2320
|
+
{
|
|
2321
|
+
"id": "V-36392",
|
|
2322
|
+
"title": "Applications providing information flow control must provide the capability for privileged administrators to enable/disable security policy filters.\n",
|
|
2323
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: Information flow control only applies to a CDS. An MDM server is not a cross domain solution.",
|
|
2324
|
+
"severity": "medium"
|
|
2325
|
+
},
|
|
2326
|
+
{
|
|
2327
|
+
"id": "V-36393",
|
|
2328
|
+
"title": "Applications employed to write data to portable digital media must use cryptographic mechanisms to protect and restrict access to information on portable digital media.",
|
|
2329
|
+
"description": "When data is written to portable digital media such as thumb drives, floppy diskettes, compact disks, magnetic tape etc, there is risk of data loss. \nRationale for non-applicability: MDM server does not write to portable media.",
|
|
2330
|
+
"severity": "medium"
|
|
2331
|
+
},
|
|
2332
|
+
{
|
|
2333
|
+
"id": "V-36394",
|
|
2334
|
+
"title": "Applications providing information flow controls must provide the capability for privileged administrators to configure security policy filters to support different organizational security policies.\n",
|
|
2335
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \n\nFrom an application perspective, flow control is established once application data flow modeling has been completed. Data flow modeling can be described as: the process of identifying, modeling and documenting how data moves around an information system. Data flow modeling examines processes (activities that transform data from one form to another), data stores (the holding areas for data), external entities (what sends data into a system or receives data from a system), and data flows (routes by which data can flow). \n\nOnce the application data flows have been identified, corresponding flow controls can be applied at the appropriate points.\n\nA few examples of flow control restrictions include: keeping export controlled information from being transmitted in the clear to the Internet and blocking information marked as classified but is being transported to an unapproved destination. Information flow control policies and enforcement mechanisms are commonly employed by organizations to control the flow of information between designated sources and destinations (e.g., networks, individuals, devices) within information systems and between interconnected systems. Flow control is based on the characteristics of the information and/or the information path.\n\nApplication specific examples of flow control enforcement can be found in information protection software (e.g., guards, proxies, gateways and cross domain solutions) employing rule sets or establish configuration settings restricting information system services or provide message filtering capability based on content (e.g., using key word searches or document characteristics). \n\nA crucial part of any flow control solution is the ability to create policy filters. Policy filters serve to enact and enforce the organizational policy as it pertains to controlling data flow. \n\nOrganization-defined security policy filters include, file type checking filters, structured data filters, unstructured data filters, metadata content filters, and hidden content filters. \n\n- Structured data permits the interpretation of its content by virtue of atomic elements that are understandable by an application and indivisible. \n- Unstructured data refers to masses of (usually) digital information does not have a data structure or does have a data structure that is not easily readable by a machine. Unstructured data consists of two basic categories: (i) bitmap objects that are inherently non language-based (i.e., image, video, or audio files); and (ii) textual objects based on a written or printed language (i.e., commercial off-the-shelf word processing documents, spreadsheets, or emails).\n\nApplications providing information flow control must provide the capability for privileged administrators to configure security policy filters to support different security policies.\n",
|
|
2336
|
+
"severity": "medium"
|
|
2337
|
+
},
|
|
2338
|
+
{
|
|
2339
|
+
"id": "V-36395",
|
|
2340
|
+
"title": "Applications scanning for malicious code must scan all media used for system maintenance prior to use.",
|
|
2341
|
+
"description": "There are security-related issues arising from software brought into the information system specifically for diagnostic and repair actions. (e.g., a software packet sniffer installed on a system in order to troubleshoot system traffic, or a vendor installing or running a diagnostic application in order to troubleshoot an issue with a vendor supported system).\nRationale for non-applicability: Malicious code scanning is not within the scope of MDM server functionality.",
|
|
2342
|
+
"severity": "medium"
|
|
2343
|
+
},
|
|
2344
|
+
{
|
|
2345
|
+
"id": "V-36396",
|
|
2346
|
+
"title": "The application must monitor for unauthorized remote connections to the information system on an organization defined frequency.\n",
|
|
2347
|
+
"description": "Organizations need to monitor for unauthorized remote access connections to information systems in order to determine if break-in attempts or other unauthorized activity is occurring. There are already other SRG requirements for applications to generate audit connection logs to record connection activity. It is for the organization to determine which of those audited connections is unauthorized. \nRationale for non-applicability: This requirement is better managed by the operating system.",
|
|
2348
|
+
"severity": "medium"
|
|
2349
|
+
},
|
|
2350
|
+
{
|
|
2351
|
+
"id": "V-36397",
|
|
2352
|
+
"title": "The application must employ automated mechanisms enabling authorized users to make information sharing decisions based on access authorizations of sharing partners and access restrictions on information to be shared.\n",
|
|
2353
|
+
"description": "User based collaboration and information sharing applications present challenges regarding classification and dissemination of information generated and shared among the application users. These types of applications are intended to share information created and stored within the application; however, not all users have a need to view all data created or stored within the collaboration tool. \nRationale for non-applicability: This control primarily applies to the discretionary sharing of information resources by data owners. This type of service is unrelated to MDM server functionality.",
|
|
2354
|
+
"severity": "medium"
|
|
2355
|
+
},
|
|
2356
|
+
{
|
|
2357
|
+
"id": "V-36398",
|
|
2358
|
+
"title": "Applications related to incident tracking must support organizational requirements to employ automated mechanisms to assist in the tracking of security incidents.",
|
|
2359
|
+
"description": "Incident tracking is a method of monitoring networks and systems for activity indicative of viral infection or system attack. \nRationale for non-applicability: An MDM server is not an incident tracking application.",
|
|
2360
|
+
"severity": "medium"
|
|
2361
|
+
},
|
|
2362
|
+
{
|
|
2363
|
+
"id": "V-36399",
|
|
2364
|
+
"title": "The application must support taking organization defined list of least-disruptive actions to terminate suspicious events.\n",
|
|
2365
|
+
"description": "System availability is a key tenet of system security. Organizations need to have the flexibility to be able to define the automated actions taken in response to an identified incident. This includes being able to define a least disruptive action that the application takes to terminate suspicious events. A least disruptive action may include initiating a request for human response rather than blocking traffic or disrupting system operation.\n\nRationale for non-applicability: The MDM server is not an IDS.",
|
|
2366
|
+
"severity": "medium"
|
|
2367
|
+
},
|
|
2368
|
+
{
|
|
2369
|
+
"id": "V-36400",
|
|
2370
|
+
"title": "Applications that are designed and intended to address incident response scenarios must provide a configurable capability to automatically disable an information system if any of the organization defined security violations are detected.",
|
|
2371
|
+
"description": "When responding to a security incident a capability must exist allowing authorized personnel to disable a particular system if the system exhibits a security violation and the organization determines an action is warranted. \nRationale for non-applicability: This requirement is better covered in another CCI. CCI-001274 Ensures the MDM server will have the capability to disable CMD if an incident is detected.",
|
|
2372
|
+
"severity": "medium"
|
|
2373
|
+
},
|
|
2374
|
+
{
|
|
2375
|
+
"id": "V-36401",
|
|
2376
|
+
"title": "Applications must include organization defined additional, more detailed information in the audit records for audit events identified by type, location, or subject.\n",
|
|
2377
|
+
"description": "Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control, includes: timestamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.\nRationale for non-applicability: This vulnerability is better addressed by another CCI. CCI-000130 covers audit records to a sufficient degree for the MDM server.",
|
|
2378
|
+
"severity": "medium"
|
|
2379
|
+
},
|
|
2380
|
+
{
|
|
2381
|
+
"id": "V-36402",
|
|
2382
|
+
"title": "The application must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).",
|
|
2383
|
+
"description": "Non-organizational users include all information system users other than organizational users which include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, individuals from allied nations). \nRationale for non-applicability: There is no business purpose for a non-organizational user to access the MDM server system.",
|
|
2384
|
+
"severity": "medium"
|
|
2385
|
+
},
|
|
2386
|
+
{
|
|
2387
|
+
"id": "V-36403",
|
|
2388
|
+
"title": "Applications managing network connections for devices must authenticate devices before establishing wireless network connections by using bidirectional authentication that is cryptographically based.",
|
|
2389
|
+
"description": "Device authentication is a solution enabling an organization to manage devices. \nRationale for non-applicability: While the MDM server manages wireless devices, these devices connect to the carrier infrastructure. Therefore, there would not be a direct wireless connection to the MDM server.",
|
|
2390
|
+
"severity": "medium"
|
|
2391
|
+
},
|
|
2392
|
+
{
|
|
2393
|
+
"id": "V-36404",
|
|
2394
|
+
"title": "The application must enforce configurable traffic volume thresholds representing auditing capacity for network traffic.\n",
|
|
2395
|
+
"description": "It is critical when a system is at risk of failing to process audit logs as required; actions are automatically taken to mitigate the failure. Audit processing failures include: software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. \nRationale for non-applicability: MDM server functionality involves the transfer of small policy and configuration files and other commands, none of which are expected to trigger network volume thresholds. If such protection is desired, it is better performed by the operating system or a network firewall.",
|
|
2396
|
+
"severity": "medium"
|
|
2397
|
+
},
|
|
2398
|
+
{
|
|
2399
|
+
"id": "V-36405",
|
|
2400
|
+
"title": "The application must have the capability to produce audit records on hardware-enforced, write-once media.\n",
|
|
2401
|
+
"description": "Applications are typically designed to incorporate their audit logs into the auditing sub-system hosted by the operating system. However, in some instances application developers may decide to forego the audit capabilities offered by the operating system and maintain application audit logs separately. \nRationale for non-applicability: This requirement is not applicable to an MDM server. It is applicable to a central audit management system.",
|
|
2402
|
+
"severity": "medium"
|
|
2403
|
+
},
|
|
2404
|
+
{
|
|
2405
|
+
"id": "V-36406",
|
|
2406
|
+
"title": "The application must use organization defined replay-resistant authentication mechanisms for network access to non-privileged accounts.",
|
|
2407
|
+
"description": "An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. \nRationale for non-applicability: The MDM server should only be accessed by authorized administrators, which means that non-privileged accounts will not be present.",
|
|
2408
|
+
"severity": "medium"
|
|
2409
|
+
},
|
|
2410
|
+
{
|
|
2411
|
+
"id": "V-36407",
|
|
2412
|
+
"title": "The application must support organizational requirements to enforce password complexity by the number of lower case characters used.\n",
|
|
2413
|
+
"description": "Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. \nRationale for non-applicability: The MDM server must use the Enterprise Authentication Mechanism for administrator accounts.",
|
|
2414
|
+
"severity": "medium"
|
|
2415
|
+
},
|
|
2416
|
+
{
|
|
2417
|
+
"id": "V-36408",
|
|
2418
|
+
"title": "Applications using multifactor authentication when accessing non-privileged accounts via the network must provide one of the factors by a device separate from the information system gaining access.",
|
|
2419
|
+
"description": "Multifactor authentication is defined as: using two or more factors to achieve authentication. \nRationale for non-applicability: The MDM server should only be accessed by authorized administrators, which means that non-privileged accounts will not be present.",
|
|
2420
|
+
"severity": "medium"
|
|
2421
|
+
},
|
|
2422
|
+
{
|
|
2423
|
+
"id": "V-36409",
|
|
2424
|
+
"title": "The application must support organizational requirements to enforce password complexity by the number of numeric characters used.\n",
|
|
2425
|
+
"description": "Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. \nRationale for non-applicability: The MDM server must use the Enterprise Authentication Mechanism for administrator accounts.",
|
|
2426
|
+
"severity": "medium"
|
|
2427
|
+
},
|
|
2428
|
+
{
|
|
2429
|
+
"id": "V-36410",
|
|
2430
|
+
"title": "Applications using multifactor authentication when accessing privileged accounts via the network must provide one of the factors by a device that is separate from the information system gaining access.",
|
|
2431
|
+
"description": "Multifactor authentication is defined as: using two or more factors to achieve authentication. \nRationale for non-applicability: Authentication to the MDM server is controlled by the Enterprise Authentication Mechanism.",
|
|
2432
|
+
"severity": "medium"
|
|
2433
|
+
},
|
|
2434
|
+
{
|
|
2435
|
+
"id": "V-36411",
|
|
2436
|
+
"title": "The application must support organizational requirements to enforce the number of characters that get changed when passwords are changed.\n",
|
|
2437
|
+
"description": "Passwords need to be changed at specific policy based intervals. \nRationale for non-applicability: The MDM server must use the Enterprise Authentication Mechanism for administrator accounts.",
|
|
2438
|
+
"severity": "medium"
|
|
2439
|
+
},
|
|
2440
|
+
{
|
|
2441
|
+
"id": "V-36412",
|
|
2442
|
+
"title": "The application must support organizational requirements to enforce password encryption for storage.\n",
|
|
2443
|
+
"description": "Applications must enforce password encryption when storing passwords. Passwords need to be protected at all times and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read and easily compromised.\nRationale for non-applicability: The MDM server must use the Enterprise Authentication Mechanism for administrator accounts.",
|
|
2444
|
+
"severity": "medium"
|
|
2445
|
+
},
|
|
2446
|
+
{
|
|
2447
|
+
"id": "V-36413",
|
|
2448
|
+
"title": "The application must use multifactor authentication for local access to non-privileged accounts.",
|
|
2449
|
+
"description": "Multifactor authentication is defined as: using two or more factors to achieve authentication. \nRationale for non-applicability: The MDM server should only be accessed by authorized administrators, which means that non-privileged accounts will not be present.",
|
|
2450
|
+
"severity": "medium"
|
|
2451
|
+
},
|
|
2452
|
+
{
|
|
2453
|
+
"id": "V-36414",
|
|
2454
|
+
"title": "Applications must enforce password minimum lifetime restrictions.\n",
|
|
2455
|
+
"description": "Password minimum lifetime is defined as: the minimum period of time, (typically in days) a user's password must be in effect before the user can change it. \nRationale for non-applicability: The MDM server must use the Enterprise Authentication Mechanism for administrator accounts.",
|
|
2456
|
+
"severity": "medium"
|
|
2457
|
+
},
|
|
2458
|
+
{
|
|
2459
|
+
"id": "V-36415",
|
|
2460
|
+
"title": "The application must use multifactor authentication for network access to non-privileged accounts.",
|
|
2461
|
+
"description": "Multifactor authentication is defined as: using two or more factors to achieve authentication. \nRationale for non-applicability: The MDM server should only be accessed by authorized administrators, which means that non-privileged accounts will not be present.",
|
|
2462
|
+
"severity": "medium"
|
|
2463
|
+
},
|
|
2464
|
+
{
|
|
2465
|
+
"id": "V-36416",
|
|
2466
|
+
"title": "Applications must enforce password maximum lifetime restrictions.\n",
|
|
2467
|
+
"description": "Password maximum lifetime is defined as: the maximum period of time, (typically in days) a user's password may be in effect before the user is forced to change it. \nRationale for non-applicability: The MDM server must use the Enterprise Authentication Mechanism for administrator accounts.",
|
|
2468
|
+
"severity": "medium"
|
|
2469
|
+
},
|
|
2470
|
+
{
|
|
2471
|
+
"id": "V-36417",
|
|
2472
|
+
"title": "The application must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).",
|
|
2473
|
+
"description": "To assure accountability and prevent unauthorized access, organizational users shall be identified and authenticated. \nRationale for non-applicability: The MDM server will leverage Enterprise Authentication Mechanism accounts. Therefore, the Enterprise Authentication Mechanism will perform authentication, and not the application. This is better covered by SRG-APP-149-MDM server-033-SRV.",
|
|
2474
|
+
"severity": "medium"
|
|
2475
|
+
},
|
|
2476
|
+
{
|
|
2477
|
+
"id": "V-36418",
|
|
2478
|
+
"title": "The application must support organizational requirements to prohibit password reuse for the organization defined number of generations.\n",
|
|
2479
|
+
"description": "Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. \nRationale for non-applicability: The MDM server must use the Enterprise Authentication Mechanism for administrator accounts.",
|
|
2480
|
+
"severity": "medium"
|
|
2481
|
+
},
|
|
2482
|
+
{
|
|
2483
|
+
"id": "V-36419",
|
|
2484
|
+
"title": "The application must support and must not impede organizational requirements to conduct backups of information system documentation including security-related documentation per organization defined frequency.",
|
|
2485
|
+
"description": "Information system backup is a critical step in maintaining data assurance and availability. \nRationale for non-applicability: The MDM server does not manage documentation. Documentation is readily available from a number of sources, including online.",
|
|
2486
|
+
"severity": "medium"
|
|
2487
|
+
},
|
|
2488
|
+
{
|
|
2489
|
+
"id": "V-36420",
|
|
2490
|
+
"title": "The application must support organizational requirements to enforce minimum password length.\n",
|
|
2491
|
+
"description": "Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. \nRationale for non-applicability: The MDM server must use the Enterprise Authentication Mechanism for administrator accounts.",
|
|
2492
|
+
"severity": "medium"
|
|
2493
|
+
},
|
|
2494
|
+
{
|
|
2495
|
+
"id": "V-36421",
|
|
2496
|
+
"title": "Applications providing flow control must identify data type, specification and usage when transferring information between different security domains so that policy restrictions may be applied.\n",
|
|
2497
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: An MDM server supports only one security domain.",
|
|
2498
|
+
"severity": "medium"
|
|
2499
|
+
},
|
|
2500
|
+
{
|
|
2501
|
+
"id": "V-36422",
|
|
2502
|
+
"title": "Backup / Disaster Recovery oriented applications must be capable of backing up user-level information per a defined frequency.",
|
|
2503
|
+
"description": "Information system backup is a critical step in maintaining data assurance and availability. \nRationale for non-applicability: The MDM server is not a Backup / Disaster Recovery oriented application. To the extent such services are needed, they would be provided by the operating system or backup agent software. In addition, the administrators who access the MDM server are not expected to have any user-level information to perform their administrative functions.",
|
|
2504
|
+
"severity": "medium"
|
|
2505
|
+
},
|
|
2506
|
+
{
|
|
2507
|
+
"id": "V-36423",
|
|
2508
|
+
"title": "Applications must adhere to the principles of least functionality by providing only essential capabilities.",
|
|
2509
|
+
"description": "Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). \nRationale for non-applicability: MDM server functionality is controlled by the assigned administrator role. ",
|
|
2510
|
+
"severity": "medium"
|
|
2511
|
+
},
|
|
2512
|
+
{
|
|
2513
|
+
"id": "V-36424",
|
|
2514
|
+
"title": "Applications, when transferring information between different security domains, must decompose information into policy-relevant subcomponents for submission to policy enforcement mechanisms.\n",
|
|
2515
|
+
"description": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: An MDM server supports only one security domain.",
|
|
2516
|
+
"severity": "medium"
|
|
2517
|
+
},
|
|
2518
|
+
{
|
|
2519
|
+
"id": "V-36425",
|
|
2520
|
+
"title": "Applications must provide the ability to enforce security policies regarding information on interconnected systems.\n",
|
|
2521
|
+
"description": "The application enforces approved authorizations for controlling the flow of information within the system and between interconnected systems in accordance with applicable policy. \nRationale for non-applicability: This vulnerability is better addressed by another CCI. CCI-000066 deals with remote access to the device.",
|
|
2522
|
+
"severity": "medium"
|
|
2523
|
+
},
|
|
2524
|
+
{
|
|
2525
|
+
"id": "V-36426",
|
|
2526
|
+
"title": "The MDM server must have the capability to use automated mechanisms to centrally apply configuration settings to managed mobile devices.",
|
|
2527
|
+
"description": "Configuration settings are the configurable security-related parameters of operating system. \nRationale for non-applicability: This vulnerability is better addressed by CCI-000370.\n",
|
|
2528
|
+
"severity": "medium"
|
|
2529
|
+
},
|
|
2530
|
+
{
|
|
2531
|
+
"id": "V-36427",
|
|
2532
|
+
"title": "The application must bind security attributes to information to facilitate information flow policy enforcement.\n",
|
|
2533
|
+
"description": "The application enforces approved authorizations for controlling the flow of information within the system and between interconnected systems in accordance with applicable policy. Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. \nRationale for non-applicability: This vulnerability is better addressed by another CCI. CCI-000066 deals with remote access to the device.",
|
|
2534
|
+
"severity": "medium"
|
|
2535
|
+
},
|
|
2536
|
+
{
|
|
2537
|
+
"id": "V-36428",
|
|
2538
|
+
"title": "The application must support the enforcement of a two-person rule for changes to organization defined application components and system-level information.",
|
|
2539
|
+
"description": "Regarding access restrictions for changes made to organization defined information system components and system level information. Any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have significant effects on the overall security of the system. \nRationale for non-applicability: The IA posture of the MDM server does not warrant application of the two-person rule.",
|
|
2540
|
+
"severity": "medium"
|
|
2541
|
+
},
|
|
2542
|
+
{
|
|
2543
|
+
"id": "V-36429",
|
|
2544
|
+
"title": "Applications must be able to function within separate processing domains (virtualized systems), when specified, so as to enable finer-grained allocation of user privileges.\n",
|
|
2545
|
+
"description": "Applications must employ the concept of least privilege, allowing only authorized accesses for users (and processes acting on behalf of users) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions. \nRationale for non-applicability: An MDM server supports only one security domain.",
|
|
2546
|
+
"severity": "medium"
|
|
2547
|
+
},
|
|
2548
|
+
{
|
|
2549
|
+
"id": "V-36430",
|
|
2550
|
+
"title": "The MDM server must have a DoD approved host-based firewall installed on the host server.\n",
|
|
2551
|
+
"description": "Most information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations. Since MDM server is a critical component of the mobility architecture and it must be configured to only those ports, protocols, and services (PPS) necessary to support functionality, all others must be expressly disabled or removed. A host firewall installed on the MDM server provides a protection mechanism to ensure unwanted service requests do not reach the MDM server and outbound traffic is limited to only MDM server functionality.",
|
|
2552
|
+
"severity": "high"
|
|
2553
|
+
}
|
|
2554
|
+
]
|
|
2555
|
+
}
|