Checklist Summary:

The Apple iOS/iPadOS 17 Security Technical Implementation Guide (STIG) provides the technical security policies, requirements, and implementation details for applying security concepts to Apple devices running iOS/iPadOS 17 that process, store, or transmit unclassified data marked as “Controlled Unclassified Information (CUI)” or below. The STIG is based on the Protection Profile for Mobile Device Fundamentals (MDFPP) version 3.3 STIG Template. Requirements compliance is achieved by leveraging a combination of configuration profiles, user-based enforcement (UBE), and reporting. The scope of this STIG covers only the Corporate Owned Personally Enabled (COPE) and Corporate Owned Business Only (COBO)1 use cases. The items addressed in the STIG are not specific to an iOS/iPadOS hardware type/model; rather, they are tied to the version of the operating system running on the iPhone or iPad (e.g., iOS 17 or iPadOS 17). This STIG assumes that for the COPE use case, the technology used for data separation between work apps, data and personal apps, and data that has been certified by the National Information Assurance Partnership (NIAP) is compliant with the data separation requirements of the MDFPP2. As of the publication date of this STIG, the only data separation technology or application that is NIAP-certified for an Apple iOS/iPadOS device is the native iOS/iPadOS managed/unmanaged application technology. The configuration requirements and controls implemented by this STIG allow the user unrestricted activity in downloading and installing personal (unmanaged) apps and data (music, photos, etc.) with authorizing official (AO) approval and within any restrictions imposed by the AO. Note: If the AO has approved the use/storage of DOD data in one or more personal (unmanaged) apps, allowing unrestricted user activity in downloading and installing personal (unmanaged) apps on the iOS/iPadOS 17 device may not be warranted due to the risk of possible loss of or unauthorized access to DOD data. This STIG assumes that if a DOD Wi-Fi network allows an iOS/iPadOS mobile device to connect to a DOD network, the Wi-Fi network complies with the Network Infrastructure STIG; for example, wireless access points and bridges must not be connected directly to the enclave network. Supervision of iOS devices, which Apple introduced with iOS 5 and provide the administrator more control of an iOS/iPadOS device than is available for an unsupervised device, is required for all DOD iPhone and iPad deployments. Supervised mode is intended for institutionally owned devices. Supervised mode provides the DOD more control over managed iOS/iPadOS devices by providing access to additional device management controls, including disabling a user from modifying installed accounts, removing the management profile (MDM profile), accessing the Apple App Store, and installing new versions of iOS and iPadOS. 1 Work data/apps only – no personal data/apps. 2 The primary Protection Profile requirement is FDP_ACF_EXT.1.2. A device can be supervised using one of two methods: First, it can be enrolled in Apple’s Automated Device Enrollment/Apple Business Management (ABM) and supervised during the activation of the device. Second, an iOS/iPadOS device can be placed in supervised mode by using the Apple Configurator (AC2) tool. Automated Device Enrollment registration of an iPhone and iPad can occur if the device is purchased directly from Apple (Apple Government Team or Apple’s Retail Business Team), an Apple authorized reseller, or manually via AC2. The DOD procurement office must provide the third-party reseller with the agency’s ABM customer number, which can be obtained by applying at http://deploy.apple.com as a business.

Checklist Role:

• Operating System

Known Issues:

Not provided.

Target Audience:

Not provided.

Target Operational Environment:

• Managed
• Specialized Security-Limited Functionality (SSLF)

Testing Information:

Not provided.

Regulatory Compliance:

This document is provided under the authority of DODI 8500.01.

Comments/Warnings/Miscellaneous:

Not provided.

Disclaimer:

DISA accepts no liability for the consequences of applying specific configuration settings made on the basis of the SRGs/STIGs. It must be noted that the configuration settings specified should be evaluated in a local, representative test environment before implementation in a production environment, especially within large user populations. The extensive variety of environments makes it impossible to test these configuration settings for all potential software configurations. For some production environments, failure to test before implementation may lead to a loss of required functionality. Evaluating the risks and benefits to a system’s particular circumstances and requirements is the system owner’s responsibility. The evaluated risks resulting from not applying specified configuration settings must be approved by the responsible AO. Furthermore, DISA implies no warranty that the application of all specified configurations will make a system 100 percent secure. Security guidance is provided for the DOD. While other agencies and organizations are free to use it, care must be given to ensure that all applicable security guidance is applied at both the device hardening level and the architectural level due to the fact that some settings may not be configurable in environments outside the DOD architecture.

Product Support:

Not provided.

Point of Contact:

Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Sponsor:

Not provided.

Licensing:

Not provided.

Change History:

NEW checklist - 10/19/23
updated to FINAL - 11/20/23
Updated resource per DISA - 2/5/24

Dependency/Requirements:

URL	Description

References:

Reference URL	Description

NIST checklist record last modified on 02/05/2024