{
"stig": {
"date": "2020-05-15",
"description": "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: disa.stig_spt@mail.mil.",
"findings": {
"V-93845": {
"checkid": "C-93163r1_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that users are prevented from adding personal email accounts to the work email app. \n\nThis procedure is performed on both the MDM Administrator console and the Samsung Android device. \n\nConfirm if Method #1 or Method #2 is used at the Samsung device site and follow the appropriate procedure. \n\n**** \n\nMethod #1: On the MDM console, for the Workspace, in the \"Knox account\" group, verify that the account addition whitelist only includes DoD-approved email domains. \n\nRefer to the MDM documentation to determine if the account addition blacklist is also required to be configured when enforcing an account addition whitelist. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Workspace\". \n3. Tap \"Accounts\". \n4. Tap \"Add account\". \n5. Tap the account type for the work email app. \n6. Verify that an account with a DoD-approved email domain can be added. \n7. Verify that an account without a DoD-approved email domain cannot be added. \n\nIf on the MDM console the account addition whitelist includes domains that are not DoD-approved email domains, or on the Samsung Android device the user is able to add an account without a DoD-approved email domain, this is a finding. \n\n**** \n\nMethod #2: On the MDM console, for the Workspace, do the following: \n1. In the \"Knox account\" group, verify that all email domains are blacklisted in the account addition blacklist. \n2. Verify that the user's email account for the work email app has been provisioned. \n\nRefer to the MDM documentation to determine how to verify that a user's work email account is provisioned for the work email app. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Workspace\". \n3. Tap \"Accounts\". \n4. Tap \"Add account\". \n5. Verify that no accounts can be added. \n6. Verify that the user's work email app has been provisioned with the work email account.\n\nIf on the MDM console the account addition blacklist is not set to blacklist all email domains, or on the Samsung Android device the user is able to add an account, this is a finding.",
"description": "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 addition to whitelisted accounts mitigates this vulnerability.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100091r1_fix",
"fixtext": "Configure Samsung Android Workspace to prevent users from adding personal email accounts to the work email app. \n\nDo one of the following: \n- Method #1: Allow users to only add DoD-approved email accounts to the work email app. \n- Method #2: Disallow users from adding any email accounts to the work email app and provision the users' email account on their behalf. \n\n**** \n\nMethod #1: On the MDM console, for the Workspace, in the \"Knox account\" group, add all DoD-approved email domains to the account addition whitelist. \n\nRefer to the MDM documentation to determine if an account addition blacklist is also required to be configured when enforcing an account addition whitelist. \n\n**** \n\nMethod #2: On the MDM console, for the Workspace, do the following: \n1. In the \"Knox account\" group, blacklist all email domains in the account addition blacklist. \n2. Provision the user's email account for the work email app. \n\nRefer to the MDM documentation to determine how to provision users' work email accounts for the work email app.",
"iacontrols": null,
"id": "V-93845",
"ruleID": "SV-103931r1_rule",
"severity": "medium",
"title": "The Samsung Android Workspace must be configured to prevent users from adding personal email accounts to the work email app.",
"version": "KNOX-09-000025"
},
"V-93847": {
"checkid": "C-93165r1_chk",
"checktext": "Review device configuration settings to confirm that the system application disable list has been configured. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Knox application\" group, verify the system application disable list contains all apps that have not been approved for DoD use by the Authorizing Official (AO). \n\nOn 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. \n\nIf 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.",
"description": "The system application disable list controls user access to/execution of all core and preinstalled applications. \n\nCore application: Any application integrated into Samsung Android by Google or Samsung. \n\nPreinstalled application: Additional noncore applications included in the Samsung Android build by Google, Samsung, or the wireless carrier. \n\nSome system applications can compromise DoD data or upload users' information to non-DoD-approved servers. A user must be blocked from using such applications that exhibit behavior that can result in compromise of DoD data or DoD user information. \n\nThe site administrator must analyze all preinstalled applications on the device and disable all applications not approved for DoD use by configuring the system application disable list.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100093r1_fix",
"fixtext": "Configure Samsung Android to enforce the system application disable list. \n\nOn 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. \n\nNote: 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.",
"iacontrols": null,
"id": "V-93847",
"ruleID": "SV-103933r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to enforce the system application disable list.",
"version": "KNOX-09-000045"
},
"V-93849": {
"checkid": "C-93167r1_chk",
"checktext": "Review the Samsung Android Workspace configurations settings to confirm that the system application disable list has been configured. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn 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 Authorizing Official (AO). \n\nOn 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. \n\nIf 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.",
"description": "The system application disable list controls user access to/execution of all core and preinstalled applications. \n\nCore application: Any application integrated into Samsung Android by Google or Samsung. \n\nPreinstalled application: Additional noncore applications included in the Samsung Android build by Google, Samsung, or the wireless carrier. \n\nSome system applications can compromise DoD data or upload users' information to non-DoD-approved servers. A user must be blocked from using such applications that exhibit behavior that can result in compromise of DoD data or DoD user information. \n\nThe site administrator must analyze all preinstalled applications on the device and disable all applications not approved for DoD use by configuring the system application disable list.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100095r1_fix",
"fixtext": "Configure Samsung Android Workspace to enforce the system application disable list. \n\nOn 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. \n\nRefer to the \"System Apps for disablement (other characteristics)\" and \"System Apps That Must Not Be Disabled\" tables in the Supplemental document for this STIG.",
"iacontrols": null,
"id": "V-93849",
"ruleID": "SV-103935r1_rule",
"severity": "medium",
"title": "Samsung Android Workspace must be configured to enforce the system application disable list.",
"version": "KNOX-09-000055"
},
"V-93851": {
"checkid": "C-93169r1_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that an application installation whitelist has been configured. \n\nThis procedure is performed only on the MDM Administration console. \n\nOn 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 Authorizing Official (AO). \n\nIf the application installation whitelist contains non-AO-approved packages, this is a finding.",
"description": "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 restricting user access to/execution of core and preinstalled applications. \n\nCore application: Any application integrated into the operating system by the operating system or mobile device vendors. \n\nPreinstalled application: Additional noncore applications included in the operating system build by the operating system vendor, mobile device vendor, or wireless carrier. \n\nRequiring 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 unauthorized and malicious applications to be downloaded, installed, and executed on the mobile device, causing a compromise of DoD data accessible by these applications. \n\nThe application whitelist, in addition to controlling the installation of applications on the mobile device, must control user access to/execution of all core applications (included in the operating system by the operating system vendor) and preinstalled applications (provided by the mobile device vendor and wireless carrier), or the mobile device must provide an alternate method of restricting user access to/execution of core and preinstalled applications.\n\nSFR ID: FMT_SMF_EXT.1.1 #8b",
"fixid": "F-100097r1_fix",
"fixtext": "Configure Samsung Android Workspace to enforce an application installation whitelist. \n\nThe 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-000055. \n\nOn the MDM console, for the Workspace, in the \"Knox application\" group, add each AO-approved package to the application installation whitelist. \n\nRefer to the MDM documentation to determine the following: \n- If an application installation blacklist is also required to be configured when enforcing an application installation whitelist. \n- If the MDM supports adding packages to the application installation whitelist by package name and/or digital signature or supports a combination of the two. \n\nNote: 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.",
"iacontrols": null,
"id": "V-93851",
"ruleID": "SV-103937r1_rule",
"severity": "medium",
"title": "Samsung Android Workspace 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.",
"version": "KNOX-09-000085"
},
"V-93853": {
"checkid": "C-93171r1_chk",
"checktext": "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. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn 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. \n\nOn 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. \n\nIf 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.",
"description": "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 unauthorized and malicious applications to be downloaded, installed, and executed on the mobile device, causing a compromise of DoD data accessible by these applications. Applications with the listed characteristics have features that can cause the compromise of sensitive DoD data or have features with no known application in the DoD environment. \n\nApplication note: 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 restricting user access to/execution of core and preinstalled applications. \n\nCore application: Any application integrated into the operating system by the operating system or mobile device vendors. \n\nPreinstalled application: Additional noncore applications included in the operating system build by the operating system vendor, mobile device vendor, or wireless carrier.\n\nSFR ID: FMT_SMF_EXT.1.1 #8b",
"fixid": "F-100099r1_fix",
"fixtext": "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. \n\nThe system application disable list controls user access to/execution of core and preinstalled applications. It does not control the installation of applications. \n\nOn 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. \n\nNote: 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 mobile MD diagnostic data to non-DoD servers\" need to be added the system application disable list.",
"iacontrols": null,
"id": "V-93853",
"ruleID": "SV-103939r1_rule",
"severity": "medium",
"title": "The Samsung Android whitelist must be configured to not include applications with the following characteristic: - transmit MD diagnostic data to non-DoD servers.",
"version": "KNOX-09-000115"
},
"V-93855": {
"checkid": "C-93173r1_chk",
"checktext": "Review the 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. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the Workspace, in the \"Knox application\" group, verify that the system application disable list contains all apps identified as having non-DoD-approved characteristics. \n\nOn 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. \n\nIf 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.",
"description": "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 unauthorized and malicious applications to be downloaded, installed, and executed on the mobile device, causing a compromise of DoD data accessible by these applications. Applications with the listed characteristics have features that can cause the compromise of sensitive DoD data or have features with no known application in the DoD environment. \n\nApplication note: 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 MD must provide an alternate method of restricting user access to/execution of core and preinstalled applications. \n\nCore application: Any application integrated into the operating system by the operating system or mobile device vendors. \n\nPreinstalled application: Additional non-core applications included in the operating system build by the operating system vendor, mobile device vendor, or wireless carrier.\n\nSFR ID: FMT_SMF_EXT.1.1 #8b",
"fixid": "F-100101r1_fix",
"fixtext": "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.\n\nThe system application disable list controls user access to/execution of core and preinstalled applications. It does not control the installation of applications. \n\nOn 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. \n\nNote: 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.",
"iacontrols": null,
"id": "V-93855",
"ruleID": "SV-103941r1_rule",
"severity": "medium",
"title": "The Samsung Android Workspace whitelist must be configured to not include applications with the following characteristics: - back up MD data to non-DoD cloud servers (including user and application access to cloud backup services); - transmit MD diagnostic data to non-DoD servers; - voice assistant application if available when MD is locked; - voice dialing application if available when MD is locked; - allows synchronization of data or applications between devices associated with user; and - allows unencrypted (or encrypted but not FIPS 140-2 validated) data sharing with other MDs or printers.",
"version": "KNOX-09-000125"
},
"V-93857": {
"checkid": "C-93175r1_chk",
"checktext": "Review device configuration settings to confirm that installation from unauthorized application repositories is disallowed. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Knox restrictions\" group, verify that \"allow install unknown sources\" is not selected. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Apps\". \n3. Tap the Overflow menu (three vertical dots). \n4. Tap \"Special Access\". \n5. Tap \"Install unknown apps\". \n6. Tap a listed app. \n7. Verify that \"Allow from this source\" cannot be enabled. \n\nIf on the MDM console \"allow install unknown source\" is selected, or on the Samsung Android device the user can enable \"allow from this source\" for an app, this is a finding.",
"description": "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 of DoD data accessible by these unauthorized/malicious applications.\n\nSFR ID: FMT_SMF_EXT.1.1 #8a",
"fixid": "F-100103r1_fix",
"fixtext": "Configure Samsung Android to disallow installation from unauthorized application repositories. \n\nOn the MDM console, for the device, in the \"Knox restrictions\" group, unselect \"allow install unknown sources\".",
"iacontrols": null,
"id": "V-93857",
"ruleID": "SV-103943r1_rule",
"severity": "medium",
"title": "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.",
"version": "KNOX-09-000135"
},
"V-93859": {
"checkid": "C-93177r1_chk",
"checktext": "Review device configuration settings to confirm that the Knox audit log is enabled. \n\nThis procedure is performed on the MDM Administration console only. \n\nOn the MDM console, for the device, in the \"Knox audit log\" group, verify that \"enable audit log\" is selected. \n\nIf on the MDM console the \"enable audit log\" is not selected, this is a finding.",
"description": "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. The requirement statement lists key events for which the system must generate an audit record.\n\nSFR ID: FAU_GEN.1.1 #8",
"fixid": "F-100105r1_fix",
"fixtext": "Configure Samsung Android to enable the Knox audit log. \n\nOn the MDM console, for the device, in the \"Knox audit log\" group, select \"enable audit log\".",
"iacontrols": null,
"id": "V-93859",
"ruleID": "SV-103945r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to enable the Knox audit log.",
"version": "KNOX-09-000175"
},
"V-93861": {
"checkid": "C-93179r1_chk",
"checktext": "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. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the Workspace, in the \"Knox RCP\" group, do the following: \n1. Verify that \"allow move applications to workspace\" is not selected. \n2. Verify that \"allow move files to personal\" is not selected. \n3. Verify that \"allow sharing clipboard to personal\" is not selected. \n4. Verify that \"sync calendar to personal\" is not selected. \n5. Verify that \"sync contact to personal\" is not selected. \n\nOn the Samsung Android device, do the following: \n1. Swipe up to access the App screen. \n2. Tap the \"Workspace\" tab. \n3. Open the \"My Files\" app. \n4. Find a file and select it with a long tap. \n5. From the Overflow menu (three vertical dots), tap \"Move to Personal\". \n6. Verify that the message \"Security policy restricts this action\" is displayed. \n7. Navigate back to the \"Workspace\" App screen, and using any Workspace app, copy text to the clipboard. \n8. Navigate to the \"Personal\" App screen, and using a Personal app, verify that clipboard text cannot be pasted. \n9. Open Settings. \n10. Tap \"Workspace\". \n11. Verify that \"Install apps\" is disabled and cannot be tapped. \n12. Tap \"Notifications and data\". \n13. Verify that \"Export calendar to Personal\" is disabled and cannot be enabled. \n\nThis is a finding if, on the MDM console: \n- \"allow move applications to workspace\" is selected; \n- \"allow move files to personal\" is selected; \n- \"allow sharing clipboard to personal\" is selected; \n- \"sync calendar to personal\" is enabled is selected; or \n- \"sync contact to personal\" is selected. \n\nThis is a finding if, on the Samsung Android device: \n- \"Move to Personal\" file is not blocked; \n- Clipboard text can be pasted to Personal app; \n- \"Install apps\" is enabled or can be tapped; or \n- \"Export calendar to Personal\" is enabled or can be enabled.",
"description": "App data sharing gives apps the ability to access the data of other apps for enhanced user functionality. However, sharing also poses a significant risk that unauthorized users or apps will obtain access to DoD sensitive information. To mitigate this risk, there are data sharing restrictions. If a user is allowed to make exceptions to the data sharing restriction policy, the user could enable unauthorized sharing of data, leaving it vulnerable to breach. Limiting the granting of exceptions to either the administrator or common application developer mitigates this risk. \n\nCopying/pasting data between applications in different application processes or groups of application processes is considered an exception to the access control policy and therefore, the administrator must be able to enable/disable the feature. Other exceptions include allowing any data or application sharing between process groups.\n\nSFR ID: FMT_SMF_EXT.1.1 #42, FDP_ACF_EXT.1.2",
"fixid": "F-100107r1_fix",
"fixtext": "Configure 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. \n\nOn the MDM console, for the Workspace, in the \"Knox RCP\" group, do the following: \n1. Unselect \"allow move applications to workspace\". \n2. Unselect \"allow move files to personal\". \n3. Unselect \"allow sharing clipboard to personal\". \n4. Unselect \"sync calendar to personal\". \n5. Unselect \"sync contact to personal\". \n\nNote: The \"allow move files to workspace\" option may be selected if there is a DoD mission need for this feature.",
"iacontrols": null,
"id": "V-93861",
"ruleID": "SV-103947r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to disable exceptions to the access control policy that prevents [application processes, groups of application processes] from accessing [all, private] data stored by other [application processes, groups of application processes].",
"version": "KNOX-09-000245"
},
"V-93863": {
"checkid": "C-93181r1_chk",
"checktext": "Review Device configuration settings to confirm a legacy Knox Workspace has been created. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, verify that a legacy Knox Workspace has been created. \n\nOn the Samsung Android device, verify the existence of the \"Personal\" and \"Workspace\" tabs on the App screen. \n\nIf on the MDM console, a \"legacy 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.",
"description": "The Knox Workspace is the designated application group for the COPE use case.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100109r1_fix",
"fixtext": "Configure Samsung Android to create a legacy Knox Workspace. \n\nOn the MDM console, create a legacy Knox Workspace.",
"iacontrols": null,
"id": "V-93863",
"ruleID": "SV-103949r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to create a Knox Workspace.",
"version": "KNOX-09-000265"
},
"V-93865": {
"checkid": "C-93183r1_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that the content of Workspace notifications is redacted when the device is locked. \n\nThis procedure is performed on both the MDM console and the Samsung Android device. \n\nOn the MDM console, for the Workspace, in the \"Knox RCP\" group, verify that \"allow show detailed notifications\" is not selected. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Workspace\". \n3. Tap \"Notification and data\". \n4. Verify that \"Show notification content\" is disabled. \n\nIf on the MDM console \"allow show detailed notifications\" is selected, or on the Samsung Android device \"Show notification content\" is not disabled, this is a finding.",
"description": "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 notifications can contain sensitive information. When they are available on the lock screen, an adversary can see them merely by being in close physical proximity to the device. Configuring the mobile operating system to redact the contents of the notifications when the device is locked mitigates this risk.\n\nSFR ID: FMT_SMF_EXT.1.1 #19",
"fixid": "F-100111r1_fix",
"fixtext": "Configure Samsung Android Workspace to redact the content of Workspace notifications when the device is locked. \n\nOn the MDM console, for the Workspace, in the \"Knox RCP\" group, unselect \"allow show detailed notifications\".",
"iacontrols": null,
"id": "V-93865",
"ruleID": "SV-103951r1_rule",
"severity": "medium",
"title": "Samsung Android Workspace must be configured to not display the following notifications when the device is locked: - all notifications.",
"version": "KNOX-09-000305"
},
"V-93867": {
"checkid": "C-93185r1_chk",
"checktext": "Review a sample of site User Agreements of Samsung device users or similar training records and training course content. \n\nVerify 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. \n\nIf any Samsung device user has not completed required training, this is a finding.",
"description": "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 an unmanaged personal space, the user must receive training on risks. If a user is not aware of their responsibilities and does not comply with UBE requirements, the security posture of the Samsung mobile device may become compromised and DoD sensitive data may become compromised.\n\nSFR ID: NA",
"fixid": "F-100113r1_fix",
"fixtext": "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. \n\nTraining topics: \n\n- Operational security concerns introduced by unmanaged applications/unmanaged personal space, including applications using global positioning system (GPS) tracking. \n- Need to ensure no DoD data is saved to the personal space or transmitted from a personal app (for example, from personal email). \n- 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. \n- How to configure the following UBE controls (users must configure the control) on the Samsung device: \n**Secure use of Calendar Alarm \n**Local screen mirroring and MirrorLink procedures (authorized/not authorized for use) \n**Do not connect Samsung devices (either via DeX Station or dongle) to any DoD network via Ethernet connection \n**Do not upload DoD contacts via smart call and caller ID services \n**Do not remove DoD intermediate and root PKI digital certificates \n**Disable Wi-Fi Sharing \n**Do not configure a DoD network (work) VPN profile on any third-party VPN client installed in the personal space \n**Enable Secure Startup and must not disable at any time\n**Must not disable Strong Protection at any time\n- 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.",
"iacontrols": null,
"id": "V-93867",
"ruleID": "SV-103953r1_rule",
"severity": "medium",
"title": "Samsung Android device users must complete required training.",
"version": "KNOX-09-000355"
},
"V-93869": {
"checkid": "C-93187r1_chk",
"checktext": "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. \n\nIf accessories that provide wired networking capabilities to Samsung Android devices are connected to DoD networks, this is a finding. \n\nNote: Connections to a site's guest network that provides Internet-only access can be used. \n\nNote: This setting cannot be managed by the MDM administrator and is a User-Based Enforcement (UBE) requirement.",
"description": "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 have a number of personal apps installed that may include malware or have high-risk behaviors (for example, offloading data from the phone to third-party servers outside the United States). In addition, smartphones do not generally meet security requirements for computer devices to connect directly to DoD networks. \n\nNote: Samsung DeX mode (with input devices) will not work unless the \"USB host mode exception list\" is configured (see requirement KNOX-09-000755 for more information).\n\nSFR ID: FMT_MOF_EXT.1.2 #47",
"fixid": "F-100115r1_fix",
"fixtext": "When using an accessory that provides wired networking capabilities to a Samsung Android device, do not connect the accessory to a DoD network. \n\nNote: This setting cannot be managed by the MDM administrator and is a UBE requirement.",
"iacontrols": null,
"id": "V-93869",
"ruleID": "SV-103955r1_rule",
"severity": "medium",
"title": "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.).",
"version": "KNOX-09-000365"
},
"V-93871": {
"checkid": "C-93189r1_chk",
"checktext": "Review device configuration settings to confirm that the minimum password length is six or more characters. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Android password constraints\" group, verify that the \"minimum password length\" is \"6\" or greater. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Lock screen\". \n3. Tap \"Screen lock type\". \n4. Enter current password. \n5. Tap \"Password\". \n6. Verify that passwords entered with fewer than six characters are not accepted. \n\nIf 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.",
"description": "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, and the size of the password space. The longer the minimum length of the password is, the larger the password space. Having a too-short minimum password length significantly reduces password strength, increasing the chance of password compromise and resulting device and data compromise.\n\nSFR ID: FMT_SMF_EXT.1.1 #1a",
"fixid": "F-100117r1_fix",
"fixtext": "Configure Samsung Android to enforce a minimum password length of six characters. \n\nOn the MDM console, in the Android password constraints, set the \"minimum password length\" to \"6\" or greater.",
"iacontrols": null,
"id": "V-93871",
"ruleID": "SV-103957r1_rule",
"severity": "low",
"title": "Samsung Android must be configured to enforce a minimum password length of six characters.",
"version": "KNOX-09-000375"
},
"V-93873": {
"checkid": "C-93191r1_chk",
"checktext": "Review device configuration settings to confirm that passwords with two repeating or sequential characters are prevented. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, do the following: \n1. For the device, in the \"Knox password constraint\" group, verify that \"maximum sequential characters\" is \"2\" or less. \n2. For the device, in the \"Knox password constraint\" group, verify that \"maximum sequential numbers\" is \"2\" or less. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Lock screen\". \n3. Tap \"Screen lock type\". \n4. Enter current password. \n5. Tap \"Password\". \n6. Verify that passwords with two or more sequential characters or numbers are not accepted. \n\nIf 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.",
"description": "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 sequential characters. Therefore, disallowing repeating or sequential characters increases password strength and decreases risk.\n\nSFR ID: FMT_SMF_EXT.1.1 #1b",
"fixid": "F-100119r1_fix",
"fixtext": "Configure Samsung Android to prevent passwords from containing more than two repeating or sequential characters. \n\nOn the MDM console, for the device, in the \"Knox password constraints\" group: \n1. Set \"maximum sequential characters\" to \"2\". \n2. Set \"maximum sequential numbers\" to \"2\".",
"iacontrols": null,
"id": "V-93873",
"ruleID": "SV-103959r1_rule",
"severity": "low",
"title": "Samsung Android must be configured to not allow passwords that include more than two repeating or sequential characters.",
"version": "KNOX-09-000395"
},
"V-93875": {
"checkid": "C-93193r1_chk",
"checktext": "Review device configuration settings to confirm that the device locks the screen after 15 minutes (or less) of inactivity. \n\nThis procedure is performed on both the MDM Administration Console and the Samsung Android device. \n\nOn the MDM console, in the Android lock screen restrictions, verify that the \"max time to screen lock\" is \"15\" minutes or less. \n\nOn the Samsung Android device, do the following: \n1. Unlock the device. \n2. Refrain from performing any activity on the device for 15 minutes. \n3. Verify that the device requires the user to enter the device unlock password to access the device. \n\nIf 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.",
"description": "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, etc. Such devices are much more likely to be in an unlocked state when acquired by an adversary, thus granting immediate access to the data on the mobile device. The maximum timeout period of 15 minutes has been selected to balance functionality and security; shorter timeout periods may be appropriate depending on the risks posed to the mobile device.\n\nSFR ID: FMT_SMF_EXT.1.1 #2b",
"fixid": "F-100121r1_fix",
"fixtext": "Configure Samsung Android to lock the device display after 15 minutes (or less) of inactivity. \n\nOn the MDM console, for the device, in the \"Android lock screen restrictions\" group, set the \"max time to screen lock\" to \"15\" minutes.",
"iacontrols": null,
"id": "V-93875",
"ruleID": "SV-103961r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to lock the display after 15 minutes (or less) of inactivity.",
"version": "KNOX-09-000405"
},
"V-93877": {
"checkid": "C-93195r1_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that the Workspace is locked after 15 minutes (or less) of inactivity. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the Workspace, in the \"Knox password constraints\" group, verify that \"maximum time to lock\" is set to 15 minutes. \n\nOn the Samsung Android device, do the following: \n1. Tap any app on the \"Workspace\" App screen. \n2. Refrain from using the device for 15 minutes. \n3. Verify that the device requires the user to enter the Workspace password to access any app on the \"Workspace\" App screen. \n\nIf 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. \n\nNote: 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.",
"description": "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, etc. Such devices are much more likely to be in an unlocked state when acquired by an adversary, thus granting immediate access to the data on the mobile device. The maximum timeout period of 15 minutes has been selected to balance functionality and security; shorter timeout periods may be appropriate, depending on the risks posed to the mobile device.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100123r1_fix",
"fixtext": "Configure Samsung Android Workspace to lock after 15 minutes (or less) of inactivity. \n\nOn the MDM console, for the Workspace, in the \"Knox password constraints\" group, set the \"maximum time to lock\" to 15 minutes.",
"iacontrols": null,
"id": "V-93877",
"ruleID": "SV-103963r1_rule",
"severity": "medium",
"title": "Samsung Android Workspace must be configured to lock after 15 minutes (or less) of inactivity.",
"version": "KNOX-09-000415"
},
"V-93879": {
"checkid": "C-93197r1_chk",
"checktext": "Review device configuration settings to confirm that the maximum number of consecutive failed authentication attempts is set to \"10\" or fewer. \n\nThis procedure is performed on the MDM Administration console only. \n\nOn 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. \n\nIf on the MDM console \"max password failures for local wipe\" is more than \"10\", this is a finding.",
"description": "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 less gives authorized users the ability to make a few mistakes when entering the password but still provides adequate protection against dictionary or brute force attacks on the password.\n\nSFR ID: FMT_SMF_EXT.1.1 #2c, FIA_AFL_EXT.1.5",
"fixid": "F-100125r1_fix",
"fixtext": "Configure Samsung Android to allow only 10 consecutive failed authentication attempts before device wipe. \n\nOn the MDM console, for the Device, in the \"Android lock screen restrictions\" group, set the \"max password failures for local wipe\" to \"10\".",
"iacontrols": null,
"id": "V-93879",
"ruleID": "SV-103965r1_rule",
"severity": "low",
"title": "Samsung Android must be configured to not allow more than 10 consecutive failed authentication attempts.",
"version": "KNOX-09-000435"
},
"V-93881": {
"checkid": "C-93199r1_chk",
"checktext": "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. \n\nThis procedure is performed on the MDM Administration console only. \n\nOn the MDM console, for the Workspace, in the \"Knox password constraints\" group, verify that \"max password failures for local wipe\" is \"10\" or fewer. \n\nIf on the MDM console \"max password failures for local wipe\" is more than \"10\", this is a finding.",
"description": "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 less gives authorized users the ability to make a few mistakes when entering the password but still provides adequate protection against dictionary or brute force attacks on the password.\n\nSFR ID: FMT_SMF_EXT.1.1 #2c, FIA_AFL_EXT.1.5",
"fixid": "F-100127r2_fix",
"fixtext": "Configure Samsung Android Workspace to allow only 10 consecutive failed authentication attempts before Workspace wipe. \n\nOn the MDM console, for the Workspace, in the \"Knox password constraints\" group, set \"max password failures for local wipe\" to \"10\".",
"iacontrols": null,
"id": "V-93881",
"ruleID": "SV-103967r1_rule",
"severity": "low",
"title": "Samsung Android Workspace must be configured to not allow more than 10 consecutive failed authentication attempts.",
"version": "KNOX-09-000445"
},
"V-93883": {
"checkid": "C-93201r1_chk",
"checktext": "Review device configuration settings to confirm that trust agents are disabled. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Android lock screen restrictions\" group, verify that \"disable trust agents\" is selected. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Biometrics and security\". \n3. Tap \"Other security settings\". \n4. Tap \"Trust agents\". \n5. Verify that all listed trust agents are disabled and cannot be enabled. \n\nIf 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.",
"description": "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 access to DoD sensitive data if compromised. By not permitting the use of non-password authentication mechanisms, users are forced to use passcodes that meet DoD passcode requirements.\n\nSFR ID: FMT_SMF_EXT.1.1 #23, FIA_UAU.5.1",
"fixid": "F-100131r1_fix",
"fixtext": "Configure Samsung Android to disable trust agents. \n\nOn the MDM console, for the device, in the \"Android lock screen restriction\" group, select \"disable trust agents\".",
"iacontrols": null,
"id": "V-93883",
"ruleID": "SV-103969r1_rule",
"severity": "medium",
"title": "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.",
"version": "KNOX-09-000475"
},
"V-93885": {
"checkid": "C-93203r1_chk",
"checktext": "Review device configuration settings to confirm that Face Recognition is disabled. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Knox password constraints\" group, verify that \"disable face\" is selected. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Lock screen\". \n3. Tap \"Screen lock type\". \n4. Enter current password. \n5. Verify that \"Face\" is disabled and cannot be enabled. \n\nIf on the MDM console \"disable face\" is not selected, or on the Samsung Android device \"Face\" can be enabled, this is a finding.",
"description": "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 mechanisms, users are forced to use passcodes that meet DoD passcode requirements.\n\nSFR ID: FMT_SMF_EXT.1.1 #23, FIA_UAU.5.1",
"fixid": "F-100133r1_fix",
"fixtext": "Configure Samsung Android to disable Face Recognition. \n\nOn the MDM console, for the device, in the \"Knox password constraints\" group, select \"disable face\".",
"iacontrols": null,
"id": "V-93885",
"ruleID": "SV-103971r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to disable Face Recognition. \n \nNote: This requirement is not applicable (NA) for specific biometric authentication factors included in the products Common Criteria evaluation.",
"version": "KNOX-09-000505"
},
"V-93887": {
"checkid": "C-93205r1_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that automatic completion of Samsung Internet app text input is disabled. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the Workspace, in the \"Knox restrictions\" group, verify that \"allow autofill\" is not selected. \n\nOn the Samsung Android device, do the following: \n1. From the \"Workspace\" App screen, launch the \"Samsung Internet\" app. \n2. From the collapsed menu icon (three horizontal bars) on the toolbar, tap \"Settings\". \n3. Tap \"Privacy and security\". \n4. Verify that \"Autofill forms\" is disabled and cannot be enabled. \n\nIf 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.",
"description": "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 functionality, an adversary who learns a user's Samsung Android device password, or who otherwise is able to unlock the device, may be able to further breach other systems by relying on the autofill feature to provide information unknown to the adversary. By disabling the autofill functionality, the risk of an adversary gaining further information about the device's user or compromising other systems is significantly mitigated.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100135r1_fix",
"fixtext": "Configure Samsung Android Workspace to disable automatic completion of Samsung Internet app text input. \n\nOn the MDM console, for the Workspace, in the \"Knox restrictions\" group, unselect \"allow autofill\".",
"iacontrols": null,
"id": "V-93887",
"ruleID": "SV-103973r1_rule",
"severity": "medium",
"title": "Samsung Android Workspace must be configured to disable automatic completion of Samsung Internet browser text input.",
"version": "KNOX-09-000595"
},
"V-93889": {
"checkid": "C-93207r1_chk",
"checktext": "Review configuration settings to confirm that multi-user mode has been disabled. \n\nThis procedure is performed on both the MDM Administrator console and the Samsung Android device. \n\nOn the MDM console, in Knox MultiUser, verify that \"allow multi-user mode\" is not selected. \n\nOn the Samsung Android device, open Settings and verify that the \"User\" setting is not available. \n\nIf on the MDM console \"allow multi-user mode\" is selected, or on the Samsung Android device the \"User\" setting is available, this is a finding.",
"description": "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 for user accounts. In addition, the MDFPP does not include design requirements for multi-user account services. Disabling multi-user mode mitigates the risk of not meeting DoD multi-user account security policies.\n\nSFR ID: FMT_SMF_EXT.1.1 #47b",
"fixid": "F-100137r1_fix",
"fixtext": "Configure Samsung Android to disable multi-user modes. \n\nOn the MDM console, in Knox MultiUser, unselect \"allow multi-user mode\".",
"iacontrols": null,
"id": "V-93889",
"ruleID": "SV-103975r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to disable multi-user modes.",
"version": "KNOX-09-000645"
},
"V-93891": {
"checkid": "C-93209r2_chk",
"checktext": "Review device configuration settings to confirm that all Bluetooth profiles are disabled except HSP, HFP, and SPP, A2DP, AVRCP, and PBAP. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn 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\". \n\nOn 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. \n\nIf 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. \n\nNote: Disabling the Bluetooth radio will satisfy this requirement.\n",
"description": "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.\n\nSFR ID: FMT_SMF_EXT.1.1 #18h",
"fixid": "F-100139r2_fix",
"fixtext": "Configure Samsung Android to disable all Bluetooth profiles except HSP, HFP, SPP, A2DP, AVRCP, and PBAP. \n\nOn the MDM console, for the device, in the \"Knox Bluetooth\" group, select \"HFP, HSP, SPP, A2DP, AVRCP, and PBAP\" in the \"allowed profiles\".\n",
"iacontrols": null,
"id": "V-93891",
"ruleID": "SV-103977r2_rule",
"severity": "low",
"title": "Samsung Android must be configured to disable all Bluetooth profiles except HSP (Headset Profile), HFP (HandsFree Profile), SPP (Serial Port Profile), A2DP (Advanced Audio Distribution Profile), AVRCP (Audio/Video Remote Control Profile), and PBAP (Phone Book Access Profile).",
"version": "KNOX-09-000665"
},
"V-93893": {
"checkid": "C-93211r1_chk",
"checktext": "Review device configuration settings to confirm that USB mass storage mode has been disabled. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Knox restrictions\" group, verify that \"disable USB media player\" is selected. \n\nConnect the Samsung Android device to a non-DoD network-managed PC with a USB cable. \n\nOn the PC, browse the mounted Samsung Android device and verify that it does not display any folders or files. \n\nIf on the MDM console \"disable USB media player\" is not selected, or the PC can mount and browse folders and files on the Samsung Android device, this is a finding.",
"description": "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 exfiltration. Prohibiting USB mass storage mode mitigates this risk.\n\nSFR ID: FMT_SMF_EXT.1.1 #39a",
"fixid": "F-100141r1_fix",
"fixtext": "Configure Samsung Android to disable USB mass storage mode. \n\nOn the MDM console, for the device, in the \"Knox restrictions\" group, select \"disable USB media player\".",
"iacontrols": null,
"id": "V-93893",
"ruleID": "SV-103979r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to disable USB mass storage mode.",
"version": "KNOX-09-000685"
},
"V-93895": {
"checkid": "C-93213r1_chk",
"checktext": "Review device configuration settings to confirm that Knox CC Mode is enabled. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Knox restrictions\" group, verify that \"enable CC mode\" is selected. \n\nOn the Samsung Android device, to verify that CC Mode has not failed, do the following: \n1. Open Settings. \n2. Tap \"About phone\". \n3. Tap \"Software information\". \n4. Verify that the Security software version for MDF does not display \"Disabled\". \n\nFor Samsung Android devices prior to Galaxy S10, to verify that CC Mode is enabled, do the following: \n1. Open Settings. \n2. Tap \"Biometric and security\". \n3. Tap \"Secure startup\". \n4. Verify that \"Do not require\" is disabled. \n\nFor Galaxy S10 (or newer devices), to verify that CC Mode is enabled, do the following: \n1. Open Settings. \n2. Tap \"Biometric and security\". \n3. Verify that \"Strong Protection\" is enabled and cannot be disabled. \n\nIf 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.",
"description": "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 operation. \n\nCC Mode implements the following behavioral/functional changes: \n\n- FOTA signature verification uses additional SHA-512 signature check. \n- Download Mode is disabled and all updates will occur via FOTA only. \n- IKEv1 operates in Main Mode only. \n- HTTPS audit logging in enabled. \n- Certificates without a Subject Alternative Name (SAN) field are rejected. \n- Certificates that do not pass Strict Host Name verification are rejected. \n- Certificates provided by servers must have the Extended Key Usage field set as Server Authentication. \n- Allows only authenticated Bluetooth connections. \n- Additional Key Zeroization is performed.\n\nFollowing is the list of prerequisites the user/MDM has to set in addition to calling CC Mode API to be fully compliant with the MDFPP requirements and the Samsung device Common Criteria certification:\n- Screen lock type: Alphanumeric or complex of type password, face disabled\n- Password Attempts: 1 <= value <= 30 and wipe after exceeding\n- No password recovery and history\n- Certificate revocation check enabled, OCSP check enabled\n- Secure start-up or strong protection enabled\n- SD Card encryption enabled\n\nFor reference, the STIGIDs for the policies above are as follows:\nFor KPE(AE):\n- KNOX-09-000710: Enable CC mode\n- KNOX-09-001440: Minimum password quality\n- KNOX-09-000500: Disable face\n- KNOX-09-000430/(KNOX-09-000440): Max password failures for local wipe\n- KNOX-09-001370/(KNOX-09-001360): Password recovery\n- KNOX-09-001390/(KNOX-09-001400): Password history length\n- KNOX-09-001050/(KNOX-09-001040): Revocation check\n- KNOX-09-001340/(KNOX-09-001330): OCSP check\n- KNOX-09-001420: Secure Startup\n- KNOX-09-000980: Enable external storage encryption, or disallow mount physical media\n\nFor KPE(Legacy): add \"5\" to the end of the requirement number for above and in addition: \n- KNOX-09-001475: minimum password quality for workspace\n\nNote: STIGIDs listed above not in parentheses are personal space requirements. STIGIDs in parentheses are workspace requirements.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100143r1_fix",
"fixtext": "Configure Samsung Android to enable Knox CC Mode. \n\nOn the MDM console, for the device, in the \"Knox restrictions\" group, select \"enable CC mode\". \n\nThe following configuration must also be implemented for the Samsung Android device to be operating in the NIAP-certified compliant CC Mode of operation: \n- KNOX-09-001445/(KNOX-09-001475): Minimum password quality \n- KNOX-09-000505: Disable face \n- KNOX-09-000435/(KNOX-09-000445): Max password failures for local wipe \n- KNOX-09-001375/(KNOX-09-001365): Password recovery \n- KNOX-09-001395/(KNOX-09-001405): Password history length \n- KNOX-09-001055/(KNOX-09-001045): Revocation check \n- KNOX-09-001345/(KNOX-09-001335): OCSP check \n- KNOX-09-001425: Secure Startup (for devices prior to Galaxy S10)\n- KNOX-09-001485: Strong Protection (for Galaxy S10 (or newer) devices)\n- KNOX-09-000985: Enable external storage encryption\n\nNote: STIGIDs listed above not in parentheses are personal space requirements. STIGIDs in parentheses are workspace requirements.",
"iacontrols": null,
"id": "V-93895",
"ruleID": "SV-103981r1_rule",
"severity": "high",
"title": "Samsung Android must be configured to enable Knox Common Criteria (CC) Mode.",
"version": "KNOX-09-000715"
},
"V-93897": {
"checkid": "C-93215r1_chk",
"checktext": "Review device configuration settings to confirm that configuration of the date and time is disallowed. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Knox Date Time\" group, verify that \"date time change enabled\" is not selected. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"General management\". \n3. Tap \"Date and time\". \n4. Verify that \"Automatic date and time\" is on and the user cannot disable it. \n\nIf on the MDM console \"date time change enabled\" is selected, or on the Samsung Android device \"Automatic date and time\" is not set or the user can disable it, this is a finding.",
"description": "Determining the correct time a particular application event occurred on a system is critical when conducting forensic analysis and investigating system events.\n\nPeriodically synchronizing internal clocks with an authoritative time source is necessary to correctly correlate the timing of events that occur across the enterprise. The three authoritative time sources for Samsung Android are an authoritative time server that is synchronized with redundant United States Naval Observatory (USNO) time servers as designated for the appropriate DoD network (NIPRNet or SIPRNet), or the Global Positioning System (GPS), or the wireless carrier. \n\nTime stamps generated by the audit system in Samsung Android must 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\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100145r1_fix",
"fixtext": "Configure Samsung Android to disallow configuration of the date and time. \n\nOn the MDM console, for the device, in the \"Knox Date Time\" group, unselect \"date time change enabled\".",
"iacontrols": null,
"id": "V-93897",
"ruleID": "SV-103983r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to disallow configuration of date and time.",
"version": "KNOX-09-000735"
},
"V-93899": {
"checkid": "C-93217r1_chk",
"checktext": "Review device configuration settings to confirm that the USB host mode exception list is configured. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Knox restrictions\" group, verify that \"USB host mode exception list\" is set with \"HID\". \n\nOn the Samsung Android device, do the following: \n1. Connect a micro USB-to-USB \"On the Go\" (OTG) adapter to the device. \n2. Connect a USB thumb drive to the adapter. \n3. Verify that the device cannot access the USB thumb drive. \n\nIf 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.",
"description": "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 others based on their USB device class. \n\nWith some USB device classes, a user can copy sensitive DoD information to external USB storage unencrypted, resulting in compromise of DoD data. However, some USB device classes, such as Human Interface Devices (HID), do not allow data to be copied. \n\nDisabling all USB devices except for HID mitigates the risk of compromising sensitive DoD data. \n\nThis allows for DeX mode to be used with a USB keyboard and mouse without compromising DoD data.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100147r1_fix",
"fixtext": "Configure Samsung Android with a USB host mode exception list. \n\nOn the MDM console, for the device, in the \"Knox restrictions\" group, select \"HID\" in the \"USB host mode exception list\".",
"iacontrols": null,
"id": "V-93899",
"ruleID": "SV-103985r1_rule",
"severity": "medium",
"title": "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.",
"version": "KNOX-09-000755"
},
"V-93901": {
"checkid": "C-93219r1_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that Share Via List is disallowed. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the Workspace, in the \"Knox restrictions\" group, verify that \"disallow share via list\" is selected. \n\nOn the Samsung Android device, in the Workspace, attempt to share by long pressing a file and tapping \"Share\". \n\nIf 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.",
"description": "The 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.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100149r1_fix",
"fixtext": "Configure Samsung Android Workspace to disallow Share Via List. \n\nOn the MDM console, for the Workspace, in the \"Knox restrictions\" group, select \"disallow share via list\". \n\nNote: Disabling \"share via list\" will also disable functionality such as \"Gallery Sharing\" and \"Direct Sharing\".",
"iacontrols": null,
"id": "V-93901",
"ruleID": "SV-103987r1_rule",
"severity": "medium",
"title": "Samsung Android Workspace must be configured to disallow the Share Via List feature.",
"version": "KNOX-09-000785"
},
"V-93903": {
"checkid": "C-93221r1_chk",
"checktext": "Review device configuration settings to confirm that backup to locally connected systems has been disabled. \n\nDisabling backup to locally connected systems is validated by the validation procedure in \"Disable USB mass storage\", which is included in KNOX-09-000685.\n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Knox restrictions\" group, verify that \"disable USB media player\" is selected.\n\nConnect the Samsung Android device to a non-DoD network-managed PC with a USB cable. \n\nOn the PC, browse the mounted Samsung Android device and verify that it does not display any folders or files. \n\nIf on the MDM console \"disable USB media player\" is not selected, or the PC can mount and browse folders and files on the Samsung Android device, this is a finding.",
"description": "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 are no longer present. This leaves the backed-up data vulnerable to attack. Disabling backup to external systems mitigates this risk.\n\nSFR ID: FMT_SMF_EXT.1.1 #40",
"fixid": "F-100151r1_fix",
"fixtext": "Configure Samsung Android to disable backup to locally connected systems. \n\nDisabling backup to locally connected systems is implemented by the configuration policy rule \"Disable USB mass storage\", which is included in KNOX-09-000685.\n\nOn the MDM console, for the device, in the \"Knox restrictions\" group, select \"disable USB media player\".",
"iacontrols": null,
"id": "V-93903",
"ruleID": "SV-103989r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to not allow backup of [all applications, configuration data] to locally connected systems.",
"version": "KNOX-09-000845"
},
"V-93905": {
"checkid": "C-93223r2_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that backup to a remote system (including commercial clouds) has been disabled.\n\nThis procedure is performed on the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the Workspace, do the following: \n1. In the \"Knox restrictions\" group, verify that \"allow google accounts auto sync\" is not selected. \n2. In the \"Knox application\" group, verify that the system application disable list contains all preinstalled cloud backup system apps. \n\nOn the Samsung Android device: \n1. Open Settings. \n2. Tap \"Workspace\". \n3. Tap \"Accounts\". \n4. Tap a listed Google account. \n5. Tap \"Sync account\" and verify that all sync options are disabled and cannot be enabled. \n6. Review the apps on the \"Workspace\" App screen and confirm that none of the cloud backup system apps are present. \n\nIf on the MDM console \"allow google accounts auto sync\" is selected, or on the Samsung Android device \"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.",
"description": "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 capability is often used to synchronize data across multiple devices. In this case, DoD devices may synchronize DoD sensitive information to a user's personal device or other unauthorized computers that are vulnerable to breach. Disallowing remote backup mitigates this risk.\n\nSFR ID: FMT_SMF_EXT.1.1 #40",
"fixid": "F-100153r1_fix",
"fixtext": "Configure the Samsung Android Workspace to disable backup to remote systems (including commercial clouds). \n\nOn the MDM console, for the Workspace, do the following: \n1. In the \"Knox restrictions\" group, unselect \"allow google accounts auto sync\". \n2. In the \"Knox application\" group, add all preinstalled public cloud backup system apps to the system application disable list if not already configured. \n\nNote: 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-000125.",
"iacontrols": null,
"id": "V-93905",
"ruleID": "SV-103991r1_rule",
"severity": "medium",
"title": "Samsung Android Workspace must be configured to not allow backup of [all applications, configuration data] to remote systems.",
"version": "KNOX-09-000875"
},
"V-93907": {
"checkid": "C-93225r1_chk",
"checktext": "Review device configuration settings to confirm developer mode is disallowed. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Knox restrictions\" group, verify that \"allow developer mode\" is not selected. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"About phone\". \n3. Tap \"Software information\". \n4. Keep tapping \"Build number\". \n5. Verify that message \"Developer mode has been enabled\" is displayed but \"Developer options\" is not available in Settings. \n\nIf on the MDM console \"allow developer mode\" is selected, or on the Samsung Android device \"Developer options\" can be enabled by the user, this is a finding.",
"description": "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 sensitive information. Disabling developer modes mitigates this risk.\n\nSFR ID: FMT_SMF_EXT.1.1 #26",
"fixid": "F-100155r1_fix",
"fixtext": "Configure Samsung Android to disallow developer mode. \n\nOn the MDM console, for the device, in the \"Knox restrictions\" group, unselect \"allow developer mode\".",
"iacontrols": null,
"id": "V-93907",
"ruleID": "SV-103993r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to disable developer modes.",
"version": "KNOX-09-000925"
},
"V-93909": {
"checkid": "C-93227r1_chk",
"checktext": "Review device configuration to confirm that unsecured hotspots are disallowed. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Knox Wifi\" group, verify that \"allow unsecured hotspot\" is not selected. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Connections\". \n3. Tap \"Mobile Hotspot and Tethering\". \n4. Tap \"Mobile Hotspot\". \n5. Tap Overflow menu (three vertical dots). \n6. Tap \"Configure Mobile Hotspot\". \n7. Tap \"Open in Security drop down\". \n8. Verify that \"Save\" is disabled. \n\nIf 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.",
"description": "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 vulnerabilities to access information and computing resources on the device. Requiring authentication to establish personal hotspot connections mitigates this risk. \n\nApplication note: If hotspot functionality is permitted, it must be authenticated via a preshared key. There is no requirement to enable hotspot functionality.\n\nSFR ID: FMT_SMF_EXT.1.1 #41a",
"fixid": "F-100157r1_fix",
"fixtext": "Configure Samsung Android to disallow unsecured hotspots. \n\nOn the MDM console, in the Knox Wifi restrictions, unselect \"allow unsecured hotspot\".",
"iacontrols": null,
"id": "V-93909",
"ruleID": "SV-103995r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to enable authentication of personal hotspot connections to the device using a preshared key.",
"version": "KNOX-09-000945"
},
"V-93911": {
"checkid": "C-93229r1_chk",
"checktext": "Review device configuration settings to determine if Knox external storage encryption is enabled. \n\nIf the mobile device does not support removable media, this procedure is not applicable and is not a finding. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Knox encryption\" group, verify that \"enable external storage encryption\" is selected. \n\nOn the Samsung Android device, verify that a MicroSD card must be encrypted before use. \n\nIf 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.",
"description": "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 on data access, an adversary can read removable media directly, thereby circumventing operating system controls. Encrypting the data ensures confidentiality is protected even when the operating system is not running.\n\nSFR ID: FMT_SMF_EXT.1.1 #21, #47f",
"fixid": "F-100159r1_fix",
"fixtext": "Configure Samsung Android to enable Knox external storage encryption. \n\nIf the mobile device does not support removable media, this guidance is not applicable. \n\nOn the MDM console, for the device, in the \"Knox encryption\" group, select \"enable external storage encryption\".",
"iacontrols": null,
"id": "V-93911",
"ruleID": "SV-103997r1_rule",
"severity": "high",
"title": "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.",
"version": "KNOX-09-000985"
},
"V-93913": {
"checkid": "C-93231r1_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that CRL checking is enabled for all apps. \n\nThis procedure is performed on the MDM Administration console only. \n\nOn the MDM console, for the Workspace, in the \"Knox certificate\" group, verify that \"revocation check\" is configured to \"enable for all apps\". \n\nIf on the MDM console \"revocation check\" is not configured to \"enable for all apps\", this is a finding.",
"description": "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 certificate.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100161r1_fix",
"fixtext": "Configure Samsung Android Workspace to enable CRL checking for all apps. \n\nOn the MDM console, for the Workspace, in the \"Knox certificate\" group, configure \"revocation check\" to \"enable for all apps\". \n\nRefer 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).",
"iacontrols": null,
"id": "V-93913",
"ruleID": "SV-103999r1_rule",
"severity": "medium",
"title": "Samsung Android Workspace must be configured to enable Certificate Revocation List (CRL) status checking.",
"version": "KNOX-09-001045"
},
"V-93915": {
"checkid": "C-93233r1_chk",
"checktext": "Review device configuration settings to confirm that CRL checking is enabled for all apps. \n\nThis procedure is performed on the MDM Administration console only. \n\nOn the MDM console, for the device, in the \"Knox certificate\" group, verify that \"revocation check\" is configured to \"enable for all apps\". \n\nIf on the MDM console \"revocation check\" is not configured to \"enable for all apps\", this is a finding.",
"description": "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 certificate.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100163r1_fix",
"fixtext": "Configure Samsung Android to enable CRL checking for all apps. \n\nOn the MDM console, for the device, in the \"Knox certificate\" group, configure \"revocation check\" to \"enable for all apps\". \n\nRefer 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).",
"iacontrols": null,
"id": "V-93915",
"ruleID": "SV-104001r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to enable Certificate Revocation List (CRL) status checking.",
"version": "KNOX-09-001055"
},
"V-93917": {
"checkid": "C-93235r3_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that the DoD root and intermediate PKI certificates are installed.\n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device.\n\nThe current DoD root and intermediate PKI certificates may be obtained in self-extracting zip files at http://iase.disa.mil/pki-pke (for NIPRNet). \n\nOn the MDM console, for the Workspace, in the \"Knox certificate\" group, verify that the DoD root and intermediate PKI certificates are listed.\n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Biometrics and security\". \n3. Tap \"Other security settings\". \n4. Tap \"View security certificates\". \n5. Verify the DoD root and intermediate certificates are listed under the \"Work\" list in the \"User\" tab.\n\nIf on the MDM console the DoD root and intermediate certificates are not listed in the \"Knox certificate\" group, or on the Samsung Android device \"View security certificates\" does not list the DoD root and intermediate certificates, this is a finding.",
"description": "DoD root and intermediate PKI certificates are used to verify the authenticity of PKI certificates of users and web services. If the root and intermediate certificates are not available, an adversary could falsely sign a certificate in such a way that it could not be detected. Providing access to the DoD root and intermediate PKI certificates greatly diminishes the risk of this attack.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100165r1_fix",
"fixtext": "Configure Samsung Android Workspace to install DoD root and intermediate certificates. \n\nOn the MDM console, for the Workspace, in the \"Knox certificate\" group, use \"install a CA certificate\" to install the DoD root and intermediate certificates. \n\nThe current DoD root and intermediate PKI certificates may be obtained in self-extracting zip files at http://iase.disa.mil/pki-pke (for NIPRNet) or \nhttp://iase.rel.disa.smil.mil/pki-pke/function_pages/tools.html (for SIPRNet).",
"iacontrols": null,
"id": "V-93917",
"ruleID": "SV-104003r2_rule",
"severity": "medium",
"title": "Samsung Android Workspace must have the DoD root and intermediate PKI certificates installed.",
"version": "KNOX-09-001075"
},
"V-93921": {
"checkid": "C-93239r1_chk",
"checktext": "Confirm if Method #1 or Method #2 is used at the Samsung device site and follow the appropriate procedure. \n\n**** \n\nMethod #1: Review the signed user agreements for several Samsung device users and verify that the agreement includes the required DoD warning banner text. \n\nIf the required DoD warning text is not included in all reviewed signed user agreements, this is a finding. \n\n**** \n\nMethod #2: This procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn 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. \n\nOn the Samsung Android device, verify that that after a reboot the required DoD warning banner text is displayed. \n\nIf 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.",
"description": "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, directives, policies, regulations, standards, and guidance. Required banners help ensure that DoD can audit and monitor the activities of mobile device users without legal restriction. \n\nSystem use notification messages can be displayed when individuals first access or unlock the mobile device. The banner must be implemented as a \"click-through\" banner at device unlock (to the extent permitted by the operating system). A \"click-through\" banner prevents further activity on the information system unless and until the user executes a positive action to manifest agreement by clicking on a box indicating \"OK.\" \n\nThe approved DoD text must be used exactly as required in the KS referenced in DoDI 8500.01. For devices accommodating banners of 1300 characters, the banner text is: \n\nYou are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. \nBy using this IS (which includes any device attached to this IS), you consent to the following conditions: \n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. \n-At any time, the USG may inspect and seize data stored on this IS. \n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. \n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. \n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. \n\nFor devices with severe character limitations, the banner text is: \n\nI've read & consent to terms in IS user agreem't. \n\nThe administrator must configure the banner text exactly as written without any changes.\n\nSFR ID: FMT_SMF_EXT.1.1 #36",
"fixid": "F-100169r1_fix",
"fixtext": "Configure the DoD warning banner by either of the following methods (required text is found in the Vulnerability Discussion): \n\n- Method #1: Place the DoD warning banner text in the user agreement signed by each Samsung device user. \n- Method #2: Configure Samsung Android to display the DoD-mandated warning banner text. \n\nUse either Method #1 (preferred method) or Method #2. \n\n**** \n\nMethod #1: Include the DoD warning banner text in the user agreement that will be signed by each Samsung device user. \n\n**** \n\nMethod #2: On the MDM console, for the device, in the \"Knox banner\" group, configure the \"banner text\" with the DoD-mandated warning banner text. \n\nNote: 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.",
"iacontrols": null,
"id": "V-93921",
"ruleID": "SV-104007r1_rule",
"severity": "low",
"title": "Samsung Android must be configured to display the DoD advisory warning message at startup or each time the user unlocks the device.",
"version": "KNOX-09-001165"
},
"V-93923": {
"checkid": "C-93241r1_chk",
"checktext": "Review device configuration settings to confirm that the most recently released version of Samsung Android is installed. \n\nThis procedure is performed on both the MDM console and the Samsung Android device. \n\nIn 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. \n\nOn the Samsung Android device, to see the installed operating system version: \n1. Open Settings. \n2. Tap \"About phone\". \n3. Tap \"Software information\". \n\nOn the Samsung Android device, to confirm that the installed operating system is the latest released version: \n1. Open Settings. \n2. Tap \"Software updates\". \n3. Tap \"Check for system updates\". \n4. Verify that \"No update is necessary at this time\" is displayed. \n\nIf 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. \n\nNote: Some wireless carriers list the version of the latest Android operating system release by mobile device model online: \n- ATT: https://www.att.com/devicehowto/dsm.html#!/popular/make/Samsung \n- T-Mobile: https://support.t-mobile.com/docs/DOC-34510 \n- Verizon Wireless: https://www.verizonwireless.com/support/software-updates/ \n\nGoogle's Android operating system patch website: https://source.android.com/security/bulletin/ \nSamsung's Android operating system patch website: https://security.samsungmobile.com/securityUpdate.smsb",
"description": "Required security features are not available in earlier operating system versions. In addition, there may be known vulnerabilities in earlier versions.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100171r1_fix",
"fixtext": "Install the latest released version of the Samsung Android operating system on all managed Samsung devices. \n\nNote: In most cases, operating system updates are released by the wireless carrier (for example, Sprint, T-Mobile, Verizon Wireless, and ATT).",
"iacontrols": null,
"id": "V-93923",
"ruleID": "SV-104009r1_rule",
"severity": "high",
"title": "Samsung Android devices must have the latest available Samsung Android operating system installed.",
"version": "KNOX-09-001305"
},
"V-93925": {
"checkid": "C-93243r1_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that OCSP checking is enabled for all apps. \n\nThis procedure is performed on the MDM Administration console only. \n\nOn the MDM console, for the Workspace, in the \"Knox certificate\" group, verify that \"OCSP check\" is configured to \"enable for all apps\". \n\nIf on the MDM console \"OCSP check\" is not configured to \"enable for all apps\", this is a finding.",
"description": "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 about a certificate, it will then try to use CRL checking. The OCSP response server must be listed in the certificate information under Authority Info Access. \n\nThis feature must be enabled for a Samsung Android device to be in the NIAP-certified Common Criteria (CC) mode of operation.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100173r1_fix",
"fixtext": "Configure Samsung Android Workspace to enable OCSP checking for all apps. \n\nOn the MDM, for the Workspace, in the \"Knox certificate\" group, configure \"OCSP check\" to \"enable for all apps\". \n\nRefer 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).",
"iacontrols": null,
"id": "V-93925",
"ruleID": "SV-104011r1_rule",
"severity": "medium",
"title": "Samsung Android Workspace must be configured to enable the Online Certificate Status Protocol (OCSP).",
"version": "KNOX-09-001335"
},
"V-93927": {
"checkid": "C-93245r1_chk",
"checktext": "Review device configuration settings to confirm that OCSP checking is enabled for all apps. \n\nThis procedure is performed on the MDM Administration console only. \n\nOn the MDM console, for the device, in the \"Knox certificate\" group, verify that \"OCSP check\" is configured to \"enable for all apps\". \n\nIf on the MDM console \"OCSP check\" is not configured to \"enable for all apps\", this is a finding.",
"description": "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 about a certificate, it will then try to use CRL checking. The OCSP response server must be listed in the certificate information under Authority Info Access. \n\nThis feature must be enabled for a Samsung Android device to be in the NIAP-certified Common Criteria (CC) mode of operation.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100175r1_fix",
"fixtext": "Configure Samsung Android to enable OCSP checking for all apps. \n\nOn the MDM, for the device, in the \"Knox certificate\" group, configure \"OCSP check\" to \"enable for all apps\". \n\nRefer 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).",
"iacontrols": null,
"id": "V-93927",
"ruleID": "SV-104013r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to enable the Online Certificate Status Protocol (OCSP).",
"version": "KNOX-09-001345"
},
"V-93929": {
"checkid": "C-93247r1_chk",
"checktext": "Verify that the Microsoft EAS Password Recovery has been disabled on the Exchange server. \n\nIf on the Microsoft EAS server \"password recovery\" is not disabled, this is a finding.",
"description": "Password Recovery is a feature of Microsoft EAS. Exceeding the Password Attempts limit triggers the Lock screen to open a Password Recovery Mode. \n\nThis feature must be disabled for a Samsung Android device to be in the NIAP-certified Common Criteria (CC) mode of operation.\n\nIf Microsoft EAS Password Recovery is enabled, the Samsung device will be out of compliance with the CC Mode configuration. This requirement is configured on the Exchange server. It is the responsibility of the DoD mobile service provider to ensure that the Exchange server has been configured in compliance with the requirement.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100177r1_fix",
"fixtext": "Configure Samsung Android Workspace to not enable Microsoft EAS Password Recovery. \n\nThe DoD mobile service provider should verify that the Exchange server is configured to disable Microsoft EAS Password Recovery.",
"iacontrols": null,
"id": "V-93929",
"ruleID": "SV-104015r1_rule",
"severity": "medium",
"title": "Samsung Android Workspace must be configured to not enable Microsoft Exchange ActiveSync (EAS) password recovery. This requirement is not applicable if not using Microsoft EAS.",
"version": "KNOX-09-001365"
},
"V-93931": {
"checkid": "C-93249r1_chk",
"checktext": "Verify that the Microsoft EAS password recovery has been disabled on the Exchange server. \n\nIf on the Microsoft EAS server \"password recovery\" is not disabled, this is a finding.",
"description": "Password Recovery is a feature of Microsoft EAS. Exceeding the Password Attempts limit triggers the Lock screen to open a Password Recovery Mode. \n\nThis feature must be disabled for a Samsung Android device to be in the NIAP-certified Common Criteria (CC) mode of operation. \n\nIf Microsoft EAS password recovery is enabled, the Samsung device will be out of compliance with the CC Mode configuration. This requirement is configured on the Exchange server. It is the responsibility of the DoD mobile service provider to ensure the Exchange server has been configured in compliance with the requirement.\n\nThe requirement is only applicable if using Microsoft Exchange ActiveSync in the device (personal side).\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100179r1_fix",
"fixtext": "Configure Samsung Android to not enable Microsoft EAS password recovery. \n\nThe DoD mobile service provider should verify that the Exchange server is configured to disable Microsoft EAS password recovery.",
"iacontrols": null,
"id": "V-93931",
"ruleID": "SV-104017r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to not enable Microsoft Exchange ActiveSync (EAS) password recovery. This requirement is not applicable if not using Microsoft EAS.",
"version": "KNOX-09-001375"
},
"V-93933": {
"checkid": "C-93251r1_chk",
"checktext": "Review device configuration settings to confirm that the password history is set to a length of \"0\". \n\nThis procedure is performed on the MDM console only. \n\nOn the MDM console, for the device, in the \"Android password constraints\" group, verify that \"password history length\" is set to \"0\". \n\nIf on the MDM console \"password history length\" is not set to \"0\", this is a finding.",
"description": "Password History Length controls the number of most recently used Passwords stored in the Password History list. \n\nThe Password History list does not store the actual value of the previous passwords but instead calculates the hash value of the passwords. When the user attempts to set a new password, the hash value of the password is first calculated and the Password History list is checked to determine if it already contains a matching value, rejecting the password if it does. If the password is accepted, the oldest entry in the Password History list is removed, and the newly calculated password hash is added to the list. \n\nThe MDFPP requires that values derived from passwords are destroyed when no longer needed; therefore, the calculated hash values of previous passwords should not be stored in the Password History list. \n\nThis feature must be configured for a Samsung Android device to be in the NIAP-certified Common Criteria (CC) mode of operation.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100181r1_fix",
"fixtext": "Configure Samsung Android to set the password history with a length of \"0\". \n\nOn the MDM console, for the device, in the \"Android password constraints\" group, set \"password history length\" to \"0\".",
"iacontrols": null,
"id": "V-93933",
"ruleID": "SV-104019r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to set the password history with a length of 0.",
"version": "KNOX-09-001395"
},
"V-93935": {
"checkid": "C-93253r1_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that the password history is set to a length of \"0\". \n\nThis procedure is performed on the MDM console only. \n\nOn the MDM console, for the Workspace, in the \"Knox password constraints\" group, verify that \"password history length\" is set to \"0\". \n\nIf on the MDM console \"password history length\" is not set to \"0\", this is a finding.",
"description": "Password History Length controls the number of most recently used passwords stored in the Password History list. \n\nThe Password History list does not store the actual value of the previous passwords but instead calculates the hash value of the passwords. When the user attempts to set a new password, the hash value of the password is first calculated and the Password History list is checked to determine if it already contains a matching value, rejecting the password if it does. If the password is accepted, the oldest entry in the Password History list is removed, and the newly calculated password hash is added to the list. \n\nThe MDFPP requires that values derived from passwords are destroyed when no longer needed; therefore, the calculated hash values of previous passwords should not be stored in the Password History list. \n\nThis feature must be configured for a Samsung Android device to be in the NIAP-certified Common Criteria (CC) mode of operation.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100183r1_fix",
"fixtext": "Configure Samsung Android Workspace to set the password history with a length of \"0\". \n\nOn the MDM console, for the Workspace, in the \"Knox password constraints\" group, set \"password history length\" to \"0\".",
"iacontrols": null,
"id": "V-93935",
"ruleID": "SV-104021r1_rule",
"severity": "medium",
"title": "Samsung Android Workspace must be configured to set the password history with a length of 0.",
"version": "KNOX-09-001405"
},
"V-93937": {
"checkid": "C-93255r1_chk",
"checktext": "Review device configuration settings to confirm that Secure Startup is enabled. \n\nThis procedure is performed on the Samsung Android device prior to Galaxy S10 only. \n\nThis setting cannot be managed by the MDM administrator and is a User-Based Enforcement (UBE) requirement. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Biometric and security\". \n3. Tap \"Other security settings\". \n4. Tap \"Secure startup\". \n5. Verify that \"Require password when device powers on\" is already selected and \"Do not require\" is not selected. \n\nIf on the Samsung Android device \"Do not require\" is selected, this is a finding.",
"description": "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. \n\nThis feature must be enabled for a Samsung Android device to be in the NIAP-certified Common Criteria (CC) mode of operation.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100185r1_fix",
"fixtext": "Configure Samsung Android to enable Secure Startup. \n\nThis guidance is only applicable to devices prior to Galaxy S10. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Biometrics and security\". \n3. Tap \"Other security settings\". \n4. Tap \"Secure startup\". \n5. Tap option \"Require password when device powers on\". \n6. Tap \"Apply\". \n7. Enter the current password.",
"iacontrols": null,
"id": "V-93937",
"ruleID": "SV-104023r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to enforce that Secure Startup is enabled. This requirement is Not Applicable (NA) to Galaxy S10 (or newer) devices.",
"version": "KNOX-09-001425"
},
"V-93939": {
"checkid": "C-93257r2_chk",
"checktext": "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. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the device, in the \"Android password constraints\" group, verify that the \"minimum password quality\" is \"PIN\" (see note).\n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Lock screen\". \n3. Tap \"Screen lock type\". \n4. Verify that \"Swipe\u201d, \u201cPattern\u201d, and \u201cNone\" cannot be enabled. \n\nIf 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.\n\nNote: Some MDM consoles may display \u201cNumeric\u201d and \u201cNumeric-Complex\u201d instead of \u201cPIN\u201d. Either selection is acceptable but \u201cNumeric-Complex\u201d 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.\n",
"description": "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 likely to be in an unlocked state when acquired by an adversary, thus granting immediate access to the data on the mobile device and possibly access to DoD networks. \n\nSetting a lock type enables a screen-lock policy, and each lock type has a password strength. 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, and the size of the password space. A minimum level of complexity is needed to ensure a simple password or easily guessed password is not used. \n\nConfiguring a minimum password complexity mitigates both the risk associated with an adversary acquiring a device in an unlocked state and a screen lock type with a weak authentication factor.\n\nSFR ID: FMT_SMF_EXT.1.1 #2a",
"fixid": "F-100187r2_fix",
"fixtext": "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. \n\nOn the MDM console, for the device, in the \"Android password constraints\" group, set \"minimum password quality\" (or password type) to \"PIN\".\n\nNote: Some MDM consoles may display \u201cNumeric\u201d and \u201cNumeric-Complex\u201d instead of \u201cPIN\u201d. Either selection is acceptable but \u201cNumeric-Complex\u201d 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.\n",
"iacontrols": null,
"id": "V-93939",
"ruleID": "SV-104025r2_rule",
"severity": "medium",
"title": "Samsung Android must be configured to enable a screen-lock policy that will lock the display after a period of inactivity.",
"version": "KNOX-09-001445"
},
"V-93941": {
"checkid": "C-93259r1_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that passwords with less than four characters are prevented. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the Workspace, in the \"Knox password constraints\" group, verify that \"minimum password length\" is \"4\" or greater. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Workspace\". \n3. Tap \"Lock type\". \n4. Enter current password. \n5. Tap \"Password\". \n6. Verify that passwords with less than four characters are not accepted. \n\nIf on the MDM console \"minimum password length\" is greater than \"4\", or if on the Samsung Android device a password with fewer than four characters is accepted, this is a finding. \n\nNote: This configuration setting will allow users to implement fingerprint unlock for the CONTAINER, which is approved for use. The use of a password to move between CONTAINER and personal areas is only required if the password is needed to provide data separation between the two processing environments. For the Samsung devices, the password is required to enable the CONTAINER and implement data separation.",
"description": "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, and the size of the password space. The longer the minimum length of the password is, the larger the password space. Having a too-short minimum password length significantly reduces password strength, increasing the chance of password compromise and resulting device and data compromise.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100189r1_fix",
"fixtext": "Configure Samsung Android Workspace to enforce a minimum password length of four characters. \n\nOn the MDM console, for the Workspace, in the \"Knox password constraints\" group, set \"minimum password length\" to \"4\" or greater.",
"iacontrols": null,
"id": "V-93941",
"ruleID": "SV-104027r1_rule",
"severity": "medium",
"title": "Samsung Android Workspace must be configured to enforce a minimum password length of four characters.",
"version": "KNOX-09-001455"
},
"V-93943": {
"checkid": "C-93261r1_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that passwords with two repeating or sequential characters are prevented. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the Workspace, do the following: \n1. In the \"Knox password constraint\" group, verify that \"maximum sequential characters\" is \"2\" or less. \n2. In the \"Knox password constraint\" group, verify that \"maximum sequential numbers\" is \"2\" or less. \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Workspace\". \n3. Tap \"Lock type\". \n4. Enter current password. \n5. Tap \"Password\". \n6. Verify that passwords with two or more sequential characters or numbers are not accepted. \n\nIf 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.",
"description": "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 sequential characters. Therefore, disallowing repeating or sequential characters increases password strength and decreases risk.\n\nSFR ID: FMT_SMF_EXT.1.1 #1b",
"fixid": "F-100191r1_fix",
"fixtext": "Configure Samsung Android Workspace to prevent passwords from containing more than two repeating or sequential characters. \n\nOn the MDM console, for the Workspace, in the \"Knox password constraints\" group: \n1. Set \"maximum sequential characters\" to \"2\". \n2. Set \"maximum sequential numbers\" to \"2\".",
"iacontrols": null,
"id": "V-93943",
"ruleID": "SV-104029r1_rule",
"severity": "low",
"title": "Samsung Android Workspace must be configured to not allow passwords that include more than two repeating or sequential characters.",
"version": "KNOX-09-001465"
},
"V-93945": {
"checkid": "C-93263r2_chk",
"checktext": "Review the Samsung Android Workspace configuration settings to confirm that the device uses a screen-lock policy that will lock the Workspace after a period of inactivity and that the lock type is configured with a minimum password quality. \n\nThis procedure is performed on both the MDM Administration console and the Samsung Android device. \n\nOn the MDM console, for the Workspace, in the \"Knox password constraints\" group, verify that the \"minimum password quality\" is \"PIN\". \n\nOn the Samsung Android device, do the following: \n1. Open Settings. \n2. Tap \"Workspace\". \n3. Tap \"Lock type\". \n4. Verify that \"Swipe, Pattern, and None\" cannot be enabled. \n\nIf on the MDM console \"minimum password quality\" is not set to \"PIN\", or on the Samsung Android device the user can select a lock type other than \"password\", this is a finding.\nNote: Some MDM consoles may display \u201cNumeric\u201d and \u201cNumeric-Complex\u201d instead of \u201cPIN\u201d. Either selection is acceptable but \u201cNumeric-Complex\u201d 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.\n",
"description": "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 likely to be in an unlocked state when acquired by an adversary, thus granting immediate access to the data on the mobile device and possibly access to DoD networks. \n\nSetting a lock type enables a screen-lock policy, and each lock type has a password strength. 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, and the size of the password space. A minimum level of complexity is needed to ensure a simple password or easily guessed password is not used. \n\nConfiguring a minimum password complexity mitigates both the risk associated with an adversary acquiring a device in an unlocked state and a screen lock type with a weak authentication factor.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100193r2_fix",
"fixtext": "Configure Samsung Android Workspace to enforce a screen-lock policy that will lock the Workspace after a period of inactivity with a lock type that is configured with a minimum password quality. \n\nOn the MDM console, for the Workspace, in the \"Knox password constraints\" group, set \"minimum password quality\" to \"PIN\".\n\nNote: Some MDM consoles may display \u201cNumeric\u201d and \u201cNumeric-Complex\u201d instead of \u201cPIN\u201d. Either selection is acceptable but \u201cNumeric-Complex\u201d 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.\n",
"iacontrols": null,
"id": "V-93945",
"ruleID": "SV-104031r2_rule",
"severity": "medium",
"title": "Samsung Android Workspace must be configured to enable a screen-lock policy that will lock the Workspace after a period of inactivity.",
"version": "KNOX-09-001475"
},
"V-93947": {
"checkid": "C-93265r1_chk",
"checktext": "Review device configuration settings to confirm that Strong Protection is enabled.\n\nThis procedure is performed on the Samsung Android Galaxy S10 (or newer) devices only.\n\nThis setting cannot be managed by the MDM administrator and is a User-Based Enforcement (UBE) requirement.\n\nOn the Samsung Android device, do the following:\n1. Open Settings.\n2. Tap \"Biometric and security\".\n3. Tap \"Other security settings\".\n4. Verify \"Strong Protection\" is enabled.\n\nIf on the Samsung Android device \"Strong Protection\u201d is disabled, this is a finding.",
"description": "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.\n\nThis feature must be enabled for a Samsung Android device to be in the NIAP-certified CC mode of operation.\n\nSFR ID: FMT_SMF_EXT.1.1 #47",
"fixid": "F-100195r1_fix",
"fixtext": "Configure Samsung Android to enable Strong Protection.\n\nThis guidance is only applicable to Galaxy S10 (or newer) devices.\n\nOn the Samsung Android device, do the following:\n1. Open Settings.\n2. Tap \"Biometrics and security\".\n3. Tap \"Other security settings\".\n4. Tap \"Strong Protection\".\n5. Tap to enable.\n6. Enter the current password.",
"iacontrols": null,
"id": "V-93947",
"ruleID": "SV-104033r1_rule",
"severity": "medium",
"title": "Samsung Android must be configured to enforce that Strong Protection is enabled. This requirement is Not Applicable (NA) for devices older than Galaxy S10.",
"version": "KNOX-09-001485"
}
},
"profiles": {
"MAC-1_Classified": {
"description": "",
"findings": {
"V-93845": "true",
"V-93847": "true",
"V-93849": "true",
"V-93851": "true",
"V-93853": "true",
"V-93855": "true",
"V-93857": "true",
"V-93859": "true",
"V-93861": "true",
"V-93863": "true",
"V-93865": "true",
"V-93867": "true",
"V-93869": "true",
"V-93871": "true",
"V-93873": "true",
"V-93875": "true",
"V-93877": "true",
"V-93879": "true",
"V-93881": "true",
"V-93883": "true",
"V-93885": "true",
"V-93887": "true",
"V-93889": "true",
"V-93891": "true",
"V-93893": "true",
"V-93895": "true",
"V-93897": "true",
"V-93899": "true",
"V-93901": "true",
"V-93903": "true",
"V-93905": "true",
"V-93907": "true",
"V-93909": "true",
"V-93911": "true",
"V-93913": "true",
"V-93915": "true",
"V-93917": "true",
"V-93921": "true",
"V-93923": "true",
"V-93925": "true",
"V-93927": "true",
"V-93929": "true",
"V-93931": "true",
"V-93933": "true",
"V-93935": "true",
"V-93937": "true",
"V-93939": "true",
"V-93941": "true",
"V-93943": "true",
"V-93945": "true",
"V-93947": "true"
},
"id": "MAC-1_Classified",
"title": "I - Mission Critical Classified"
},
"MAC-1_Public": {
"description": "",
"findings": {
"V-93845": "true",
"V-93847": "true",
"V-93849": "true",
"V-93851": "true",
"V-93853": "true",
"V-93855": "true",
"V-93857": "true",
"V-93859": "true",
"V-93861": "true",
"V-93863": "true",
"V-93865": "true",
"V-93867": "true",
"V-93869": "true",
"V-93871": "true",
"V-93873": "true",
"V-93875": "true",
"V-93877": "true",
"V-93879": "true",
"V-93881": "true",
"V-93883": "true",
"V-93885": "true",
"V-93887": "true",
"V-93889": "true",
"V-93891": "true",
"V-93893": "true",
"V-93895": "true",
"V-93897": "true",
"V-93899": "true",
"V-93901": "true",
"V-93903": "true",
"V-93905": "true",
"V-93907": "true",
"V-93909": "true",
"V-93911": "true",
"V-93913": "true",
"V-93915": "true",
"V-93917": "true",
"V-93921": "true",
"V-93923": "true",
"V-93925": "true",
"V-93927": "true",
"V-93929": "true",
"V-93931": "true",
"V-93933": "true",
"V-93935": "true",
"V-93937": "true",
"V-93939": "true",
"V-93941": "true",
"V-93943": "true",
"V-93945": "true",
"V-93947": "true"
},
"id": "MAC-1_Public",
"title": "I - Mission Critical Public"
},
"MAC-1_Sensitive": {
"description": "",
"findings": {
"V-93845": "true",
"V-93847": "true",
"V-93849": "true",
"V-93851": "true",
"V-93853": "true",
"V-93855": "true",
"V-93857": "true",
"V-93859": "true",
"V-93861": "true",
"V-93863": "true",
"V-93865": "true",
"V-93867": "true",
"V-93869": "true",
"V-93871": "true",
"V-93873": "true",
"V-93875": "true",
"V-93877": "true",
"V-93879": "true",
"V-93881": "true",
"V-93883": "true",
"V-93885": "true",
"V-93887": "true",
"V-93889": "true",
"V-93891": "true",
"V-93893": "true",
"V-93895": "true",
"V-93897": "true",
"V-93899": "true",
"V-93901": "true",
"V-93903": "true",
"V-93905": "true",
"V-93907": "true",
"V-93909": "true",
"V-93911": "true",
"V-93913": "true",
"V-93915": "true",
"V-93917": "true",
"V-93921": "true",
"V-93923": "true",
"V-93925": "true",
"V-93927": "true",
"V-93929": "true",
"V-93931": "true",
"V-93933": "true",
"V-93935": "true",
"V-93937": "true",
"V-93939": "true",
"V-93941": "true",
"V-93943": "true",
"V-93945": "true",
"V-93947": "true"
},
"id": "MAC-1_Sensitive",
"title": "I - Mission Critical Sensitive"
},
"MAC-2_Classified": {
"description": "",
"findings": {
"V-93845": "true",
"V-93847": "true",
"V-93849": "true",
"V-93851": "true",
"V-93853": "true",
"V-93855": "true",
"V-93857": "true",
"V-93859": "true",
"V-93861": "true",
"V-93863": "true",
"V-93865": "true",
"V-93867": "true",
"V-93869": "true",
"V-93871": "true",
"V-93873": "true",
"V-93875": "true",
"V-93877": "true",
"V-93879": "true",
"V-93881": "true",
"V-93883": "true",
"V-93885": "true",
"V-93887": "true",
"V-93889": "true",
"V-93891": "true",
"V-93893": "true",
"V-93895": "true",
"V-93897": "true",
"V-93899": "true",
"V-93901": "true",
"V-93903": "true",
"V-93905": "true",
"V-93907": "true",
"V-93909": "true",
"V-93911": "true",
"V-93913": "true",
"V-93915": "true",
"V-93917": "true",
"V-93921": "true",
"V-93923": "true",
"V-93925": "true",
"V-93927": "true",
"V-93929": "true",
"V-93931": "true",
"V-93933": "true",
"V-93935": "true",
"V-93937": "true",
"V-93939": "true",
"V-93941": "true",
"V-93943": "true",
"V-93945": "true",
"V-93947": "true"
},
"id": "MAC-2_Classified",
"title": "II - Mission Support Classified"
},
"MAC-2_Public": {
"description": "",
"findings": {
"V-93845": "true",
"V-93847": "true",
"V-93849": "true",
"V-93851": "true",
"V-93853": "true",
"V-93855": "true",
"V-93857": "true",
"V-93859": "true",
"V-93861": "true",
"V-93863": "true",
"V-93865": "true",
"V-93867": "true",
"V-93869": "true",
"V-93871": "true",
"V-93873": "true",
"V-93875": "true",
"V-93877": "true",
"V-93879": "true",
"V-93881": "true",
"V-93883": "true",
"V-93885": "true",
"V-93887": "true",
"V-93889": "true",
"V-93891": "true",
"V-93893": "true",
"V-93895": "true",
"V-93897": "true",
"V-93899": "true",
"V-93901": "true",
"V-93903": "true",
"V-93905": "true",
"V-93907": "true",
"V-93909": "true",
"V-93911": "true",
"V-93913": "true",
"V-93915": "true",
"V-93917": "true",
"V-93921": "true",
"V-93923": "true",
"V-93925": "true",
"V-93927": "true",
"V-93929": "true",
"V-93931": "true",
"V-93933": "true",
"V-93935": "true",
"V-93937": "true",
"V-93939": "true",
"V-93941": "true",
"V-93943": "true",
"V-93945": "true",
"V-93947": "true"
},
"id": "MAC-2_Public",
"title": "II - Mission Support Public"
},
"MAC-2_Sensitive": {
"description": "",
"findings": {
"V-93845": "true",
"V-93847": "true",
"V-93849": "true",
"V-93851": "true",
"V-93853": "true",
"V-93855": "true",
"V-93857": "true",
"V-93859": "true",
"V-93861": "true",
"V-93863": "true",
"V-93865": "true",
"V-93867": "true",
"V-93869": "true",
"V-93871": "true",
"V-93873": "true",
"V-93875": "true",
"V-93877": "true",
"V-93879": "true",
"V-93881": "true",
"V-93883": "true",
"V-93885": "true",
"V-93887": "true",
"V-93889": "true",
"V-93891": "true",
"V-93893": "true",
"V-93895": "true",
"V-93897": "true",
"V-93899": "true",
"V-93901": "true",
"V-93903": "true",
"V-93905": "true",
"V-93907": "true",
"V-93909": "true",
"V-93911": "true",
"V-93913": "true",
"V-93915": "true",
"V-93917": "true",
"V-93921": "true",
"V-93923": "true",
"V-93925": "true",
"V-93927": "true",
"V-93929": "true",
"V-93931": "true",
"V-93933": "true",
"V-93935": "true",
"V-93937": "true",
"V-93939": "true",
"V-93941": "true",
"V-93943": "true",
"V-93945": "true",
"V-93947": "true"
},
"id": "MAC-2_Sensitive",
"title": "II - Mission Support Sensitive"
},
"MAC-3_Classified": {
"description": "",
"findings": {
"V-93845": "true",
"V-93847": "true",
"V-93849": "true",
"V-93851": "true",
"V-93853": "true",
"V-93855": "true",
"V-93857": "true",
"V-93859": "true",
"V-93861": "true",
"V-93863": "true",
"V-93865": "true",
"V-93867": "true",
"V-93869": "true",
"V-93871": "true",
"V-93873": "true",
"V-93875": "true",
"V-93877": "true",
"V-93879": "true",
"V-93881": "true",
"V-93883": "true",
"V-93885": "true",
"V-93887": "true",
"V-93889": "true",
"V-93891": "true",
"V-93893": "true",
"V-93895": "true",
"V-93897": "true",
"V-93899": "true",
"V-93901": "true",
"V-93903": "true",
"V-93905": "true",
"V-93907": "true",
"V-93909": "true",
"V-93911": "true",
"V-93913": "true",
"V-93915": "true",
"V-93917": "true",
"V-93921": "true",
"V-93923": "true",
"V-93925": "true",
"V-93927": "true",
"V-93929": "true",
"V-93931": "true",
"V-93933": "true",
"V-93935": "true",
"V-93937": "true",
"V-93939": "true",
"V-93941": "true",
"V-93943": "true",
"V-93945": "true",
"V-93947": "true"
},
"id": "MAC-3_Classified",
"title": "III - Administrative Classified"
},
"MAC-3_Public": {
"description": "",
"findings": {
"V-93845": "true",
"V-93847": "true",
"V-93849": "true",
"V-93851": "true",
"V-93853": "true",
"V-93855": "true",
"V-93857": "true",
"V-93859": "true",
"V-93861": "true",
"V-93863": "true",
"V-93865": "true",
"V-93867": "true",
"V-93869": "true",
"V-93871": "true",
"V-93873": "true",
"V-93875": "true",
"V-93877": "true",
"V-93879": "true",
"V-93881": "true",
"V-93883": "true",
"V-93885": "true",
"V-93887": "true",
"V-93889": "true",
"V-93891": "true",
"V-93893": "true",
"V-93895": "true",
"V-93897": "true",
"V-93899": "true",
"V-93901": "true",
"V-93903": "true",
"V-93905": "true",
"V-93907": "true",
"V-93909": "true",
"V-93911": "true",
"V-93913": "true",
"V-93915": "true",
"V-93917": "true",
"V-93921": "true",
"V-93923": "true",
"V-93925": "true",
"V-93927": "true",
"V-93929": "true",
"V-93931": "true",
"V-93933": "true",
"V-93935": "true",
"V-93937": "true",
"V-93939": "true",
"V-93941": "true",
"V-93943": "true",
"V-93945": "true",
"V-93947": "true"
},
"id": "MAC-3_Public",
"title": "III - Administrative Public"
},
"MAC-3_Sensitive": {
"description": "",
"findings": {
"V-93845": "true",
"V-93847": "true",
"V-93849": "true",
"V-93851": "true",
"V-93853": "true",
"V-93855": "true",
"V-93857": "true",
"V-93859": "true",
"V-93861": "true",
"V-93863": "true",
"V-93865": "true",
"V-93867": "true",
"V-93869": "true",
"V-93871": "true",
"V-93873": "true",
"V-93875": "true",
"V-93877": "true",
"V-93879": "true",
"V-93881": "true",
"V-93883": "true",
"V-93885": "true",
"V-93887": "true",
"V-93889": "true",
"V-93891": "true",
"V-93893": "true",
"V-93895": "true",
"V-93897": "true",
"V-93899": "true",
"V-93901": "true",
"V-93903": "true",
"V-93905": "true",
"V-93907": "true",
"V-93909": "true",
"V-93911": "true",
"V-93913": "true",
"V-93915": "true",
"V-93917": "true",
"V-93921": "true",
"V-93923": "true",
"V-93925": "true",
"V-93927": "true",
"V-93929": "true",
"V-93931": "true",
"V-93933": "true",
"V-93935": "true",
"V-93937": "true",
"V-93939": "true",
"V-93941": "true",
"V-93943": "true",
"V-93945": "true",
"V-93947": "true"
},
"id": "MAC-3_Sensitive",
"title": "III - Administrative Sensitive"
}
},
"slug": "samsung_android_os_9_with_knox_3.x_cope_use_case_kpelegacy_deployment",
"title": "Samsung Android OS 9 with Knox 3.x COPE Use Case KPE(Legacy) Deployment Security Technical Implementation Guide",
"version": "1"
}
}