Samsung Android OS 9 with Knox 3.x COPE Use Case KPE(AE) Deployment STIG

Samsung Android OS 9 with Knox 3.x COPE Use Case KPE(AE) Deployment Security Technical Implementation Guide

The Samsung Android OS 9 with Knox 3.x COPE Use Case KPE(AE) Deployment Security Technical Implementation Guide (V1 R4) has 50 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.

Find STIG checks

50STIG checks

Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.

Severity

Version

V1 · R4

CurrentPublished Wed Jul 27 2022 What changed in V1R4

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.

Samsung Android OS 9 with Knox 3.x COPE Use Case KPE(AE) Deployment Security Technical Implementation Guide

Assessment Title

Rule Text

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.

Description

Discussion Text

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.

Application 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.

Core application: Any application integrated into the operating system by the operating system or mobile device vendors.

Preinstalled application: Additional noncore applications included in the operating system build by the operating system vendor, mobile device vendor, or wireless carrier.

SFR ID: FMT_SMF_EXT.1.1 #8b

New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.

Objective

V-217747

Rule

SV-217747r617473_rule

Severity

medium

Rule Version

KNOX-09-000120

Documentable

false

IA Controls

NIST SP 800-53

Rev 5

Assessment Procedure

Check Text

Review Samsung Android Workspace configuration settings to confirm that the system application disable list has been configured to include all system apps that have been identified as having non-DoD-approved characteristics. 

This procedure is performed on both the MDM Administration console and the Samsung Android device. 

Confirm if Method #1 or Method #2 is used at the Samsung device site and follow the appropriate procedure. 

**** 

Method #1: On the MDM console, for the Workspace, in the "managed Google Play" group, verify that the system application disable list contains all apps identified as having non-DoD-approved characteristics. 

On the Samsung Android device, review the apps on the "Workspace" App screen and confirm that none of the apps listed in the system application disable list are present. 

If the system application disable list does not contain all the apps that have been identified as having non-DoD-approved characteristics, or if an app listed can be found on the "Workspace" App screen of the Samsung Android device, this is a finding. 

**** 

Method #2: On the MDM console, for the device, in the "Knox application" group, verify that the system application disable list contains all apps identified as having non-DoD-approved characteristics. 

On the Samsung Android device, review the apps on the "Workspace" App screen and confirm that none of the apps listed in the system application disable list are present. 

If the system application disable list does not contain all the apps that have been identified as having non-DoD-approved characteristics, or if an app listed can be found on the "Workspace" App screen of the Samsung Android device, this is a finding.

Implementation Procedure

Fix Text

Configure the Samsung Android Workspace to include all system apps in the system app disable list that have been identified as having non-DoD-approved characteristics. 

Do one of the following: 
- Method #1 (preferred): Use managed Google Play for the Workspace (managed profile). 
- Method #2: Use the Knox system application disable list. 

**** 

Method #1: On the MDM console, for the Workspace, in the "managed Google Play" group, add all system app packages that have been identified as having non-DoD-approved characteristics to the system application disable list. 

**** 

Method #2: On the MDM console, for the Workspace, in the "Knox application" group, add all system app packages that have been identified as having non-DoD-approved characteristics to the system application disable list. 

**** 

Note: Refer to the "System Apps for Disablement (Non-DoD-Approved Characteristics)" and "System Apps That Must Not Be Disabled" tables in the Supplemental document for this STIG.

STIG check 6 of 50 in the Samsung Android OS 9 with Knox 3.x COPE Use Case KPE(AE) Deployment STIG checklist

← Previous · V-217746The Samsung Android whitelist must be configured to not include applications with the following characteristic: - transmit MD diagnostic data to non-DoD servers.Next · V-217748 →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.