This is a potential security issue, you are being redirected to https://ncp.nist.gov
|Samsung Android OS 10.0||cpe:/o:google:android:10.0 (View CVEs)|
The Samsung Android OS 10 with Knox 3.x Security Technical Implementation Guide (STIG) provides the technical security policies, requirements, and implementation details for applying security concepts to Samsung Android 10 with Knox devices. The scope of this STIG covers only the Corporate Owned Personally Enabled (COPE) and Corporate Owned Business Only (COBO)1 use cases. The Bring Your Own Device (BYOD) and Choose Your Own Device (CYOD)2 use cases are not in scope for this STIG. In addition, the STIG supports two different Knox Platform for Enterprise (KPE) device deployment modes: Legacy managed device [KPE(LEGACY)] and fully managed device [KPE(AE)]. (See the Supplemental document for a detailed review of KPE). Note: It is expected that a future Samsung Android STIG will require all Department of Defense (DoD) deployments to use KPE(AE) only. It is recommended that DoD mobile service providers support KPE(AE) deployments to the maximum extent possible now. This STIG assumes that for the COPE use case, the technology used for data separation between work apps and data as well as personal apps and data has been certified by the National Information Assurance Partnership (NIAP) as compliant with the data separation requirements of the Protection Profile for Mobile Device Fundamentals (MDF)3. The configuration requirements and controls implemented by this STIG allow unrestricted activity by the user in downloading and installing personal apps and data (music, photos, etc.) with Authorizing Official (AO) approval and within any restrictions imposed by the AO for the COPE use case. See the STIG Supplemental document, Section 7, Configuration of the Personal Environment, for more information. This STIG assumes that if a DoD Wi-Fi network allows a Samsung mobile device to connect to the network, the Wi-Fi network complies with the Network Infrastructure STIG; for example, wireless access points and bridges must not be connected directly to the enclave network. With AO approval, this STIG allows two forms of biometric authentication for device unlock and work environment/workspace unlock: fingerprint and iris scan. Both fingerprint and iris scan biometric methods have successfully passed a Common Criteria evaluation using the Protection Profile for MDF v3.1 for the previous version of the Samsung platform (Android 8) and will be reviewed again during the Samsung Android 9 Common Criteria evaluation. Other Samsung-supported biometric methods are not approved, including facial recognition, intelligent scanning, and trust agents. Knox Mobile Enrollment (KME) enables large-scale Samsung Android device deployments so organizations can mobilize their employees with ease. KME allows DoD mobile service
This document is a requirement for all DoD administered systems and all systems connected to DoD networks. These requirements are designed to assist Security Managers (SMs), Information Assurance Managers (IAMs), Information Assurance Officers (IAOs), and System Administrators (SAs) with configuring and maintaining security controls.
DoD Directive (DoDD) 8500.1 and 8500.2
Comments or proposed revisions to this document should be sent via email to the following address: email@example.com. DISA will coordinate all change requests with the relevant DoD organizations before inclusion in this document. Approved changes will be made in accordance with the DISA maintenance release schedule.
updated to FINAL - 5/15/2020