{"stig":{"title":"Samsung Android 14 MDFPP 3.3 BYOAD Security Technical Implementation Guide","version":"1","release":"3"},"checks":[{"vulnId":"V-260439","ruleId":"SV-260439r959010_rule","severity":"medium","ruleTitle":"Samsung Android must be enrolled as a BYOD device.","description":"The Work profile is the designated application group for the BYOD use case.\n\nSFR ID: FMT_MOF_EXT.1.2 #47","checkContent":"Review the configuration to determine if the Samsung Android devices are enrolled in a DOD-approved use case.\n\nThis validation procedure is performed on both the management tool Administration Console and the Samsung Android device. \n\nOn the management tool, verify the default enrollment is set to \"Work profile for personally-owned devices\".\n\nOn the Samsung Android device: \n1. Open Settings >> Security and privacy >> More security settings >> Device admin apps.\n2. Verify the management tool Agent is listed.\n3. Go to the app drawer.\n4. Verify a \"Personal\" and \"Work\" tab are present.\n\nIf on the management tool the default enrollment is not set as \"Work profile for personally-owned devices\", or on the Samsung Android device the \"Personal\" and \"Work\" tabs are not present or the management tool Agent is not listed, this is a finding.","fixText":"Enroll the Samsung Android devices in a DOD-approved use case.\n\nOn the management tool, configure the default enrollment as \"Work profile for personally-owned devices\".\n\nRefer to the management tool documentation to determine how to configure the device enrollment.","ccis":["CCI-000366"]},{"vulnId":"V-260440","ruleId":"SV-260440r958390_rule","severity":"low","ruleTitle":"Samsung Android must be configured to display the DOD advisory warning message at startup or each time the user unlocks the device.","description":"Before granting access to the system, the mobile operating system is required to display the DOD-approved system use notification message or banner 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 Knowledge Service 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. Refer to 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","checkContent":"The DOD warning banner can be displayed using the following method (required text is found in the Vulnerability Discussion):\n\nPlace the DOD warning banner in the user agreement signed by each Samsung Android device user (preferred method).\nNote: It is not possible for the EMM to force a warning banner be placed on the device screen when using \"work profile for employee-owned devices (BYOD)\" deployment mode.\n\nReview the signed user agreements for several Samsung Android device users and verify the agreement includes the required DOD warning banner text.\n\nIf the required warning banner text is not on all signed user agreements reviewed, this is a finding.","fixText":"Configure the DOD warning banner by either of the following methods (required text is found in the Vulnerability Description):\n\nPlace the DOD warning banner in the user agreement signed by each Samsung Android device user (preferred method).\n\nNote: It is not possible for the EMM to force a warning banner be placed on the device screen when using \"work profile for employee-owned devices (BYOD)\".","ccis":["CCI-000048"]},{"vulnId":"V-260441","ruleId":"SV-260441r985626_rule","severity":"medium","ruleTitle":"Samsung Android must be configured to not allow passwords that include more than four repeating or sequential characters.","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. Therefore, disallowing repeating or sequential characters increases password strength and decreases risk.\n\nSFR ID: FMT_SMF_EXT.1.1 #1b","checkContent":"Review the configuration to determine if the Samsung Android devices' Work Environment is disallowing passwords containing more than four repeating or sequential characters.\n\nThis validation procedure is performed on both the management tool and the Samsung Android device.\n\nOn the management tool, in the device password policies, verify \"minimum password quality\" is set to \"Numeric(Complex)\" or better.\n\nOn the Samsung Android device, confirm if the user has \"One Lock\" enabled (Settings >> Security and privacy >> More security settings >> Work profile security >> Use one lock).\n\nIf \"One Lock\" is enabled:\n1. Open Settings >> Lock screen >> Screen lock type.\n2. Enter current password. \n3. Tap \"PIN\". \n4. Verify that PINs with more than four repeating or sequential numbers are not accepted.\n\nIf \"One Lock\" is disabled:\n1. Open Settings >> Security and privacy >> More security settings >> Work profile security >> Work profile lock type.\n2. Enter current password. \n3. Tap \"PIN\". \n4. Verify that PINs with more than four repeating or sequential numbers are not accepted.\n\nIf on the management tool \"minimum password quality\" is not set to \"Numeric(Complex)\" or better, or on the Samsung Android device a password with more than four repeating or sequential numbers is accepted, this is a finding.","fixText":"Configure the Samsung Android devices to disallow passwords containing more than four repeating or sequential characters.\n\nOn the management tool, in the device password policies, set \"minimum password quality\" to \"Numeric(Complex)\" or better.\n\nIf the management tool does not support \"Numeric(Complex)\" but does support \"Numeric\", Knox Platform for Enterprise (KPE) can be used to achieve STIG compliance. In this case, configure this policy with value \"Numeric\" and use an additional KPE policy (innately by the management tool or via KSP) \"Maximum Numeric Sequence Length\" with value \"4\".","ccis":["CCI-000195"]},{"vulnId":"V-260442","ruleId":"SV-260442r985624_rule","severity":"medium","ruleTitle":"Samsung Android must be configured to enforce a minimum password length of six characters.","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 complete 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","checkContent":"Review the configuration to determine if the Samsung Android devices' Work Environment is enforcing a minimum password length of six characters.\n\nThis validation procedure is performed on both the management tool and the Samsung Android device.\n\nOn the management tool, in the Work Environment password policies, verify \"minimum password length\" is set to \"6\".\n\nOn the Samsung Android device, confirm if the user has \"One Lock\" enabled (Settings >> Security and privacy >> More security settings >> Work profile security >> Use one lock).\n\nIf \"One Lock\" is enabled:\n1. Open Settings >> Lock screen >> Screen lock type.\n2. Enter current password.\n3. Tap \"PIN\".\n4. Verify the text \"PIN must contain at least\", followed by a value of at least \"6 digits\", appears above the PIN entry.\n\nIf \"One Lock\" is disabled:\n1. Open Settings >> Security and privacy >> More security settings >> Work profile security >> Work profile lock type.\n2. Enter current password.\n3. Tap \"PIN\".\n4. Verify the text \"PIN must contain at least\", followed by a value of at least \"6 digits\", appears above the PIN entry.\n\nIf on the management tool \"minimum password length\" is not set to \"6\", or on the Samsung Android device the text \"PIN must contain at least\" is followed by a value of less than \"6 digits\", this is a finding.","fixText":"Configure the Samsung Android devices to enforce a minimum password length of six characters.\n\nOn the management tool, in the device password policies, set \"minimum password length\" to \"6\".","ccis":["CCI-000205"]},{"vulnId":"V-260443","ruleId":"SV-260443r958388_rule","severity":"medium","ruleTitle":"Samsung Android must be configured to not allow more than 10 consecutive failed authentication attempts.","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 fewer attempts 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","checkContent":"Review the configuration to determine if the Samsung Android devices' Work Environment is allowing only 10 or fewer consecutive failed authentication attempts.\n\nThis validation procedure is performed on both the management tool and the Samsung Android device.\n\nOn the management tool, in the device password policies, verify \"max password failures for local wipe\" is set to \"10\" attempts or less.\n\nOn the Samsung Android device, confirm if the user has \"One Lock\" enabled (Settings >> Security and privacy >> More security settings >> Work profile security >> Use one lock).\n\nIf \"One Lock\" is enabled:\n1. Lock the device.\n2. Make attempts to unlock the Device with incorrect PIN and validate that the device reports that if you do not enter the correct PIN within the next few attempts that a wipe will occur.\n\nIf \"One Lock\" is disabled:\n1. Wait for the Work profile to Lock (determined by Auto lock work profile configuration) - or reboot the Device.\n2. Attempt to unlock the Work profile with an incorrect PIN and validate that the device reports \"9\" or less attempts left.\n\nIf on the management tool \"max password failures for local wipe\" is not set to \"10\" attempts or less, or on the Samsung Android device - after making incorrect PIN entry attempts - it does not report that the device will wipe, this is a finding.","fixText":"Configure the Samsung Android devices to allow only 10 or fewer consecutive failed authentication attempts.\n\nOn the management tool, in the device password policies, set \"max password failures for local wipe\" to \"10\" attempts or fewer.\n\nA device password must be set for \"max password failures for local wipe\" to become active.","ccis":["CCI-000044"]},{"vulnId":"V-260445","ruleId":"SV-260445r985628_rule","severity":"medium","ruleTitle":"Samsung Android must be configured to disable authentication mechanisms providing user access to protected data other than a Password Authentication Factor: Face recognition.","description":"The biometric factor can be used to authenticate the user to unlock the mobile device. Unapproved/evaluated biometric mechanisms could allow unauthorized users to have access to DOD sensitive data if compromised. By not permitting the use of unapproved/evaluated biometric authentication mechanisms, this risk is mitigated.\n\nSFR ID: FMT_SMF_EXT.1.1 #22, FIA_UAU.5.1","checkContent":"Note: This requirement is not applicable for specific biometric authentication factors included in the product's Common Criteria evaluation.\n\nReview the configuration to determine if the Samsung Android devices' Work Environment is disabling Face Recognition.\n\nThis validation procedure is performed on both the management tool and the Samsung Android device.\n\nFace recognition is not a feature available for unlocking the Work profile unless \"One Lock\" is used.\n\nOtherwise, on the management tool, in the Work Environment restrictions, verify that \"Face\" is set to \"Disable\".\n\nOn the Samsung Android device, confirm if the user has \"One Lock\" enabled (Settings >> Security and privacy >> More security settings >> Work profile security >> Use one lock).\n\nIf \"One Lock\" is enabled:\n1. Open Settings >> Lock screen >> Screen lock type.\n2. Enter current password.\n3. Verify that \"Face\" is disabled and cannot be enabled.\n\nThe disablement of Face cannot be verified while \"One Lock\" is disabled, as they are not an available feature for Work profiles. To verify, the Admin would need to temporarily enable \"One Lock\" for the purpose of testing only and follow the above instruction. After testing, the User would have to reset their Work profile password when \"One Lock\" was turned off again.\n\nIf on the management tool \"Face\" is not set to \"Disable\", or on the Samsung Android device \"Face\" can be enabled, this is a finding.","fixText":"Note: This requirement is not applicable for specific biometric authentication factors included in the product's Common Criteria evaluation.\n\nConfigure the Samsung Android devices to disable Face Recognition.\n\nOn the management tool, in the device restrictions, set \"Face Recognition\" to \"Disable\".","ccis":["CCI-000767"]},{"vulnId":"V-260446","ruleId":"SV-260446r971318_rule","severity":"medium","ruleTitle":"Samsung Android must be configured to enable a screen-lock policy that will lock the display after a period of inactivity - Disable trust agents.","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 #2a","checkContent":"Review the configuration to determine if the Samsung Android devices' Work Environment is disabling Trust Agents.\n\nThis validation procedure is performed on both the management tool and the Samsung Android device.\n\nOn the management tool, in the device restrictions, verify that \"Trust Agents\" are set to \"Disable\".\n\nOn the Samsung Android device, confirm if the user has \"One Lock\" enabled (Settings >> Security and privacy >> More security settings >> Work profile security >> Use one lock).\n\nIf \"One Lock\" is enabled:\n1. Open Settings >> Security and privacy >> More security settings >> Trust agents.\n2. Verify that all listed Trust Agents are disabled and cannot be enabled.\n\nThe disablement of Trust Agents cannot be verified while \"One Lock\" is disabled, as they are not an available feature for Work profiles. To verify, the Admin would need to temporarily enable \"One Lock\" for the purpose of testing only and follow the above instruction. After testing, the User would have to reset their Work profile password when \"One Lock\" was turned off again.\n\nIf on the management tool \"Trust Agents\" are not set to \"Disable\", or on the Samsung Android device a \"Trust Agent\" can be enabled, this is a finding.\n\nNote: If the management tool has been correctly configured but a Trust Agent is still enabled, configure the \"List of approved apps listed in managed Google Play\" to disable it; refer to KNOX-14-710190.\n\nException: Trust Agents may be used if the Authorizing Official (AO) allows a screen lock timeout after four hours (or more) of inactivity. This may be applicable to tactical use case.","fixText":"Configure the Samsung Android devices to disable Trust Agents.\n\nOn the management tool, in the device restrictions, set \"Trust Agents\" to \"Disable\".","ccis":["CCI-000767"]},{"vulnId":"V-260447","ruleId":"SV-260447r959010_rule","severity":"medium","ruleTitle":"Samsung Android's Work profile must have the DOD root and intermediate PKI certificates installed.","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_MOF_EXT.1.2 #47","checkContent":"Review the configuration to determine if the Samsung Android's Work profile has the DOD root and intermediate PKI certificates installed.\n\nThis validation procedure is performed on both the management tool and the Samsung Android device.\n\nThe current DOD root and intermediate PKI certificates may be obtained in self-extracting zip files at https://cyber.mil/pki-pke (for NIPRNet).\n\nOn the management tool, in the Work profile policy management, verify the DOD root and intermediate PKI certificates are installed.\n\nOn the Samsung Android device: \n1. Open Settings >> Security and privacy >> More security settings >> View security certificates.\n2. In the User tab, verify the DOD root and intermediate PKI certificates are listed in the Work profile.\n\nIf on the management tool the DOD root and intermediate PKI certificates are not listed in the Work profile, or on the Samsung Android device the DOD root and intermediate PKI certificates are not listed in the Work profile, this is a finding.","fixText":"Install the DOD root and intermediate PKI certificates into the Samsung Android devices' Work profile.\n\nThe current DOD root and intermediate PKI certificates may be obtained in self-extracting zip files at https://cyber.mil/pki-pke (for NIPRNet).\n\nOn the management tool, in the Work profile policy management, install the DOD root and intermediate PKI certificates.","ccis":["CCI-000366"]},{"vulnId":"V-260448","ruleId":"SV-260448r958804_rule","severity":"medium","ruleTitle":"Samsung Android's Work profile must be configured to enforce an application installation policy by specifying an application allowlist that restricts applications by the following characteristics: Names.","description":"The application allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all core and preinstalled applications, or the MD must provide an alternate method of restricting user access/execution to core and preinstalled applications. \n\nCore application: Any application integrated into the OS by the OS or MD vendors.\n\nPreinstalled application: Additional noncore applications included in the OS build by the OS vendor, MD vendor, or wireless carrier.\n\nRequiring all authorized applications to be in an application allowlist prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allowlist. Failure to configure an application allowlist 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 allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all core applications (included in the OS by the OS vendor) and preinstalled applications (provided by the MD vendor and wireless carrier), or the MD must provide an alternate method of restricting user access/execution to core and preinstalled applications.\n\nSFR ID: FMT_SMF_EXT.1.1 #8b","checkContent":"Review the configuration to determine if the Work profile on the Samsung Android device is allowing users to install only applications that have been approved by the Authorizing Official (AO).\n\nThis validation procedure is performed only on the management tool.\n\nOn the management tool, in the app catalog for managed Google Play, verify that only AO-approved apps are available.\n\nIf on the management tool the app catalog for managed Google Play includes non-AO-approved apps, this is a finding.","fixText":"Configure the Work profile on Samsung Android devices to allow users to install only applications that have been approved by the AO.\n\nIn addition to any local policy, the AO must not approve applications that have certain prohibited characteristic; these are covered in KNOX-14-710200.\n\nOn the management tool, in the app catalog for managed Google Play, add each AO-approved app to be available.\n\nNote: Managed Google Play is an allowed App Store.","ccis":["CCI-001764"]},{"vulnId":"V-260449","ruleId":"SV-260449r1032950_rule","severity":"medium","ruleTitle":"Samsung Android's Work profile must be configured to not allow installation of applications with the following characteristics: \n\n- Back up MD data to non-DOD cloud servers (including user and application access to cloud backup services);\n- Transmit MD diagnostic data to non-DOD servers;\n- Voice assistant application if available when MD is locked;\n- Voice dialing application if available when MD is locked;\n- Allows synchronization of data or applications between devices associated with user; and\n- Allows unencrypted (or encrypted but not FIPS 140-3 validated) data sharing with other MDs or printers.\n- Apps which backup their own data to a remote system.","description":"Requiring all authorized applications to be in an application allowlist prevents the execution of any applications (e.g., unauthorized, malicious) that are not part of the allowlist. Failure to configure an application allowlist 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 allowlist, in addition to controlling the installation of applications on the MD, must control user access/execution of all core and preinstalled applications, or the MD must provide an alternate method of restricting user access/execution to core and preinstalled applications.\n\nCore application: Any application integrated into the OS by the OS or MD vendors.\n\nPreinstalled application: Additional noncore applications included in the OS build by the OS vendor, MD vendor, or wireless carrier.\n\nSFR ID: FMT_SMF_EXT.1.1 #8b","checkContent":"Verify requirement KNOX-14-710190 (managed Google Play) has been implemented. Verify the application allowlist does not include applications with the following characteristics:\n\n- Back up MD data to non-DOD cloud servers (including user and application access to cloud backup services);\n- Transmit MD diagnostic data to non-DOD servers;\n- Voice assistant application if available when MD is locked;\n- Voice dialing application if available when MD is locked;\n- Allows synchronization of data or applications between devices associated with user;\n- Payment processing; and\n- Allows unencrypted (or encrypted but not FIPS 140-3 validated) data sharing with other MDs, display screens (screen mirroring), or printers.\n- Apps which backup their own data to a remote system. If managed Google Play has not been implemented, this is a finding.\n\nThis validation procedure is performed only on the EMM Administration Console.\n\nOn the EMM console:\n\n1. Review the list of selected Managed Google Play apps.\n2. Review the details and privacy policy of each selected app to ensure the app does not include prohibited characteristics.\n\nIf the EMM console device policy includes applications with unauthorized characteristics, this is a finding.","fixText":"The Authorizing Official (AO) must not approve applications with the following characteristics for installation by users in the Work profile:\n\n- Back up MD data to non-DOD cloud servers (including user and application access to cloud backup services);\n- Transmit MD diagnostic data to non-DOD servers;\n- Voice assistant application if available when MD is locked;\n- Voice dialing application if available when MD is locked;\n- Allows synchronization of data or applications between devices associated with user;\n- Payment processing; and\n- Allows unencrypted (or encrypted but not FIPS 140-3 validated) data sharing with other MDs, display screens (screen mirroring), or printers.\n- Apps which backup their own data to a remote system.\n\nImplement managed Google Play (refer to requirement KNOX-14-710190).","ccis":["CCI-000366","CCI-000803"]},{"vulnId":"V-260450","ruleId":"SV-260450r958404_rule","severity":"medium","ruleTitle":"Samsung Android must be configured to not display the following (Work Environment) notifications when the device is locked: All notifications.","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 MOS to not send notifications to the lock screen mitigates this risk.\n\nSFR ID: FMT_SMF_EXT.1.1 #18","checkContent":"Review the configuration to determine if the Samsung Android devices are not displaying (Work Environment) notifications when the device is locked.\n\nNotifications of incoming phone calls are acceptable even when the device is locked.\n\nThis validation procedure is performed on both the management tool Administration Console and the Samsung Android device.\n\nOn the management tool, in the Work profile restrictions section, verify \"Unredacted Notifications\" is set to \"Disallow\".\n\nOn the Samsung Android device: \n1. Open Settings >> Notifications >> Lock screen notifications.\n2. Verify \"Sensitive work profile notifications\" is disabled.\n\nIf on the management tool \"Unredacted Notifications\" is not set to \"Disallow\", or on the Samsung Android device \"Sensitive work profile notifications\" is not disabled, this is a finding.","fixText":"Configure the Samsung Android devices to not display (Work Environment) notifications when the device is locked.\n\nOn the management tool, in the Work profile restrictions section, set \"Unredacted Notifications\" to \"Disallow\".","ccis":["CCI-000060"]},{"vulnId":"V-260451","ruleId":"SV-260451r959010_rule","severity":"medium","ruleTitle":"Samsung Android's Work profile must be configured to prevent users from adding personal email accounts to the work email app.","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 to allowlisted accounts mitigates this vulnerability.\n\nSFR ID: FMT_MOF_EXT.1.2 #47","checkContent":"Review the configuration to determine if the Samsung Android devices are preventing users from adding personal email accounts to the work email app.\n\nOn the management tool, in the device restrictions section, verify \"Modify accounts\" is set to \"Disallow\".\n\nOn the Samsung Android device: \n1. Open Settings >> Accounts and backup >> Manage accounts.\n2. Navigate to the \"Work\" tab.\n3. Verify no account can be added.\n\nIf on the management tool \"Modify accounts\" is not set to \"Disallow\", or on the Samsung Android device an account can be added, this is a finding.","fixText":"Configure the Samsung Android devices to prevent users from adding personal email accounts to the work email app.\n\nOn the management tool, in the Work profile restrictions, set \"Modify accounts\" to \"Disallow\".","ccis":["CCI-000366"]},{"vulnId":"V-260452","ruleId":"SV-260452r1137819_rule","severity":"medium","ruleTitle":"Samsung Android's Work profile must be configured to not allow backup of all applications, configuration data to remote systems.- Disable Data Sync Framework.","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 MOS. 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. The Data Sync Framework allows apps to synchronize data between the mobile device and other web based services. This uses accounts for services the user has added to the mobile device. Preventing the user from adding accounts to the device mitigates this risk.\n\nFor BYOD Work profile data cannot be backed up remotely via Backup Services. Work profile data could be backed up thru adding an account to an app that supports the data sync framework, however, this is mitigated by preventing adding any accounts to the Work profile.\n\nSFR ID: FMT_SMF_EXT.1.1 #40","checkContent":"Verify requirement KNOX-14-710230 (disallow modify accounts) has been implemented.\n\nIf \"disallow modify accounts\" has not been implemented, this is a finding.","fixText":"Disallow modify accounts (refer to requirement KNOX-14-710230).","ccis":["CCI-001090"]},{"vulnId":"V-260453","ruleId":"SV-260453r1137824_rule","severity":"medium","ruleTitle":"Samsung Android's Work profile must be configured to disable exceptions to the access control policy that prevent application processes and groups of application processes from accessing all data stored by other application processes and groups of application processes.","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, primarily from sharing data from personal (unmanaged) apps and work (managed) apps. 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\nCopy/paste of 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","checkContent":"Review the Samsung documentation and inspect the configuration to verify the Samsung Android devices are enabling an access control policy that prevents application processes and groups of application processes from accessing all data stored by other application processes and groups of application processes.\n\nThis validation procedure is performed on both the management tool and the Samsung Android device.\n\nOn the management tool, in the Work profile restrictions, set \"Cross profile copy/paste\" to \"Disallow\".\n\nOn the Samsung Android device: \n1. Using any Work app, copy text to the clipboard.\n2. Using any Personal app, verify the clipboard text cannot be pasted.\n\nIf on the management tool \"Cross profile copy/paste\" is not set to \"Disallow\", or on the Samsung Android device the clipboard text can be pasted into a Personal app, this is a finding.","fixText":"Configure the Samsung Android devices to enable an access control policy that prevents application processes and groups of application processes from accessing all data stored by other application processes and groups of application processes.\n\nOn the management tool, in the Work profile restrictions section, set \"Cross profile copy/paste\" to \"Disallow\".","ccis":["CCI-002233","CCI-002530"]},{"vulnId":"V-260454","ruleId":"SV-260454r959010_rule","severity":"medium","ruleTitle":"Samsung Android's Work profile must allow only the Administrator (management tool) to perform the following management function: Install/remove DOD root and intermediate PKI certificates.","description":"DOD root and intermediate PKI certificates are used to verify the authenticity of PKI certificates of users and web services. If the user is allowed to remove root and intermediate certificates, the user could allow an adversary to falsely sign a certificate in such a way that it could not be detected. Restricting the ability to remove DOD root and intermediate PKI certificates to the Administrator mitigates this risk.\n\nSFR ID: FMT_MOF_EXT.1.2 #47","checkContent":"Review the configuration to determine if the Samsung Android devices' Work profile is preventing users from removing DOD root and intermediate PKI certificates.\n\nThis validation procedure is performed on both the management tool and the Samsung Android device.\n\nOn the management tool, in the Work profile restrictions, verify \"Configure credentials\" is set to \"Disallow\".\n\nOn the Samsung Android device: \n1. Open Settings >> Security and privacy >> More security settings >> View security certificates.\n2. In the System tab, verify no listed certificate in the Work profile can be untrusted.\n3. In the User tab, verify no listed certificate in the Work profile can be removed.\n\nIf on the management tool the device \"Configure credentials\" is not set to \"Disallow\", or on the Samsung Android device a certificate can be untrusted or removed, this is a finding.","fixText":"Configure the Samsung Android devices' Work profile to prevent users from removing DOD root and intermediate PKI certificates.\n\nOn the management tool, in the Work profile restrictions, set \"Configure credentials\" to \"Disallow\".","ccis":["CCI-000366"]},{"vulnId":"V-260455","ruleId":"SV-260455r959010_rule","severity":"medium","ruleTitle":"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, management tool server, or mobile application store.","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","checkContent":"Review the configuration to determine if the Samsung Android devices are disabling unauthorized application repositories.\n\nThis validation procedure is performed on both the management tool and the Samsung Android device.\n\nOn the management tool, in the Work profile restrictions, verify \"installs from unknown sources globally\" is set to \"Disallow\".\n\nOn the Samsung Android device:\n1. Open Settings >> Security and privacy >> More security settings >> Install unknown apps.\n2. In the \"Personal\" tab, verify that each app listed has the status \"Disabled\" under the app name or no apps are listed.\n3. In the \"Work\" tab, verify that each app listed has the status \"Disabled\" under the app name or no apps are listed.\n\nIf on the management tool \"installs from unknown sources globally\" is not set to \"Disallow\", or on the Samsung Android device an app is listed with a status other than \"Disabled\", this is a finding.","fixText":"Configure the Samsung Android devices to disable unauthorized application repositories.\n\nOn the management tool, in the Work profile restrictions, set \"installs from unknown sources globally\" to \"Disallow\".\n\nNote: Google Play must not be disabled. Disabling Google Play will cause system instability and critical updates will not be received.","ccis":["CCI-000366"]},{"vulnId":"V-260456","ruleId":"SV-260456r959010_rule","severity":"medium","ruleTitle":"Samsung Android device users must complete required training.","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: FMT_MOF_EXT.1.2 #47","checkContent":"Review a sample of site User Agreements for Samsung device users or similar training records and training course content. \n\nVerify Samsung device users have completed 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.","fixText":"Have all Samsung device users complete training on the following topics. Users should acknowledge 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 report any loss of control so the credentials can be revoked. Upon device retirement, turn-in, or reassignment, ensure 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 **Do not remove DOD intermediate and root PKI digital certificates \n **Do not configure a DOD network (work) VPN profile on any third-party VPN client installed in the personal space \n-How to implement One Lock.\n-Screenshots will not be taken of any “work” related managed data.-Screenshots will not be taken of any “work” related managed data.","ccis":["CCI-000366"]},{"vulnId":"V-260457","ruleId":"SV-260457r959010_rule","severity":"high","ruleTitle":"The Samsung Android device must have the latest available Samsung Android operating system (OS) installed.","description":"Required security features are not available in earlier OS versions. In addition, earlier versions may have known vulnerabilities.\n\nSFR ID: FMT_MOF_EXT.1.2 #47","checkContent":"Review the configuration to confirm if the Samsung Android devices have the most recently released version of Samsung Android installed.\n\nThis procedure is performed on both the management tool and the Samsung Android device. \n\nIn the management tool management console, review the version of Samsung Android installed on a sample of managed devices. This procedure will vary depending on the management tool product. Refer to the notes below to determine the latest available OS version.\n\nOn the Samsung Android device, to determine the installed OS version:\n1. Open Settings.\n2. Tap \"About phone\".\n3. Tap \"Software information\".\n\nIf the installed version of Android OS 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 OS release by mobile device model online:\n\nATT: https://www.att.com/devicehowto/dsm.html#!/popular/make/Samsung\n\nVerizon Wireless: https://www.verizonwireless.com/support/software-updates/\n\nGoogle Android OS patch website: https://source.android.com/security/bulletin/ \n\nSamsung Android OS patch website: https://security.samsungmobile.com/securityUpdate.smsb","fixText":"Install the latest released version of Samsung Android OS on all managed Samsung devices. \n\nNote: In most cases, OS updates are released by the wireless carrier (for example, T-Mobile, Verizon Wireless, and ATT).","ccis":["CCI-000366"]},{"vulnId":"V-260458","ruleId":"SV-260458r1120908_rule","severity":"low","ruleTitle":"Samsung Android 14 must prohibit DOD VPN profiles in the Personal Profile.","description":"If DOD VPN profiles are configured in the Personal Profile DOD sensitive data world be at risk of compromise and the DOD network could be at risk of being attacked by malware installed on the device.\n\nSFR ID: FMT_SMF_EXT.1.1 #3","checkContent":"Review the list of VPN profiles in the Personal Profile and determine if any VPN profiles are listed. If so, verify the VPN profiles are not configured with a DOD network VPN profile.\n\nIf any VPN profiles are installed in the Personal Profile and they have a DOD network VPN profile configured, this is a finding.\n\nNote: This setting cannot be managed by the MDM administrator and is a User-Based Enforcement (UBE) requirement.","fixText":"Do not configure DOD VPN profiles in the Personal Profile.","ccis":["CCI-000366"]},{"vulnId":"V-260459","ruleId":"SV-260459r959010_rule","severity":"medium","ruleTitle":"The Samsung Android device must be configured to enable Certificate Revocation List (CRL) status checking.","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. For this reason, users must not be able to disable this configuration.\n\nSamsung Android can control CRL checking but only using Knox APIs. Alternatively, CRL checking is based on app development best practice.\n\nSFR ID: FMT_MOF_EXT.1.2 #47","checkContent":"Review the configuration to confirm that revocation checking is enabled. Verify the revocation checklist is set to \"All Applications\".\n \nThis procedure is performed on the management tool. \n\nOn the management tool:\n1. Open Certificates Policy >> Revocation section.\n2. Select \"Get CRL\".\n3. Verify Toast message \"Get revocation check: true\".\n\nIf on the management tool the revocation check is disabled, this is a finding.","fixText":"Configure the Samsung Android devices to enable CRL revocation checks for all applications. These revocation checks must be enabled using the Knox KPE APIs.\n\nOn the management tool, in the Certificate Policy restrictions, enable \"Revocation Checks\" for \"All Applications\".","ccis":["CCI-000366"]},{"vulnId":"V-260460","ruleId":"SV-260460r959010_rule","severity":"medium","ruleTitle":"The Samsung Android device work profile must be configured to enforce the system application disable list.","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 14 by Samsung. \n \nPreinstalled application: Additional noncore applications included in the Samsung Android 14 build by 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","checkContent":"Review the configuration to confirm the system application disable list is enforced. This setting is enforced by default. Verify only approved system apps have been placed on the core allowlist.\n \nThis procedure is performed on the management tool. \n \nReview the system app allowlist and verify only approved apps are on the list.\n\nOn the management tool, in the Apps management section, select \"Unhide apps\" and verify the names of the apps listed.\n\nIf on the management tool the system app allowlist contains unapproved core apps, this is a finding.","fixText":"Configure the Samsung Android 14 device to enforce the system application disable list. \n\nThe required configuration is the default configuration when the device is enrolled. If the device configuration is changed, use the following procedure to bring the device back into compliance:\n\nOn the management tool:\n1. Open \"Apps management\" section.\n2. Select \"Hide apps\".\n3. Enter names of apps to hide.\n\nConfigure a list of approved Samsung core and preinstalled apps in the core app allowlist.","ccis":["CCI-000366"]},{"vulnId":"V-260461","ruleId":"SV-260461r959010_rule","severity":"medium","ruleTitle":"The Samsung Android device work profile must be configured to disable automatic completion of workspace internet browser text input.","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 Android 14 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","checkContent":"Review the work profile Chrome Browser app on the Samsung Android 14 autofill setting.\n\nThis validation procedure is performed on the management tool.\n\nOn the management tool:\n1. Open \"Managed Configurations\" section.\n2. Select the Chrome Browser version from the work profile.\n3. Verify \"PasswordManagerEnabled\" is turned \"OFF\".\n4. Verify \"AutofillAddressEnabled\" is turned \"OFF\".\n5. Verify \"AutofillCreditCardEnabled\" is turned \"OFF\".\n\nIf on the management tool any of the browser autofill settings are set to \"On\" in the Chrome Browser Settings, this is a finding.","fixText":"Configure the Samsung Android 14 device to disable the autofill functionality.\n\nThe required configuration is the default configuration when the device is enrolled. If the device configuration is changed, use the following procedure to bring the device back into compliance:\n\nOn the management tool:\n1. Open the \"Managed configurations\" section.\n2. Select the Chrome Browser version from the work profile.\n3. Ensure \"PasswordManagerEnabled\" is turned \"OFF\".\n4. Ensure \"AutofillAddressEnabled\" is turned \"OFF\".\n5. Ensure \"AutofillCreditCardEnabled\" is turned \"OFF\".","ccis":["CCI-000366"]},{"vulnId":"V-260462","ruleId":"SV-260462r959010_rule","severity":"medium","ruleTitle":"The Samsung Android device work profile must be configured to disable the autofill services.","description":"The autofill services allow the user to complete text inputs that could contain sensitive information, such as personally identifiable information (PII), without previous knowledge of the information. By allowing the use of autofill services, an adversary who learns a user's Android 14 device password, or who otherwise is able to unlock the device, may be able to further breach other systems by relying on the autofill services to provide information unknown to the adversary. By disabling the autofill services, the risk of an adversary gaining further information about the device's user or compromising other systems is significantly mitigated. \n \nExamples of apps that offer autofill services include Samsung Pass, Google, Dashlane, LastPass, and 1Password.\n\nSFR ID: FMT_SMF_EXT.1.1 #47","checkContent":"Review the Samsung Android 14 work profile configuration settings to confirm that autofill services are disabled. \n\nThis validation procedure is performed on the management tool.\n\nOn the management tool:\n1. Open \"Set user restrictions\".\n2. Verify \"Disable autofill\" is toggled to \"ON\".\n\nIf on the management tool the \"disallow autofill\" is not selected, this is a finding.","fixText":"Configure the Samsung Android 14 device to disable the autofill services.\n\nOn the management tool, in the Work profile User restrictions section, set \"Disable autofill\" to \"Enable\".","ccis":["CCI-000366"]},{"vulnId":"V-260463","ruleId":"SV-260463r959010_rule","severity":"low","ruleTitle":"The Samsung Android device must be configured to disable the use of third-party keyboards.","description":"Many third-party keyboard applications are known to contain malware.\n\nSFR ID: FMT_SMF_EXT.1.1 #47","checkContent":"Review the managed Samsung Android 14 configuration settings to confirm that no third-party keyboards are enabled.\n \nThis procedure is performed on the management tool.\n \nOn the management tool:\n1. Open \"Input methods\".\n2. Tap \"Set input methods\".\n3. Verify only the approved keyboards are selected.\n\nIf third-party keyboards are allowed, this is a finding.","fixText":"Configure the Samsung Android 14 device to disallow the use of third-party keyboards. \n \nOn the management tool:\n1. Open \"Input methods\".\n2. Tap \"Set input methods\".\n3. Select only the approved keyboard.\n\nAdditionally, Administrators can configure application allowlists for Google Play that do not have any third-party keyboards for user installation.","ccis":["CCI-000366"]},{"vulnId":"V-277027","ruleId":"SV-277027r1134551_rule","severity":"medium","ruleTitle":"Samsung Android 14 BYOAD devices must have a Mobile Threat Detection (MTD) app installed.","description":"DOD mobile devices are in constant risk of cyber threats. MTD apps mitigate these risks by providing real-time threat detection, malware prevention, and vulnerability analysis.\n\nSFR ID: FMT_MOF_EXT.1.2 #47","checkContent":"Confirm that an MTD app is installed on managed Samsung Android devices.\n\nThis check procedure is performed on both the device management tool and the Samsung Android BYOAD device.\n\nIn the MDM console, verify that an MTD app is listed as a managed app being deployed to site managed devices.\n\nOn the Samsung Android device:\n\n1. Open the Settings app.\n2. Tap \"Apps\" and then \"See all apps\".\n3. Verify that an MTD app is listed.\n\nIf an MTD app is not installed on the device, this is a finding.","fixText":"Install an MTD app on managed Samsung Android BYOAD devices.","ccis":["CCI-000366"]},{"vulnId":"V-282946","ruleId":"SV-282946r1183408_rule","severity":"medium","ruleTitle":"All Samsung Android 14 BYOAD installations must be removed.","description":"Samsung Android 14 BYOAD is no longer supported by Samsung and may contain security vulnerabilities.\n\nSatisfies: FMT_MOF_EXT.1.2 #47\nReference: PP-MDF-993300","checkContent":"Verify there are no installations of Samsung Android 14 BYOAD at the site.\n\nIf Samsung Android 14 BYOAD is being used at the site, this is a finding.","fixText":"Remove all installations of Samsung Android 14 BYOAD.","ccis":[]}]}