Samsung Android OS 9 with Knox 3.x COBO Use Case KPE(Legacy) Deployment Security Technical Implementation Guide
This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: [email protected]
Details
Version / Release: V1R2
Published: 2019-10-01
Updated At: 2019-11-11 10:48:55
Compare/View Releases
Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Download
Filter
Severity | Open | Not Reviewed | Not Applicable | Not a Finding |
---|---|---|---|---|
Overall | 0 | 0 | 0 | 0 |
Low | 0 | 0 | 0 | 0 |
Medium | 0 | 0 | 0 | 0 |
High | 0 | 0 | 0 | 0 |
Vuln | Rule | Version | CCI | Severity | Title | Description | Status | Finding Details | Comments |
---|---|---|---|---|---|---|---|---|---|
SV-103041r1_rule | KNOX-09-000015 | CCI-000366 | MEDIUM | Samsung Android must be configured to prevent users from adding personal email accounts to the work email app. | If the user is able to add a personal email account (POP3, IMAP, EAS) to the work email app, it could be used to forward sensitive DoD data to unauthorized recipients. Restricting email account addition to the administrator or restricting email account ad | ||||
SV-103043r1_rule | KNOX-09-000045 | CCI-000366 | MEDIUM | Samsung Android must be configured to enforce the system application disable list. | The system application disable list controls user access to/execution of all core and preinstalled applications. Core application: Any application integrated into Samsung Android by Google or Samsung. Preinstalled application: Additional noncore appli | ||||
SV-103045r1_rule | KNOX-09-000075 | CCI-000366 | MEDIUM | Samsung Android must be configured to enforce an application installation policy by specifying an application whitelist that restricts applications by the following characteristics: list of digital signatures, list of package names. | The application whitelist, in addition to controlling the installation of applications on the mobile device, must control user access to/execution of all core and preinstalled applications, or the mobile device must provide an alternate method of restrict | ||||
SV-103047r1_rule | KNOX-09-000105 | CCI-000366 | MEDIUM | The Samsung Android whitelist must be configured to not include applications with the following characteristics: - back up mobile device data to non-DoD cloud servers (including user and application access to cloud backup services); - transmit mobile device diagnostic data to non-DoD servers; - voice assistant application if available when the mobile device is locked; - voice dialing application if available when the mobile device is locked; - allows synchronization of data or applications between devices | Requiring all authorized applications to be in an application whitelist prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the whitelist. Failure to configure an application whitelist properly could allow unaut | ||||
SV-103655r1_rule | KNOX-09-000135 | CCI-000366 | MEDIUM | Samsung Android must be configured to enforce an application installation policy by specifying one or more authorized application repositories, including [DoD-approved commercial app repository, MDM server, mobile application store]: - disallow unknown app installation sources. | Forcing all applications to be installed from authorized application repositories can prevent unauthorized and malicious applications from being installed and executed on mobile devices. Allowing such installations and executions could cause a compromise | ||||
SV-103659r1_rule | KNOX-09-000175 | CCI-000366 | MEDIUM | Samsung Android must be configured to enable the Knox audit log. | Audit logs enable monitoring of security-relevant events and subsequent forensics when breaches occur. They help identify attacks so that breaches can be prevented or limited in their scope, and they facilitate analysis to improve performance and security | ||||
SV-103661r1_rule | KNOX-09-000285 | CCI-000051 | MEDIUM | Samsung Android must be configured to not display the following notifications when the device is locked: all notifications. | Many mobile devices display notifications on the lock screen so that users can obtain relevant information in a timely manner without having to frequently unlock the phone to determine if there are new notifications. However, in many cases, these notifica | ||||
SV-103663r1_rule | KNOX-09-000355 | CCI-000366 | MEDIUM | Samsung Android device users must complete required training. | The security posture of Samsung devices requires the device user to configure several required policy rules on their device. User-Based Enforcement (UBE) is required for these controls. In addition, if the Authorizing Official (AO) has approved the use of | ||||
SV-103665r1_rule | KNOX-09-000365 | CCI-000366 | MEDIUM | Any accessory that provides wired networking capabilities to a Samsung Android device must not be connected to a DoD network (for example: DeX Station [LAN port], USB to Ethernet adapter, etc.). | If a Samsung Android device uses an accessory that provides wired networking capabilities, and that accessory is connected to a DoD network, then the Samsung Android device would also be connected to the DoD network. Samsung Android devices most likely ha | ||||
SV-103667r1_rule | KNOX-09-000375 | CCI-000205 | LOW | Samsung Android must be configured to enforce a minimum password length of six characters. | Password strength is a measure of the effectiveness of a password in resisting guessing and brute force attacks. The ability to crack a password is a function of how many attempts an adversary is permitted, how quickly an adversary can do each attempt, an | ||||
SV-103669r1_rule | KNOX-09-000395 | CCI-000366 | LOW | Samsung Android must be configured to not allow passwords that include more than two repeating or sequential characters. | Password strength is a measure of the effectiveness of a password in resisting guessing and brute force attacks. Passwords that contain repeating or sequential characters are significantly easier to guess than those that do not contain repeating or sequen | ||||
SV-103671r1_rule | KNOX-09-000405 | CCI-000057 | MEDIUM | Samsung Android must be configured to lock the display after 15 minutes (or less) of inactivity. | The screen lock timeout must be set to a value that helps protect the device from unauthorized access. Having a too-long timeout would increase the window of opportunity for adversaries who gain physical access to the mobile device through loss, theft, et | ||||
SV-103673r1_rule | KNOX-09-000435 | CCI-000044 | LOW | Samsung Android must be configured to not allow more than 10 consecutive failed authentication attempts. | The more attempts an adversary has to guess a password, the more likely the adversary will enter the correct password and gain access to resources on the device. Setting a limit on the number of attempts mitigates this risk. Setting the limit at 10 or les | ||||
SV-103675r1_rule | KNOX-09-000475 | CCI-000366 | MEDIUM | Samsung Android must be configured to disable trust agents. Note: This requirement is not applicable (NA) for specific biometric authentication factors included in the products Common Criteria evaluation. | Trust agents allow a user to unlock a mobile device without entering a passcode when the mobile device is, for example, connected to a user-selected Bluetooth device or in a user-selected location. This technology would allow unauthorized users to have ac | ||||
SV-103677r1_rule | KNOX-09-000505 | CCI-000366 | MEDIUM | Samsung Android must be configured to disable Face Recognition. Note: This requirement is not applicable (NA) for specific biometric authentication factors included in the products Common Criteria evaluation. | The Face Recognition feature allows a user's face to be registered and used to unlock the device. This technology would allow unauthorized users to have access to DoD sensitive data if compromised. By not permitting the use of non-password authentication | ||||
SV-103679r1_rule | KNOX-09-000585 | CCI-000366 | MEDIUM | Samsung Android must be configured to disable automatic completion of Samsung Internet browser text input. | The autofill functionality in the web browser allows the user to complete a form that contains sensitive information, such as personally identifiable information (PII), without previous knowledge of the information. By allowing the use of autofill functio | ||||
SV-103681r1_rule | KNOX-09-000645 | CCI-000366 | MEDIUM | Samsung Android must be configured to disable multi-user modes. | Multi-user mode allows multiple users to share a mobile device by providing a degree of separation between user data. To date, no mobile device with multi-user mode features meets DoD requirements for access control, data separation, and non-repudiation f | ||||
SV-103683r1_rule | KNOX-09-000665 | CCI-000366 | LOW | Samsung Android must be configured to disable all Bluetooth profiles except HSP (Headset Profile), HFP (HandsFree Profile), and SPP (Serial Port Profile). | Some Bluetooth profiles provide the capability for remote transfer of sensitive DoD data without encryption or otherwise do not meet DoD IT security policies and therefore should be disabled. SFR ID: FMT_SMF_EXT.1.1 #18h | ||||
SV-103685r1_rule | KNOX-09-000685 | CCI-000381 | MEDIUM | Samsung Android must be configured to disable USB mass storage mode. | USB mass storage mode enables the transfer of data and software from one device to another. This software can include malware. When USB mass storage is enabled on a mobile device, it becomes a potential vector for malware and unauthorized data exfiltratio | ||||
SV-103687r1_rule | KNOX-09-000715 | CCI-000366 | HIGH | Samsung Android must be configured to enable Knox Common Criteria (CC) Mode. | The Knox Platform for Enterprise (KPE) CC Mode feature is a superset of other features and behavioral changes that are mandatory MDFPP requirements. If CC Mode is not implemented, the device will not be operating in the NIAP-certified compliant CC mode of | ||||
SV-103689r1_rule | KNOX-09-000735 | CCI-000366 | MEDIUM | Samsung Android must be configured to disallow configuration of date and time. | Determining the correct time a particular application event occurred on a system is critical when conducting forensic analysis and investigating system events. Periodically synchronizing internal clocks with an authoritative time source is necessary to | ||||
SV-103691r1_rule | KNOX-09-000755 | CCI-000366 | MEDIUM | Samsung Android must be configured to enforce a USB host mode exception list. Note: This configuration allows DeX mode (with input devices), which is DoD-approved for use. | The USB host mode feature allows USB devices to connect to the device (e.g., USB flash drives, USB mouse, USB keyboard) using a micro USB-to-USB adapter cable. The USB host mode exception list allows selected USB devices to operate while disallowing other | ||||
SV-103693r1_rule | KNOX-09-000775 | CCI-000366 | MEDIUM | Samsung Android must be configured to disable the Share Via List feature. | e Share Via List feature allows the transfer of data between nearby Samsung devices via Android Beam, Wi-Fi Direct, Link Sharing, and Share to Device. If sharing were enabled, sensitive DoD data could be compromised. SFR ID: FMT_SMF_EXT.1.1 #47 | ||||
SV-103695r1_rule | KNOX-09-000805 | CCI-000366 | MEDIUM | Samsung Android must be configured to disallow outgoing beam. | Outgoing beam allows transfer of data through near field communication (NFC) and Bluetooth by touching two unlocked devices together. If it were enabled, sensitive DoD data could be transmitted. SFR ID: FMT_SMF_EXT.1.1 #47 | ||||
SV-103697r1_rule | KNOX-09-000825 | CCI-000366 | MEDIUM | Samsung Android must be configured to enforce that Wi-Fi Sharing is disabled. | Wi-Fi sharing is an optional configuration of Wi-Fi Tethering/Mobile Hotspot, which allows the device to share its Wi-Fi connection with other wirelessly connected devices instead of its mobile (cellular) connection. Wi-Fi sharing grants the "other" dev | ||||
SV-103699r1_rule | KNOX-09-000845 | CCI-000097 | MEDIUM | Samsung Android must be configured to not allow backup of [all applications, configuration data] to locally connected systems. | Data on mobile devices is protected by numerous mechanisms, including user authentication, access control, and cryptography. When the data is backed up to an external system (either locally connected or cloud-based), many if not all of these mechanisms ar | ||||
SV-103701r1_rule | KNOX-09-000865 | CCI-002338 | MEDIUM | Samsung Android must be configured to not allow backup of [all applications, configuration data] to remote systems. | Backups to remote systems (including cloud backup) can leave data vulnerable to breach on the external systems, which often offer less protection than the mobile operating system. Where the remote backup involves a cloud-based solution, the backup capabil | ||||
SV-103703r1_rule | KNOX-09-000925 | CCI-000381 | MEDIUM | Samsung Android must be configured to disable developer modes. | Developer modes expose features of the mobile operating system that are not available during standard operation. An adversary may leverage a vulnerability inherent in a developer mode to compromise the confidentiality, integrity, and availability of DoD s | ||||
SV-103705r1_rule | KNOX-09-000945 | CCI-002314 | MEDIUM | Samsung Android must be configured to enable authentication of personal hotspot connections to the device using a preshared key. | If no authentication is required to establish personal hotspot connections, an adversary may be able to use that device to perform attacks on other devices or networks without detection. A sophisticated adversary may also be able to exploit unknown system | ||||
SV-103707r1_rule | KNOX-09-000985 | CCI-001199 | HIGH | Samsung Android must be configured to enable encryption for data at rest on removable storage media or alternately, the use of removable storage media must be disabled. | The mobile operating system must ensure the data being written to the mobile device's removable media is protected from unauthorized access. If data at rest is unencrypted, it is vulnerable to disclosure. Even if the operating system enforces permissions | ||||
SV-103709r1_rule | KNOX-09-001055 | CCI-000366 | MEDIUM | Samsung Android must be configured to enable Certificate Revocation List (CRL) status checking. | A CRL allows a certificate issuer to revoke a certificate for any reason, including improperly issued certificates and compromise of the private keys. Checking the revocation status of the certificate mitigates the risk associated with using a compromised | ||||
SV-103711r1_rule | KNOX-09-001085 | CCI-000366 | MEDIUM | Samsung Android must have the DoD root and intermediate PKI certificates installed. | DoD root and intermediate PKI certificates are used to verify the authenticity of PKI certificates of users and web services. If the root and intermediate certificates are not available, an adversary could falsely sign a certificate in such a way that it | ||||
SV-103713r1_rule | KNOX-09-001165 | CCI-000048 | LOW | Samsung Android must be configured to display the DoD advisory warning message at startup or each time the user unlocks the device. | The mobile operating system is required to display the DoD-approved system use notification message or banner before granting access to the system that provides privacy and security notices consistent with applicable federal laws, Executive Orders, direct | ||||
SV-103715r1_rule | KNOX-09-001305 | CCI-000366 | HIGH | Samsung Android devices must have the latest available Samsung Android operating system installed. | Required security features are not available in earlier operating system versions. In addition, there may be known vulnerabilities in earlier versions. SFR ID: FMT_SMF_EXT.1.1 #47 | ||||
SV-103717r1_rule | KNOX-09-001345 | CCI-000366 | MEDIUM | Samsung Android must be configured to enable the Online Certificate Status Protocol (OCSP). | OCSP is a protocol for obtaining the revocation status of a certificate. It addresses problems associated with using Certificate Revocation Lists (CRLs). When OCSP is enabled, it is used prior to CRL checking. If OCSP could not get a decisive response abo | ||||
SV-103719r1_rule | KNOX-09-001375 | CCI-000366 | MEDIUM | Samsung Android must be configured to not enable Microsoft Exchange ActiveSync (EAS) password recovery. This requirement is not applicable if not using Microsoft EAS. | Password Recovery is a feature of Microsoft EAS. Exceeding the Password Attempts limit triggers the Lock screen to open a Password Recovery Mode. This feature must be disabled for a Samsung Android device to be in the NIAP-certified Common Criteria (CC) | ||||
SV-103721r1_rule | KNOX-09-001395 | CCI-000366 | MEDIUM | Samsung Android must be configured to set the password history with a length of 0. | Password History Length controls the number of most recently used Passwords stored in the Password History list. The Password History list does not store the actual value of the previous passwords but instead calculates the hash value of the passwords. | ||||
SV-103723r1_rule | KNOX-09-001425 | CCI-000366 | MEDIUM | Samsung Android must be configured to enforce that Secure Startup is enabled. This requirement is Not Applicable (NA) to Galaxy S10 (or newer) devices. | Secure Startup protects the Samsung Android device by requiring the user password to be entered before the device starts up. When Secure Startup is enabled, the default cryptographic keys are replaced with keys derived from the user password. This featu | ||||
SV-103725r2_rule | KNOX-09-001445 | CCI-000057 | MEDIUM | Samsung Android must be configured to enable a screen-lock policy that will lock the display after a period of inactivity. | The screen-lock timeout helps protect the device from unauthorized access. Devices without a screen-lock timeout provide an opportunity for adversaries who gain physical access to the mobile device through loss, theft, etc. Such devices are much more like | ||||
SV-103727r1_rule | KNOX-09-001485 | CCI-000366 | MEDIUM | Samsung Android must be configured to enforce that Strong Protection is enabled. This requirement is Not Applicable (NA) for devices older than Galaxy S10. | Strong Protection protects the Samsung Android devices that use File Based Encryption (FBE). When Strong Protection is enabled, the default cryptographic keys used to protect the user's apps and data are replaced with keys derived from the user password. | ||||