RubyGems - kriterion - Versions diffs - 0.0.1 - Mend

kriterion 0.0.1

Files changed (564) hide show

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

data/standards/stig_operating_system_security_requirements_guide.json ADDED

@@ -0,0 +1,1961 @@
+{
+  "name": "stig_operating_system_security_requirements_guide",
+  "date": "2013-03-28",
+  "description": "None",
+  "title": "Operating System Security Requirements Guide",
+  "version": "None",
+  "item_syntax": "^\\w-\\d+$",
+  "section_separator": null,
+  "items": [
+    {
+      "id": "V-28769",
+      "title": "The operating system must  provide automated support for account management functions.",
+      "description": "A comprehensive account management process that includes automation helps to ensure the accounts designated as requiring attention are consistently and promptly addressed. Examples include, but are not limited to using automation to take action on multiple accounts designated as inactive, suspended or terminated, or by disabling accounts located in non-centralized account stores, such as, multiple servers.\n\nEnterprise environments make user account management challenging and complex. A user management process requiring administrators to manually address account management functions adds risk of potential oversight.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28770",
+      "title": "The operating system must automatically terminate temporary accounts after an organization-defined time period for each type of account.",
+      "description": "When temporary and emergency accounts are created, there is a risk the temporary account may remain in place and active after the need for the account no longer exists.\n\nTo address this, in the event temporary accounts are required, accounts designated as temporary in nature must be automatically terminated after an organization-defined time period. Such a process and capability greatly reduces the risk of accounts being misused, hijacked, or data compromised.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28773",
+      "title": "The operating system must automatically disable inactive accounts after an organization-defined time period.",
+      "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 pertaining to their own account. Inactive 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.  \n\nThere is a risk that inactive accounts can potentially obtain and maintain undetected access to an application. The operating system must track periods of user inactivity and disable the accounts after an organization-defined period of inactivity.\n\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28774",
+      "title": "The operating system must enforce maximum password lifetime restrictions.",
+      "description": "Passwords need to be changed at specific policy based intervals. Any password no matter how complex can eventually be cracked. \n\nOne method of minimizing this risk is to use complex passwords and periodically change them. If the operating system does not limit the lifetime of passwords and force users to change their passwords, there is the risk that system passwords could be compromised.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28775",
+      "title": "The operating system must prohibit password reuse for the organization-defined number of generations.",
+      "description": "Password complexity, or strength, is a measure of the effectiveness of a password in resisting guessing and brute-force attacks. \n\nTo meet password policy requirements, passwords need to be changed at specific policy based intervals. \n\nIf the operating system allows the user to consecutively reuse their password when the password has exceeded its defined lifetime, the end result is a password that is not changed, per policy requirements.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28776",
+      "title": "The operating system must enforce minimum password length.",
+      "description": "Password complexity, or strength, is a measure of the effectiveness of a password in resisting guessing and brute-force attacks. \n\nPassword length is one factor of several that helps to determine strength and how long it takes to crack a password. The shorter the password is, the lower the number of possible combinations that need to be tested before the password is compromised. \n\nUse of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28777",
+      "title": "The operating system must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.",
+      "description": "To prevent the compromise of authentication information, such as passwords during the authentication process, the feedback from the operating system shall not provide any information allowing an unauthorized user to compromise the authentication mechanism. \n\nObfuscation of user provided information that is typed into the system is a method used when addressing this risk. \n\nFor example, displaying asterisks when a user types in a password, is an example of obscuring feedback of authentication information.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28778",
+      "title": "The operating system must enforce approved authorizations for logical access to the system in accordance with applicable policy.",
+      "description": "Strong access controls are critical to securing  data. 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 operating system 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 operating system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28779",
+      "title": "The operating system, when transferring information between different security domains, must identify information flows by data type specification and usage.",
+      "description": "Information flow control regulates where information is allowed to travel\nwithin 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 the information. \n\nFlow control is based on the characteristics of the information and/or the information path. \n\nA security domain is defined as a domain that implements a security policy and is administered by a single authority.\n\nData type specification and usage include using file naming to reflect type of data and limiting data transfer based on file type.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28780",
+      "title": "The operating system, when transferring information between different security domains, must decompose information into policy-relevant subcomponents for submission to policy enforcement mechanisms.",
+      "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\nPolicy enforcement mechanisms include the filtering and/or sanitization rules that are applied to information prior to transfer to a different security domain.  \n\nParsing transfer files facilitates policy decisions on source, destination, certificates, classification, subject, attachments, and other information security-related component differentiators. \n\nPolicy rules for cross domain transfers include, limitations on embedding components/information types within other components/information types, prohibiting more than two-levels of embedding, and prohibiting the transfer of archived information types.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28781",
+      "title": "The operating system must enforce security policies regarding information on interconnected systems.",
+      "description": "The operating system enforces approved authorizations for controlling the flow of information within the system and between interconnected systems in accordance with applicable policy. \n\nInformation 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 the information. \n\nTransferring information between interconnected information systems of differing security policies introduces risk that such transfers violate one or more policies. While security policy violations may not be absolutely prohibited, policy guidance from information owners/stewards is implemented at the policy enforcement point between the interconnected systems. Specific architectural solutions are mandated, when required, to reduce the potential for undiscovered vulnerabilities.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28782",
+      "title": "The operating system must bind security attributes to information to facilitate information flow policy enforcement.",
+      "description": "Operating system 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 the information.  \n\nAttribution is a critical component of a security concept of operations. The ability to identify source and destination points for information flowing in an information system, allows forensic reconstruction of events when required, and increases policy compliance by attributing policy violations to specific organizations/individuals.  Binding security attributes to information allows policy enforcement mechanisms to act on the information and enforce policy.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28783",
+      "title": "The operating system must track problems associated with the security attribute binding.",
+      "description": "The operating system enforces approved authorizations for controlling the flow of information within the system and between interconnected systems in accordance with applicable policy. \n\nInformation 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 the information. \n\nAttribution is a critical component of a security concept of operations. Attribution (e.g., the ability to attribute actions to certain individuals) is a critical component of a security concept of operations. The ability to identify source and destination points for information flowing in an information system, allows forensic reconstruction of events when required, and increases policy compliance by attributing policy violations to specific organizations/individuals. In order to identify when problems occur when binding security attributes to information, tracking problems and/or auditing of these events must occur.\n\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28785",
+      "title": "The operating system must provide the capability for a privileged administrator to configure organization-defined security policy filters to support different security policies.",
+      "description": "In order to control changes in policy, a privileged administrator must be able to change policy filters to support different security policies.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28786",
+      "title": "The operating system must enforce logical access restrictions associated with changes to the information system.",
+      "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 can potentially have significant effects on the overall security of the system. \n\nAccordingly, only qualified and authorized individuals should be allowed to obtain access to operating system for the purpose of initiating changes, including upgrades and modifications.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28787",
+      "title": "The operating system must employ automated mechanisms to enforce access restrictions.",
+      "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\nAccordingly, only qualified and authorized individuals should be allowed to obtain access to information system components for the purposes of initiating changes, upgrades, and modifications.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28789",
+      "title": "The operating system must employ automated mechanisms to support auditing of the enforcement actions.",
+      "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. \n\nAccordingly, only qualified and authorized individuals are allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. \n\nAuditing this information is critical to both the configuration management process and in the event of an intrusion.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28790",
+      "title": "The operating system must prevent the installation of organization-defined critical software programs that are not signed with a certificate that is recognized and approved by the organization.",
+      "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. \n\nAccordingly, software defined by the organization as critical software must be signed with a certificate that is recognized and approved by the organization.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28792",
+      "title": "The operating system must support the requirement to automatically audit on account creation.",
+      "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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28793",
+      "title": "The operating system must enforce a two-person rule for changes to organization-defined information system components and system-level information.",
+      "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 operating system can potentially have significant effects on the overall security of the system. \n\nAccordingly, only qualified and authorized individuals are allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications. \n\nA two person rule requires two separate individuals acknowledge and approve those changes. Two person rule for changes to critical operating system components helps to reduce risks pertaining to availability and integrity.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28794",
+      "title": "The operating system must employ automated mechanisms to centrally apply configuration settings.",
+      "description": "Configuration settings are the configurable security-related parameters of operating system.  \n\nSecurity-related parameters are those parameters impacting the security state of the system including parameters related to meeting other security control requirements. \n\nRather than visiting each and every system when making  configuration changes, organizations will employ automated tools that can make changes across all systems.  This greatly increases efficiency and manageability of applications in a large scale environment.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28796",
+      "title": "The operating system must employ automated mechanisms to centrally verify configuration settings.",
+      "description": "Configuration settings are the configurable security-related parameters of information technology products that are part of the information system. Security-related parameters are those parameters impacting the security state of the system including parameters related to meeting other security control requirements. \n\nRather than visiting each and every system when verifying  configuration changes, organizations will employ automated tools that can make changes across all systems.  This greatly increases efficiency and manageability of applications in a large scale environment.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28798",
+      "title": "The operating system must employ automated mechanisms to respond to unauthorized changes to organization-defined configuration settings.",
+      "description": "Configuration settings are the configurable security-related parameters of information technology products that are part of the information system. Security-related parameters are those parameters impacting the security state of the system including parameters related to meeting other security control requirements. \n\nResponses to unauthorized changes to configuration settings can include, alerting designated organizational personnel, restoring mandatory/organization-defined configuration settings, or in the extreme case, halting affected information system processing.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28801",
+      "title": "The operating system must be configured to provide essential capabilities.",
+      "description": "Operating 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) and will reduce the attack surface of the operating system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28802",
+      "title": "The operating system must configure the information system to specifically prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services.",
+      "description": "Operating 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) or may present unacceptable risk into the information system environment.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28803",
+      "title": "The operating system must employ automated mechanisms to prevent program execution in accordance with the organization defined specifications.",
+      "description": "Operating systems are capable of providing a wide variety of functions and services.  Execution must be disabled based on organization defined specifications.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28804",
+      "title": "The operating system must employ automated mechanisms, per organization-defined frequency, to detect the addition of unauthorized components/devices into the operating system.",
+      "description": "Baselining of systems both allow for a mechanism to determine when unauthorized additions or changes are made. It also ensures the appropriate patch management is in place for the components on the system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28805",
+      "title": "The operating system must dynamically manage user privileges and associated access authorizations.",
+      "description": "While user identities remain relatively constant over time, user privileges may change more frequently based on the ongoing mission/business requirements and operational needs of the organization. The operating system needs to be able to dynamically manage user privileges and access authorization decisions.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28806",
+      "title": "The operating system must conduct backups of user-level information contained in the operating system per organization-defined frequency to conduct backups consistent with recovery time and recovery point objectives.",
+      "description": "Operating  system backup is a critical step in maintaining data assurance and availability. \n\nUser-level information is data generated by information system and/or application users.\n\nBackups shall be consistent with organizational recovery time and recovery point objectives.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28807",
+      "title": "The operating system 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.",
+      "description": "Operating system backup is a critical step in maintaining data assurance and availability. \n\nSystem-level information includes system-state information, operating system and application software, and licenses. \n\nBackups must be consistent with organizational recovery time and recovery point objectives.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28809",
+      "title": "The operating system must conduct backups of operating system documentation including security-related documentation per organization-defined frequency to conduct backups that is consistent with recovery time and recovery point objectives.",
+      "description": "Operating system backup is a critical step in maintaining data assurance and availability. \n\nInformation system and security related documentation contains information pertaining to system configuration and security settings.  \n\nBackups shall be consistent with organizational recovery time and recovery point objectives.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28810",
+      "title": "The operating system must implement transaction recovery for transaction-based systems. ",
+      "description": "Recovery and reconstitution constitutes executing an operating system contingency plan comprised of activities to restore essential missions and business functions. \n\nTransaction rollback and transaction journaling are examples of mechanisms supporting transaction recovery.\n\nWhile this is typically a database function, operating systems could be transactional in nature with respect to file processing. ",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28811",
+      "title": "The operating system  must enforce explicit rules governing the installation of software by users.",
+      "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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28812",
+      "title": "The operating system must uniquely  identify and must authenticate organizational users (or processes acting on behalf of organizational users).",
+      "description": "To assure accountability and prevent unauthorized access, organizational users shall be identified and authenticated. \n\nOrganizational users include employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers,  individuals from allied nations). \n\nUsers (and any processes acting on behalf of users) are uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization outlining specific user actions that can be performed on the information system without identification or authentication.\n\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28813",
+      "title": "The operating system must use multifactor authentication for network access to privileged accounts.",
+      "description": "Multifactor authentication is defined as using two or more factors to achieve authentication. \n\nFactors include: \n(i) something you know (e.g., password/PIN); \n(ii) something you have (e.g., cryptographic identification device, or token); or \n(iii) something you are (e.g., biometric). \n\nA privileged account is defined as an operating system account with authorizations of a privileged user. \n\n\nNetwork access is defined as access to an operating system by a user (or a process acting on behalf of a user) communicating through a network.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28818",
+      "title": "The operating system must enforce dual authorization, based on organizational policies and procedures for organization-defined privileged commands.",
+      "description": "Dual authorization mechanisms require two distinct approving authorities to approve the use of the command prior to it being invoked. An organization may determine certain commands or configuration changes require dual-authorization before being activated.  The operating system must have the ability to enforce this dual authorization.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28819",
+      "title": "The operating system must use multifactor authentication for network access to non-privileged accounts.",
+      "description": "Multifactor authentication is defined as using two or more factors to achieve authentication. \n\nFactors include: \n(i) something you know (e.g., password/PIN); \n(ii) something you have (e.g., cryptographic identification device, token); or \n(iii) something you are (e.g., biometric). \n\nA non-privileged account is defined as an operating system account with authorizations of a regular or non-privileged user. \n\nNetwork access is defined as access to an information system by a user (or a process acting on behalf of a user) communicating through a network.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28820",
+      "title": "The operating system must use multifactor authentication for local access to privileged accounts.",
+      "description": "Multifactor authentication is defined as using two or more factors to achieve authentication. \n\nFactors include: \n(i) something you know (e.g., password/PIN); \n(ii) something you have (e.g., cryptographic identification device, token); or \n(iii) something you are (e.g., biometric). \n\nA privileged account is defined as an operating system account with authorizations of a privileged user. \n\nLocal access is defined as access to an organizational information system by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28821",
+      "title": "The operating system must use multifactor authentication for local access to non-privileged accounts.",
+      "description": "Multifactor authentication is defined as using two or more factors to achieve authentication. \n\nFactors include: \n(i) something you know (e.g., password/PIN); \n(ii) something you have (e.g., cryptographic identification device, token); or \n(iii) something you are (e.g., biometric). \n\nA non-privileged account is defined as an operating system account with authorizations of a regular or non-privileged user. \n\nLocal access is defined as access to an organizational information system by a user (or process acting on behalf of a user) communicating through a direct connection without the use of a network.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28822",
+      "title": "The operating system must require individuals to be authenticated with an individual authenticator prior to using a group authenticator.",
+      "description": "To assure individual accountability and prevent unauthorized access, organizational users shall be individually identified and authenticated. \n\nUsers (and any processes acting on behalf of users) need to be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization which outlines specific user actions that can be performed on the operating system without identification or authentication.\n\nRequiring individuals to be authenticated with an individual authenticator prior to using a group authenticator allows for traceability of actions, as well as, adding an additional level of protection of the actions that can be taken with group account knowledge.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28823",
+      "title": "The operating system must use multifactor authentication for network access to privileged accounts where one of the factors is provided by a device separate from the information system being accessed.",
+      "description": "Multifactor authentication is defined as using two or more factors to achieve authentication. \n\nFactors include: \n(i) something you know (e.g., password/PIN); \n(ii) something you have (e.g., cryptographic identification device, token); or \n(iii) something you are (e.g., biometric). \n\nA privileged account is defined as an information system account with authorizations of a privileged user. \n\nWhen one of the authentication factors is provided by a device separate from the system that is gaining access, this is referred to as Out of Band 2 Factor Authentication (OOB2FA). OOB2FA employs separate communication channels at least one of which is independently maintained and trusted to authenticate an end user. One channel could be a mobile device that is registered to the user. Upon a logon attempt, the system sends instructions to the device in the form of on-screen prompts instructing the user how to complete the login process.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28824",
+      "title": "The operating system must use multifactor authentication for network access to non-privileged accounts where one of the factors is provided by a device separate from the operating system being accessed.",
+      "description": "Multifactor authentication is defined as using two or more factors to achieve authentication. \n\nFactors include: \n(i) something you know (e.g., password/PIN); \n(ii) something you have (e.g., cryptographic identification device, token); or \n(iii) something you are (e.g., biometric). \n\nA non-privileged account is defined as an information system account with authorizations of a regular or non-privileged user. \n\nWhen one of the authentication factors is provided by a device separate from the system that is gaining access, this is referred to as out of band 2 factor authentication.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28825",
+      "title": "The operating system must use organization-defined replay-resistant authentication mechanisms for network access to privileged accounts.",
+      "description": "An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. \n\nTechniques used to address this include protocols using challenges (e.g., TLS, WS_Security), time synchronous, or challenge-response one-time authenticators.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28826",
+      "title": "The operating system must use organization-defined replay-resistant authentication mechanisms for network access to non-privileged accounts.",
+      "description": "An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. \n\nTechniques used to address this include protocols using challenges (e.g., TLS, WS_Security), time synchronous, or challenge-response one-time authenticators.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28827",
+      "title": "The operating system must uniquely identify and authenticate an organization-defined list of specific and/or types of devices before establishing a connection.",
+      "description": "Device authentication is a solution enabling an organization to manage both users and devices. It is an additional layer of authentication ensuring only specific pre-authorized devices operated by specific pre-authorized users can access the network. \n\nDevice authentication requires unique identification and authentication that may be defined by type, by specific device, or by a combination of type and device as deemed appropriate by the organization.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28828",
+      "title": "The operating system must authenticate devices before establishing remote network connections using bidirectional cryptographically based authentication between devices. ",
+      "description": "Device authentication is a solution enabling an organization to manage devices. \n\nIt is an additional layer of authentication ensuring only specific pre-authorized devices operated by specific pre-authorized users can access the network. \n\nDevice authentication requires unique identification and authentication that may be defined by type, by specific device, or by a combination of type and device as deemed appropriate by the organization. \n\nBidirectional authentication provides a means for both connecting parties to mutually authenticate one another and cryptographically based authentication provides a secure means of authenticating without the use of clear text passwords.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28829",
+      "title": "The operating system must authenticate devices before establishing wireless network connections using bidirectional cryptographically based authentication between devices. ",
+      "description": "Device authentication is a solution enabling an organization to manage devices. \n\nIt is an additional layer of authentication ensuring only specific pre-authorized devices operated by specific pre-authorized users can access the network. \n\nDevice authentication requires unique identification and authentication that may be defined by type, by specific device, or by a combination of type and device as deemed appropriate by the organization. \n\nBidirectional authentication provides a means for both connecting parties to mutually authenticate one another and cryptographically based authentication provides a secure means of authenticating without the use of clear text passwords.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28830",
+      "title": "The operating system must authenticate devices before establishing network connections using bidirectional cryptographically based authentication between devices. ",
+      "description": "Device authentication is a solution enabling an organization to manage both users and devices. \n\nIt is an additional layer of authentication ensuring only specific pre-authorized devices operated by specific pre-authorized users can access the network. \n\nDevice authentication requires unique identification and authentication that may be defined by type, by specific device, or by a combination of type and device as deemed appropriate by the organization. \n\nBidirectional authentication provides a means for both connecting parties to mutually authenticate one another and cryptographically based authentication provides a secure means of authenticating without the use of clear text passwords.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28831",
+      "title": "The operating system must manage information system identifiers for users and devices by disabling the user identifier after an organization-defined time period of inactivity.",
+      "description": "Inactive 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. \n\nAttackers able to exploit an inactive account can potentially obtain and maintain undetected access to the operating system. Operating 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 data compromised.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28832",
+      "title": "The operating system must dynamically manage identifiers, attributes, and associated access authorizations.",
+      "description": "Dynamic management of identities and association of attributes and privileges with these identities are anticipated and provisioned. Pre-established trust relationships and mechanisms with appropriate authorities to validate identities and related credentials are essential.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28833",
+      "title": "The operating system 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.",
+      "description": "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. \n\nApplications utilizing encryption are required to use approved encryption modules meeting the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. \n\nFIPS 140-2 is the current standard for validating cryptographic modules and NSA Type-X (where X=1, 2, 3, 4) products are NSA certified hardware based encryption modules.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28834",
+      "title": "The operating system must uniquely identify and must authenticate non-organizational users (or processes acting on behalf of non-organizational users).",
+      "description": "Non-organizational users include all operating system users other than organizational users which include employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, individuals from allied nations). \n\nNon-organizational users shall be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization when related to the use of anonymous access.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28835",
+      "title": "The operating system must implement a configurable capability to automatically disable the operating system if any of the organization-defined lists of security violations are detected.",
+      "description": "When responding to a security incident a capability must exist allowing automated processes to disable a particular system if the system exhibits a security violation and the organization determines such an action is warranted. \n\nOrganizations shall define a list of security violations warranting an immediate disabling of a system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28836",
+      "title": "The operating system must employ automated mechanisms to assist in the tracking of security incidents.",
+      "description": "This is not applicable for operating systems. This requirement is specific for monitoring applications or network devices that are purposed for this requirement.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28837",
+      "title": "The operating system must check all media containing diagnostic and test programs for malicious code before the media can be used in the information system.",
+      "description": "This is not applicable for operating systems.  Operating systems require the use of malicious code protection.  It is the requirement of that software to check media.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28838",
+      "title": "The operating system must employ automated mechanisms to restrict the use of maintenance tools to authorized personnel only.",
+      "description": "The intent of this control is to address the security-related issues arising from the software brought into the operating system specifically for diagnostic and repair actions (e.g., a software packet sniffer introduced for the purpose of a particular maintenance activity).  \n\nDue to the nature of the tools, these tools must be restricted to authorized personnel only.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28840",
+      "title": "The operating system must employ strong identification and authentication techniques in the establishment of non-local maintenance and diagnostic sessions.",
+      "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\nThe act of managing systems includes the ability to access system configuration details, diagnostic information, user information, as well as installation of software.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28841",
+      "title": "The operating system must terminate all sessions and network connections when non-local maintenance is completed.",
+      "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\nThe operating system needs to ensure all sessions and network connections are terminated when non-local maintenance is completed.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28842",
+      "title": "The operating system must audit non-local maintenance and diagnostic sessions.",
+      "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, in order to conduct system diagnostics. \n\nFor traceability of maintenance, logging events associated with a non-local administrative access or diagnostic session must be performed.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28843",
+      "title": "The operating system must protect non-local maintenance sessions through the use of a strong authenticator tightly bound to the user.",
+      "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\nIdentification and authentication techniques used in the establishment of non-local maintenance and diagnostic sessions must be accomplished via strong authenticator (i.e., two factor authentication).",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28844",
+      "title": "The operating system must employ cryptographic mechanisms to protect the integrity and confidentiality of non-local maintenance and diagnostic communications.",
+      "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. To protect the integrity and confidentiality of non-local maintenance and diagnostics, all packets associated with these sessions must be encrypted.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28848",
+      "title": "The operating system must use cryptographic mechanisms to protect and restrict access to information on portable digital media.",
+      "description": "When data is written to portable digital media, such as thumb drives, floppy diskettes, compact disks, and magnetic tape, etc., there is risk of data loss. \n\nAn organizational assessment of risk guides the selection of media and associated information contained on the media requiring restricted access. \n\nOrganizations need to document in policy and procedures the media requiring restricted access, individuals authorized to access the media, and the specific measures taken to restrict access. 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 if accessed by other than authorized personnel. \n\nIn these situations, it is assumed the physical access controls where the media resides provide adequate protection. The employment of cryptography is at the discretion of the information owner/steward. \n\nWhen the organization has determined the risk warrants it, data written to portable digital media must be encrypted.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28852",
+      "title": "The operating system must employ cryptographic mechanisms to protect information in storage.",
+      "description": "When data is written to digital media, such as hard drives, mobile computers, external/removable hard drives, personal digital assistants, flash/thumb drives, etc., there is risk of data loss and data compromise. \n\nAn organizational assessment of risk guides the selection of media and associated information contained on the media requiring restricted access. Organizations need to document in policy and procedures the media requiring restricted access, individuals authorized to access the media, and the specific measures taken to restrict access. \n\nFewer 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 if accessed by other than authorized personnel. In these situations, it is assumed the physical access controls 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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28853",
+      "title": "The operating system must separate user functionality (including user interface services) from operating system management functionality.",
+      "description": "Operating system management functionality includes functions necessary to administer machine, network components, workstations, or servers, and typically requires privileged user access. \n\nThe separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, combinations of these methods, or other methods as appropriate. \n\nThis may include isolating the administrative interface on a different domain and with additional access controls.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28854",
+      "title": "The operating system must prevent the presentation of information system management-related functionality at an interface for general (i.e., non-privileged) users.",
+      "description": "Operating system management functionality includes functions necessary to administer the operating, network components, workstations, or servers, and typically requires privileged user access. \n\nThe separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, combinations of these methods, or other methods as appropriate.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28855",
+      "title": "The operating system must isolate security functions from nonsecurity functions.",
+      "description": "Operating system management functionality includes functions necessary to administer the operating, network components, workstations, or servers, and typically requires privileged user access. \n\nThe separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, combinations of these methods, or other methods as appropriate.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28856",
+      "title": "The operating system must isolate security functions enforcing access and information flow control from both non-security functions and from other security functions.",
+      "description": "The operating 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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28857",
+      "title": "The operating system must implement an information system isolation boundary to minimize the number of non-security functions included within the boundary containing security functions.",
+      "description": "The operating 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 operating system maintains a separate execution domain (e.g., address space) for each executing process.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28859",
+      "title": "The operating system must implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.",
+      "description": "The operating 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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28860",
+      "title": "The operating system must prevent unauthorized and unintended information transfer via shared system resources.",
+      "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) obtaining 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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28861",
+      "title": "The operating system must not share resources used to interface with systems operating at different security levels.",
+      "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) obtaining access to a shared system resource (e.g., registers, main memory, secondary storage) after the resource has been released back to the operating system. Shared resources include memory, input/output queues, and network interface cards.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28862",
+      "title": "The operating system must protect against or must limit the effects of the organization-defined or referenced types of Denial of Service attacks.",
+      "description": "A variety of technologies exist to limit, or in some cases, eliminate the effects of Denial of Service attacks. \n\nEmploying increased capacity combined with service redundancy may reduce the susceptibility to some Denial of Service attacks.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28863",
+      "title": "The operating system must restrict the ability of users to launch Denial of Service attacks against other information systems or networks.",
+      "description": "When it comes to Denial of Service attacks (DoS), most of the attention is paid to ensuring the systems and applications are not victims of these attacks. \n\nWhile it is true those accountable for systems want to ensure they are not affected by a DoS attack, they also need to ensure their systems are not used to launch such an attack against others. To that extent, a variety of technologies exist to limit, or in some cases, eliminate the effects of DoS attacks.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28864",
+      "title": "The operating system must manage excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of Denial of Service attacks.",
+      "description": "In the case of Denial of Service attacks, care must be taken when designing the operating system so as to ensure that the operating system makes the best use of system resources.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28865",
+      "title": "The operating system must limit the use of resources by priority.",
+      "description": "Priority protection helps prevent a lower-priority process from delaying or interfering with the operating system servicing any higher-priority process. Operating systems must limit potential high volume usage resources to protect against a Denial of Service.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28866",
+      "title": "The operating system must monitor and control communications at the external boundary of the information system and at key internal boundaries within the system.",
+      "description": "The operating system must monitor and control communications at the  boundary of the operating system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28868",
+      "title": "The operating system must prevent public access into an organization’s internal networks, except as appropriately mediated by managed interfaces employing boundary protection devices.",
+      "description": "Access into an organization’s internal network and to key internal boundaries must be tightly controlled and managed. In the case of the operating system, the key boundary may be the workstation on the public internet.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28869",
+      "title": "The operating system at managed interfaces must deny network traffic by default and must allow network traffic by exception (i.e., deny all, permit by exception).",
+      "description": "Access into an organizations internal network and to key internal boundaries must be tightly controlled and managed.  In the case of the operating system, the boundary may be the workstation on the public internet.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28870",
+      "title": "The operating system must prevent remote devices that have established a non-remote connection with the system from communicating outside of the communication path with resources in external networks.",
+      "description": "This control enhancement is implemented within the remote device (e.g., notebook/laptop computer) via configuration settings not configurable by the user of the 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 the 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, in effect allowing unauthorized external connections into the system. This is a split-tunneling requirement that can be controlled via the operating system by disabling interfaces.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28871",
+      "title": "The operating system must route organization-defined internal communications traffic to organization-defined external networks through authenticated proxy servers within the managed interfaces of boundary protection devices.",
+      "description": "A proxy server is designed to hide the identity of the client when making a connection to a server on the outside of its network.   This prevents any hackers on the outside of learning IP addresses within the private network. With a proxy acting as the mediator, the client does not interact directly with the servers it is connecting to—the proxy server is in the middle handling both sides of the session.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28872",
+      "title": "The operating system, at managed interfaces, must deny network traffic and must audit internal users (or malicious code) posing a threat to external information systems.",
+      "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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28882",
+      "title": "The operating system must connect to external networks or information systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security architecture.",
+      "description": "The operating system must ensure traffic flows through only managed interfaces. For operating systems on the perimeter of the network (e.g., laptops connecting remotely) this helps protect the data on the endpoint.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28885",
+      "title": "The operating system must enforce the number of characters changed when passwords are changed.",
+      "description": "Passwords need to be changed at specific policy based intervals.  \n\nIf the operating system allows the user to consecutively reuse extensive portions of their password when they change their password, the end result is a password that may be compromised if the old password was known or guessable.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28887",
+      "title": "The operating system must enforce password encryption for storage.",
+      "description": "Passwords need to be protected at all times and encryption is the standard method for protecting passwords while in storage so unauthorized users/processes cannot gain access.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28888",
+      "title": "The operating system must enforce password encryption for transmission.",
+      "description": "Passwords need to be protected at all times and encryption is the standard method for protecting passwords during transmission to ensure unauthorized users/processes do not gain access to them.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28889",
+      "title": "The operating system must enforce minimum password lifetime restrictions.",
+      "description": "Passwords need to be changed at specific policy based intervals, however if the information system or application allows the user to immediately and continually change their password then the password could be repeatedly changed in a short period of time defeating the organization’s policy regarding password reuse.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28890",
+      "title": "The operating system must check incoming communications to ensure the communications are coming from an authorized source and routed to an authorized destination.",
+      "description": "In the case of the operating system, the boundary may be the workstation on the public internet.\n\nIn order to thwart an attack the operating system must be able to ensure communications are coming from an authorized source and routed to an authorized destination.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28891",
+      "title": "The operating system must notify the user of the number of successful logins/accesses that occur during the organization-defined time period.",
+      "description": "Users need to be aware of activity that occurs regarding their  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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28892",
+      "title": "The operating system must implement host-based boundary protection mechanisms for servers, workstations, and mobile devices.",
+      "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. For the operating system, this requirement ensures the operating system either can natively support this requirement or has an application installed to support this requirement.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28893",
+      "title": "The operating system must notify the user of the number of unsuccessful login/access attempts that occur during organization-defined time period.",
+      "description": "Users need to be aware of activity that occurs regarding their  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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28894",
+      "title": "The operating system must isolate organization-defined key information security tools, mechanisms, and support components from other internal information system components via physically separate subnets with managed interfaces to other portions of the system.",
+      "description": "This is a physical separation requirement and is not applicable.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28895",
+      "title": "The operating system must notify the user of organization-defined security-related changes to the user’s account that occur during the organization-defined time period.",
+      "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 that requires the user be notified. In those instances where organizations define such events, the operating system must notify the affected user or users.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28896",
+      "title": "The operating system must route all networked, privileged accesses through a dedicated, managed interface for purposes of access control and auditing.",
+      "description": "Managed interfaces employing boundary protection must be used for operating systems when using privileged accesses.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28898",
+      "title": "The operating system must prevent discovery of specific system components (or devices) composing a managed interface.",
+      "description": "Allowing discovery of operating system resources, names, or components can lead to giving information to an attacker that may be used as an attack vector.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28899",
+      "title": "The operating system must prevent non-privileged users from circumventing malicious code protection capabilities.\n",
+      "description": " Malicious code protection software must be protected so as to prevent a non-privileged user or a 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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28900",
+      "title": "The operating system must support and maintain the binding of organization-defined security attributes to information in storage.",
+      "description": "Security attributes are abstractions representing the basic properties or characteristics of an entity (e.g., subjects, objects) with respect to safeguarding information. \n\nThese attributes are typically associated with internal data structures (e.g., records, buffers, files) within the information 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. \n\nThe term security label is often used to associate a set of security attributes with a specific information object as part of the data structure for that object (e.g., user access privileges, nationality, affiliation as contractor). \n\nThese attributes may be assigned during data processing however these assignments also need to be maintained while the data is in storage.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28901",
+      "title": "The operating system must update malicious code protection mechanisms only when directed by a privileged user.\n",
+      "description": "This is not applicable for operating systems.  This requirement would be for the malicious code protection application.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28902",
+      "title": "The operating system must employ automated mechanisms to enforce strict adherence to protocol format.",
+      "description": "Crafted packets not conforming to IEEE standards can be used by malicious people to exploit a host’s protocol stack to create a Denial of Service or force a device reset.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28903",
+      "title": "The operating system must support and maintain the binding of organization-defined security attributes to information in process.",
+      "description": "Security attributes are abstractions representing the basic properties or characteristics of an entity (e.g., subjects, objects) with respect to safeguarding information. \n\nThese attributes are typically associated with internal data structures (e.g., records, buffers, files) within the information 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. \n\nThe term security label is often used to associate a set of security attributes with a specific information object as part of the data structure for that object (e.g., user access privileges, nationality, affiliation as contractor).\n\nIn this case the security attributes are to be bound to the information in process.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28904",
+      "title": "The operating system must not allow users to introduce removable media into the information system.\n",
+      "description": "Malicious code is known to propagate via removable media such as floppy disks, USB or flash drives, and removable hard drives. \n\nIn order to prevent propagation and potential infection due to malware contained on removable media the operating system must be able to restrict and/or limit the use of removable media.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28905",
+      "title": "The operating system must fail securely in the event of an operational failure of a boundary protection device.",
+      "description": "Fail secure is a condition achieved by the operating system employing a set of information system mechanisms to ensure, in the event of an operational failure of a boundary protection device at a managed interface, the system does not enter into an unsecure state where security properties no longer hold.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28906",
+      "title": "The operating system must support and maintain the binding of organization-defined security attributes to information in transmission.",
+      "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) within the information 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. \n\nThe term security label is used to associate a set of security attributes with a specific information object as part of the data structure for that object (e.g., user access privileges, nationality, affiliation as contractor). A security label is defined as the means used to associate a set of security attributes with a specific information object as part of the data structure for the object.\n\nIn this case the security attributes are to be bound to the information in transmission.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28907",
+      "title": "The operating system must protect the integrity of transmitted information.",
+      "description": "Ensuring the integrity of transmitted information requires the operating system take feasible measures to employ transmission layer security.  This requirement applies to communications across internal and external networks. \n\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28908",
+      "title": "The operating system must automatically audit account modification.",
+      "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. \n\nAuditing of account modification is one method and best practice for mitigating this risk. A comprehensive account management process will ensure an audit trail which documents the modification of user accounts and, as required, notifies appropriate individuals.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28909",
+      "title": "The operating system must automatically audit account disabling actions.",
+      "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 affecting user accessibility and operating system processing, the operating system must audit account disabling actions and, as required, notify as required 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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28910",
+      "title": "The operating system must employ cryptographic mechanisms to recognize changes to information during transmission unless otherwise protected by alternative physical measures.",
+      "description": "Ensuring the integrity of transmitted information requires operating systems take measures to employ some form of cryptographic mechanism in order to recognize changes to information. This is usually achieved through the use of checksums, cryptographic hash, or message authentication.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28912",
+      "title": "The operating system must maintain the integrity of information during aggregation, packaging, and transformation in preparation for transmission.",
+      "description": "Ensuring the confidentiality of transmitted information requires the operating system take  measures in preparing information for transmission.  This can be accomplished via access control or encryption.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28913",
+      "title": "The operating system must automatically audit account termination.",
+      "description": "Accounts are utilized for identifying individual application users or for identifying the application processes themselves. When accounts are deleted, a Denial of Service could happen. The operating system must audit and notify, as required, to mitigate the Denial of Service risk.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28914",
+      "title": "The operating system must enforce approved authorizations for controlling the flow of information between interconnected systems in accordance with applicable policy.",
+      "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 the information. \nInformation 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. \n\nFlow control is based on the characteristics of the information and/or the information path.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28915",
+      "title": "The operating system must protect the confidentiality of transmitted information.",
+      "description": "Ensuring the confidentiality of transmitted information requires operating systems take feasible measures to employ transmission layer security. This requirement applies to communications across internal and external networks. \n\nWhen transmitting data, operating systems need to leverage transmission protection mechanisms, such as TLS, SSL, VPNs, or IPSEC.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28916",
+      "title": "The operating system must dynamically reconfigure security attributes in accordance with an identified security policy as information is created and combined.",
+      "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., data records, buffers, files) within the application 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. \n\nThe term security label is often used to associate a set of security attributes with a specific information object as part of the data structure for that object (e.g., user access privileges, nationality, affiliation as contractor). A security label is defined as the means used to associate a set of security attributes with a specific information object as part of the data structure for the object.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28918",
+      "title": "The operating system must employ cryptographic mechanisms to prevent unauthorized disclosure of information during transmission unless otherwise protected by alternative physical measures.",
+      "description": "Ensuring the confidentiality of transmitted information requires operating systems take feasible measures to employ transmission layer security. This requirement applies to communications across internal and external networks. \n\nWhen transmitting data, operating systems need to leverage transmission protection mechanisms, such as TLS, SSL, VPNs, or IPSEC.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28919",
+      "title": "The operating system must only allow authorized entities to change security attributes.",
+      "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. \n\nThe term security label is often used to associate a set of security attributes with a specific information object as part of the data structure for that object (e.g., user access privileges, nationality, affiliation as contractor). A security label is defined as the means used to associate a set of security attributes with a specific information object as part of the data structure for the object.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28920",
+      "title": "The organization must interconnect and configure individual intrusion detection tools into a system-wide intrusion detection system using common protocols.\n",
+      "description": "This requirement concerns network connection of devices and is not applicable to operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28921",
+      "title": "The operating system must maintain the confidentiality of information during aggregation, packaging, and transformation in preparation for transmission.",
+      "description": "Confidentiality of the data must be maintained to ensure unauthorized users or processes do not have access to it.  This can be accomplished via access control mechanisms or encryption.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28923",
+      "title": "The operating system must monitor inbound and outbound communications for unusual or unauthorized activities or conditions.\n",
+      "description": "This is not applicable for operating systems.  This requirement would be for the IDS/IPS device or application.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28925",
+      "title": "The operating system 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.",
+      "description": "This requirement applies to both internal and external networks. \n\nTerminating network connections associated with communications sessions means de-allocating associated TCP/IP address/port pairs at the operating system level.\n\nThe time period of inactivity may, as the organization deems necessary, be a set of time periods by type of network access or for specific accesses.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28926",
+      "title": "The operating system must provide a near real-time alert when any of the organization-defined list of compromise or potential compromise indicators occurs. ",
+      "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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28927",
+      "title": "The operating system must maintain the binding of security attributes to information with sufficient assurance that the information--attribute association can be used as the basis for automated policy actions.",
+      "description": "The term security label is often used to associate a set of security attributes with a specific information object as part of the data structure for that object (e.g., user access privileges, nationality, affiliation as contractor). A security label is defined as: the means used to associate a set of security attributes with a specific information object as part of the data structure for that object.\n\nSecurity 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) within the information 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. \n\nExamples of automated policy actions include automated access control decisions (e.g., Mandatory Access Control decisions), or decisions to release (or not release) information (e.g., information flows via cross domain systems).",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28929",
+      "title": "The operating system must establish a trusted communications path between the user and organization-defined security functions within the operating system.",
+      "description": "The user interface must provide an unspoofable and faithful communication channel between the user and any entity trusted to manipulate authorities on the user's behalf. \n\nA trusted path shall be employed for high-confidence connections between the security functions of the information system and the user (e.g., for login).",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28930",
+      "title": "The operating system must only allow authorized users to associate security attributes with information.",
+      "description": "The term security label is often used to associate a set of security attributes with a specific information object as part of the data structure for that object (e.g., user access privileges, nationality, affiliation as contractor). A security label is defined as the means used to associate a set of security attributes with a specific information object as part of the data structure for that object.\n\nSecurity 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) within the information 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. \n\nThroughout the course of normal usage, authorized users of operating systems handling sensitive data will have the need to associate security attributes with information. Operating systems maintaining the binding of organization defined security attributes to data must ensure that authorized users can associate security attributes with information.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28931",
+      "title": "The operating system must produce, control, and distribute symmetric cryptographic keys using NIST-approved or NSA-approved key management technology and processes.",
+      "description": "Cryptographic key management and establishment can be performed using manual procedures or automated mechanisms with supporting manual procedures. \n\nIn addition to being required for the effective operation of a cryptographic mechanism, effective cryptographic key management provides protections to maintain the availability of the information in the event of the loss of cryptographic keys by users.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28932",
+      "title": "The operating system must display security attributes in human-readable form on each object output from the system to system output devices to identify an organization-identified set of special dissemination, handling, or distribution instructions using organization-identified human readable, standard naming conventions.",
+      "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 information 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. \n\nThe term security label is often used to associate a set of security attributes with a specific information object as part of the data structure for that object (e.g., user access privileges, nationality, affiliation as contractor). A security label is defined as the means used to associate a set of security attributes with a specific information object as part of the data structure for the object.\n\nSecurity attributes need to be displayed in human readable form in order to determine how the data should be disseminated, handled, and what distribution instructions apply to the data. When applications generate or output data, the associated security attributes need to be displayed.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28934",
+      "title": "The operating system must produce, control, and distribute symmetric and asymmetric cryptographic keys using NSA-approved key management technology and processes.",
+      "description": "Cryptographic key management and establishment can be performed using manual procedures or automated mechanisms with supporting manual procedures. \n\nIn addition to being required for the effective operation of a cryptographic mechanism, effective cryptographic key management provides protections to maintain the availability of the information in the event of the loss of cryptographic keys by users.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28935",
+      "title": "The operating system must disable the use of organization-defined networking protocols within the operating system deemed to be nonsecure except for explicitly identified components in support of specific operational requirements.",
+      "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 nonsecure except for explicitly identified components in support of specific operational requirements.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28936",
+      "title": "The operating system must produce, control, and distribute asymmetric cryptographic keys using approved PKI Class 3 certificates or prepositioned keying material.",
+      "description": "Cryptographic key management and establishment can be performed using manual procedures or automated mechanisms with supporting manual procedures. \n\nIn addition to being required for the effective operation of a cryptographic mechanism, effective cryptographic key management provides protections to maintain the availability of the information in the event of the loss of cryptographic keys by users.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28937",
+      "title": "The operating system must prevent non-privileged users from circumventing intrusion detection and prevention capabilities.\n",
+      "description": "Intrusion detection and prevention capabilities must be architected and implemented 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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28938",
+      "title": "The operating system must notify an organization-defined list of incident response personnel (identified by name and/or by role) of suspicious events.\n",
+      "description": "This is not applicable for operating systems.  This requirement would be for the IDS/IPS device or application.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28939",
+      "title": "The operating system must produce, control, and distribute asymmetric cryptographic keys using approved PKI Class 3 or Class 4 certificates and hardware security tokens that protect the user’s private key.",
+      "description": "Cryptographic key management and establishment can be performed using manual procedures or automated mechanisms with supporting manual procedures. \n\nIn addition to being required for the effective operation of a cryptographic mechanism, effective cryptographic key management provides protections to maintain the availability of the information in the event of the loss of cryptographic keys by users.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28941",
+      "title": "The operating system must enforce the organization-defined time period during which the limit of consecutive invalid access attempts by a user is counted.",
+      "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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28942",
+      "title": "The operating system must protect information obtained from intrusion-monitoring tools from unauthorized access, modification, and deletion.\n",
+      "description": "Intrusion-monitoring tools can accumulate a significant amount of sensitive data; examples could include user account information and application data not related to the intrusion monitoring application itself. \n\nIntrusion monitoring tools also obtain information that is critical to conducting forensic analysis on attacks that occur within the network. This data may be sensitive in nature. Information obtained by intrusion monitoring applications in the course of evaluating network and system security needs to be protected.\n\nWhile this is an operating system requirement, the data collected may be in different files or locations depending upon the IDS/IPS product being used.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28943",
+      "title": "The operating system must implement required cryptographic protections using cryptographic modules that comply with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.",
+      "description": "Cryptography is only as strong as the encryption modules/algorithms that are employed to encrypt the data. \n\nUse of weak or un-tested encryption algorithms undermines the purposes of utilizing encryption to protect data.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28945",
+      "title": "The operating system must make provisions so encrypted traffic is visible to information system monitoring tools.\n",
+      "description": "This requirement is a combination of the network placement and the applications being used and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28946",
+      "title": "The operating system must use cryptography to protect the integrity of remote access sessions.",
+      "description": "Remote access is any access to an organizational operating system by a user (or an information system) communicating through an external, non-organization-controlled network. \n\nIf cryptography is not used to protect these sessions, then the session data traversing the remote connection could be intercepted and potentially modified. Cryptography provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection, thereby providing a degree of integrity. The encryption strength of mechanism is selected based on the security categorization of the information traversing the remote connection.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28947",
+      "title": "The operating system must analyze outbound communications traffic at the external boundary of the system (i.e., system perimeter).\n",
+      "description": "This is not applicable for the operating system. This is a network perimeter requirement.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28948",
+      "title": "The operating system must ensure remote sessions for accessing an organization-defined list of security functions and security-relevant information are audited.",
+      "description": "Remote access is any access to an organizational operating system by a user (or an information system) communicating through an external, non-organization-controlled network. \n\nRemote access to security functions (e.g., user management, audit log management, etc.) and security relevant information requires the activity be audited by the organization. Any operating system providing remote access must support organizational requirements to audit access or organization-defined security functions and security-relevant information.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28952",
+      "title": "The operating system must employ FIPS-validated cryptography to protect unclassified information.",
+      "description": "Cryptography is only as strong as the encryption modules/algorithms employed to encrypt the data. \n\nUse of weak or un-tested encryption algorithms undermines the purposes of utilizing encryption to protect data.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28953",
+      "title": "The operating system must employ NSA-approved cryptography to protect classified information.",
+      "description": "Cryptography is only as strong as the encryption modules/algorithms employed to encrypt the data. \n\nUse of weak or un-tested encryption algorithms undermines the purposes of utilizing encryption to protect data.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28954",
+      "title": "The operating system must provide the capability to capture/record and log all content related to a user session.",
+      "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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28955",
+      "title": "The operating system must employ FIPS-validated cryptography to protect information when it must be separated from individuals who have the necessary clearances, yet lack the necessary access approvals.",
+      "description": "Cryptography is only as strong as the encryption modules/algorithms employed to encrypt the data. \n\nUse of weak or un-tested encryption algorithms undermines the purposes of utilizing encryption to protect data.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28956",
+      "title": "The operating system must provide the capability to remotely view/hear all content related to an established user session in real time.",
+      "description": "If required at the operating system, this requirement will be fulfilled by an application.  This requirement is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28957",
+      "title": "The operating system must initiate session audits at system start-up.",
+      "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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28958",
+      "title": "The operating system must produce audit records containing sufficient information to establish the identity of any user/subject associated with the event.",
+      "description": "Operating system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control, includes time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28959",
+      "title": "The operating system must protect audit tools from unauthorized access.",
+      "description": "Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. \n\nDepending 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. \n\nIt is imperative that access to audit tools be controlled and protected from unauthorized access.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28960",
+      "title": "The operating system must employ FIPS-validate or NSA-approved cryptography to implement digital signatures.",
+      "description": "Cryptography is only as strong as the encryption modules/algorithms employed to encrypt the data. \n\nUse of weak or un-tested encryption algorithms undermines the purposes of utilizing encryption to protect data.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28961",
+      "title": "The operating system must protect audit tools from unauthorized modification.",
+      "description": "Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. \n\nDepending 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. \n\nIf the tools are compromised it could provide attackers with the capability to manipulate log data. It is imperative that audit tools be controlled and protected from unauthorized modification.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28962",
+      "title": "The operating system must protect the integrity and availability of publicly available information and applications.",
+      "description": "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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28963",
+      "title": "The operating system must protect audit tools from unauthorized deletion.",
+      "description": "Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. \n\nDepending 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.  If the tools are deleted, it would affect the administrator’s ability to access and review log data.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28964",
+      "title": "The operating system must prohibit remote activation of collaborative computing devices, excluding the organization-defined exceptions where remote activation is to be allowed.",
+      "description": "Collaborative computing devices include networked white boards, cameras, and microphones. Collaborative software examples include instant messaging or chat clients.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28966",
+      "title": "The operating system must block both inbound and outbound traffic between instant messaging clients, independently configured by end users and external service providers.",
+      "description": "Blocking restrictions do not include instant messaging services configured by an organization to perform an authorized function. \n\nThis requirement specifies blocking any external instant messaging clients not configured and managed by the organization.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28969",
+      "title": "The operating system must associate security attributes with information exchanged between information systems.\n",
+      "description": "When data is exchanged between information systems, the security attributes associated with the data needs to be maintained.  \n\nSecurity attributes are an abstraction representing the basic properties or characteristics of an entity with respect to safeguarding information; typically associated with internal data structures (e.g., records, buffers, files) within the operating system and 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. \n\nSecurity attributes may be explicitly or implicitly associated with the information contained within the information system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28970",
+      "title": "The operating system must validate the integrity of security attributes exchanged between systems.\n",
+      "description": "When data is exchanged between information systems, the security attributes associated with the data needs to be maintained. \n\nSecurity attributes are an abstraction representing the basic properties or characteristics of an entity with respect to safeguarding information; typically associated with internal data structures (e.g., records, buffers, files) within the information system and 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. \n\nSecurity attributes may be explicitly or implicitly associated with the information contained within the information system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28971",
+      "title": "The operating system must issue or obtain public key certificates under an appropriate certificate policy from an approved service provider.",
+      "description": "For user certificates, each organization attains certificates from an approved, shared service provider, as required by OMB policy. \n\nFor federal agencies operating a legacy public key infrastructure cross-certified with the Federal Bridge Certification Authority at medium assurance or higher, this Certification Authority will suffice. \n\nThis control focuses on certificates with a visibility external to the information system and does not include certificates related to internal system operations, for example, application-specific time services.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28972",
+      "title": "The operating system must implement detection and inspection mechanisms to identify unauthorized mobile code.\n",
+      "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. \n\nMobile code technologies include Java, JavaScript, ActiveX, PDF, Postscript, Shockwave movies, Flash animations, and VBScript. Usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on organizational servers and mobile code downloaded and executed on individual workstations. ",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28973",
+      "title": "The operating system must ensure the development of mobile code to be deployed in information systems meets organization-defined mobile code requirements.\n",
+      "description": "This requirement is not applicable to operating systems as operating systems do not control the development of the code.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28974",
+      "title": "The operating system must limit privileges to change software resident within software libraries (including privileged programs).",
+      "description": "When dealing with change control issues, it should be noted that any changes to the hardware, software, and/or firmware components of the operating system can potentially have significant effects on the overall security of the system. \n\nOnly qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28975",
+      "title": "The operating system must prevent the download of prohibited mobile code.\n",
+      "description": "Decisions regarding the employment of mobile code within operating systems are based on the potential for the code to cause damage to the system if used maliciously. \n\nMobile code technologies include Java, JavaScript, ActiveX, PDF, Postscript, Shockwave movies, Flash animations, and VBScript. Usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on organizational servers and mobile code downloaded and executed on individual workstations.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28976",
+      "title": "The operating system must automatically implement organization-defined safeguards and countermeasures if security functions (or mechanisms) are changed inappropriately.",
+      "description": "Any changes to the hardware, software, and/or firmware components of the operating system can potentially have significant effects on the overall security of the system. \n\nAccordingly, only qualified and authorized individuals must be allowed to obtain access to operating system components for purposes of initiating changes, including upgrades and modifications.\n\nIn order to ensure a prompt response to unauthorized changes to application security functions or security mechanisms, organizations may define countermeasures and safeguards the operating system must undertake in the event these types of operating system changes occur.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28978",
+      "title": "The operating system must prevent the automatic execution of mobile code in organization-defined software applications and must require organization-defined actions prior to executing the code.\n",
+      "description": "Decisions regarding the employment of mobile code within operating systems are based on the potential for the code to cause damage to the system if used maliciously. \n\nMobile code technologies include Java, JavaScript, ActiveX, PDF, Postscript, Shockwave movies, Flash animations, and VBScript. \n\nUsage restrictions and implementation guidance apply to both the selection and use of mobile code installed on organizational servers and mobile code downloaded and executed on individual workstations.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28979",
+      "title": "The operating system uniquely must identify destination domains for information transfer.",
+      "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 the information. \n\nAttribution, e.g., the ability to attribute actions to certain individuals, is a critical component of a security concept of operations. The ability to identify source and destination points for information flowing in an information system, allows forensic reconstruction of events when required, and increases policy compliance by attributing policy violations to specific organizations/individuals.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28980",
+      "title": "The operating system uniquely must authenticate destination domains for information transfer.",
+      "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 the information. \n\nThe ability to identify source and destination points for information flowing in an information system, allows forensic reconstruction of events when required, and increases policy compliance by attributing policy violations to specific organizations/individuals. Means to enforce this enhancement include ensuring that the information system resolution labels distinguish between information systems and organizations, and between specific system components or individuals involved in preparing, sending, receiving, or disseminating information.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28982",
+      "title": "The operating system must track problems associated with the information transfer.",
+      "description": "When an operating system transfers data, there is the chance an error or problem with the data transfer may occur. The operating system needs to track failures and any problems encountered when performing data transfers, so problems can be identified and remediated. \n\nSome potential issues with a failed or problematic data transfer include leaving sensitive data in a processing queue indefinitely, partial or incomplete data transfers, and corrupted data transfers. Tracking problems with data transfers also serves to create a forensic record that can be retained to assist in investigations regarding the flow of data.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28983",
+      "title": "The information system must provide additional data origin and integrity artifacts along with the authoritative data the system returns in response to name/address resolution queries.\n",
+      "description": "This is a resolution issue and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28984",
+      "title": "The information system must reject or delay, as defined by the organization, network traffic generated above configurable traffic volume thresholds.",
+      "description": "This is a network traffic requirement and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28985",
+      "title": "The operating system, 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.\n",
+      "description": "This is a resolution issue and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28987",
+      "title": "The operating system must ensure unauthorized, security-relevant configuration changes detected are tracked.",
+      "description": "Configuration settings are the configurable security-related parameters of information technology products that are part of the information system. Security-related parameters are those parameters impacting the security state of the system including parameters related to meeting other security control requirements. \n\nSecurity-related parameters include registry settings; account, file, and directory settings (i.e., permissions); and settings for services, ports, protocols, and remote connections.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28988",
+      "title": "The information system 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",
+      "description": "This is a resolution issue and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28989",
+      "title": "The operating system must enforce password complexity by the number of special characters used.",
+      "description": "Password complexity, or strength, is a measure of the effectiveness of a password in resisting guessing and brute-force attacks. \n\nPassword complexity is one factor in determining how long it takes to crack a password. \n\nThe more complex the password is, the greater the number of possible combinations that need to be tested before the password is compromised. \n\nUse of a complex password helps to increase the time and resources required to compromise the password.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28991",
+      "title": "The information system must perform data origin authentication and data integrity verification on all resolution responses received whether or not local client systems explicitly request this service.\n",
+      "description": "This is a resolution issue and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28992",
+      "title": "The operating system must protect non-local maintenance sessions by separating the maintenance session from other network sessions with the information system by either physically separated communications paths or logically separated communications paths.",
+      "description": "This is a requirement that maintenance needs to be done on a separate interface or encrypted channel so as to segment maintenance activity from regular usage. When performing non-local maintenance, there is a possibility of the session being monitored and replayed to gain unauthorized access into a system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28993",
+      "title": "The operating system must take corrective actions, when unauthorized mobile code is identified.",
+      "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. \n\nMobile code technologies include Java, JavaScript, ActiveX, PDF, Postscript, Shockwave movies, Flash animations, and VBScript. Usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on organizational servers and mobile code downloaded and executed on individual workstations.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28994",
+      "title": "The information systems that collectively provide name/address resolution service for an operating system must be fault-tolerant.\n",
+      "description": "This is a resolution issue and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28996",
+      "title": "The information system, when operating as part of a distributed, hierarchical namespace, must provide the means to enable verification of a chain of trust among parent and child domains (if the child supports secure resolution services).",
+      "description": "This is a resolution issue and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28997",
+      "title": "The operating system must recognize only system-generated session identifiers. ",
+      "description": "This requirement focuses on communications protection at the application session, versus network packet level and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28998",
+      "title": "The operating system must preserve organization-defined system state information in the event of a system failure.",
+      "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\nPreserving operating system state information helps to facilitate system restart and return to the operational mode of the organization with less disruption of mission/business processes.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-28999",
+      "title": "The operating system must employ malicious code protection mechanisms at workstations, servers, or mobile computing devices on the network to detect and eradicate malicious code transported by electronic mail, electronic mail attachments, web  accesses, removable media, or other common means.",
+      "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. \n\nThe requirement states that malicious code protection mechanisms, such as anti-virus, must be used on workstations, servers, and mobile computing devices. For the operating system, this means an anti-virus application must be installed.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29000",
+      "title": "The information systems collectively must provide name/address resolution service for an operating system implement internal/external role separation.\n",
+      "description": "This is a resolution issue and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29001",
+      "title": "The operating system must take organization-defined list of least disruptive actions to terminate suspicious events.",
+      "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 the operating system takes to terminate suspicious events. The least disruptive actions may include initiating a request for human response.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29002",
+      "title": "The operating system must provide mechanisms to protect the authenticity of communications sessions.\n",
+      "description": "This control focuses on communications protection at the application session, versus packet level and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29003",
+      "title": "The operating system must analyze outbound communications traffic at selected interior points within the system (e.g., subnets, subsystems), as deemed necessary, to discover anomalies.",
+      "description": "This is a networking component requirement and is not applicable to operating system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29004",
+      "title": "The operating system must invalidate session identifiers upon user logout or other session termination.\n",
+      "description": "This requirement focuses on communications protection at the application session, versus network packet level and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29005",
+      "title": "The operating system must employ a wireless intrusion detection system to detect attack attempts to the information system.",
+      "description": "This is a network monitoring traffic analysis requirement to deploy wireless intrusion detection system. This is not applicable for operating systems.\n\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29006",
+      "title": "The information system must provide a readily observable logout capability whenever authentication is used to gain access to web pages.\n",
+      "description": "Since this requirement is specific for web pages, it is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29007",
+      "title": "The operating system must employ a wireless intrusion detection system to detect potential compromises/breaches to the information system.",
+      "description": "This is a network monitoring traffic analysis requirement to deploy wireless intrusion detection system. This is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29008",
+      "title": "The operating system must generate a unique session identifier for each session.\n",
+      "description": "This requirement focuses on communications protection at the application session, versus network packet level and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29009",
+      "title": "The operating system must verify the correct operation of security functions in accordance with organization-defined conditions and in accordance with organization-defined frequency (if periodic verification).\n",
+      "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 operating system to exhibit the desired security behavior or satisfy a security property for example, successful login triggers an audit entry.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29010",
+      "title": "The operating system must generate unique session identifiers with organization-defined randomness requirements.\n",
+      "description": "This requirement focuses on communications protection at the application session, versus network packet level and is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29011",
+      "title": "The operating  system must provide notification of failed automated security tests.\n",
+      "description": "The need to verify security functionality applies to all security functions. \n\nFor those security functions unable to execute automated self-tests the organization either implements compensating security controls or explicitly accepts the risk of not performing the verification as required. Upon detection of security function anomalies or failure of automated self-tests, the operating system must respond in accordance with organization-defined responses and alternative actions.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29012",
+      "title": "The operating system must fail to an organization-defined known-state for organization-defined types of failures.\n",
+      "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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29013",
+      "title": "The operating system must provide automated support for the management of distributed security testing.\n",
+      "description": "The need to verify security functionality applies to all security functions.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29014",
+      "title": "The operating system must respond to security function anomalies in accordance with organization-defined responses and alternative action(s).",
+      "description": "The need to verify security functionality applies to all security functions. \n\nFor those security functions unable to execute automated self-tests the organization either implements compensating security controls or explicitly accepts the risk of not performing the verification as required. Information system transitional states include startup, restart, shutdown, and abort.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29015",
+      "title": "The operating system must employ malicious code protection mechanisms at workstations, servers, or mobile computing devices on the network to detect and take action on unsolicited messages transported by electronic mail, electronic mail attachments, web access, removable media, or other common means.",
+      "description": "This is not applicable for operating systems. This requirement would be for the malicious code protection application.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29016",
+      "title": "The operating system must detect unauthorized changes to software and information.\n",
+      "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.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29018",
+      "title": "The information system must include components proactively seeking to identify web-based malicious code. ",
+      "description": "This is an application specific requirement is not applicable for operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29019",
+      "title": "The operating system must protect the confidentiality and integrity of information at rest.\n",
+      "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 operating system must ensure the data being written to these devices is protected. In most cases, this is done via encryption.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29020",
+      "title": "The operating system must protect the integrity of information during the processes of data aggregation, packaging, and transformation in preparation for transmission.\n",
+      "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 operating system take steps to validate and assure the integrity of data while at these stages of processing.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29021",
+      "title": "The operating system at organization-defined information system components must load and execute the operating environment from hardware-enforced, read-only media.\n",
+      "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. Hardware-enforced, read-only media includes CD-R/DVD-R disk drives. Use of non-modifiable storage ensures the integrity of the software program from the point of creation of the read-only image.\n\nFor this requirement, the operating environment is the operating system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29023",
+      "title": "The operating system at organization-defined information system components must load and execute organization-defined applications from hardware-enforced, read-only media.\n",
+      "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 includes  CD-R/DVD-R disk drives.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29024",
+      "title": "The operating system must employ malicious code protection mechanisms at operating system entry and exit points to detect and take action on unsolicited messages transported by electronic mail, electronic mail attachments, web accesses, removable media or other  common means.\n",
+      "description": "This is not applicable for operating systems.  This requirement would be for the malicious code protection application.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29025",
+      "title": "The operating system must update spam protection mechanisms (including signature definitions) when new releases are available in accordance with organizational configuration management policy and procedures.\n",
+      "description": "This is an email requirement and is not applicable to operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29026",
+      "title": "The information system must automatically update spam protection mechanisms (including signature definitions).\n",
+      "description": "This is an email requirement and is not applicable to operating system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29027",
+      "title": "The operating system must enforce one or more organization-defined nondiscretionary access control policies over an organization-defined set of users and resources.",
+      "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) within the operating system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29029",
+      "title": "The operating system must employ organization-defined information system components with no writeable storage that are persistent across component restart or power on/off.\n",
+      "description": "Organizations may require operating systems to be non-modifiable or to be stored and executed on non-writeable storage. Use of non-modifiable storage ensures the integrity of the program from the point of creation of the read-only image and eliminates the possibility of malicious code insertion.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29030",
+      "title": "The operating system must prevent access to organization-defined security-relevant information except during secure, non-operable system states.",
+      "description": "Security-relevant information is any information within the information system potentially impacting the operation of security functions in a manner that could result in failure to enforce the system security policy or maintain isolation of code and data. Organizations may define specific security relevant information requiring protection.\n\nFiltering rules for routers and firewalls, cryptographic key management information, key configuration parameters for security services, and access control lists are examples of security-relevant information. \n\nSecure, 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). \n\nAccess to these types of data is to be prevented unless the system is in a maintenance mode or has otherwise been brought off-line. The goal is to minimize the potential that a security configuration or data may be dynamically and perhaps surreptitiously overwritten or changed (without going through a formal system change process documenting the changes).\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29031",
+      "title": "The operating system must install software update automatically.\n",
+      "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. Organizations (including any contractor to the organization) are required to 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 expeditiously.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29032",
+      "title": "The operating system must employ automated mechanisms or must have an application installed that on an organization-defined frequency  determines the state of information system components with regard to flaw remediation.\n",
+      "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. \n\nThis role is usually assigned to patch management software deployed in order to track the number of systems installed in the network, as well as, the types of software installed on these systems, the corresponding versions and the related flaws that require patching. \n\nFrom an operating system requirement perspective, the operating system must perform this or there must be an application installed performing this function.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29034",
+      "title": "The operating system must support automated patch management tools to facilitate flaw remediation to organization-defined information system components.\n",
+      "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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29035",
+      "title": "The operating system must enforce information flow control using explicit security attributes on information, source, and destination objects as a basis for flow control decisions.",
+      "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 the information. \n\nExamples of flow control restrictions include: keeping export controlled information from being transmitted in the clear to the Internet; and blocking outside traffic claiming to be from within the organization and not passing any web requests to the Internet that are not from the internal web proxy. 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\nInformation flow enforcement mechanisms compare security attributes on all information (data content and data structure), source and destination objects, and respond appropriately (e.g., block, quarantine, alert administrator) when the mechanisms encounter information flows not explicitly allowed by the information flow policy. Information flow enforcement using explicit security attributes can be used, for example, to control the release of certain types of information.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29036",
+      "title": "The operating system must have malicious code protection mechanisms at system entry and exit points to detect and eradicate malicious code transported by electronic mail, electronic mail attachments, web accesses, removable media, or other common means. ",
+      "description": "In order to minimize potential negative impact to the organization caused by malicious code, it is imperative that malicious code is identified and eradicated prior to entering protected enclaves via operating system entry and exit points. \n\nThe requirement states that AV and malware protection applications must be used at entry and exit points. For the operating system, this means an anti-virus application must be installed on machines that are the entry and exit points.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29037",
+      "title": "The operating system must enforce information flow control using protected processing domains (e.g., domain type-enforcement) as a basis for flow control decisions.",
+      "description": "Protected processing domains can be used to separate different data types.  The operating system must enforce information flow control to ensure information does not pass into domains that are not authorized to process it.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29038",
+      "title": "The operating system must update malicious code protection mechanisms (including signature definitions) whenever new releases are available in accordance with organizational configuration management policy and procedures.\n",
+      "description": "This is not applicable for operating systems.  This requirement would be for the malicious code protection application.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29040",
+      "title": "The operating system must configure malicious code protection mechanisms to perform periodic scans of the information system on an organization-defined frequency.\n",
+      "description": "This is not applicable for operating systems.  This requirement would be for the malicious code protection application.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29041",
+      "title": "The operating system must enforce dynamic information flow control based on policy that must allow or disallow information flows based upon changing conditions or operational considerations.",
+      "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 the information. \n\nThe operating system must enforce flow control decisions based upon changing conditions.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29042",
+      "title": "The operating system must 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",
+      "description": "This is not applicable for operating systems.  This requirement would be for the malicious code protection application.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29044",
+      "title": "The operating system must configure malicious code protection mechanisms to perform organization-defined action(s) in response to malicious code detection.\n",
+      "description": "This is not applicable for operating systems.  This requirement would be for the malicious code protection application.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29045",
+      "title": "The operating system must address the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the information system.\n",
+      "description": "This is not applicable for operating systems.  This requirement would be for the malicious code protection application.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29046",
+      "title": "The operating system must prevent encrypted data from bypassing content checking mechanisms.",
+      "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 the information. \n\nWhen data is encrypted, mechanisms designed to examine data content to detect attacks or malicious code are unable to accomplish this task unless they are capable of unencrypting the data.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29048",
+      "title": "The operating system must automatically update malicious code protection mechanisms, including signature definitions.\n",
+      "description": "This is not applicable for operating systems. This requirement would be for the malicious code protection application.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29050",
+      "title": "The operating system must enforce organization-defined limitations on the embedding of data types within other data types.",
+      "description": "Embedding of data within other data is often used for the clandestine transfer of data.  Embedding of data within other data can circumvent protections in place to protect information and systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29051",
+      "title": "The operating system must enforce information flow control on metadata.",
+      "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 the information. \n\nMetadata is defined as data providing information about one or more other pieces of data, such as, purpose of the data, author/creator of the data, network location of where data was created, and application specific data information.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29053",
+      "title": "The operating system must support organization-defined one-way flows using hardware mechanisms.",
+      "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 the information. \n\nThe operating system must be able to support the hardware mechanisms associated with one way data flows.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29055",
+      "title": "The operating system must enforce information flow control using organization-defined security policy filters as a basis for flow control decisions.",
+      "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 the information. \n\nOrganization-defined security policy filters may include, dirty word filters, file type checking filters, structured data filters, unstructured data filters, metadata content filters, and hidden content filters.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29056",
+      "title": "The operating system must provide the capability for a privileged administrator to enable/disable organization-defined security policy filters.",
+      "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 the information. \n\nOrganization-defined security policy filters may include: dirty word filters, file type checking filters, metadata content filters, and hidden content filters. \n\nIn order to effectively manage these filters, the operating system must provide the mechanism to enable/disable these filters.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29057",
+      "title": "The operating system must provide the capability for a privileged administrator to configure the organization-defined security policy filters to support different security policies.",
+      "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 the information. \n\nOrganization-defined security policy filters may include, dirty word filters, file type checking filters, metadata content filters, and hidden content filters. \n\nIn order to effectively manage these filters, the operating system must provide the mechanism to configure these filters.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29058",
+      "title": "The operating system must take organization-defined actions upon audit failure (e.g., shut down information system, overwrite oldest audit records, stop generating audit records).\n",
+      "description": "It is critical when a system is at risk of failing to process audit logs, as required, it detects and takes action 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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29059",
+      "title": "The operating system must implement separation of duties through assigned information system access authorizations.",
+      "description": "Separation of duties is a prevalent Information Technology control implemented at different layers of the information system, including the operating system and in applications. It serves to eliminate or reduce the possibility that a single user may carry out prohibited action. Separation of duties requires the person accountable for approving an action is not the same person who is tasked with implementing or carrying out the action. \n\nAdditionally, the person or entity accountable for monitoring the activity must be separate as well. \n\nExamples of separation of duties include: (i) mission functions and distinct information system support functions are divided among different individuals/roles; (ii) different individuals perform operating system support functions (e.g., system management, systems programming, configuration management, quality assurance and testing, network security); (iii) security personnel who administer access control functions do not administer audit functions; and (iv) different administrator accounts for different roles.\n\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29060",
+      "title": "The operating system must provide a warning when allocated audit record storage volume reaches an organization-defined percentage of maximum audit record storage capacity.\n",
+      "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. \n\nIf audit log capacity were to be exceeded then events that subsequently occur will not be recorded.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29061",
+      "title": "The operating system must provide a real-time alert when organization-defined audit failure events occur.\n",
+      "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. \n\nOrganizations must define audit failure events requiring an application to send an alarm. When those defined events occur, the application will provide a real-time alert to the appropriate personnel.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29062",
+      "title": "The information system must enforce configurable traffic volume thresholds representing auditing capacity for network traffic.\n",
+      "description": "This is not applicable for operating systems as network traffic monitoring is outside the scope of the operating system monitoring.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29063",
+      "title": "The operating system 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.",
+      "description": "This requirement is intended to limit exposure due to operating from within a privileged account or role. The inclusion of 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\nTo limit exposure and provide forensic history of activity when operating from within a privileged account or role, the operating system must support organizational requirements that users of information system accounts, or roles, with access to organization-defined list of security functions or security-relevant information, use non-privileged accounts, or roles, when accessing other (non-security) system functions.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29064",
+      "title": "To support audit review, analysis, and reporting the operating system must integrate audit review, analysis, and reporting processes to support organizational processes for investigation and response to suspicious activities. ",
+      "description": "This is not applicable to operating systems.  The data from the operating system will be used by an application which will meet the requirement. ",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29065",
+      "title": "The operating system must enforce the organization-defined limit of consecutive invalid access attempts by a user during the organization-defined time period.",
+      "description": "Anytime an authentication method is exposed, allowing for the utilization of an operating system, there is a risk that attempts will be made to obtain unauthorized access. \n\nTo defeat these attempts, organizations define the number of times a user account may consecutively fail a login attempt. The organization also defines the period of time in which these consecutive failed attempts may occur. \n\nBy 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",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29066",
+      "title": "Operating system must support the capability to centralize the review and analysis of audit records from multiple components within the system.\n",
+      "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. \n\nSegregation of logging data to multiple disparate computer systems is counterproductive and makes log analysis and log event alarming difficult to implement and manage, particularly when the system or application has multiple logging components written to different locations or systems.\n\nTo support the centralized capability, the operating system must be able to provide the information in a format that can be extracted and used allowing the application performing the centralization of the log records to meet this requirement.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29067",
+      "title": "The operating system must support  an audit reduction capability.\n",
+      "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\nAn audit reduction capability provides support for near real-time audit review and analysis requirements and after-the-fact investigations of security incidents.   \n\nThe operating system must integrate into the information system or organizational audit reduction capability.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29068",
+      "title": "The operating system, 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.",
+      "description": "Anytime an authentication method is exposed to allow for the utilization of an operating system, there is a risk that attempts will be made to obtain unauthorized access. \n\nTo defeat these attempts, organizations define the number of times a user account may consecutively fail a login attempt. The organization also defines the period of time in which these consecutive failed attempts may occur. \n\nBy 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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29069",
+      "title": "The operating system audit records must be able to be used by a report generation capability.\n",
+      "description": "Logging the actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or to simply identify a network element that has been configured improperly. 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. \n\nThe operating system audit records must be able to be consumed by the audit report generation capability.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29070",
+      "title": "The operating system must display the DoD approved system use notification message or banner before granting access to the system.",
+      "description": "The operating system is required to display the DoD approved system use notification message or banner before granting access to the system.  This ensures all the legal requirements are met as far as auditing and monitoring are concerned.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29071",
+      "title": "The operating system must retain the notification message or banner on the screen until users take explicit actions to logon for further access.",
+      "description": "To establish acceptance of system usage policy, a click-through banner at operating system logon is required. The banner must prevent further activity on the application unless and until the user executes a positive action to manifest agreement by clicking the indicated acceptance.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29072",
+      "title": "The operating system must provide the capability to automatically process audit records for events of interest based upon selectable, event criteria.\n",
+      "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\nThis is generally accomplished by removing records generated by specified classes of events, such as records generated by nightly backups. \n\nAn audit reduction capability provides support for near real-time audit review and analysis based on policy requirements regarding what must be audited on the system and after-the-fact investigations of security incidents. \n\nAudit reduction and reporting tools do not alter original audit records.\n\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29073",
+      "title": "The operating system, upon successful logon, must display to the user the date and time of the last logon (access).",
+      "description": "Users need to be aware of activity that occurs regarding their  account. Providing users with information regarding the date and time of their last successful login allows the user to determine if any unauthorized activity has occurred and gives them an opportunity to notify administrators.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29074",
+      "title": "The operating system, upon successful logon/access, must display to the user the number of unsuccessful logon/access attempts since the last successful logon/access.",
+      "description": "Users need to be aware of activity that occurs regarding their  account. Providing users with information regarding the number of unsuccessful attempts that were 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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29075",
+      "title": "The operating system must use internal system clocks to generate time stamps for audit records.\n",
+      "description": "Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. \n\nTime stamps generated by the information system shall include both date and time. The time may be expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29076",
+      "title": "The operating system must check the validity of information inputs.\n",
+      "description": "Invalid user input occurs when a user inserts data or characters the system is unprepared to process that data. This results in unanticipated behavior that could lead to a compromise.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29077",
+      "title": "The operating system must synchronize internal information system clocks on an organization-defined frequency with an organization-defined authoritative time source.\n",
+      "description": "Determining the correct time a particular application event occurred on a system is critical when conducting forensic analysis and investigating system events.  \n\nSynchronization of system clocks is needed in order to correctly correlate the timing of events that occur across multiple systems. To meet this requirement the organization will define an authoritative time source and frequency to which each system will synchronize its internal clock.  \n\nAn example is utilizing the NTP protocol to synchronize with centralized NTP servers. Time stamps generated by the information system shall include both date and time. The time may be expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29078",
+      "title": "The operating system must limit the number of concurrent sessions for each  account to an organization-defined number of sessions.",
+      "description": "Limiting the number of allowed users and sessions per user can limit risks related to Denial of Service attacks. The organization may define the maximum number of concurrent sessions for an information system account globally, by account type, by account, or a combination thereof. \n\nThis requirement addresses concurrent sessions for a single information system account and does not address concurrent sessions by a single user via multiple  accounts.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29079",
+      "title": "The operating system must protect audit information from unauthorized read access.\n",
+      "description": "If audit data were to become compromised then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult if not impossible to achieve. \n\nTo ensure the veracity of audit data the operating system  must protect audit information from unauthorized access.  \n\nThis requirement can be achieved through multiple methods which will depend upon system architecture and design.  Some commonly employed methods include ensuring log files have the proper file system permissions utilizing file system protections and limiting log data location. \n\nAudit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29080",
+      "title": "The operating system must retain the session lock until the user reestablishes access using established identification and authentication procedures.",
+      "description": "A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the system but does not want to log out because of the temporary nature of the absence. \n\nOnce invoked, the session lock shall remain in place until the user re-authenticates. No other system activity aside from re-authentication can unlock the system.\n\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29081",
+      "title": "The operating system must protect audit information from unauthorized modification.\n",
+      "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\nTo ensure the veracity of audit data the operating system  must protect audit information from unauthorized modification.  \n\nAudit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29082",
+      "title": "The operating system must initiate a session lock after the organization-defined time period of inactivity.",
+      "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  system but does not log out because of the temporary nature of the absence. \n\nThe organization defines the period of inactivity to pass before a session lock is initiated, so this must be configurable.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29083",
+      "title": "The operating system must protect audit information from unauthorized deletion.\n",
+      "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\nTo ensure the veracity of audit data the operating system must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods which will depend upon system architecture and design. \n\nAudit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit information system activity.\n\n\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29084",
+      "title": "The operating system must produce audit records on hardware-enforced, write-once media.\n",
+      "description": "The protection of audit records from unauthorized or accidental deletion or modification requires the operating system produce audit records on hardware-enforced write-once media.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29085",
+      "title": "The operating system must provide the capability for users to directly initiate session lock mechanisms.",
+      "description": "A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the  system but does not want to log out because of the temporary nature of the absence. \n\nRather than be forced to wait for a period of time to expire before the user session can be locked, the operating system needs to provide users with the ability to manually invoke a session lock so users may secure their account should the need arise for them to temporarily vacate the immediate physical vicinity.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29086",
+      "title": "The operating system must protect against an individual falsely denying having performed a particular action.\n",
+      "description": "Non-repudiation of actions taken is required in order to maintain  integrity. \n\nNon-repudiation protects individuals against later claims by an author of not having updated a particular file, invoked a specific command, or copied a specific file.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29087",
+      "title": "The operating system session lock mechanism, when activated on a device with a display screen, must place a publicly viewable pattern onto the associated display, hiding what was previously visible on the screen.",
+      "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  system but does not log out because of the temporary nature of the absence. \n\nThe session lock will also include an obfuscation of the display screen to prevent other users from reading what was previously displayed.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29088",
+      "title": "The operating system must provide audit record generation capability for the auditable events defined in at the organizational level for the organization-defined information system components.\n",
+      "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, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29089",
+      "title": "The operating system must employ automated mechanisms to facilitate the monitoring and control of remote access methods.",
+      "description": "Remote network access is accomplished by leveraging common communication protocols and establishing a remote connection.   \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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29090",
+      "title": "The operating system must allow designated organizational personnel to select which auditable events are to be audited by the operating system.\n",
+      "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).  \n\nOrganizations will define the organizational personal accountable for selecting auditable events.  The operating system must allow the designated personnel to select the items to be audited.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29091",
+      "title": "The operating system must generate audit records for the selected list of auditable events as defined in DoD list of events.\n",
+      "description": "The list of audited events is the set of events for which audits are to be generated. \n\nThis 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",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29092",
+      "title": "The operating system must use cryptography to protect the confidentiality of remote access sessions.",
+      "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\nUsing cryptography ensures confidentiality of the remote access connections.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29093",
+      "title": "The operating system must support the capability to compile audit records from multiple components within the system into a system-wide (logical or physical) audit trail that is time-correlated to within organization-defined level of tolerance.\n",
+      "description": "Audit generation and audit records can be generated from various components within the information system. 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\nThe events that occur must be time-correlated on order to conduct accurate forensic analysis.  In addition, the correlation must meet a certain tolerance criteria.  \n\nThe operating system must be able to have audit events correlated to the level of tolerance determined by the organization.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29094",
+      "title": "The operating system must monitor for unauthorized connections of mobile devices to organizational information systems.",
+      "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\nOrganization-controlled mobile devices include those devices for which the organization has the authority to specify and the ability to enforce specific security requirements.\n\nUsage restrictions and implementation guidance related to mobile devices include, configuration management, device identification and authentication, implementation of mandatory protective software (e.g., malicious code detection, firewall), scanning devices for malicious code, updating virus protection software, scanning for critical software updates and patches, conducting primary operating system (and possibly other resident software) integrity checks, and disabling unnecessary hardware (e.g., wireless, infrared).\n\nIn order to detect unauthorized mobile device connections, organizations must first identify and document what mobile devices are authorized.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29095",
+      "title": "The operating system, for PKI-based authentication must validate certificates by constructing a certification path with status information to an accepted trust anchor.\n",
+      "description": "A trust anchor is an authoritative entity represented via a public key and associated data. \n\nWhen there is a chain of trust, usually the top entity to be trusted becomes the trust anchor, for example, a Certification Authority (CA). A certification path starts with the Subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. \n\nPath validation is necessary for a relying party to make an informed trust decision when presented with any certificate that is not already explicitly trusted. \n\n\nStatus information for certification paths includes, certificate revocation lists or online certificate status protocol responses.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29096",
+      "title": "The operating system must disable information system functionality that  provides the capability for automatic execution of code on mobile devices without user direction.",
+      "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\nAuto execution vulnerabilities can result in malicious programs being automatically executed. Examples of information system functionality providing the capability for automatic execution of code are Auto Run and Auto Play. Auto Run and Auto Play are components of the Microsoft Windows operating system that dictate what actions the system takes when a drive is mounted. This requirement is designed to address vulnerabilities that arise when mobile devices such as USB memory sticks or other mobile storage devices are automatically mounted and applications are automatically invoked without user knowledge or acceptance.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29097",
+      "title": "The operating system, for PKI-based authentication must enforce authorized access to the corresponding private key.\n",
+      "description": "The cornerstone of the PKI is the private key used to encrypt or digitally sign information.  \n\nIf the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and can pretend to be the authorized user. \n\nBoth the holders of a digital certificate and the issuing authority must protect the computers, storage devices or whatever they use to keep the private keys.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29098",
+      "title": "The operating system, for PKI-based authentication must map the authenticated identity to the user account.\n",
+      "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.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29099",
+      "title": "The operating system must employ automated mechanisms to enable authorized users to make information sharing decisions based on access authorizations of sharing partners and access restrictions on information to be shared.",
+      "description": "Depending on the information sharing circumstance, the sharing partner may be defined at the individual, group, or organization level and information may be defined by specific content, type, or security categorization.\n\nThe operating system must restrict data in some manner (e.g., privileged medical, contract-sensitive, proprietary, personally identifiable information, special access programs/compartments) and must provide the capability to automatically enable authorized users to make information sharing decisions based upon access authorizations.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29100",
+      "title": "The operating system must enforce password complexity by the number of upper case characters used.\n",
+      "description": "Password complexity or strength is a measure of the effectiveness of a password in resisting guessing and brute-force attacks. \n\nPassword complexity is one factor of several that determine how long it takes to crack a password. The more complex the password is, the greater the number of possible combinations that need to be tested before the password is compromised. \n\nUse of a complex password helps to increase the time and resources required to compromise the password.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29101",
+      "title": "The operating system must identify potentially security-relevant error conditions.\n",
+      "description": "The structure and content of error messages need to be carefully considered by the organization. The extent to which the operating system is able to identify and handle error conditions is guided by organizational policy and operational requirements.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29102",
+      "title": "The operating system must enforce password complexity by the number of lower case characters used.\n",
+      "description": "Password complexity, or strength, is a measure of the effectiveness of a password in resisting guessing and brute-force attacks. \n\nPassword complexity is one factor of several that determine how long it takes to crack a password. \n\nThe more complex the password is, the greater the number of possible combinations that need to be tested before the password is compromised. \n\nUse of a complex password helps to increase the time and resources required to compromise the password.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29103",
+      "title": "The operating system must produce audit records containing sufficient information to establish what type of events occurred.",
+      "description": "Operating system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29104",
+      "title": "The operating system must generate error messages providing information necessary for corrective actions without revealing organization-defined sensitive or potentially harmful information in error logs and administrative messages that could be exploited. ",
+      "description": "Any operating system providing too much information in error logs and in administrative messages to the screen, risks compromising the data and security of the structure and content of error messages needs to be carefully considered by the organization.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29105",
+      "title": "The operating system must produce audit records containing sufficient information to establish when (date and time) the events occurred.",
+      "description": "Operating system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.\n\nWithout sufficient information establishing where the audit events occurred, investigation into the cause of events is severely hindered.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29106",
+      "title": "The operating system must produce audit records containing sufficient information to establish where the events occurred.",
+      "description": "Operating system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked. \n\nWithout sufficient information establishing where the audit events occurred, investigation into the cause of events is severely hindered.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29107",
+      "title": "The operating system must produce audit records containing sufficient information to establish the sources of the events.",
+      "description": "Operating system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.\n\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29108",
+      "title": "The operating system must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.",
+      "description": "Operating system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked. \n\nSuccess and failure indicators ascertain the outcome of a particular event. As such, they also provide a means to measure the impact of an event and help authorized personnel to determine the appropriate response.\n\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29109",
+      "title": "The operating system must include organization-defined additional, more detailed information in the audit records for audit events identified by type, location, or subject.",
+      "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, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29110",
+      "title": "The operating system must support the requirement to centrally  manage the content of audit records generated by organization-defined information system components.",
+      "description": "Operating system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked. \n\nCentralized management of audit records and logs provides for efficiency in maintenance of records, as well as, the backup and archiving of those records. When organizations define application components that require requiring centralized audit log management, operating systems need to support the requirement.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29111",
+      "title": "The operating system must allocate audit record storage capacity.",
+      "description": "Operating system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.\n\nIt is imperative the operating system configured, allocate storage capacity to contain audit records.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29112",
+      "title": "The operating system must configure auditing to reduce the likelihood of storage capacity being exceeded.",
+      "description": "Operating system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.\n\nCare must be taken to evaluate that the audit records being produced do not exceed the storage capacity.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29113",
+      "title": "The operating system must alert designated organizational officials in the event of an audit processing failure.",
+      "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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29117",
+      "title": "The operating system must reveal error messages only to authorized personnel.\n",
+      "description": "If the operating system 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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29118",
+      "title": "The operating system must support the requirement  that organizations, if an information system component failure is detected must activate an organization-defined alarm and/or automatically shuts down the operating system.\n",
+      "description": "Predictable failure prevention requires organizational planning to address system failure issues. If a subsystem of the operating system, hardware, or the operating system itself, is key to maintaining systems and security fails to function, the system could continue operating in an insecure state. The organization must be prepared for and the operating system must support capability that alarms for such conditions and/or automatically shuts down the operating system or the subsystem of the operating system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29119",
+      "title": "The operating system must associate the identity of the information producer with the information.\n",
+      "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.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29120",
+      "title": "The operating system must validate the binding of the information producer’s identity to the information.\n",
+      "description": "Validation of the binding between information and the information producer’s identity allows the operating system to recognize and appropriately handle information with altered identity bindings.  Without validation, forged identity bindings may not be recognized, undermining trust in the bindings. The validation of bindings can be achieved, for example, by the use of cryptographic checksums.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29121",
+      "title": "The operating system must maintain reviewer/releaser identity and credentials within the established chain of custody for all information reviewed or released.\n",
+      "description": "When it comes to data review and data release, there must be a correlation between the reviewed data and the person who performs the review. If the reviewer is a human or if the review function is automated but separate from the release/transfer function, the operating system associates the identity of the reviewer of the information to be released with the information and the information label.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29122",
+      "title": "The operating system must validate the binding of the reviewer’s identity to the information at the transfer/release point prior to release/transfer from one security domain to another security domain.\n",
+      "description": "This non-repudiation control enhancement is intended to mitigate the risk that information could be modified between review and transfer/release particularly when the transfer is occurring between security domains.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29124",
+      "title": "The operating system must invoke a system shutdown in the event of an audit failure, unless an alternative audit capability exists.\n",
+      "description": "It is critical when an operating 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. \n\nAudit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29125",
+      "title": "The operating system must employ automated mechanisms to alert security personnel of any organization-defined inappropriate or unusual activities with security implications.\n",
+      "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. \n\nAutomated alarming mechanisms provide the appropriate personnel with the capability to immediately respond and react to events categorized as unusual or having security implications that could be detrimental to system and/or organizational security.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29126",
+      "title": "The operating system must back up audit records on an organization-defined frequency onto a different system or media than the system being audited.\n",
+      "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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29127",
+      "title": "The operating system must use cryptographic mechanisms to protect the integrity of audit information.\n",
+      "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.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29128",
+      "title": "The operating system must protect the audit records resulting from non-local accesses to privileged accounts and the execution of privileged functions.\n",
+      "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.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29129",
+      "title": "The operating system must produce a system-wide (logical or physical) audit trail composed of audit records in a standardized format.\n",
+      "description": "Audits records can be generated from various components within the operating system. 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",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29130",
+      "title": "The operating system must monitor for atypical usage of operating system accounts.\n",
+      "description": "Atypical account usage is behavior that is not part of normal usage cycles, e.g., accounts logging in after hours or on weekends.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29134",
+      "title": "The operating system must enforce an organization-defined  Discretionary Access Control (DAC) policy that must allow users to specify and control sharing by named individuals or groups of individuals, or by both.",
+      "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) in the operating system.  ",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29135",
+      "title": "The operating system must enforce approved authorizations for controlling the flow of information within the system in accordance with applicable policy.\n",
+      "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 the information.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29137",
+      "title": "The operating system, when transferring information between different security domains, must implement policy filters constraining data structure and content to organization-defined information security policy requirements. ",
+      "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 the information. \n\nExamples of constraints include ensuring: (i) character data fields only contain printable ASCII; (ii) character data fields only contain alpha-numeric characters; (iii) character data fields do not contain special characters; and (iv) maximum field sizes and file lengths are enforced based upon organization-defined security policy.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29138",
+      "title": "The operating system, when transferring information between different security domains, must detect unsanctioned information.\n",
+      "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 the information. \n\nActions to support this requirement include but are not limited to: checking all transferred information for malware; implementing dirty word list searches on transferred information; and applying the same protection measures to metadata (e.g., security attributes) that is applied to the information payload.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29139",
+      "title": "The operating system, when transferring information between different security domains, must prohibit the transfer of unsanctioned information in accordance with the security policy.\n",
+      "description": "Information flow control regulates where information is allowed to travel within an operating system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to the information. \n\nActions to support this requirement include but are not limited to: checking all transferred information for malware; implementing dirty word list searches on transferred information; and applying the same protection measures to metadata (e.g., security attributes) that is applied to the information payload.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29140",
+      "title": "The operating system must uniquely identify source domains for information transfer.\n",
+      "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 the information. \n\nThe ability to identify source and destination points for information flowing in an information system, allows forensic reconstruction of events when required, and increases policy compliance by attributing policy violations to specific organizations/individuals.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29141",
+      "title": "The operating system must uniquely authenticate source domains for information transfer.\n",
+      "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 the information. \n\nThe ability to identify source and destination points for information flowing in an information system, allows forensic reconstruction of events when required, and increases policy compliance by attributing policy violations to specific organizations/individuals.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29142",
+      "title": "The operating system must provide additional protection for mobile devices accessed via login by purging information from the device after organization-defined number of consecutive, unsuccessful login attempts to the mobile device.\n",
+      "description": "Mobile devices present additional risks related to attempted unauthorized access. If they are lost, stolen, or misplaced, attempts can be made to unlock the device by guessing the PIN. In order to address this risk, mobile devices shall provide additional protection enabling the device to automatically wipe itself clean and purge itself of any and all data. \n\nThis requirement applies only to mobile devices for which a login occurs (e.g., personal digital assistants, smart phones) and not to mobile devices accessed without a login, such as removable media. In certain situations, this requirement may not apply to mobile devices if the information on the device is encrypted with sufficiently strong encryption mechanisms, making purging unnecessary. The login is to the mobile device, not to any one account on the device. \n\nTherefore, a successful login to any account on the mobile device resets the unsuccessful login count to zero.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-29143",
+      "title": "The operating system for publicly accessible systems must display the system use information when appropriate, before granting further access.\n",
+      "description": "Requirement applies to publicly accessible systems.  System use notification messages can be implemented in the form of warning banners displayed when individuals log in to the information system. System 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",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30375",
+      "title": "The operating system must ensure the acquisition of mobile code to be deployed in information systems meets organization-defined mobile code requirements.",
+      "description": "This requirement is not applicable to operating systems as the acquisition of operating systems does not impact mobile code.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30376",
+      "title": "The operating system must prevent the execution of prohibited mobile code. ",
+      "description": "Decisions regarding the employment of mobile code within operating systems are based on the potential for the code to cause damage to the system if used maliciously. \n\nMobile code technologies include Java, JavaScript, ActiveX, PDF, Postscript, Shockwave movies, Flash animations, and VBScript. Usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on organizational servers and mobile code downloaded and executed on individual workstations.\n",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30377",
+      "title": "The operating system must enforce a Discretionary Access Control (DAC) policy that limits propagation of access rights.",
+      "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) in the operating system.  ",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30378",
+      "title": "The operating system must enforce a Discretionary Access Control (DAC) policy that includes or excludes access to the granularity of a single user.",
+      "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) in the operating system. \nThis requirement mandates the granularity of the access is at the user level.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30379",
+      "title": "The operating system must protect wireless access to the system using authentication.",
+      "description": "This is a network element check and does not apply to operating systems. ",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30380",
+      "title": "The operating system must protect wireless access to the system using encryption.\n",
+      "description": "This is a network element check and does not apply to the operating system. ",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30381",
+      "title": "The operating system must enforce requirements for the connection of mobile devices to operating systems.",
+      "description": "Wireless access introduces security risks which must be addressed through implementation of strict controls and procedures such as authentication, encryption, and defining what resources that can be accessed.  The organization will define the requirements for connection of mobile devices.  In order to ensure that the connection provides adequate integrity and confidentiality of the connection, the operating system must enforce these requirements.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30382",
+      "title": "The operating system must automatically terminate emergency accounts after an organization-defined time period for each type of account.",
+      "description": "When emergency accounts are created, there is a risk that the emergency account may remain in place and active after the need for the account no longer exists. To address this, in the event emergency accounts are required, accounts that are designated as temporary in nature must be automatically terminated after an organization-defined time period. Such a process and capability greatly reduces the risk that accounts will be misused, hijacked, or data compromised.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30383",
+      "title": "The operating system must notify, as required, appropriate individuals when accounts are created.",
+      "description": "Monitoring account creation is critical to ensure only appropriate personnel have access to the operating system.  This reduces the possibility a rogue account will be created.  In order to facilitate the monitoring, the operating system must notify designated personnel when an account is created.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30384",
+      "title": "The operating system must notify, as required, appropriate individuals when accounts are modified.",
+      "description": "Monitoring account modification is critical to ensure only appropriate personnel have access to the operating system.  This reduces the possibility that an account will be given more access than is intended.  In order to facilitate the monitoring, the operating system must notify designated personnel when an account is modified.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30385",
+      "title": "The operating system must notify, as required, appropriate individuals when account is disabled.",
+      "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 of a rogue administrator account that may be deleting traces of activity.  In order to facilitate the monitoring, the operating system must notify designated personnel when an account is disabled.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30386",
+      "title": "The operating system must notify, as required, appropriate individuals for account termination. ",
+      "description": "Monitoring account termination is critical to ensure a denial of service situation does not exist on the operating system.  An unexpected account termination can also be a sign of a rogue administrator account that may be deleting traces of activity.  In order to facilitate the monitoring, the operating system must notify designated personnel when an account is terminated.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30387",
+      "title": "The operating system must use cryptographic mechanisms to protect the integrity of audit tools.",
+      "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.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30388",
+      "title": "The operating system must employ automated mechanisms to centrally manage configuration settings.",
+      "description": "Configuration settings are the configurable security-related parameters of information technology products that are part of the information system. Security-related parameters are those parameters impacting the security state of the system including parameters related to meeting other security control requirements. Security-related parameters include, for example, registry settings; account, file, and directory settings (i.e., permissions); and settings for services, ports, protocols, and remote connections. Rather than visiting each system when making configuration changes, organizations must employ automated tools that can make changes across all systems. This greatly increases efficiency and manageability of applications in a large scale environment. ",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30389",
+      "title": "The operating system must employ cryptographic mechanisms to prevent unauthorized disclosure of information at rest unless otherwise protected by alternative physical measures.",
+      "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) within an organizational information system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30390",
+      "title": "The operating system must enforce requirements for remote connections to the information system.",
+      "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 operating system must enforce these requirements.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30391",
+      "title": "The operating system must route all remote accesses through managed access control points.",
+      "description": "This is a network control and is not applicable to operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30392",
+      "title": "The operating system must monitor for unauthorized remote connections to the information system on an organization-defined frequency.",
+      "description": "This is a network control and is not applicable to the operating system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30393",
+      "title": "The operating system must disable network access by components/devices or notifies designated organizational officials.",
+      "description": "This is a network function and is not applicable to operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30394",
+      "title": "The operating system must employ automated mechanisms to detect the presence of unauthorized software on organizational information systems and notify designated organizational officials in accordance with the organization-defined frequency.",
+      "description": "Malicious software can establish a base on individual desktops and servers.  Employing an automated mechanism to detect this type of software will aide in elimination of the software from the operating system.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30395",
+      "title": "The operating system must protect against unauthorized physical connections across the boundary protections implemented at an organization-defined list of managed interfaces.",
+      "description": "This is a network boundary check and is not applicable to operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30396",
+      "title": "The operating system must ensure the use of mobile code to be deployed in information systems meets organization-defined mobile code requirements. ",
+      "description": "This is an application requirement and does not apply to operating systems.",
+      "severity": "medium"
+    },
+    {
+      "id": "V-30397",
+      "title": "The operating system must enforce password complexity by the number of numeric characters used.",
+      "description": "Password complexity, or strength, is a measure of the effectiveness of a password in resisting guessing and brute-force attacks. \n\nPassword complexity is one factor of several that determine how long it takes to crack a password. \n\nThe more complex the password is, the greater the number of possible combinations that need to be tested before the password is compromised. \n\nUse of a complex password helps to increase the time and resources required to compromise the password.",
+      "severity": "medium"
+    }
+  ]
+}