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
Review the Samsung Android Workspace configuration settings to confirm that users are prevented from adding personal email accounts to the work email app. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the Workspace, do the following: 1. In the "Android account" group, verify that "account management" is configured to "disable for the work email app". 2. Provision the user's email account for the work email app. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Workspace". 3. Tap "Accounts". 4. Tap "Add account". 5. Verify that an account for the work email app cannot be added. If on the MDM console "account management" is not disabled for the work email app, or on the Samsung Android device the user can add an account for the work email app, this is a finding.
Configure Samsung Android Workspace to prevent users from adding personal email accounts to the work email app. On the MDM console, for the Workspace, do the following: 1. In the "Android account" group, configure "account management" to "disable for the work email app". 2. Provision the user's email account for the work email app. Refer to the MDM documentation to determine how to provision users' work email accounts for the work email app.
Review device configurations settings to confirm that the system application disable list has been configured. This procedure is performed on both the MDM Administration console and the Samsung Android device. Confirm if Method #1 or Method #2 is used at the Samsung device site and follow the appropriate procedure. **** Method #1: On the MDM console, for the device, in the "managed Google Play" group, verify that the system application disable list contains all apps that have not been approved for DoD use by the Authorizing Official (AO). On the Samsung Android device, review the apps on the "Personal" App screen and confirm that none of the apps listed in the system application disable list are present. If the system application disable list does not contain all the apps that have not been approved by the AO, or if an app listed can be found on the "Personal" App screen of the Samsung Android device, this is a finding. **** Method #2: On the MDM console, for the device, in the "Knox application" group, verify that the system application disable list contains all apps that have not been approved for DoD use by the AO. On the Samsung Android device, review the apps on the "Personal" App screen and confirm that none of the apps listed in the system application disable list are present. If the system application disable list does not contain all the apps that have not been approved by the AO, or if an app listed can be found on "Personal" App screen of the Samsung Android device, this is a finding.
Configure Samsung Android to enforce the system application disable list. Do one of the following: - Method # 1 (preferred): Use managed Google Play for the device (managed device). - Method #2: Use the Knox system application disable list. **** Method #1: On the MDM console, for the device, in the "managed Google Play" group, add all non-AO-approved system app packages to the system application disable list. **** Method #2: On the MDM console, for the device, in the "Knox application" group, add all non-AO-approved system app packages to the system application disable list. **** Note: Refer to the "System Apps for disablement (other characteristics)" and "System Apps That Must Not Be Disabled" tables in the Supplemental document for this STIG.
Review the Samsung Android Workspace configurations settings to confirm that the system application disable list has been configured. This procedure is performed on both the MDM Administration console and the Samsung Android device. Confirm if Method #1 or Method #2 is used at the Samsung device site and follow the appropriate procedure. **** Method #1: On the MDM console, for the Workspace, in the "managed Google Play" group, verify that the system application disable list contains all apps that have not been approved for DoD use by the Authorizing Official (AO). On the Samsung Android device, review the apps on the "Workspace" App screen and confirm that none of the apps listed in the system application disable list are present. If the system application disable list does not contain all the apps that have not been approved by the AO, or if an app listed can be found on the "Workspace" App screen of the Samsung Android device, this is a finding. **** Method #2: On the MDM console, for the Workspace, in the "Knox application" group, verify that the system application disable list contains all apps that have not been approved for DoD use by the AO. On the Samsung Android device, review the apps on the "Workspace" App screen and confirm that none of the apps listed in the system application disable list are present. If the system application disable list does not contain all the apps that have not been approved by the AO, or if an app listed can be found on the "Workspace" App screen of the Samsung Android device, this is a finding.
Configure Samsung Android Workspace to enforce the system application disable list. Do one of the following: - Method # 1 (preferred): Use managed Google Play for the Workspace (managed profile). - Method #2: Use the Knox system application disable list. **** Method #1: On the MDM console, for the Workspace, in the "managed Google Play" group, add all non-AO-approved system app packages to the system application disable list. **** Method #2: On the MDM console, for the Workspace, in the "Knox application" group, add all non-AO-approved system app packages to the system application disable list. **** Refer to the "System Apps for disablement (other characteristics)" and "System Apps That Must Not Be Disabled" tables in the Supplemental document for this STIG.
Review the Samsung Android Workspace configuration settings to confirm that an application installation whitelist has been configured. This procedure is performed only on the MDM Administration console. Confirm if Method #1 or Method #2 is used at the Samsung device site and follow the appropriate procedure. **** Method #1: On the MDM console, for the Workspace, in the "managed Google Play" group, verify that each package listed on the application installation whitelist has been approved for DoD use by the Authorizing Official (AO). If the application installation whitelist contains non-AO-approved packages, this is a finding. **** Method #2: On the MDM console, for the Workspace, in the "Knox application" group, verify that each package listed on the application installation whitelist has been approved for DoD use by the AO. If the application installation whitelist contains non-AO-approved packages, this is a finding.
Configure Samsung Android Workspace to enforce an application installation whitelist. The application installation whitelist does not control user access to/execution of all core and preinstalled applications, and guidance for doing so is covered in KNOX-09-000050. Do one of the following: - Method #1: Use managed Google Play for the Workspace (managed profile). - Method #2: Use Knox application installation whitelist. **** Method #1: On the MDM console, for the Workspace, in the "managed Google Play" group, add each AO-approved package to the managed Google Play application installation whitelist. **** Method #2: On the MDM console, for the Workspace, in the "Knox application" group, add each AO-approved package to the application installation whitelist. Refer to the MDM documentation to determine the following: - If an application installation blacklist is also required to be configured when enforcing an "application installation whitelist". - If MDM supports adding packages to the "application installation whitelist by package name and/or digital signature or supports a combination of the two. **** Note: Refer to the "System Apps That Must Not Be Disabled" table in the Supplemental document for this STIG. These apps must be included in the application installation whitelist to allow updates.
Review device configuration settings to confirm that the system application disable list has been configured to include all system apps that have been identified to transmit mobile device diagnostic data to non-DoD servers. This procedure is performed on both the MDM Administration console and the Samsung Android device. Confirm if Method #1 or Method #2 is used at the Samsung device site, and follow the appropriate procedure. **** Method #1: On the MDM console, for the device, in the "managed Google Play" group, verify that the system application disable list contains all apps identified to transmit mobile device diagnostic data to non-DoD servers. On the Samsung Android device, review the apps on the "Personal" App screen and confirm that none of the apps listed in the system application disable list are present. If the system application disable list does not contain all the apps that have been identified to transmit mobile device diagnostic data to non-DoD servers, or if an app listed can be found on the "Personal" App screen of the Samsung Android device, this is a finding. **** Method #2: On the MDM console, for the device, in the "Knox application" group, verify that the system application disable list contains all apps identified to transmit mobile device diagnostic data to non-DoD servers. On the Samsung Android device, review the apps on the "Personal" App screen and confirm that none of the apps listed in the system application disable list are present. If the system application disable list does not contain all the apps that have been identified to transmit mobile device diagnostic data to non-DoD servers, or if an app listed can be found on the "Personal" App screen of the Samsung Android device, this is a finding.
Configure Samsung Android to include all system apps in the system app disable list that have been identified to transmit mobile device diagnostic data to non-DoD servers. Do one of the following: - Method # 1 (preferred): Use managed Google Play for the device (managed device). - Method #2: Use the Knox system application disable list. **** Method #1: On the MDM console, for the device, in the "managed Google Play" group, add all system app packages that have been identified to transmit mobile data diagnostic data to non-DoD servers to the system application disable list. **** Method #2: On the MDM console, for the device, in the "Knox application" group, add all system app packages that have been identified to transmit mobile device diagnostic data to non-DoD servers to the system application disable list. **** Note: Refer to the "System Apps for Disablement (Non-DoD-Approved Characteristics)" and "System Apps That Must Not Be Disabled" tables in the Supplemental document for this STIG. Only system apps that are identified with the characteristic of "transmit MD diagnostic data to non-DoD servers" need to be added to the system application disable list.
Review Samsung Android Workspace configuration settings to confirm that the system application disable list has been configured to include all system apps that have been identified as having non-DoD-approved characteristics. This procedure is performed on both the MDM Administration console and the Samsung Android device. Confirm if Method #1 or Method #2 is used at the Samsung device site and follow the appropriate procedure. **** Method #1: On the MDM console, for the Workspace, in the "managed Google Play" group, verify that the system application disable list contains all apps identified as having non-DoD-approved characteristics. On the Samsung Android device, review the apps on the "Workspace" App screen and confirm that none of the apps listed in the system application disable list are present. If the system application disable list does not contain all the apps that have been identified as having non-DoD-approved characteristics, or if an app listed can be found on the "Workspace" App screen of the Samsung Android device, this is a finding. **** Method #2: On the MDM console, for the device, in the "Knox application" group, verify that the system application disable list contains all apps identified as having non-DoD-approved characteristics. On the Samsung Android device, review the apps on the "Workspace" App screen and confirm that none of the apps listed in the system application disable list are present. If the system application disable list does not contain all the apps that have been identified as having non-DoD-approved characteristics, or if an app listed can be found on the "Workspace" App screen of the Samsung Android device, this is a finding.
Configure the Samsung Android Workspace to include all system apps in the system app disable list that have been identified as having non-DoD-approved characteristics. Do one of the following: - Method #1 (preferred): Use managed Google Play for the Workspace (managed profile). - Method #2: Use the Knox system application disable list. **** Method #1: On the MDM console, for the Workspace, in the "managed Google Play" group, add all system app packages that have been identified as having non-DoD-approved characteristics to the system application disable list. **** Method #2: On the MDM console, for the Workspace, in the "Knox application" group, add all system app packages that have been identified as having non-DoD-approved characteristics to the system application disable list. **** Note: Refer to the "System Apps for Disablement (Non-DoD-Approved Characteristics)" and "System Apps That Must Not Be Disabled" tables in the Supplemental document for this STIG.
Review device configuration settings to confirm that installation from unauthorized application repositories is disallowed. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the device, in the "Android user restrictions" group, verify that "disallow install unknown sources" is selected. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Apps". 3. Tap the Overflow menu (three vertical dots). 4. Tap "Special Access". 5. Tap "Install unknown apps". 6. Tap a listed app. 7. Verify that "Allow from this source" cannot be enabled. If on the MDM console "disallow install unknown sources" is not selected, or on the Samsung Android device the user can enable "allow from this source" for an app, this is a finding.
Configure Samsung Android to disallow installation from unauthorized application repositories. On the MDM console, for the device, in the "Android user restrictions" group, select "disallow install unknown sources".
Review device configuration settings to confirm that the Knox audit log is enabled. This procedure is performed on the MDM Administration console only. On the MDM console, for the device, in the "Knox audit log" group, verify that "enable audit log" is selected. If on the MDM console the "enable audit log" is not selected, this is a finding.
Configure Samsung Android to enable the Knox audit log. On the MDM console, for the device, in the "Knox audit log" group, select "enable audit log".
Review the Samsung Android Workspace configuration settings to confirm that the access control policy that prevents groups of application processes from accessing all data stored by other groups of application processes has been enabled. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the Workspace, in the "Knox RCP" group, do the following: 1. Verify that "allow move applications to workspace" is not selected. 2. Verify that "allow move files to personal" is not selected. 3. Verify that "allow sharing clipboard to personal" is not selected. 4. Verify that "sync calendar to personal" is not selected. 5. Verify that "sync contact to personal" is not selected. On the Samsung Android device, do the following: 1. Swipe up to access the App screen. 2. Tap the "Workspace" tab. 3. Open the "My Files" app. 4. Find a file and select it with a long tap. 5. From the Overflow menu (three vertical dots), tap "Move to Personal". 6. Verify that the message "Security policy restricts this action" is displayed. 7. Navigate back to the "Workspace" App screen and, using any Workspace app, copy text to the clipboard. 8. Navigate to the "Personal" App screen and, using a Personal app, verify that the clipboard text cannot be pasted. 9. Open Settings. 10. Tap "Workspace". 11. Verify that "Install apps" is disabled and cannot be tapped. 12. Tap "Notifications and data". 13. Verify that "Export calendar to Personal" is disabled and cannot be enabled. This is a finding if, on the MDM console: - "allow move applications to workspace" is selected; - "allow move files to personal" is selected; - "allow sharing clipboard to personal" is selected; - "sync calendar to personal" is enabled is selected; or - "sync contact to personal" is selected. This is a finding if, on the Samsung Android device: - "Move to Personal" file is not blocked; - Clipboard text can be pasted to Personal app; - "Install apps" is enabled or can be tapped; or - "Export calendar to Personal" is enabled or can be enabled.
Configure the Samsung Android Workspace to enable the access control policy that prevents groups of application processes from accessing all data stored by other groups of application processes. On the MDM console, for the Workspace, in the "Knox RCP" group, do the following: 1. Unselect "allow move applications to workspace". 2. Unselect "allow move files to personal". 3. Unselect "allow sharing clipboard to personal". 4. Unselect "sync calendar to personal". 5. Unselect "sync contact to personal". Note: The "allow move files to workspace" option may be selected if there is a DoD mission need for this feature.
Review Device configuration settings to confirm that a Knox Workspace has been created. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, verify that a Knox Workspace has been created. On the Samsung Android device, verify the existence of the "Personal" and "Workspace" tabs on the App screen. If on the MDM console, a "Knox Workspace" has not been created, or on the Samsung Android device the "Personal" and "Workspace" tabs are not present on the App screen, this is a finding.
Configure Samsung Android to create a Knox Workspace. On the MDM console, create a Knox Workspace.
Review the Samsung Android Workspace configuration settings to confirm that the content of Workspace notifications is redacted when the device is locked. This procedure is performed on both the MDM console and the Samsung Android device. On the MDM console, for the Workspace, in the "Android lock screen restrictions" group, verify that "disable unredacted notification" is selected. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Workspace". 3. Tap "Notification and data". 4. Verify that "Show notification content" is disabled. If on the MDM console "disable unredacted notifications" is not selected, or on the Samsung Android device "Show notification content" is not disabled, this is a finding.
Configure Samsung Android Workspace to redact the content of Workspace notifications when the device is locked. On the MDM console, for the Workspace, in the "Android lock screen restrictions" group, select "disable unredacted notifications".
Review a sample of site User Agreements for Samsung device users or similar training records and training course content. Verify that Samsung device users have completed the required training. The intent is that required training is renewed on a periodic basis in a time period determined by the AO. If any Samsung device user has not completed the required training, this is a finding.
Have all Samsung device users complete training on the following topics. Users should acknowledge that they have reviewed training via a signed User Agreement or similar written record. Training topics: - Operational security concerns introduced by unmanaged applications/unmanaged personal space, including applications using global positioning system (GPS) tracking. - Need to ensure no DoD data is saved to the personal space or transmitted from a personal app (for example, from personal email). - If the Purebred key management app is used, users are responsible for maintaining positive control of their credentialed device at all times. The DoD PKI certificate policy requires subscribers to maintain positive control of the devices that contain private keys and to report any loss of control so the credentials can be revoked. Upon device retirement, turn-in, or reassignment, ensure that a factory data reset is performed prior to device hand-off. Follow mobility service provider decommissioning procedures as applicable. - How to configure the following UBE controls (users must configure the control) on the Samsung device: **Secure use of Calendar Alarm **Local screen mirroring and MirrorLink procedures (authorized/not authorized for use) **Do not connect Samsung devices (either via DeX Station or dongle) to any DoD network via Ethernet connection **Do not upload DoD contacts via smart call and caller ID services **Do not remove DoD intermediate and root PKI digital certificates **Disable Wi-Fi Sharing **Do not configure a DoD network (work) VPN profile on any third-party VPN client installed in the personal space **Enable Secure Startup, and must not disable at any time **Must not disable Strong Protection at any time - AO guidance on acceptable use and restrictions, if any, on downloading and installing personal apps and data (music, photos, etc.) in the Samsung device personal space.
Review accessories that provide wired networking capabilities to Samsung Android devices at the site and verify that the accessories are not connected to a DoD network. If accessories that provide wired networking capabilities to Samsung Android devices are connected to DoD networks, this is a finding. Note: Connections to a site's guest network that provides Internet-only access can be used. Note: This setting cannot be managed by the MDM administrator and is a User-Based Enforcement (UBE) requirement.
When using an accessory that provides wired networking capabilities to a Samsung Android device, do not connect the accessory to a DoD network. Note: This setting cannot be managed by the MDM administrator and is a UBE requirement.
Review device configuration settings to confirm that the minimum password length is six or more characters. This procedure is performed on both the MDM administration console and the Samsung Android device. On the MDM console, for the device, in the "Android password constraints" group, verify that the "minimum password length" is "6" or greater. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Lock screen". 3. Tap "Screen lock type". 4. Enter current password. 5. Tap "Password". 6. Verify that passwords entered with fewer than six characters are not accepted. If on the MDM console "minimum password length" is less than "6", or on the Samsung Android device a password of less than "6" characters is accepted, this is a finding.
Configure Samsung Android to enforce a minimum password length of six characters. On the MDM console, in the Android password constraints, set the "minimum password length" to "6" or greater.
Review device configuration settings to confirm that passwords with two repeating or sequential characters are prevented. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, do the following: 1. For the device, in the "Knox password constraint" group, verify that "maximum sequential characters" is "2" or less. 2. For the device, in the "Knox password constraint" group, verify that "maximum sequential numbers" is "2" or less. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Lock screen". 3. Tap "Screen lock type". 4. Enter current password. 5. Tap "Password". 6. Verify that passwords with two or more sequential characters or numbers are not accepted. If on the MDM console "maximum sequential characters" or "maximum sequential numbers" is more than "2", or on the Samsung Android device a password with two or more sequential characters or numbers is accepted, this is a finding.
Configure Samsung Android to prevent passwords from containing more than two repeating or sequential characters. On the MDM console, for the device, in the "Knox password constraints" group: 1. Set "maximum sequential characters" to "2". 2. Set "maximum sequential numbers" to "2".
Review device configuration settings to confirm that the device locks the screen after 15 minutes (or less) of inactivity. This procedure is performed on both the MDM Administration Console and the Samsung Android device. On the MDM console, in the Android lock screen restrictions, verify that the "max time to screen lock" is "15" minutes or less. On the Samsung Android device, do the following: 1. Unlock the device. 2. Refrain from performing any activity on the device for 15 minutes. 3. Verify that the device requires the user to enter the device unlock password to access the device. If on the MDM console "max time to lock" is not set to "15" minutes or less, or the Samsung Android device does not require the user to authenticate to unlock after 15 minutes of inactivity, this is a finding.
Configure Samsung Android to lock the device display after 15 minutes (or less) of inactivity. On the MDM console, for the device, in the "Android lock screen restrictions" group, set the "max time to screen lock" to "15" minutes.
Review the Samsung Android Workspace configuration settings to confirm that the Workspace is locked after 15 minutes (or less) of inactivity. This validation procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the Workspace, in the "Android lock screen restrictions" group, verify that the "max time to screen lock" is set to "15" minutes. On the Samsung Android device, do the following: 1. Tap any app on the "Workspace" App screen. 2. Refrain from using the device for 15 minutes. 3. If "One Lock" is disabled, verify that the device requires the user to enter the Workspace password to access any app on the "Workspace" App screen. 4. If "One Lock" is enabled, verify that the device requires the user to enter the device unlock password to access the device. If on the MDM console "maximum time to lock" is not set to "15" minutes or less, or the Samsung Android Workspace does not lock after 15 minutes, this is a finding. Note: If "When screen turns off" is selected in the Samsung Android Workspace setting Workspace >> Auto lock Workspace, the Workspace will not lock until the screen turns off, regardless of the maximum lock timeout.
Configure Samsung Android Workspace to lock after 15 minutes (or less) of inactivity. On the MDM console, for the Workspace, in the "Android lock screen restriction" group, set the "max time to screen lock" to "15" minutes.
Review device configuration settings to confirm that the maximum number of consecutive failed authentication attempts is set to "10" or fewer. This procedure is performed on the MDM Administration console only. On the MDM console, for the device, in the "Android lock screen restrictions" group, verify that the "max password failures for local wipe" is "10" or fewer. If on the MDM console, "max password failures for local wipe" is more than "10", this is a finding.
Configure Samsung Android to allow only 10 consecutive failed authentication attempts before device wipe. On the MDM console, for the device, in the "Android lock screen restrictions" group, set the "max password failures for local wipe" to "10".
Review the Samsung Android Workspace configuration settings to confirm that the maximum number of consecutive failed Workspace authentication attempts is set to "10" or fewer. This procedure is performed on the MDM Administration console only. On the MDM console, for the Workspace, in the "Android lock screen restrictions" group, verify that "max password failures for local wipe" is "10" or fewer. If on the MDM console "max password failures for local wipe" is more than "10", this is a finding.
Configure Samsung Android Workspace to allow only 10 consecutive failed authentication attempts before Workspace wipe. On the MDM console, for the Workspace, in the "Android lock screen restrictions" group, set "max password failures for local wipe" to "10".
Review device configuration settings to confirm that trust agents are disabled. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the device, in the "Android lock screen restrictions" group, verify that "disable trust agents" is selected. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Biometrics and security". 3. Tap "Other security settings". 4. Tap "Trust agents". 5. Verify that all listed trust agents are disabled and cannot be enabled. If on the MDM console "disable trust agents" is not selected, or on the Samsung Android device a trust agent can be enabled, this is a finding.
Configure Samsung Android to disable trust agents. On the MDM console, for the device, in the "Android lock screen restriction" group, select "disable trust agents".
Review device configuration settings to confirm that Face Recognition is disabled. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the device, in the "Android lock restrictions" group, verify that "disable face" is selected. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Lock screen". 3. Tap "Screen lock type". 4. Enter current password. 5. Verify that "Face" is disabled and cannot be enabled. If on the MDM console "disable face" is not selected, or on the Samsung Android device "Face" can be enabled, this is a finding.
Configure Samsung Android to disable Face Recognition. On the MDM console, for the device, in the "Android lock screen restriction" group, select "disable face".
Review the Samsung Android Workspace configuration settings to confirm that automatic completion of Samsung Internet app text input is disabled. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the Workspace, in the "Knox restrictions" group, verify that "allow autofill" is not selected. On the Samsung Android device, do the following: 1. From the "Workspace" App screen, launch the "Samsung Internet" app. 2. From the collapsed menu icon (three horizontal bars) on the toolbar, tap "Settings". 3. Tap "Privacy and security". 4. Verify that "Autofill forms" is disabled and cannot be enabled. If on the MDM console "allow autofill" is selected, or if on the Samsung Android device "Autofill forms" can be enabled by the user, this is a finding.
Configure Samsung Android Workspace to disable automatic completion of Samsung Internet app text input. On the MDM console, for the Workspace, in the "Knox restrictions" group, unselect "allow autofill".
Review the Samsung Android Workspace configuration settings to confirm that autofill services are disabled. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the Workspace, in the "Android user restrictions" group, verify that "disallow autofill" is selected. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Workspace". 3. Tap "More settings". 4. Tap "Keyboard and input". 5. Verify that "Autofill service" is not present. If on the MDM console "disallow autofill" is selected, or on the Samsung Android device "Autofill service" is present, this is a finding.
Configure Samsung Android Workspace to disable the autofill services. On the MDM console, in the Android user restrictions, select "disallow autofill".
Review device configuration settings to confirm that all Bluetooth profiles are disabled except HSP, HFP, and SPP, A2DP, AVRCP, and PBAP. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the device, in the "Knox Bluetooth" group, verify that only "HFP, HSP, SPP, A2DP, AVRCP, and PBAP" are selected in the "allowed profiles". On the Samsung Android device, verify that a Bluetooth peripheral that uses a profile other than HSP, HFP, SPP, A2DP, AVRCP, or PBAP (e.g., a Bluetooth keyboard) cannot be paired. If on the MDM console "allowed profiles" has any selection other than "HSP, HFP, SPP, A2DP, AVRCP, and PBAP", or the Samsung Android device is able to pair with a Bluetooth keyboard, this is a finding. Note: Disabling the Bluetooth radio will satisfy this requirement.
Configure Samsung Android to disable all Bluetooth profiles except HSP, HFP, SPP, A2DP, AVRCP, and PBAP. On the MDM console, for the device, in the "Knox Bluetooth" group, select "HFP, HSP, SPP, A2DP, AVRCP, and PBAP" in the "allowed profiles".
Review device configuration settings to confirm that USB file transfer has been disallowed. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the device, in the "Android user restrictions" group, verify that "disallow usb file transfer" is selected. Connect the Samsung Android device to a non-DoD network-managed PC with a USB cable. On the PC, browse the mounted Samsung Android device and verify that it does not display any folders or files. If on the MDM console "disallow USB file transfer" is not selected, or the PC can mount and browse folders and files on the Samsung Android device, this is a finding.
Configure Samsung Android to disallow USB file transfer. On the MDM console, for the device, in the "Android user restrictions" group, select "disallow USB file transfer".
Review device configuration settings to confirm that Knox CC Mode is enabled. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the device, in the "Knox restrictions" group, verify that "enable CC mode" is selected. On the Samsung Android device, to verify that CC Mode has not failed, do the following: 1. Open Settings. 2. Tap "About phone". 3. Tap "Software information". 4. Verify that the Security software version for MDF does not display "Disabled". For Samsung Android devices prior to Galaxy S10, to verify that CC Mode is enabled, do the following: 1. Open Settings. 2. Tap "Biometric and security". 3. Tap "Secure startup". 4. Verify that "Do not require" is disabled. For Galaxy S10 (or newer devices), to verify that CC Mode is enabled, do the following: 1. Open Settings. 2. Tap "Biometric and security". 3. Verify that "Strong Protection" is enabled and cannot be disabled. If on the MDM console "enable CC mode" is not selected, or on the Samsung Android device the software version for "MDF" displays "Disabled", or on a Galaxy S10 (or newer device) "Strong Protection" can be disabled, or on a device older than a Galaxy S10 "Do not require" is not disabled, this is a finding.
Configure Samsung Android to enable Knox CC Mode. On the MDM console, for the device, in the "Knox restrictions" group, select "enable CC mode". The following configuration must also be implemented for the Samsung Android device to be operating in the NIAP-certified compliant CC mode of operation: - KNOX-09-001440: Minimum password quality - KNOX-09-000500: Disable face - KNOX-09-000430/(KNOX-09-000440): Max password failures for local wipe - KNOX-09-001370/(KNOX-09-001360): Password recovery - KNOX-09-001390/(KNOX-09-001400): Password history length - KNOX-09-001050/(KNOX-09-001040): Revocation check - KNOX-09-001340/(KNOX-09-001330): OCSP check - KNOX-09-001420: Secure Startup (for devices prior to Galaxy S10) - KNOX-09-001480: Strong Protection (for Galaxy S10 (or newer) devices) - KNOX-09-000980: Enable external storage encryption or disallow mount physical media Note: STIGIDs listed above not in parentheses are personal space requirements. STIGIDs in parentheses are workspace requirements.
Review device configuration settings to confirm that configuration of the date and time is disallowed. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the device, in the "Android user restrictions" group, verify that "disallow config date time" is selected. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "General management". 3. Tap "Date and time". 4. Verify that "Automatic date and time" is on and the user cannot disable it. If on the MDM console "disallow config date time" is not selected, or on the Samsung Android device "Automatic date and time" is not set or the user can disable it, this is a finding.
Configure Samsung Android to disallow configuration of the date and time. On the MDM console, for the device, in the "Android user restrictions" group, select "disallow config date time".
Review device configuration settings to confirm that the USB host mode exception list is configured. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the device, in the "Knox restrictions" group, verify that "HID" is selected in the "USB host mode exception list". On the Samsung Android device, do the following: 1. Connect a micro USB-to-USB "On the Go" (OTG) adapter to the device. 2. Connect a USB thumb drive to the adapter. 3. Verify that the device cannot access the USB thumb drive. If on the MDM console "USB host mode exception list" has any selection other than "HID", or on the Samsung Android device the USB thumb drive can be mounted, this is a finding.
Configure Samsung Android with a USB host mode exception list. On the MDM console, for the device, in the "Knox restrictions" group, select "HID" in the "USB host mode exception list".
Review the Samsung Android Workspace configuration settings to confirm that Share Via List is disallowed. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the Workspace, in the "Knox restrictions" group, verify that "disallow share via list" is selected. On the Samsung Android device, in the Workspace, attempt to share by long pressing a file and tapping "Share". If on the MDM console "disallow share via list" is not selected, or on the Samsung Android device the user is able to share in the Workspace, this is a finding.
Configure Samsung Android Workspace to disallow Share Via List. On the MDM console, for the Workspace, in the "Knox restrictions" group, select "disallow share via list". Note: Disabling "share via list" will also disable functionality such as "Gallery Sharing" and "Direct Sharing".
Review device configuration settings to confirm that backup to locally connected systems has been disabled. Disabling backup to locally connected systems is validated by the validation procedure in "Disable USB mass storage", which is included in KNOX-09-000680. Review device configuration settings to confirm that USB file transfer has been disallowed. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the device, in the "Android user restrictions" group, verify that "disallow usb file transfer" is selected. Connect the Samsung Android device to a non-DoD network-managed PC with a USB cable. On the PC, browse the mounted Samsung Android device and verify that it does not display any folders or files. If on the MDM console "disallow USB file transfer" is not selected, or the PC can mount and browse folders and files on the Samsung Android device, this is a finding.
Configure Samsung Android to disable backup to locally connected systems. Disabling backup to locally connected systems is implemented by the configuration policy rule "Disable USB mass storage", which is included in KNOX-09-000680. On the MDM console, for the device, in the "Android user restrictions" group, select "disallow USB file transfer".
Review the Samsung Android Workspace configuration settings to confirm that backup to a remote system (including commercial clouds) has been disabled. This procedure is performed on the MDM Administration console and the Samsung Android device. Refer to the procedure in KNOX-09-000050 for Method #1 and #2 for verifying the "application disable list". On the MDM console, for the Workspace, do the following: 1. In the "Android device owner" group, verify that "enable backup service" is not selected. 2. In the "Knox restrictions" group, verify that "allow google accounts auto sync" is not selected. 3. Verify that the system application disable list contains all preinstalled cloud backup system apps. On the Samsung Android device: 1. Open Settings. 2. Tap "Workspace". 3. Tap "Accounts". 4. Tap a listed Google account. 5. Tap "Sync account" and verify that all sync options are disabled and cannot be enabled. 6. Review the apps on the "Workspace" App screen and confirm that none of the cloud backup system apps are present. If on the MDM console "enable backup service" is selected or "allow google accounts auto sync" is selected, or on the Samsung Android device "Backup service not available" is not listed, "sync options" are enabled for a Google Account, or a "cloud backup" system app is present on the "Workspace" App Screen, this is a finding.
Configure the Samsung Android Workspace to disable backup to remote systems (including commercial clouds). Refer to the guidance in KNOX-09-000050 for Method #1 and #2 for configuring the "application disable list". On the MDM console, for the Workspace, do the following: 1. In the "Android device owner" group, unselect "enable backup service". 2. In the "Knox restrictions" group, unselect "allow google accounts auto sync". 3. Add all preinstalled public cloud backup system apps to the system application disable list if not already configured. Note: The guidance for disablement of system apps that have the characteristic "back up MD data to non-DoD cloud servers (including user and application access to cloud backup services)" is covered by KNOX-09-000120.
Review device configuration settings to confirm that debugging features are disallowed. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the device, in the "Android user restrictions" group, verify that "disallow debugging features" is selected. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "About phone". 3. Tap "Software information". 4. Tap "Build number". 5. Verify that the message "Unable to perform action" is displayed. If on the MDM console "disallow debugging features" is not selected, or on the Samsung Android device the "Unable to perform action" message is not displayed, this is a finding.
Configure Samsung Android to disallow debugging features. On the MDM console, for the device, in the "Android user restrictions" group, select "disallow debugging features".
Review device configuration to confirm that unsecured hotspots are disallowed. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the device, in the "Knox Wifi" group, verify that "allow unsecured hotspot" is not selected. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Connections". 3. Tap "Mobile Hotspot and Tethering". 4. Tap "Mobile Hotspot". 5. Tap Overflow menu (three vertical dots). 6. Tap "Configure Mobile Hotspot". 7. Tap "Open in Security drop down". 8. Verify that "Save" is disabled. If on the MDM console "allow unsecured hotspot" is selected, or on the Samsung Android device an Open Mobile Hotspot configuration can be saved, this is a finding.
Configure Samsung Android to disallow unsecured hotspots. On the MDM console, in the Knox Wifi restrictions, unselect "allow unsecured hotspot".
Review device configuration settings to confirm that mounting of physical storage media is disallowed or Knox external storage encryption is enabled. If the mobile device does not support removable media, this procedure is not applicable and is not a finding. This procedure is performed on both the MDM Administration console and the Samsung Android device. Confirm if Method #1 or Method #2 is used at the Samsung device site and follow the appropriate procedure. **** Method #1: On the MDM console, for the device, in the "Android user restrictions" group, verify that "disallow mount physical media" is selected. On the Samsung Android device, verify that a MicroSD card cannot be mounted. If on the MDM console "disallow mount physical media" is not selected, or a MicroSD card can be mounted by the Samsung Android device, this is a finding. **** Method #2: On the MDM console, for the device, in the "Knox encryption" group, verify that "enable external storage encryption" is selected. On the Samsung Android device, verify that a MicroSD card must be encrypted before use. If on the MDM console "enable external storage encryption" is not selected, or a MicroSD card can be used on the Samsung Android device without first being encrypted, this is a finding.
Configure Samsung Android to disallow mount of physical storage media or enable Knox external storage encryption. If the mobile device does not support removable media, this guidance is not applicable. Do one of the following: - Method #1: Disallow mounting of physical storage media. - Method #2: Enable external storage encryption. **** Method #1: On the MDM console, for the device, in the "Android user restrictions" group, select "disallow mount physical media". **** Method #2: On the MDM console, for the device, in the "Knox encryption" group, select "enable external storage encryption".
Review the Samsung Android Workspace configuration settings to confirm that CRL checking is enabled for all apps. This procedure is performed on the MDM Administration console only. On the MDM console, for the Workspace, in the "Knox certificate" group, verify that "revocation check" is configured to "enable for all apps". If on the MDM console "revocation check" is not configured to "enable for all apps", this is a finding.
Configure Samsung Android Workspace to enable CRL checking for all apps. On the MDM console, for the Workspace, in the "Knox certificate" group, configure "revocation check" to "enable for all apps". Refer to the MDM documentation to determine how to configure revocation checking to "enable for all apps". Some may, for example, allow a wildcard string: "*" (asterisk).
Review device configuration settings to confirm that CRL checking is enabled for all apps. This procedure is performed on the MDM Administration console only. On the MDM console, for the device, in the "Knox certificate" group, verify that "revocation check" is configured to "enable for all apps". If on the MDM console "revocation check" is not configured to "enable for all apps", this is a finding.
Configure Samsung Android to enable CRL checking for all apps. On the MDM console, for the device, in the "Knox certificate" group, configure "revocation check" to "enable for all apps". Refer to the MDM documentation to determine how to configure revocation checking to "enable for all apps". Some may, for example, allow a wildcard string: "*" (asterisk).
Review the Samsung Android Workspace configuration settings to confirm that the DoD root and intermediate PKI certificates are installed. This procedure is performed on both the MDM Administration console and the Samsung Android device. The current DoD root and intermediate PKI certificates may be obtained in self-extracting zip files at http://iase.disa.mil/pki-pke (for NIPRNet). On the MDM console, for the Workspace, in the "Android certificate" group, verify that the DoD root and intermediate PKI certificates are listed. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Biometrics and security". 3. Tap "Other security settings". 4. Tap "View security certificates". 5. Verify that the DoD root and intermediate certificates are listed under the "Work" list in both the "System" and "User" tabs. If on the MDM console the DoD root and intermediate certificates are not listed in the "Android certificate" group, or on the Samsung Android device "View security certificates" does not list the DoD root and intermediate certificates, this is a finding.
Configure Samsung Android Workspace to install DoD root and intermediate certificates. On the MDM console, for the Workspace, in the "Android certificate" group, use "install a CA certificate" to install the DoD root and intermediate certificates. The current DoD root and intermediate PKI certificates may be obtained in self-extracting zip files at http://iase.disa.mil/pki-pke (for NIPRNet).
Review device configuration settings to confirm that the DoD root and intermediate PKI certificates are installed. This procedure is performed on both the MDM Administration console and the Samsung Android device. The current DoD root and intermediate PKI certificates may be obtained in self-extracting zip files at http://iase.disa.mil/pki-pke (for NIPRNet). On the MDM console, for the device, in the "Android certificate" group, verify that the DoD root and intermediate PKI certificates are listed. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Biometrics and security". 3. Tap "Other security settings". 4. Tap "View security certificates". 5. Verify the DoD root and intermediate certificates are listed under the "Personal" list in both the "System" and "User" tabs. If on the MDM console the DoD root and intermediate certificates are not listed in the "Android certificate" group, or on the Samsung Android device "View security certificates" does not list the DoD root and intermediate certificates, this is a finding.
Configure Samsung Android to install DoD root and intermediate certificates. On the MDM console, for the device, in the "Android certificate" group, use "install a CA certificate" to install the DoD root and intermediate certificates. The current DoD root and intermediate PKI certificates may be obtained in self-extracting zip files at http://iase.disa.mil/pki-pke (for NIPRNet).
Confirm if Method #1 or Method #2 is used at the Samsung device site and follow the appropriate procedure. **** Method #1: Review the signed user agreements for several Samsung device users and verify that the agreement includes the required DoD warning banner text. If the required DoD warning text is not included in all reviewed signed user agreements, this is a finding. **** Method #2: This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the device, in the "Knox banner" group, verify that the "banner text" is configured with the required DoD warning banner text On the Samsung Android device, verify that after a reboot the required DoD warning banner text is displayed. If on the MDM console the "banner text" is not configured with the required DoD warning banner text, or after a reboot the required DoD warning banner text is not displayed on the Samsung Android device, this is a finding.
Configure the DoD warning banner by either of the following methods (required text is found in the Vulnerability Discussion): - Method #1: Place the DoD warning banner text in the user agreement signed by each Samsung device user. - Method #2: Configure Samsung Android to display the DoD-mandated warning banner text. Use either Method #1 (preferred) or Method #2. **** Method #1: Include the DoD warning banner text in the user agreement that will be signed by each Samsung device user. **** Method #2: On the MDM console, for the device, in the "Knox banner" group, configure the "banner text" with the DoD-mandated warning banner text. Note: On some MDM consoles, the Knox banner is automatically enabled while the Samsung Android device is enrolled. In this case, the above guidance is not applicable.
Review device configuration settings to confirm that the most recently released version of Samsung Android is installed. This procedure is performed on both the MDM console and the Samsung Android device. In the MDM management console, review the version of Samsung Android installed on a sample of managed devices. This procedure will vary depending on the MDM product. See the notes below to determine the latest available operating system version. On the Samsung Android device, to see the installed operating system version: 1. Open Settings. 2. Tap "About phone". 3. Tap "Software information". On the Samsung Android device, to confirm that the installed operating system is the latest released version: 1. Open Settings. 2. Tap "Software updates". 3. Tap "Check for system updates". 4. Verify that "No update is necessary at this time" is displayed. If the installed version of the Android operating system on any reviewed Samsung devices is not the latest released by the wireless carrier, this is a finding. Note: Some wireless carriers list the version of the latest Android operating system release by mobile device model online: - ATT: https://www.att.com/devicehowto/dsm.html#!/popular/make/Samsung - T-Mobile: https://support.t-mobile.com/docs/DOC-34510 - Verizon Wireless: https://www.verizonwireless.com/support/software-updates/ Google's Android operating system patch website: https://source.android.com/security/bulletin/ Samsung's Android operating system patch website: https://security.samsungmobile.com/securityUpdate.smsb
Install the latest released version of the Samsung Android operating system on all managed Samsung devices. Note: In most cases, operating system updates are released by the wireless carrier (for example, Sprint, T-Mobile, Verizon Wireless, and ATT).
Review the Samsung Android Workspace configuration settings to confirm that OCSP checking is enabled for all apps. This procedure is performed on the MDM Administration console only. On the MDM console, for the Workspace, in the "Knox certificate" group, verify that "OCSP check" is configured to "enable for all apps". If on the MDM console "OCSP check" is not configured to "enable for all apps", this is a finding.
Configure Samsung Android Workspace to enable OCSP checking for all apps. On the MDM, for the Workspace, in the "Knox certificate" group, configure "OCSP check" to "enable for all apps". Refer to the MDM documentation to determine how to configure OCSP checking to "enable for all apps". Some may, for example, allow a wildcard string: "*" (asterisk).
Review device configuration settings to confirm that OCSP checking is enabled for all apps. This procedure is performed on the MDM Administration console only. On the MDM console, for the device, in the "Knox certificate" group, verify that "OCSP check" is configured to "enable for all apps". If on the MDM console "OCSP check" is not configured to "enable for all apps", this is a finding.
Configure Samsung Android to enable OCSP checking for all apps. On the MDM, for the device, in the "Knox certificate" group, configure "OCSP check" to "enable for all apps". Refer to the MDM documentation to determine how to configure OCSP checking to "enable for all apps". Some may, for example, allow a wildcard string: "*" (asterisk).
Verify that the Microsoft EAS Password Recovery has been disabled on the Exchange server. If on the Microsoft EAS server "password recovery" is not disabled, this is a finding.
Configure Samsung Android Workspace to not enable Microsoft EAS Password Recovery. The DoD mobile service provider should verify that the Exchange server is configured to disable Microsoft EAS Password Recovery.
Verify that the Microsoft EAS password recovery has been disabled on the Exchange server. If on the Microsoft EAS server "password recovery" is not disabled, this is a finding.
Configure Samsung Android to not enable Microsoft EAS password recovery. The DoD mobile service provider should verify that the Exchange server is configured to disable Microsoft EAS password recovery.
Review device configuration settings to confirm that the password history is set to a length of "0". This procedure is performed on the MDM console only. On the MDM console, for the device, in the "Android password constraints" group, verify that "password history length" is set to "0". If on the MDM console "password history length" is not set to "0", this is a finding.
Configure Samsung Android to set the password history with a length of "0". On the MDM console, for the device, in the "Android password constraints" group, set "password history length" to "0".
Review the Samsung Android Workspace configuration settings to confirm that the password history is set to a length of "0". This procedure is performed on the MDM console only. On the MDM console, for the Workspace, in the "Android password constraints" group, verify that "password history length" is set to "0". If on the MDM console "password history length" is not set to "0", this is a finding.
Configure Samsung Android Workspace to set the password history with a length of "0". On the MDM console, for the Workspace, in the "Android password constraints" group, set "password history length" to "0".
Review device configuration settings to confirm that Secure Startup is enabled. This procedure is performed on the Samsung Android device prior to Galaxy S10 only. This setting cannot be managed by the MDM administrator and is a User-Based Enforcement (UBE) requirement. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Biometric and security". 3. Tap "Other security settings". 4. Tap "Secure startup". 5. Verify that "Require password when device powers on" is already selected and "Do not require" is not selected. If on the Samsung Android device "Do not require" is selected, this is a finding.
Configure Samsung Android to enable Secure Startup. This guidance is only applicable to devices prior to Galaxy S10. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Biometrics and security". 3. Tap "Other security settings". 4. Tap "Secure startup". 5. Tap option "Require password when device powers on". 6. Tap "Apply". 7. Enter the current password,
Review device configuration settings to confirm that the device uses a screen-lock policy that will lock the display after a period of inactivity and that the lock type is configured with a minimum password quality. This procedure is performed on both the MDM Administration console and the Samsung Android device. On the MDM console, for the device, in the "Android password constraints" group, verify that the "minimum password quality" is "PIN" (see note). On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Lock screen". 3. Tap "Screen lock type". 4. Verify that "Swipe”, :Pattern”, and “None" cannot be enabled. If on the MDM console "minimum password quality" is not set to "PIN", or on the Samsung Android device the user can select a screen lock type other than "password", this is a finding. Note: Some MDM consoles may display “Numeric” and “Numeric-Complex” instead of “PIN”. Either selection is acceptable but “Numeric-Complex” is recommended. Alphabetic, Alphanumeric, and Complex are also acceptable selections but these selections will cause the user to select a complex password, which is not required by the STIG.
Configure Samsung Android to enforce a screen-lock policy that will lock the display after a period of inactivity, with a lock type that is configured with a minimum password quality. On the MDM console, for the device, in the "Android password constraints" group, set "minimum password quality" (or password type) to "PIN". Note: Some MDM consoles may display “Numeric” and “Numeric-Complex” instead of “PIN”. Either selection is acceptable but “Numeric-Complex” is recommended. Alphabetic, Alphanumeric, and Complex are also acceptable selections but these selections will cause the user to select a complex password, which is not required by the STIG.
Review device configuration settings to confirm that Strong Protection is enabled. This procedure is performed on the Samsung Android Galaxy S10 (or newer) devices only. This setting cannot be managed by the MDM administrator and is a User-Based Enforcement (UBE) requirement. On the Samsung Android device, do the following: 1. Open Settings 2. Tap "Biometric and security". 3. Tap "Other security settings". 4. Verify "Strong Protection" is enabled. If on the Samsung Android device "Strong Protection” is disabled, this is a finding.
Configure Samsung Android to enable Strong Protection. This guidance is only applicable to Galaxy S10 (or newer) devices. On the Samsung Android device, do the following: 1. Open Settings. 2. Tap "Biometrics and security". 3. Tap "Other security settings". 4. Tap "Strong Protection". 5. Tap to enable. 6. Enter the current password.