Checklist Summary:

The Samsung Android OS 9 with Knox 3.x Security Technical Implementation Guide (STIG) provides the technical security policies, requirements, and implementation details for applying security concepts to Samsung Android 9 with Knox devices. The scope of this STIG covers only the Corporate Owned Personally Enabled (COPE) and Corporate Owned Business Only (COBO)1 use cases. The Bring Your Own Device (BYOD) and Choose Your Own Device (CYOD)2 use cases are not in scope for this STIG. In addition, the STIG supports two different Knox Platform for Enterprise (KPE) device deployment modes: Android for Enterprise (KPE(AE)) and Legacy (KPE(Legacy)). (See the Supplemental document for a detailed review of KPE). Note: It is expected that a future Samsung Android STIG will require all DoD deployments use KPE(AE) only. It is recommended that DoD mobile service providers support KPE(AE) deployments to the maximum extent possible now. This STIG is published as four separate STIG packages, with one for each use case: COPE KPE(AE) use case, COPE KPE(Legacy) use case, COBO KPE(AE) use case, and COBO KPE(Legacy) use case. Each STIG package includes a use-case-specific STIG benchmark (XML file) and a Configuration Tables document. This STIG assumes that for the COPE use case, the technology used for data separation between work apps and data and personal apps and data has been certified by the National Information Assurance Partnership (NIAP) as compliant with the data separation requirements of the Protection Profile for Mobile Device Fundamentals (MDF)3. As of the publication date of this STIG, the only data separation technology or application that is NIAP certified for Samsung mobile devices is Samsung Knox Platform for Enterprise Workspaces. The configuration requirements and controls implemented by this STIG allow unrestricted activity by the user in downloading and installing personal apps and data (music, photos, etc.) with Authorizing Official (AO) approval and within any restrictions imposed by the AO for the COPE use case. See the STIG Supplemental document, Section 6, Configuration of the Personal Space, for more information. This STIG assumes that if a DoD Wi-Fi network allows a Samsung mobile device to connect to the network, the Wi-Fi network complies with the Network Infrastructure STIG; for example, wireless access points and bridges must not be directly connected to the enclave network.

Checklist Role:

• Operating System

Known Issues:

Not provided.

Target Audience:

This document is a requirement for all DoD administered systems and all systems connected to DoD networks. These requirements are designed to assist Security Managers (SMs), Information Assurance Managers (IAMs), Information Assurance Officers (IAOs), and System Administrators (SAs) with configuring and maintaining security controls.

Target Operational Environment:

• Managed
• Specialized Security-Limited Functionality (SSLF)

Testing Information:

Not provided.

Regulatory Compliance:

DoD Directive (DoDD) 8500.1 and 8500.2

Comments/Warnings/Miscellaneous:

Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil. DISA will coordinate all change requests with the relevant DoD organizations before inclusion in this document. Approved changes will be made in accordance with the DISA maintenance release schedule.

Disclaimer:

Not provided.

Product Support:

Not provided.

Point of Contact:

disa.stig_spt@mail.mil

Sponsor:

Not provided.

Licensing:

Not provided.

Change History:

Updated status to FINAL - 7/15/19
updated URLs - 11/1/19
updated URLs per DISA - 5/5/2020
updated per DISA - 8/4/2020
Sunset per DISA - 8/1/22
null

Dependency/Requirements:

URL	Description

References:

Reference URL	Description

NIST checklist record last modified on 08/01/2022