### Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - ### Spring Security Target 416 Maetan-3dong, Yeongtong-gu, Suwon-si, Gyeonggi-do, 443-742 Korea Prepared By: [www.gossamersec.com](http://www.gossamersec.com/) Version: 0.3 10/22/2026 Samsung Electronics Co., Ltd. Version: 0.3 Samsung Galaxy Devices on Android 16 - Spring Security Target Date: 10/22/2026 #### Table of Contents 1 Security Target Introduction ............................................................................................................ 4 2 1.1 Security Target Reference ................................................................................................................. 5 1.2 TOE Reference ................................................................................................................................... 6 1.3 TOE Overview .................................................................................................................................... 6 1.4 TOE Description ................................................................................................................................. 6 1.4.1 TOE Architecture ........................................................................................................................... 8 1.4.2 TOE Documentation .................................................................................................................... 11 Conformance Claims ..................................................................................................................... 12 3 2.1 Conformance Rationale................................................................................................................... 13 Security Objectives ....................................................................................................................... 14 4 3.1 Security Objectives for the Operational Environment .................................................................... 14 Extended Components Definition .................................................................................................. 15 5 Security Requirements .................................................................................................................. 17 6 5.1 TOE Security Functional Requirements ........................................................................................... 17 5.1.1 Security Audit (FAU) .................................................................................................................... 20 5.1.2 Cryptographic Support (FCS)....................................................................................................... 21 5.1.3 User Data Protection (FDP) ......................................................................................................... 31 5.1.4 Identification and Authentication (FIA) ...................................................................................... 33 5.1.5 Security Management (FMT) ...................................................................................................... 39 5.1.6 Protection of the TSF (FPT) ......................................................................................................... 46 5.1.7 TOE Access (FTA) ......................................................................................................................... 50 5.1.8 Trusted Path/Channels (FTP) ...................................................................................................... 50 5.2 TOE Security Assurance Requirements ........................................................................................... 52 5.2.1 Development (ADV) .................................................................................................................... 52 5.2.2 Guidance Documents (AGD) ....................................................................................................... 52 5.2.3 Life-cycle Support (ALC) .............................................................................................................. 53 5.2.4 Tests (ATE) .................................................................................................................................. 54 5.2.5 Vulnerability Assessment (AVA) ................................................................................................. 55 TOE Summary Specification ........................................................................................................... 56 6.1 Security Audit .................................................................................................................................. 56 6.2 Cryptographic Support .................................................................................................................... 58 6.3 User Data Protection ....................................................................................................................... 69 6.4 Identification and Authentication ................................................................................................... 73 6.5 Security Management ..................................................................................................................... 79 6.6 Protection of the TSF ....................................................................................................................... 80 6.7 TOE Access ...................................................................................................................................... 85 6.8 Trusted Path/Channels .................................................................................................................... 85 6.9 Work Profile Functionality .............................................................................................................. 86 #### List of Tables Table 1 - Glossary................................................................................................................................................ 5 2 of 87 Samsung Electronics Co., Ltd. Version: 0.3 Samsung Galaxy Devices on Android 16 - Spring Security Target Date: 10/22/2026 Table 2 - Evaluated Devices ................................................................................................................................ 7 Table 3 - Equivalent Devices .............................................................................................................................. 7 Table 4 - Carrier Models ..................................................................................................................................... 8 Table 5 - Technical Decisions ............................................................................................................................ 13 Table 6 - Extended SFRs and SARs .................................................................................................................... 16 Table 7 - TOE Security Functional Requirements ............................................................................................. 20 Table 8 - Security Management Functions ....................................................................................................... 44 Table 9 - Bluetooth Security Management Functions ...................................................................................... 45 Table 10 - WLAN Security Management Functions .......................................................................................... 46 Table 11 - VPN Security Management Functions ............................................................................................. 46 Table 12 - Audit Events ..................................................................................................................................... 57 Table 13 - Bluetooth Audit Events ................................................................................................................... 57 Table 14 - WLAN Client Audit Events ............................................................................................................... 57 Table 15 - Asymmetric Key Generation per Module ........................................................................................ 58 Table 17 - Salt Creation .................................................................................................................................... 60 Table 18 - BoringSSL Cryptographic Algorithms ............................................................................................... 61 Table 19 - Samsung Crypto Extension Cryptographic Algorithms .................................................................... 61 Table 20 - Kernel Versions ................................................................................................................................ 61 Table 21 - Samsung Kernel Cryptographic Algorithms ..................................................................................... 61 Table 22 - TEE Environments ............................................................................................................................ 62 Table 23 - SCrypto TEE Cryptographic Algorithms............................................................................................ 62 Table 24 - Hardware Components .................................................................................................................... 63 Table 25 - Storage Hardware Algorithms ......................................................................................................... 63 Table 26 - Wi-Fi Hardware Components .......................................................................................................... 63 Table 27 - Wi-Fi Chip Algorithms ...................................................................................................................... 63 Table 28 - Mutable Key Storage Components .................................................................................................. 63 Table 29 - Mutable Key Storage Cryptographic Algorithms ............................................................................. 64 Table 30 - SoC Cryptographic Algorithms ......................................................................................................... 64 Table 31 - Key Management Matrix ................................................................................................................. 68 Table 32 - Access Control Categories ............................................................................................................... 71 Table 33 - Device biometric sensor .................................................................................................................. 75 Table 34 - Allowed Lock Screen Authentication Methods ............................................................................... 77 Table 35 - Secure Boot Public Keys ................................................................................................................... 80 Table 36 - Power-up Cryptographic Algorithm Self-Tests ................................................................................ 83 3 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 ## 1 Security Target Introduction This section identifies the Security Target (ST) and Target of Evaluation (TOE) identification, ST conventions, ST conformance claims, and the ST organization. The TOE consists of the Samsung Galaxy Devices on Android 16 - Spring provided by Samsung Electronics Co., Ltd. The TOE is being evaluated as a Mobile Device. The Security Target contains the following additional sections: - Conformance Claims (Section 2) - Security Objectives (Section 3) - Extended Components Definition (Section 4) - Security Requirements (Section 5) - TOE Summary Specification (Section 6) ####### Acronyms and Terminology AA Assurance Activity BAF Biometric Authentication Factor CC Common Criteria CCEVS Common Criteria Evaluation and Validation Scheme EAR Entropy Analysis Report FBE File-based Encryption GUI Graphical User Interface MDM Mobile Device Management NFC Near Field Communication PAD Presentation Attack Detection PAI Presentation Attack Instrument PCL Product Compliant List PP Protection Profile REK Root Encryption Key SAR Security Assurance Requirement SFR Security Functional Requirement SOC System on Chip SOF Strength of Function ST Security Target TEE Trusted Execution Environment (TrustZone) TOE Target of Evaluation TSF TOE Security Functionality U.S. United States VR Validation Report 4 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ####### Glossary Table 1 - Glossary | Device Lock Screen Android Lock Screen | The Device Lock Screen is the Android OS lock screen. | |------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | File-Based Encryption (FBE) | FBE allowed files to be encrypted with different keys and unlocked individually based on different authentication/access controls. This is implemented as part of the ext4 or f2fs file system (using fscrypt). | | Firmware Over-the-air (FOTA) | Firmware Over-the-air is a term for the process of updating the firmware (operating system and services) on the device via a wireless connection as opposed to a wired (i.e. USB) connection. | | Personal Profile | The personal profile is the common Android user on the device, such as when the device is first setup. While the name implies this space is for the end user and not the Enterprise, this can be configured as needed by the MDM. This is in contrast to a work profile. | | Work Profile | The work profile is a second profile on a device created specifically by the MDM and used to segment enterprise data from what may be personal data. The work profile maintains separate authentication to access any apps or data stored within. | ####### Conventions The following conventions have been applied in this document: - Security Functional Requirements - Part 2 of the CC defines the approved set of operations that may be applied to functional requirements: iteration, assignment, selection, and refinement. - o Iteration: allows a component to be used more than once with varying operations. In the ST, iteration is indicated by a parenthetical number placed at the end of the component. For example FDP_ACC.1(1) and FDP_ACC.1(2) indicate that the ST includes two iterations of the FDP_ACC.1 requirement. Alternately, a usually descriptive textual extension may be added after a slash (/) character to identify a specific iteration. For example, iterations of a requirement such as FCS_COP.1 might be identified as FCS_COP.1/HASH and FCS_COP.1/CRYPT. - o Assignment: allows the specification of an identified parameter. Assignments are indicated using bold and are surrounded by brackets (e.g., [ assignment ]). Note that an assignment within a selection would be identified in italics and with embedded bold brackets (e.g., [ [selectedassignment] ]). - o Selection: allows the specification of one or more elements from a list. Selections are indicated using bold italics and are surrounded by brackets (e.g., [ selection ]). - o Refinement: allows the addition of details. Refinements are indicated using bold, for additions, and strikethrough, for deletions (e.g., '… all objects …' or '… some big things …'). - Other sections of the ST - Other sections of the ST use bolding to highlight text of special interest, such as captions. ### 1.1 Security Target Reference ST Title - Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ST Version - Version 0.3 ST Date - 10/22/2026 Proprietary Documentation (sections with additional information are marked with KMD in the section title) Version: 0.3 Date: 10/22/2026 5 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 KMD Title - Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Key Management Description KMD Version - Version 0.3 KMD Date - 10/22/2026 ### 1.2 TOE Reference TOE Identification - Samsung Galaxy Devices on Android 16 - Spring TOE Developer - Samsung Electronics Co., Ltd. Evaluation Sponsor - Samsung Electronics Co., Ltd. ### 1.3 TOE Overview The Target of Evaluation (TOE) are the Samsung Galaxy Devices on Android 16 - Spring. ### 1.4 TOE Description The TOE is a mobile device based on Android 16 with a built-in IPsec VPN client and modifications made to increase the level of security provided to end users and enterprises. The TOE is intended for use as part of an enterprise mobility solution providing mobile staff with enterprise connectivity. The TOE includes a Common Criteria mode (or 'CC mode') that an administrator can invoke using an MDM. The TOE must meet the following prerequisites in order for an administrator to transition the TOE to and remain in the CC configuration. - Require a boot and device lock password (swipe, PIN, pattern, accessibility (direction), screen locks are not allowed). Acceptable biometrics are fingerprint for each device. - The maximum password failure retry policy should be less than or equal to 30. - A screen lock password required to decrypt data on boot. - Security and audit logging must be enabled. - External storage must be encrypted. - When CC mode has been enabled, the TOE behaves as follows: - o The TOE sets the system wide Android CC mode property to be enabled. - o The TOE prevents loading of custom firmware/kernels and requires all updates occur through FOTA. - o The TOE utilizes ACVP/CAVP approved cryptographic ciphers for TLS. The TOE includes the ability to create separate profiles part of the Knox Platform. A profile provides a way to segment applications and data into two separate areas on the device, such as a personal area and a work area, each with its own separate apps, data and security policies. For this effort, the TOE was evaluated both without and with profiles created. Thus, the evaluation includes several Knox-specific claims that apply when these profiles are created. The TOE also requires loaded applications must be implemented utilizing the NIAPSEC library. There are different models of the TOE, the Samsung Galaxy Devices on Android 16, and these models differ in their internal components (as described in the table below). All devices are A64 architecture. The following table shows the model numbers of the mobile devices Included in the evaluation of the Samsung Galaxy Devices on Android 16: 6 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 Table 2 - Evaluated Devices | Device Name | Chipset Vendor | SoC | Arch | Kernel | Build Number | |------------------------|------------------|-----------------------------------|--------|----------|--------------------| | Galaxy S26 Ultra 5G | Qualcomm | Snapdragon 8 Elite Gen 5 (SM8850) | ARMv8 | 6.12 | BP4A.251205.006 | | Galaxy S26+ 5G | Qualcomm | Snapdragon 8 Elite Gen 5 (SM8850) | ARMv8 | 6.12 | BP4A.251205.006 | | Galaxy S26+ 5G | Samsung | Exynos 2600 (S5E9965) | ARMv8 | 6.12 | BP4A.251205.006 | | Galaxy S26 5G | Qualcomm | Snapdragon 8 Elite Gen 5 (SM8850) | ARMv8 | 6.12 | BP4A.251205.006 | | Galaxy S26 5G | Samsung | Exynos 2600 (S5E9965) | ARMv8 | 6.12 | BP4A.251205.006 | | Galaxy XCover 7 Pro | Qualcomm | Snapdragon 7s Gen 3 (SM7635) | ARMv8 | 6.1 | BP2A.250605.031.A3 | | Galaxy XCover6 Pro | Qualcomm | Snapdragon 778G (SM7325) | ARMv8 | 5.4 | BP2A.250605.031.A3 | | Galaxy Tab Active5 Pro | Qualcomm | Snapdragon 7s Gen 3 (SM7635) | ARMv8 | 6.1 | BP2A.250605.031.A3 | | Galaxy Tab Active5 | Samsung | Exynos 1380 (S5E8835) | ARMv8 | 5.15 | BP2A.250605.031.A3 | | Galaxy A37 5G | Samsung | Exynos 1480 (S5E8845) | ARMv8 | 6.1 | BP2A.250605.031.A3 | | Galaxy A57 5G | Samsung | Exynos 1680 (S5E8865) | ARMv8 | 6.12 | BP2A.250605.031.A3 | | Galaxy A53 5G | Samsung | Exynos 1280 (S5E8825) | ARMv8 | 5.10 | BP2A.250605.031.A3 | The following table lists the tested device models and maps those to the equivalent devices with a note about the differences between the evaluated device and the equivalent models. Equivalence in this table is determined by the use of identical processors, kernel and build number, and is not made across processor types. If a device may be released with different processors around the world, a version of the device with each processor will be tested, and equivalence will be claimed specifically to similar devices utilizing the same processor. Table 3 - Equivalent Devices | Evaluated Device | SoC | Equivalent Devices | Differences | |---------------------|-----------------------------------|------------------------------|---------------------------------------------------------------| | Galaxy S26 Ultra 5G | Snapdragon 8 Elite Gen 5 (SM8850) | Galaxy S26+ 5G Galaxy S26 5G | S26 Ultra > S26+ > S26 in terms of display size | | Galaxy S26+ 5G | Exynos 2600 (S5E9965) | Galaxy S26 5G | S26+ > S26 in terms of display size | | Galaxy XCover 7 Pro | Snapdragon 7s Gen 3 (SM7635) | Galaxy Tab Active5 Pro | The Galaxy Tab Active5 Pro is a tablet with a larger display. | | Galaxy XCover 6 Pro | Snapdragon 778G (SM7325) | N/A | N/A | | Galaxy Tab Active5 | Exynos 1380 (S5E8835) | N/A | N/A | | Galaxy A37 5G | Exynos 1480 (S5E8845) | N/A | N/A | | Galaxy A57 5G | Exynos 1680 (S5E8865) | N/A | N/A | | Galaxy A53 5G | Exynos 1280 (S5E8825) | N/A | N/A | 7 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target #### 1.4.1 TOE Architecture The TOE combines with a Mobile Device Management solution (note that this evaluation does not include an MDM agent nor server) that enables the Enterprise to watch, control and administer all deployed mobile devices, across multiple mobile service providers as well as facilitate secure communications through a VPN. This partnership provides a secure mobile environment that can be managed and controlled by the environment and reduces the risks inherent in any mobile deployment. Data on the TOE is protected through the implementation of Samsung File-Based Encryption (FBE) that utilizes ACVP/CAVP certified cryptographic algorithms to encrypt device storage. This functionality is combined with a number of on-device policies including local wipe, remote wipe, password complexity, automatic lock and privileged access to security configurations to prevent unauthorized access to the device and stored data. Version: 0.3 Date: 10/22/2026 | Device Name | Chipset Vendor | Chipset Name | Base Model Number | Carrier Models | |------------------------|------------------|-----------------------------------|---------------------|----------------------------------------| | Galaxy S26 Ultra 5G | Qualcomm | Snapdragon 8 Elite Gen 5 (SM8850) | SM-S948 | W, B, Q, C, Z, N, U1, U, SC-53G, SCG37 | | Galaxy S26+ 5G | Qualcomm | Snapdragon 8 Elite Gen 5 (SM8850) | SM-S947 | W, Q, C, Z, U1, U, SC-52G, SCG38 | | Galaxy S26+ 5G | Samsung | Exynos 2600 (S5E9965) | SM-S947 | B, N | | Galaxy S26 5G | Qualcomm | Snapdragon 8 Elite Gen 5 (SM8850) | SM-S942 | W, Q, C, Z, U1, U, SC-51G, SCG36 | | Galaxy S26 5G | Samsung | Exynos 2600 (S5E9965) | SM-S942 | B, N | | Galaxy XCover7 Pro | Qualcomm | Snapdragon 7s Gen 3 (SM7635) | SM-G766 | W, B, U1, U | | Galaxy XCover6 Pro | Qualcomm | Snapdragon 778G (SM7325) | SM-G736 | W, B, U1, U | | Galaxy Tab Active5 Pro | Qualcomm | Snapdragon 7s Gen 3 (SM7635) | SM-X350 | None | | Galaxy Tab Active5 Pro | Qualcomm | Snapdragon 7s Gen 3 (SM7635) | SM-X356 | B, N | | Galaxy Tab Active5 Pro | Qualcomm | Snapdragon 7s Gen 3 (SM7635) | SM-X358 | U | | Galaxy Tab Active5 | Samsung | Exynos 1380 (S5E8835) | SM-X300 | None | | Galaxy Tab Active5 | Samsung | Exynos 1380 (S5E8835) | SM-X306 | B, N | | Galaxy Tab Active5 | Samsung | Exynos 1380 (S5E8835) | SM-X308 | U, B | | Galaxy A37 5G | Samsung | Exynos 1480 (S5E8845) | SM-A376 | W, E, B, N, U1, U | | Galaxy A37 5G | Samsung | Exynos 1480 (S5E8845) | SM-S376 | V | | Galaxy A57 5G | Samsung | Exynos 1680 (S5E8865) | SM-A576 | W, B, J, Q, C, Z, N, U1, SC-54G, SCG37 | | Galaxy A53 5G | Samsung | Exynos 1280 (S5E8825) | SM-A536 | W, E, B, N, U1, V, U, SC-53C*, SCG15* | | Galaxy A53 5G | Samsung | Exynos 1280 (S5E8825) | SM-S536 | DL | For each device, there are specific models that are validated. This table lists the specific carrier models that have the validated configuration (covering both evaluated and equivalent devices). Table 4 - Carrier Models 8 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 The Knox Platform for Enterprise provides a set of flexible deployment options for work environments. With Knox Platform for Enterprise, it is possible to segment the device into two separate areas, by convention called the personal profile and the work profile. In creating a work profile, the Enterprise establishes a completely separate workspace, with its own authentication, applications and services, and ensure they are kept separate from anything the user may do in the personal profile. Another option for deployment is Knox Separated Apps, a folder where the Enterprise can isolate a group of applications from the rest of the device, restricting access to shared information, while maintaining seamless access to the isolated applications for the user. The Samsung Knox Software Development Kit (SDK) builds on top of the existing Android security model by expanding the current set of security configuration options to more than 600 configurable policies and including additional security functionality such as application allow and block listing. ##### 1.4.1.1 Physical Boundaries The TOE is a multi-user capable mobile device based on Android 16 that incorporates the Samsung Knox SDK. The TOE does not include the user applications that run on top of the operating system, but does include controls that limit application behavior. The TOE includes an IPsec VPN client integrated into the firmware (as opposed to a downloadable application). Within an Enterprise environment, the Enterprise can manage the configuration of the mobile device, including the VPN client, through a compliant device management solution. The TOE communicates and interacts with 802.11-2012 Access Points and mobile data networks to establish network connectivity, and the through that connectivity interacts with MDM servers that allow administrative control of the TOE. ##### 1.4.1.2 Logical Boundaries This section summarizes the security functions provided by the Samsung Galaxy Devices on Android 16: ###### Security Audit ###### Cryptographic support ###### User data protection ###### Identification and authentication ###### Security management ###### Protection of the TSF ###### TOE access ###### Trusted path/channels ### 1.4.1.2.1 Security Audit The TOE generates logs for a range of security relevant events. The TOE stores the logs locally so they can be accessed by an administrator or they can be exported to an MDM. ### 1.4.1.2.2 Cryptographic Support The TOE includes multiple cryptographic libraries with ACVP certified algorithms for a wide range of cryptographic functions including the following: asymmetric key generation and establishment, symmetric key generation, encryption/decryption, cryptographic hashing and keyed-hash message authentication. These functions are supported with suitable random bit generation, key derivation, salt generation, initialization vector generation, secure key storage, and key and protected data destruction. These primitive cryptographic functions are used to implement security protocols such as TLS, EAP-TLS, IPsec, and HTTPS and to encrypt the media (including the generation and protection of data and key encryption keys) used by the TOE. Many of these cryptographic functions are also accessible as services to applications running on the TOE. 9 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 ### 1.4.1.2.3 User Data Protection The TOE controls access to system services by hosted applications, including protection of the Trust Anchor Database. Additionally, the TOE protects user and other sensitive data using encryption so that even if a device is physically lost, the data remains protected. The functionality provided by work profiles and Knox Separated Apps enhance the security of user data by providing an additional layer of separation between different categories of apps and data while the device is in use. The TOE ensures that residual information is protected from potential reuse in accessible objects such as network packets. ### 1.4.1.2.4 Identification and Authentication The TOE supports a number of features related to identification and authentication. From a user perspective, except for making phone calls to an emergency number, a password or Biometric Authentication Factor (BAF) must be correctly entered to unlock the TOE. In addition, even when the TOE is unlocked the password must be re-entered to change the password or re-enroll the biometric template. Passwords are obscured when entered so they cannot be read from the TOE's display, the frequency of entering passwords is limited and when a configured number of failures occurs, the TOE will be wiped to protect its contents. Passwords can be constructed using upper and lower case characters, numbers, and special characters and passwords between 4 and 16 characters are supported. The TOE can also be configured to utilize a biometric authentication factor (fingerprints), to unlock the device (Note: This only works after the primary authentication method, password, has been entered after the device powers on). The TOE can also serve as an 802.1X supplicant and can use X.509v3 and validate certificates for EAP-TLS, TLS and IPsec exchanges. The TOE can also act as a client or server in an authenticated Bluetooth pairing. ### 1.4.1.2.5 Security Management The TOE provides all the interfaces necessary to manage the security functions (including the VPN client) identified throughout this Security Target as well as other functions commonly found in mobile devices. Many of the available functions are available to users of the TOE while many are restricted to administrators operating through a Mobile Device Management solution once the TOE has been enrolled. Once the TOE has been enrolled and then un-enrolled, it removes all MDM policies and disables CC mode. ### 1.4.1.2.6 Protection of the TSF The TOE implements a number of features to protect itself to ensure the reliability and integrity of its security features. It protects particularly sensitive data such as cryptographic keys so that they are not accessible or exportable. It also provides its own timing mechanism to ensure that reliable time information is available (e.g., for log accountability). It enforces read, write, and execute memory page protections, uses address space layout randomization, and stack-based buffer overflow protections to minimize the potential to exploit application flaws. It also protects itself from modification by applications as well as isolates the address spaces of applications from one another to protect those applications. The TOE includes functions to perform self-tests and software/firmware integrity checking so that it might detect when it is failing or may be corrupt. If any self-tests fail, the TOE will not go into an operational mode. It also includes mechanisms (i.e., verification of the digital signature of each new image) so that the TOE itself can be updated while ensuring that the updates will not introduce malicious or other unexpected changes in the TOE. Digital signature checking also extends to verifying applications prior to their installation. 10 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 ### 1.4.1.2.7 TOE Access The TOE can be locked, obscuring its display, by the user or after a configured interval of inactivity. The TOE also has the capability to display an advisory message (banner) when users unlock the TOE for use. The TOE is also able to attempt to connect to wireless networks as configured. ### 1.4.1.2.8 Trusted Path/Channels The TOE supports the use of 802.11-2012, 802.1X, EAP-TLS, TLS, HTTPS and IPsec to secure communications channels between itself and other trusted network devices. #### 1.4.2 TOE Documentation - Samsung Android 16 on Galaxy Devices Administrator Guide, version 9.0.5, July 31, 2026 11 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ## 2 Conformance Claims This TOE is conformant to the following CC specifications: - Common Criteria for Information Technology Security Evaluation Part 2: Security functional components, Version 3.1, Revision 5, April 2017. - o Part 2 Extended - Common Criteria for Information Technology Security Evaluation Part 3: Security assurance components, Version 3.1 Revision 5, April 2017. - o Part 3 Extended - PP-Configuration for Mobile Device Fundamentals, Biometric enrollment and verification - for unlocking the device, Bluetooth, Virtual Private Network (VPN) Clients, and WLAN Clients, Version 1.1, 6 June 2025 (CFG_MDF-BIO-BT-VPNC-WLANC_V1.1) - o The PP-Configuration includes the following components: - Base-PP: Protection Profile for Mobile Device Fundamentals, Version 3.3, (PP_MDF_V3.3) - PP-Module: PP-Module for Virtual Private Network (VPN) Clients, Version 2.5, (MOD_VPNC_V2.5) - PP-Module: PP-Module for Bluetooth, Version 1.0, (MOD_BT_V1.0) - PP-Module for WLAN Client, Version 1.0 (MOD_WLANC_V1.0) - PP-Module: collaborative PP-Module for Biometric enrolment and verification - for unlocking the device - [BIOPP-Module], Version 1.1, September 12, 2022 (MOD_CPP_BIO_V1.1) - Package Claims: - o Functional Package: Functional Package for Transport Layer Security (TLS), Version 1.1, (PKG_TLS_V1.1) - Technical Decisions as of August 26, 2026: | TD No. | PP | Applied | Rationale | |----------|----------------|-----------|----------------------| | 0442 | PKG_TLS_V1.1 | Yes | | | 0469 | PKG_TLS_V1.1 | No | Not a server | | 0499 | PKG_TLS_V1.1 | Yes | | | 0513 | PKG_TLS_V1.1 | Yes | | | 0600 | MOD_BT_V1.0 | No | Not using PP_MD_V3.2 | | 0640 | MOD_BT_V1.0 | Yes | | | 0645 | MOD_BT_V1.0 | Yes | | | 0650 | MOD_BT_V1.0 | Yes | | | 0667 | MOD_WLANC_V1.0 | Yes | | | 0671 | MOD_BT_V1.0 | Yes | | | 0677 | PP_MDF_V3.3 | Yes | | | 0685 | MOD_BT_V1.0 | Yes | | | 0689 | PP_MDF_V3.3 | Yes | | | 0703 | MOD_WLANC_V1.0 | Yes | | | 0704 | PP_MDF_V3.3 | Yes | | | 0707 | MOD_BT_V1.0 | Yes | | | 0710 | MOD_WLANC_V1.0 | Yes | | Version: 0.3 Date: 10/22/2026 12 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 Table 5 - Technical Decisions | TD No. | PP | Applied | Rationale | |----------|------------------|-----------|------------------------------| | 0714 | MOD_CPP_BIO_V1.1 | Yes | | | 0724 | PP_MDF_V3.3 | Yes | | | 0726 | PKG_TLS_V1.1 | No | Not a server | | 0739 | PKG_TLS_V1.1 | Yes | | | 0770 | PKG_TLS_V1.1 | No | Not a server | | 0779 | PKG_TLS_V1.1 | No | Not a server | | 0797 | MOD_WLANC_V1.0 | Yes | | | 0837 | MOD_WLANC_V1.0 | Yes | | | 0844 | PP_MDF_V3.3 | No | Flaw remediation not claimed | | 0875 | MOD_VPNC_V2.5 | Yes | | | 0890 | MOD_VPNC_V2.5 | No | Not claiming PSK | | 0892 | MOD_CPP_BIO_V1.1 | Yes | | | 0914 | PP_MDF_V3.3 | No | PKG_TLS_V2.0 not claimed | | 0916 | MOD_WLANC_V1.0 | Yes | | | 0920 | MOD_WLANC_V1.0 | Yes | | | 0934 | PP_MDF_V3.3 | Yes | | | 0950 | PP_MDF_V3.3 | Yes | | | 0954 | MOD_VPNC_V2.5 | Yes | | | 0957 | PP_MDF_V3.3 | Yes | | | 1017 | PP_MDF_V3.3 | Yes | | | 1018 | MOD_CPP_BIO_V1.1 | Yes | | ### 2.1 Conformance Rationale The ST conforms to the requirements in PP_MDF_V3.3/MOD_BT_V1.0/MOD_WLANC_V1.0/ PKG_TLS_V1.1/MOD_VPNC_V2.5/ MOD_CPP_BIO_V1.1. For simplicity, this shall be referenced as MDF/BT/BIO//WLAN/TLS/VPNC. As explained previously, the security problem definition, security objectives, and security requirements are defined in the PP. 13 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 ## 3 Security Objectives The Security Problem Definition may be found in the MDF/BT/BIO//WLAN/TLS/VPNC and this section reproduces only the corresponding Security Objectives for operational environment for reader convenience. The MDF/BT/BIO//WLAN/TLS/VPNC offers additional information about the identified security objectives, but that has not been reproduced here and the MDF/BT/BIO//WLAN/TLS/VPNC should be consulted if there is interest in that material. In general, the MDF/BT/BIO//WLAN/TLS/VPNC has defined Security Objectives appropriate for Mobile Devices and as such are applicable to the Samsung Galaxy Devices on Android 16 TOE. ### 3.1 Security Objectives for the Operational Environment - OE.CONFIG (PP_MDF_V3.3) TOE administrators will configure the Mobile Device security functions correctly to create the intended security policy. - OE.NOTIFY (PP_MDF_V3.3) The Mobile User will immediately notify the administrator if the Mobile Device is lost or stolen. - OE.PRECAUTION (PP_MDF_V3.3) The Mobile User exercises precautions to reduce the risk of loss or theft of the Mobile Device. - OE.DATA_PROPER_USER (PP_MDF_V3.3) Administrators take measures to ensure that mobile device users are adequately vetted against malicious intent and are made aware of the expectations for appropriate use of the device. - OE.NO_TOE_BYPASS (MOD_WLANC_V1.0) Information cannot flow between external and internal networks located in different enclaves without passing through the TOE. - OE.TRUSTED_ADMIN (MOD_WLANC_V1.0) TOE Administrators are trusted to follow and apply all administrator guidance in a trusted manner. - OE.PROTECTION (MOD_CPP_BIO_V1.1) The TOE environment shall provide the SEE to protect the TOE, the TOE configuration and biometric data during runtime and storage . - OE.NO_TOE_BYPASS (MOD_VPNC_V2.5) Information cannot flow onto the network to which the VPN client's host is connected without passing through the TOE. - OE.PHYSICAL (MOD_VPNC_V2.5) Physical security, commensurate with the value of the TOE and the data it contains, is assumed to be provided by the environment. - OE.TRUSTED_CONFIG (MOD_VPNC_V2.5) Personnel configuring the TOE and its operational environment will follow the applicable security configuration guidance. 14 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ## 4 Extended Components Definition All of the extended requirements in this ST have been drawn from the MDF/BT/BIO//WLAN/TLS/VPNC/ BIOO. The MDF/BT/BIO//WLAN/TLS/VPNC/ BIO defines the following extended SFRs and SARs and since they are not redefined in this ST the MDF/BT/BIO//WLAN/TLS/VPNC/ BIO should be consulted for more information concerning those CC extensions. | Requirement Class | Requirement Component | |----------------------------------------|-----------------------------------------------------------------------------------------------| | FCS: Cryptographic support | FCS_CKM_EXT.1: Cryptographic Key Support | | | FCS_CKM_EXT.2: Cryptographic Key Random Generation | | | FCS_CKM_EXT.3: Cryptographic Key Generation | | | FCS_CKM_EXT.4: Key Destruction | | | FCS_CKM_EXT.5: TSF Wipe | | | FCS_CKM_EXT.6: Salt Generation | | | FCS_CKM_EXT.8: Bluetooth Key Generation | | | FCS_HTTPS_EXT.1: HTTPS Protocol | | | FCS_IPSEC_EXT.1: IPsec | | | FCS_IV_EXT.1: Initialization Vector Generation | | | FCS_RBG_EXT.1: Random Bit Generation | | | FCS_SRV_EXT.1: Cryptographic Algorithm Services | | | FCS_SRV_EXT.2: Cryptographic Algorithm Services | | | FCS_STG_EXT.1: Cryptographic Key Storage | | | FCS_STG_EXT.2: Encrypted Cryptographic Key Storage | | | FCS_STG_EXT.3: Integrity of Encrypted Key Storage | | | PKG_TLS_V1.1: FCS_TLS_EXT.1: TLS Protocol | | | PKG_TLS_V1.1: FCS_TLSC_EXT.1: TLS Client Protocol | | | FCS_TLSC_EXT.2: TLS Client Support for Mutual Authentication | | | FCS_TLSC_EXT.2/WLAN: TLS Client Support for Supported Groups Extension (EAP-TLS for WLAN) | | | PKG_TLS_V1.1:FCS_TLSC_EXT.4 TLS Client Support for Renegotiation | | | FCS_TLSC_EXT.5: TLS Client Support for Supported Groups Extension | | | FCS_WPA_EXT.1: Supported WPA Versions | | FDP: User data protection | FDP_ACF_EXT.1: Access Control for System Services | | FDP: User data protection | FDP_ACF_EXT.2: Access Control for System Resources | | FDP: User data protection | FDP_ACF_EXT.3: Security Attribute Based Access Control | | FDP: User data protection | FDP_DAR_EXT.1: Protected Data Encryption | | FDP: User data protection | FDP_DAR_EXT.2: Sensitive Data Encryption | | FDP: User data protection | FDP_IFC_EXT.1: Subset Information Flow Control | | FDP: User data protection | FDP_IFC_EXT.1: Subset Information Flow Control | | FDP: User data protection | FDP_STG_EXT.1: User Data Storage | | FDP: User data protection | FDP_UPC_EXT.1: Inter-TSF User Data Transfer Protection FDP_VPN_EXT.1: Split Tunnel Prevention | | FIA: Identification and authentication | FIA_AFL_EXT.1: Authentication Failure Handling | | FIA: Identification and authentication | FIA_BLT_EXT.1: Bluetooth User Authorization | | FIA: Identification and authentication | FIA_BLT_EXT.2: Bluetooth Mutual Authentication | | FIA: Identification and authentication | FIA_BLT_EXT.3: Rejection of Duplicate Bluetooth Connections | | FIA: Identification and authentication | FIA_BLT_EXT.4: Secure Simple Pairing | | FIA: Identification and authentication | FIA_BLT_EXT.6: Trusted Bluetooth Device User Authorization | | FIA: Identification and authentication | FIA_BLT_EXT.7: Untrusted Bluetooth Device User Authorization | Version: 0.3 Date: 10/22/2026 SAMSUNG 15 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 Table 6 - Extended SFRs and SARs | Requirement Class | Requirement Component | |----------------------------|----------------------------------------------------------------------------------------------| | Requirement Class | FIA_PAE_EXT.1: Port Access Entity Authentication | | Requirement Class | FIA_PMG_EXT.1: Password Management | | Requirement Class | FIA_TRT_EXT.1: Authentication Throttling | | Requirement Class | FIA_UAU_EXT.1: Authentication for Cryptographic Operation | | Requirement Class | FIA_UAU_EXT.2: Timing of Authentication | | Requirement Class | FIA_UAU_EXT.4: Secondary User Authentication | | Requirement Class | FIA_X509_EXT.1: Validation of Certificates | | Requirement Class | FIA_X509_EXT.1/WLAN: X.509 Certificate Validation | | Requirement Class | FIA_X509_EXT.2: X.509 Certificate Authentication | | Requirement Class | FIA_X509_EXT.3: Request Validation of Certificates | | Requirement Class | FIA_X509_EXT.6: Certificate Storage and Management | | Requirement Class | FIA_MBE_EXT.1 :Biometric enrolment | | Requirement Class | FIA_MBE_EXT.2: Quality of biometric templates for biometric enrolment | | Requirement Class | FIA_MBV_EXT.1:BMFPS Biometric verification | | Requirement Class | FIA_MBV_EXT.1 :UDFPS Biometric verification | | Requirement Class | FIA_MBV_EXT.2: Quality of biometric samples for biometric verification | | FMT: Security management | FMT_MOF_EXT.1: Management of Security Functions Behavior | | FMT: Security management | FMT_SMF.1: Specification of Management Functions | | FMT: Security management | FMT_SMF_EXT.2: Specification of Remediation Actions | | FMT: Security management | FMT_SMF_EXT.3 Current Administrator | | FPT: Protection of the TSF | FPT_AEX_EXT.1: Application Address Space Layout Randomization | | FPT: Protection of the TSF | FPT_AEX_EXT.2: Memory Page Permissions | | FPT: Protection of the TSF | FPT_AEX_EXT.3: Stack Overflow Protection | | FPT: Protection of the TSF | FPT_AEX_EXT.4: Domain Isolation | | FPT: Protection of the TSF | FPT_AEX_EXT.5: Kernel Address Space Layout Randomization | | FPT: Protection of the TSF | FPT_AEX_EXT.6: Write or Execute Memory Page Permissions | | FPT: Protection of the TSF | FPT_BBD_EXT.1: Application Processor Mediation | | FPT: Protection of the TSF | FPT_JTA_EXT.1: JTAG Disablement | | FPT: Protection of the TSF | FPT_KST_EXT.1: Key Storage | | FPT: Protection of the TSF | FPT_KST_EXT.2: No Key Transmission | | FPT: Protection of the TSF | FPT_KST_EXT.3: No Plaintext Key Export | | FPT: Protection of the TSF | FPT_NOT_EXT.1: Self-Test Notification FPT_TST_EXT.1: TSF Cryptographic Functionality Testing | | FPT: Protection of the TSF | FPT_TST_EXT.2/PREKERNEL: TSF Integrity Checking (Pre-kernel) | | FPT: Protection of the TSF | FPT_TST_EXT.2/POSTKERNEL: TSF Integrity Checking (Post-Kernel) | | FPT: Protection of the TSF | FPT_TUD_EXT.1: Trusted Update: TSF Version Query | | FPT: Protection of the TSF | FPT_TUD_EXT.2: TSF Update Verification | | FPT: Protection of the TSF | FPT_BDP_EXT.1 Biometric data processing | | FPT: Protection of the TSF | FPT_PBT_EXT.1 Protection of biometric template | | | FTA_SSL_EXT.1: TSF- and User-initiated Locked State | | FTA: TOE access | FTA_WSE_EXT.1: Wireless Network Access | | FTA: TOE access | FTP_ITC_EXT.1: Trusted Channel Communication | | ALC: Life Cycle Support | ALC_TSU_EXT.1: Timely Security Updates | 16 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ## 5 Security Requirements This section defines the Security Functional Requirements (SFRs) and Security Assurance Requirements (SARs) that serve to represent the security functional claims for the Target of Evaluation (TOE) and to scope the evaluation effort. The SFRs have all been drawn from the MDF/BT/BIO//WLAN/TLS/VPNC/BIO. The refinements and operations already performed in the MDF/BT/BIO//WLAN/TLS/VPNC are not identified (e.g., highlighted) here, rather the requirements have been copied from the PP_MDF_V3.3/MOD_BT_V1.0/MOD_WLANC_V1.0/ PKG_TLS_V1.1/MOD_VPNC_V2.5/ MOD_CPP_BIO_V1.1 and any residual operations have been completed herein. Of particular note, the MDF/BT/BIO//WLAN/TLS/VPNC made a number of refinements and completed some of the SFR operations defined in the Common Criteria (CC) and that PP should be consulted to identify those changes if necessary. The SARs are also drawn from the MDF/BT/BIO//WLAN/TLS/VPNC/BIO. The SARs are effectively refined since requirement-specific 'Assurance Activities' are defined in the MDF/BT/BIO//WLAN/TLS/VPNC/BIO that serve to ensure corresponding evaluations will yield more practical and consistent assurance than the assurance requirements alone. The MDF/BT/BIO//WLAN/TLS/VPNC/BIO should be consulted for the assurance activity definitions. ### 5.1 TOE Security Functional Requirements The following table identifies the SFRs that are satisfied by the Samsung Galaxy Devices on Android 16 TOE. | Requirement Class | Requirement Component | |----------------------------|--------------------------------------------------------------------------------------------------------| | FAU: Security Audit | FAU_GEN.1: Audit Data Generation | | FAU: Security Audit | MOD_BT_V1.0: FAU_GEN.1/BT Audit Data Generation (Bluetooth) | | FAU: Security Audit | MOD_WLANC_V1.0: FAU_GEN.1/WLAN: Audit Data Generation (Wireless LAN) | | FAU: Security Audit | FAU_SAR.1: Audit Review | | FAU: Security Audit | FAU_STG.1: Audit Storage Protection | | FAU: Security Audit | FAU_STG.4: Prevention of Audit Data Loss | | FCS: Cryptographic support | FCS_CKM.1: Cryptographic Key Generation | | FCS: Cryptographic support | MOD_WLANC_V1.0: FCS_CKM.1/WPA: Cryptographic Key Generation (Symmetric Keys for WPA2/WPA3 Connections) | | FCS: Cryptographic support | MOD_VPNC_V2.5: FCS_CKM.1/VPN: Cryptographic Key Generation (IKE) | | FCS: Cryptographic support | FCS_CKM.2/UNLOCKED: Cryptographic Key Establishment | | FCS: Cryptographic support | FCS_CKM.2/LOCKED: Cryptographic Key Establishment | | FCS: Cryptographic support | MOD_WLANC_V1.0: FCS_CKM.2/WLAN: Cryptographic Key Distribution (Group Temporal Key for WLAN) | | FCS: Cryptographic support | FCS_CKM_EXT.1: Cryptographic Key Support | | FCS: Cryptographic support | FCS_CKM_EXT.2: Cryptographic Key Random Generation | | FCS: Cryptographic support | FCS_CKM_EXT.3: Cryptographic Key Generation | | FCS: Cryptographic support | FCS_CKM_EXT.4: Key Destruction | | FCS: Cryptographic support | FCS_CKM_EXT.5: TSF Wipe | | FCS: Cryptographic support | FCS_CKM_EXT.6: Salt Generation | | FCS: Cryptographic support | MOD_BT_V1.0: FCS_CKM_EXT.8: Bluetooth Key Generation | | FCS: Cryptographic support | FCS_COP.1/ENCRYPT: Cryptographic operation | | FCS: Cryptographic support | FCS_COP.1/HASH: Cryptographic operation | | FCS: Cryptographic support | FCS_COP.1/SIGN: Cryptographic operation | | FCS: Cryptographic support | FCS_COP.1/KEYHMAC: Cryptographic operation | Version: 0.3 Date: 10/22/2026 17 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 | Requirement Class | Requirement Component | |----------------------------------------|-----------------------------------------------------------------------------------------------------------| | | FCS_COP.1/CONDITION: Cryptographic operation | | | FCS_HTTPS_EXT.1: HTTPS Protocol | | | MOD_VPN_CLI_V2.5: FCS_IPSEC_EXT.1: IPsec | | | FCS_IV_EXT.1: Initialization Vector Generation | | | FCS_RBG_EXT.1: Random Bit Generation | | | FCS_SRV_EXT.1: Cryptographic Algorithm Services | | | FCS_SRV_EXT.2: Cryptographic Algorithm Services | | | FCS_STG_EXT.1: Cryptographic Key Storage | | | FCS_STG_EXT.2: Encrypted Cryptographic Key Storage | | | FCS_STG_EXT.3: Integrity of Encrypted Key Storage | | | PKG_TLS_V1.1: FCS_TLS_EXT.1: TLS Protocol | | | PKG_TLS_V1.1: FCS_TLSC_EXT.1: TLS Client Protocol | | | MOD_WLANC_V1.0: FCS_TLSC_EXT.1/WLAN: TLS Client Protocol (EAP-TLS for WLAN) | | | PKG_TLS_V1.1: FCS_TLSC_EXT.2: TLS Client Support for Mutual Authentication | | | MOD_WLANC_V1.0: FCS_TLSC_EXT.2/WLAN: TLS Client Support for Supported Groups Extension (EAP-TLS for WLAN) | | | PKG_TLS_V1.1:FCS_TLSC_EXT.4 TLS Client Support for Renegotiation | | | PKG_TLS_V1.1: FCS_TLSC_EXT.5: TLS Client Support for Supported Groups Extension | | | MOD_WLANC_V1.0: FCS_WPA_EXT.1: Supported WPA Versions | | | FDP_ACF_EXT.1: Access Control for System Services | | | FDP_ACF_EXT.2: Access Control for System Resources | | | FDP_ACF_EXT.3: Security Attribute Based Access Control FDP_DAR_EXT.1: Protected Data Encryption | | FDP: User data | FDP_DAR_EXT.2: Sensitive Data Encryption FDP_IFC_EXT.1: Subset Information Flow Control | | protection | MOD_VPNC_V2.5: FDP_IFC_EXT.1: Subset Information Flow Control | | | MOD_VPNC_V2.5: FDP_RIP.2: Full Residual Information Protection | | | FDP_STG_EXT.1: User Data Storage | | | FDP_UPC_EXT.1/APPS: Inter-TSF User Data Transfer Protection (Applications) | | | FDP_UPC_EXT.1/ BLUETOOTH: Inter-TSF User Data Transfer Protection (Bluetooth) | | | FDP_VPN_EXT.1: Split Tunnel Prevention | | FIA: Identification and authentication | FIA_AFL_EXT.1: Authentication Failure Handling | | FIA: Identification and authentication | MOD_BT_V1.0: FIA_BLT_EXT.1: Bluetooth User Authorization | | FIA: Identification and authentication | MOD_BT_V1.0: FIA_BLT_EXT.2: Bluetooth Mutual Authentication | | FIA: Identification and authentication | MOD_BT_V1.0: FIA_BLT_EXT.3: Rejection of Duplicate Bluetooth Connections | | FIA: Identification and authentication | MOD_BT_V1.0: FIA_BLT_EXT.4: Secure Simple Pairing | | FIA: Identification and authentication | MOD_BT_V1.0: FIA_BLT_EXT.6: Trusted Bluetooth Device User Authorization | | FIA: Identification and authentication | MOD_BT_V1.0: FIA_BLT_EXT.7: Untrusted Bluetooth Device User Authorization | | FIA: Identification and authentication | MOD_WLANC_V1.0: FIA_PAE_EXT.1: Port Access Entity Authentication | | FIA: Identification and authentication | FIA_PMG_EXT.1: Password Management | | FIA: Identification and authentication | FIA_TRT_EXT.1: Authentication Throttling | | FIA: Identification and authentication | FIA_UAU.5: Multiple Authentication Mechanisms | | FIA: Identification and authentication | FIA_UAU.6/CREDENTIAL: Re-authenticating (Credential Change | | FIA: Identification and authentication | FIA_UAU.6/LOCKED: Re-authenticating (TSF Lock) | | FIA: Identification and authentication | FIA_UAU.7: Protected Authentication Feedback | | FIA: Identification and authentication | FIA_UAU_EXT.1: Authentication for Cryptographic Operation | | FIA: Identification and authentication | FIA_UAU_EXT.2: Timing of Authentication | | FIA: Identification and authentication | FIA_UAU_EXT.4: Secondary User Authentication | 18 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 | Requirement Class | Requirement Component | |--------------------------|-------------------------------------------------------------------------------------------| | Requirement Class | FIA_X509_EXT.1: Validation of Certificates | | Requirement Class | MOD_WLANC_V1.0: FIA_X509_EXT.1/WLAN: X.509 Certificate Validation | | Requirement Class | FIA_X509_EXT.2: X.509 Certificate Authentication | | Requirement Class | MOD_WLANC_V1.0: FIA_X509_EXT.2/WLAN: X.509 Certificate Authentication (EAP-TLS for WLAN) | | Requirement Class | FIA_X509_EXT.3: Request Validation of Certificates | | Requirement Class | MOD_WLANC_V1.0: FIA_X509_EXT.6: Certificate Storage and Management | | Requirement Class | MOD_CPP_BIO_V1.1 /FIA_MBE_EXT.1 :Biometric enrolment | | Requirement Class | MOD_CPP_BIO_V1.1 /FIA_MBE_EXT.2:Quality of biometric templates for biometric enrolment | | Requirement Class | MOD_CPP_BIO_V1.1/FIA_MBV_EXT.1/BMFPS : Biometric verification | | Requirement Class | MOD_CPP_BIO_V1.1 /FIA_MBV_EXT.1/UDFPS: Biometric verification | | Requirement Class | MOD_CPP_BIO_V1.1/FIA_MBV_EXT.2/Quality of biometric samples for biometric verification | | FMT: Security management | FMT_MOF_EXT.1: Management of Security Functions Behavior | | FMT: Security management | FMT_SMF.1: Specification of Management Functions | | FMT: Security management | MOD_BT_V1.0: FMT_SMF_EXT.1/BT: Specification of Management Functions (Bluetooth) | | FMT: Security management | MOD_WLANC_V1.0: FMT_SMF.1/WLAN: Specification of Management Functions (WLAN Client) | | FMT: Security management | MOD_VPNC_V2.5: FMT_SMF.1/VPN: Specification of Management Functions - VPN | | FMT: Security management | FMT_SMF_EXT.2: Specification of Remediation Actions | | FMT: Security management | FMT_SMF_EXT.3: Current Administrator | | FPT: the | FPT_AEX_EXT.1: Application Address Space Layout Randomization | | | FPT_AEX_EXT.2: Memory Page Permissions | | | FPT_AEX_EXT.3: Stack Overflow Protection | | | FPT_AEX_EXT.4: Domain Isolation | | | FPT_AEX_EXT.5: Kernel Address Space Layout Randomization | | | FPT_AEX_EXT.6: Write or Execute Memory Page Permissions | | | FPT_BBD_EXT.1: Application Processor Mediation | | | MOD_CPP_BIO_V1.1/FPT_BDP_EXT.1 : Biometric data processing | | | FPT_JTA_EXT.1: JTAG Disablement | | | FPT_KST_EXT.1 & MOD_CPP_BIO_V1.1/FPT_KST_EXT.1. Key Storage | | | FPT_KST_EXT.2 & MOD_CPP_BIO_V1.1/ FPT_KST_EXT.2: No Key Transmission | | | Protection of FPT_KST_EXT.3: No Plaintext Key Export | | | TSF FPT_NOT_EXT.1: Self-Test Notification | | | MOD_CPP_BIO_V1.1/FPT_PBT_EXT.1: Protection of biometric template | | | FPT_STM.1: Reliable time stamps | | | FPT_TST_EXT.1: TSF Cryptographic Functionality Testing | | | MOD_WLANC_V1.0: FPT_TST_EXT.3/WLAN: TSF Cryptographic Functionality Testing (WLAN Client) | | | MOD_VPNC_V2.5: FPT_TST_EXT.1/VPN: TSF Self-Test (VPN Client) | | | FPT_TST_EXT.2/PREKERNEL: TSF Integrity Checking (Pre-Kernel) | | | FPT_TST_EXT.2/POSTKERNEL: TSF Integrity Checking (Post-Kernel) | | | FPT_TUD_EXT.1: Trusted Update: TSF Version Query | | | FPT_TUD_EXT.2: TSF Update Verification FPT_TUD_EXT.3: Application Signing | | | FPT_TUD_EXT.6: Trusted Update Verification | 19 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 Table 7 - TOE Security Functional Requirements | Requirement Class | Requirement Component | |---------------------|------------------------------------------------------------------------------| | FTA: TOE access | FTA_SSL_EXT.1: TSF- and User-initiated Locked State | | FTA: TOE access | FTA_TAB.1: Default TOE Access Banners | | FTA: TOE access | MOD_WLANC_V1.0: FTA_WSE_EXT.1: Wireless Network Access | | FTA: TOE access | MOD_BT_V1.0: FTP_BLT_EXT.1: Bluetooth Encryption | | FTA: TOE access | MOD_BT_V1.0: FTP_BLT_EXT.2: Persistence of Bluetooth Encryption | | FTA: TOE access | MOD_BT_V1.0: FTP_BLT_EXT.3/BR: Bluetooth Encryption Parameters (BR/EDR) | | FTA: TOE access | MOD_BT_V1.0: FTP_BLT_EXT.3/LE: Bluetooth Encryption Parameters (LE) | | FTA: TOE access | FTP_ITC_EXT.1: Trusted Channel Communication | | FTA: TOE access | MOD_WLANC_V1.0: FTP_ITC.1/WLAN: Trusted Channel Communication (Wireless LAN) | #### 5.1.1 Security Audit (FAU) ##### 5.1.1.1 FAU_GEN.1: Audit Data Generation & MOD_BT_V1.0: FAU_GEN.1/BT Audit Data Generation (Bluetooth) ####### FAU_GEN.1.1 ####### FAU_GEN.1.2 The TSF shall be able to generate an audit record of the following auditable events: 1. Start-up and shutdown of the audit functions 2. All auditable events for the [not selected] level of audit 3. All administrative actions 4. Start-up and shutdown of the OS 5. Insertion or removal of removable media 6. Specifically defined auditable events in Table 12 (from Table 2 of the PP_MDF_V3.3); 7. [ Audit records reaching [90] percentage of audit capacity ] 8. [ Specifically defined auditable events as listed in Table 12 - Audit Events from Table 3 of the PP_MDF_V3.3 ] 9. [ Auditable events as listed in Table 13 - Bluetooth Audit Events from Table 2 of the MOD_BT_V1.0 ] The TSF shall record within each audit record at least the following information: 1. Date and time of the event 2. Type of event 3. Subject identity 4. The outcome (success or failure) of the event 5. Additional information in Table 12(Table 2 of the PP_MDF_V3.3) 6. [ Additional information in Table 12 (Table of the PP_MDF_V3.3) ] 7. [ For each audit event type, based on the auditable event definitions of the functional components included in the PP/ST, Additional information in the Auditable Events table of the MOD_BT_V1.0 ] (TD0707 applied) ##### 5.1.1.2 FAU_GEN.1/WLAN: Audit Data Generation (Wireless LAN) ####### FAU_GEN.1.1/WLAN The TSF shall [ implement functionality ] to generate an audit record of the following auditable events: 20 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target - a. Startup and shutdown of the audit functions; - b. All auditable events for not specified level of audit; and - c. all auditable events for mandatory SFRs specified in Table 14 - WLAN Client Audit Events ####### from Table 2 of the MOD_WLANC_V1.0. ####### FAU_GEN.1.2/WLAN The [ TSF ] shall record within each audit record at least the following information: - a. Date and time of the event, type of event, subject identity, (if relevant) the outcome (success or failure) of the event; and - b. For each audit event type, based on the auditable event definitions of the functional components included in the PP-Module/ST, Additional Audit Record Contents as specified in Table 14 - WLAN Client Audit Events from Table 2 of the MOD_WLANC_V1.0. ##### 5.1.1.3 FAU_SAR.1: Audit Review ####### FAU_SAR.1.1 ####### FAU_SAR.1.2 The TSF shall provide the audit records in a manner suitable for the user to interpret the information. ##### 5.1.1.4 FAU_STG.1: Audit Storage Protection ####### FAU_STG.1.1 ####### FAU_STG.1.2 The TSF shall be able to prevent unauthorized modifications to the stored audit records in the audit trail. ##### 5.1.1.5 FAU_STG.4: Prevention of Audit Data Loss ####### FAU_STG.4.1 The TSF shall overwrite the oldest stored audit records if the audit trail is full. #### 5.1.2 Cryptographic Support (FCS) ##### 5.1.2.1 FCS_CKM.1: Cryptographic Key Generation ####### FCS_CKM.1.1 Version: 0.3 Date: 10/22/2026 The TSF shall provide the administrator with the capability to read all audited events and record contents from the audit records. The TSF shall protect the stored audit records in the audit trail from unauthorized deletion. The TSF shall generate asymmetric cryptographic keys in accordance with a specified cryptographic key generation algorithm: - ECC schemes using 'NIST curves' P-256, P-384, and [P-521] that meet the following: FIPS PUB 186-4 , 'Digital Signature Standard (DSS)', Appendix B.4, or FIPS PUB 186 -5, "Digital Signature Standard (DSS)", Appendix A.2 1 [ - RSA schemes using cryptographic key sizes of [2048-bit or greater] that meet FIPS PUB 186-5 , 'Digital Signature Standard (DSS)', Appendix B.3 or FIPS PUB 186-5, "Digital Signature Standard (DSS)", Appendix A.1 1 Modified as per MOD_VPNC_V2.5 21 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target - FFC schemes using [ - "safe-prime" groups that meet the following: NIST Special Publication 800-56A Revision 3, "Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography" ], - ]. (TD0950 applied) ##### 5.1.2.2 MOD_WLANC_V1.0: FCS_CKM.1/WPA: Cryptographic Key Generation (Symmetric Keys for WPA2/WPA3 Connections ####### FCS_CKM.1.1/WPA The TSF shall generate symmetric cryptographic keys in accordance with a specified cryptographic key generation algorithm PRF-384 and [ PRF-704 ] (as defined in IEEE 802.112012) and specified cryptographic key sizes 256 bits and [ no other key sizes ] using a Random Bit Generator as specified in FCS_RBG_EXT.1 ##### 5.1.2.3 MOD_VPNC_V2.5: FCS_CKM.1/VPN: Cryptographic Key Generation (IKE) ####### FCS_CKM.1.1/VPN The TSF shall [ implement functionality ] to generate asymmetric cryptographic keys used for IKE peer authentication in accordance with: - FIPS PUB 1865, 'Digital Signature Standard (DSS),' Appendix A.1 for RSA schemes - FIPS PUB 1865, 'Digital Signature Standard (DSS),' Appendix A.2 for ECDSA schemes and implementing 'NIST curves,' P -256, P-384 and [P-521] ] (TD0954 applied) and specified cryptographic key sizes equivalent to, or greater than, a symmetric key strength of 112 bits. ##### 5.1.2.4 FCS_CKM.2/UNLOCKED: Cryptographic Key Establishment ####### FCS_CKM.2.1/UNLOCKED The TSF shall perform cryptographic key establishment in accordance with a specified cryptographic key establishment method: 2 - Elliptic curve-based key establishment schemes that meets the following: NIST Special Publication 80056A Revision 3, 'Recommendation for Pair -Wise Key Establishment Schemes Using Discrete Logarithm Cryptography', [ - RSA-based key establishment schemes that meet the following [ NIST Special Publication 80056B, 'Recommendation for Pair -Wise Key Establishment Schemes Using Integer Factorization Cryptography' - Finite field-based key establishment schemes that meets the following: NIST Special Publication 800-56A Revision 3, "Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography" ]. ##### 5.1.2.5 FCS_CKM.2/LOCKED: Cryptographic Key Establishment ####### FCS_CKM.2.1/LOCKED The TSF shall perform cryptographic key establishment in accordance with a specified cryptographic key establishment method: [ 2 Modified as per MOD_VPNC_V2.5 Version: 0.3 Date: 10/22/2026 22 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 - RSA-based key establishment schemes that meets the following: NIST Special Publication 800-56B, "Recommendation for Pair-Wise Key Establishment Schemes Using Integer Factorization Cryptography", - Elliptic curve-based key establishment schemes that meets the following: [NIST Special Publication 800-56A Revision 3 , 'Recommendation for Pair -Wise Key Establishment Schemes Using Discrete Logarithm Cryptography']] for the purposes of encrypting sensitive data received while the device is locked. ##### 5.1.2.6 MOD_WLANC_V1.0: FCS_CKM.2/WLAN: Cryptographic Key Distribution (Group Temporal Key for WLAN) ####### FCS_CKM.2.1/WLAN Refinement: The TSF shall decrypt Group Temporal Key in accordance with a specified cryptographic key distribution method [ AES Key Wrap in an EAPOL-Key frame ] that meets the following: [ RFC 3394 for AES Key Wrap, 802.11-2012 for the packet format and timing considerations ] and does not expose the cryptographic keys . ##### 5.1.2.7 FCS_CKM_EXT.1: Cryptographic Key Support ####### FCS_CKM_EXT.1.1 The TSF shall support a [ immutable hardware ] REK(s) with a [ symmetric ] key of strength [ 256 bits ]. ####### FCS_CKM_EXT.1.2 Each REK shall be hardware-isolated from the OS on the TSF in runtime. ####### FCS_CKM_EXT.1.3 Each REK shall be generated by a RBG in accordance with FCS_RBG_EXT.1. ##### 5.1.2.8 FCS_CKM_EXT.2: Cryptographic Key Random Generation ####### FCS_CKM_EXT.2.1 All DEKs shall be [ - randomly generated ] with entropy corresponding to the security strength of AES key sizes of [ 256 ] bits. ##### 5.1.2.9 FCS_CKM_EXT.3: Cryptographic Key Generation ####### FCS_CKM_EXT.3.1 The TSF shall use [ - asymmetric KEKs of [128-bit] security strength, - symmetric KEKs of [256-bit] security strength corresponding to at least the security strength of the keys encrypted by the KEK ]. ####### FCS_CKM_EXT.3.2 The TSF shall generate all KEKs using one of the following methods: - Derive the KEK from a Password Authentication Factor using according to FCS_COP.1.1/CONDITION and [ - Generate the KEK using an RBG that meets this profile (as specified in FCS_RBG_EXT.1), 23 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ####### FCS_CKM_EXT.4.2 The TSF shall destroy all plaintext keying material and critical security parameters when no longer needed. ##### 5.1.2.11 FCS_CKM_EXT.5: TSF Wipe ####### FCS_CKM_EXT.5.1 The TSF shall wipe all protected data by [ - Cryptographically erasing the encrypted DEKs and/or the KEKs in non-volatile memory by following the requirements in FCS_CKM_EXT.4.1 - Overwriting all Protected Data according to the following rules: - o For EEPROM, the destruction shall be executed by a single direct overwrite consisting of a pseudo random pattern using the TSF's RBG (as specified in FCS_RBG_EXT.1, followed by a read-verify. - o For flash memory, that is not wear-leveled, the destruction shall be executed [by a block erase that erases the reference to memory that stores data as well as the data itself]. - o For flash memory, that is wear-leveled, the destruction shall be executed [by a block erase]. - o For non-volatile memory other than EEPROM and flash, the destruction shall be executed by a single direct overwrite with a random pattern that is changed before each write. - Generate the KEK using a key generation scheme that meets this profile (as specified in FCS_CKM.1), - Combine the KEK from other KEKs in a way that preserves the effective entropy of each factor by [concatenating the keys and using a KDF (as described in SP 800-108) (for FBE) , encrypting one key with another] ]. Version: 0.3 Date: 10/22/2026 ##### 5.1.2.10 FCS_CKM_EXT.4: Key Destruction ####### FCS_CKM_EXT.4.1 The TSF shall destroy cryptographic keys in accordance with the specified cryptographic key destruction methods: - by clearing the KEK encrypting the target key - in accordance with the following rules - o For volatile memory, the destruction shall be executed by a single direct overwrite [ consisting of zeroes ]. - o For non-volatile EEPROM, the destruction shall be executed by a single direct overwrite consisting of a pseudo random pattern using the TSF's RBG (as specified in FCS_RBG_EXT.1), followed by a read-verify. - o For non-volatile flash memory, that is not wear-leveled, the destruction shall be executed [ by a single direct overwrite consisting of zeros followed by a readverify ]. - o For non-volatile flash memory, that is wear-leveled, the destruction shall be executed [ by a block erase ]. - o For non-volatile memory other than EEPROM and flash, the destruction shall be executed by a single direct overwrite with a random pattern that is changed before each write. 24 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ]. ####### FCS_CKM_EXT.5.2 The TSF shall perform a power cycle on conclusion of the wipe procedure. ##### 5.1.2.12 FCS_CKM_EXT.6: Salt Generation ####### FCS_CKM_EXT.6.1 The TSF shall generate all salts using a RBG that meets FCS_RBG_EXT.1. ##### 5.1.2.13 MOD_BT_V1.0: FCS_CKM_EXT.8: Bluetooth Key Generation ####### FCS_CKM_EXT.8.1 The TSF shall generate public/private ECDH key pairs every [ time a connection between devices is established ]. ##### 5.1.2.14 FCS_COP.1/ENCRYPT: Cryptographic operation ####### FCS_COP.1.1/ENCRYPT The TSF shall perform encryption/decryption in accordance with a specified cryptographic algorithm: - AES-CBC (as defined in FIPS PUB 197, and NIST SP 800-38A) mode - AES-CCMP (as defined in FIPS PUB 197, NIST SP 800-38C and IEEE 802.11-2012), - AES-GCM (as defined in NIST SP 800-38D), and [ - AES Key Wrap (KW) (as defined in NIST SP 800-38F), - AES-XTS (as defined in NIST SP 800-38E) ] and cryptographic key sizes 128-bit key sizes and [ 256-bit key sizes ]. 3 ##### 5.1.2.15 FCS_COP.1/HASH: Cryptographic operation ####### FCS_COP.1.1/HASH The TSF shall perform cryptographic hashing in accordance with a specified cryptographic algorithm SHA-1 and [ SHA-256, SHA-384, SHA-512 ] and message digest sizes 160 and [ 256, 384, 512 ] that meet the following: FIPS Pub 180-4. ##### 5.1.2.16 FCS_COP.1/SIGN: Cryptographic operation ####### FCS_COP.1.1/SIGN The TSF shall perform cryptographic signature services (generation and verification) in accordance with a specified cryptographic algorithm [ - RSA schemes using cryptographic key sizes of 2048-bit or greater that meet the following: FIPS PUB 186-4 or FIPS PUB 186-5 , 'Digital Signature Standard (DSS)', Section 4, - ECDSA schemes using 'NIST curves' P -384 and [P-256, P-521] that meet the following: FIPS PUB 186-5 , 'Digital Signature Standard (DSS)', Section 5 ]. ##### 5.1.2.17 FCS_COP.1/KEYHMAC: Cryptographic operation ####### FCS_COP.1.1/KEYHMAC 3 Modified as per MOD_VPNC_V2.5 Version: 0.3 Date: 10/22/2026 25 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 The TSF shall perform keyed-hash message authentication in accordance with a specified cryptographic algorithm HMAC-SHA-1 and [ HMAC-SHA-256, HMAC-SHA-384, HMAC-SHA512 ] and cryptographic key sizes [ 160, 256, 384, 512-bits ] and message digest sizes 160 and [ 256, 384, 512 ] bits that meet the following: FIPS Pub 1981, 'The Keyed -Hash Message Authentication Code', and FIPS Pub 180 - 4, 'Secure Hash Standard'. ##### 5.1.2.18 FCS_COP.1/CONDITION: Cryptographic operation ####### FCS_COP.1.1/CONDITION The TSF shall perform conditioning in accordance with a specified cryptographic algorithm HMAC-[ SHA-256 ] using a salt, and [ PDKDF2 with [8192] iterations, [key stretching with scrypt)] ], and output cryptographic key sizes [ 256 ] that meet the following: [ NIST SP 800132 (PBKDF2), no standard (scrypt) ]. ##### 5.1.2.19 FCS_HTTPS_EXT.1: HTTPS Protocol ####### FCS_HTTPS_EXT.1.1 The TSF shall implement the HTTPS protocol that complies with RFC 2818. ####### FCS_HTTPS_EXT.1.2 The TSF shall implement HTTPS using TLS as defined in the Package for Transport Layer Security, version 1.1. ####### FCS_HTTPS_EXT.1.3 The TSF shall notify the application and [ no other action ] if the peer certificate is deemed invalid. ##### 5.1.2.20 MOD_VPNC_V2.5: FCS_IPSEC_EXT.1: IPsec ####### FCS_IPSEC_EXT.1.1 The TSF shall implement the IPsec architecture as specified in RFC 4301. ####### FCS_IPSEC_EXT.1.2 The TSF shall implement [ tunnel mode ]. ####### FCS_IPSEC_EXT.1.3 The TSF shall have a nominal, final entry in the SPD that matches anything that is otherwise unmatched, and discards it. ####### FCS_IPSEC_EXT.1.4 The TSF shall implement the IPsec protocol ESP as defined by RFC 4303 using the cryptographic algorithms AES-GCM-128, AES-GCM-256 as specified in RFC 4106, [ AES-CBC128, AES-CBC-256 (both specified by RFC 3602) together with a Secure Hash Algorithm (SHA)-based HMAC ]. ####### FCS_IPSEC_EXT.1.5 The TSF shall implement the protocol: [ - IKEv2 as defined in RFCs 7296 (with mandatory support for NAT traversal as specified in section 2.23), RFC 8247 and [RFC 4868 for hash functions] ]. (TD0897 applied) ####### FCS_IPSEC_EXT.1.6 The TSF shall ensure the encrypted payload in the [ IKEv2 ] protocol uses the cryptographic algorithms AES-CBC-128, AES-CBC-256 as specified in RFC 6379 and [ AES-GCM-128, AESGCM-256 as specified in RFC 5282 ]. ####### FCS_IPSEC_EXT.1.7 The TSF shall ensure that [ - IKEv2 SA lifetimes can be configured by [VPN Gateway] based on [length of time]; 26 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ####### FCS_IPSEC_EXT.1.9 The TSF shall generate the secret value x used in the IKE DiffieHellman key exchange ('x' in g x mod p) using the random bit generator specified in FCS_RBG_EXT.1, and having a length of at least [ (224, 256, or 384) ] bits. ####### FCS_IPSEC_EXT.1.10 The TSF shall generate nonces used in IKE exchanges in a manner such that the probability that a specific nonce value will be repeated during the life a specific IPsec SA is less than 1 in 2^[ (112, 128, or 192) ]. ####### FCS_IPSEC_EXT.1.11 The TSF shall ensure that all IKE protocols perform peer authentication using a [ RSA, ECDSA ] that use X.509v3 certificates that conform to RFC 4945 and [ no other method ]. ####### FCS_IPSEC_EXT.1.12 The TSF shall not establish an SA if the [ IP address, Fully Qualified Domain Name (FQDN) ] and [ no other reference identifier type ] contained in a certificate does not match the expected value(s) for the entity attempting to establish a connection. ####### FCS_IPSEC_EXT.1.13 The TSF shall not establish an SA if the presented identifier does not match the configured reference identifier of the peer. ####### FCS_IPSEC_EXT.1.14 The [ VPN Gateway ] shall be able to ensure by default that the strength of the symmetric algorithm (in terms of the number of bits in the key) negotiated to protect the [ IKEv2 IKE_SA ] connection is greater than or equal to the strength of the symmetric algorithm (in terms of the number of bits in the key) negotiated to protect the IKEv2 CHILD_SA ] connection. ##### 5.1.2.21 FCS_IV_EXT.1: Initialization Vector Generation ####### FCS_IV_EXT.1.1 The TSF shall generate IVs in accordance with PP_MDF_V3.3 Table 11: References and IV Requirements for NIST-approved Cipher Modes. ##### 5.1.2.22 FCS_RBG_EXT.1: Random Bit Generation ####### FCS_RBG_EXT.1.1 The TSF shall perform all deterministic random bit generation services in accordance with NIST Special Publication 800-90A using [Hash_DRBG (any), HMAC_DRBG (any), CTR_DRBG (AES)] . ####### FCS_RBG_EXT.1.2 The deterministic RBG shall be seeded by an entropy source that accumulates entropy from [ a software-based noise source, TSF-hardware-based noise source ] with a minimum of Version: 0.3 Date: 10/22/2026 If length of time is used, it must include at least one option that is 24 hours or less for Phase 1 SAs and 8 hours or less for Phase 2 SAs. ####### FCS_IPSEC_EXT.1.8 The TSF shall ensure that all IKE protocols implement DH groups 19 (256-bit Random ECP), 20 (384-bit Random ECP), and [ - [14 (2048-bit MODP, 15 (3072-bit MODP), 16 (4096-bit MODP),) ] according to RFC 3526 - [21 (521-bit Random ECP), 24 (2048-bit MODP with 256-bit POS)] according to RFC 5114]. 27 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 [ 256 bits, 384 bits ] of entropy at least equal to the greatest security strength (according to NIST SP 800-57) of the keys and hashes that it will generate. (TD0934 applied) ####### FCS_RBG_EXT.1.3 The TSF shall be capable of providing output of the RBG to applications running on the TSF that request random bits. ##### 5.1.2.23 FCS_SRV_EXT.1: Cryptographic Algorithm Services ####### FCS_SRV_EXT.1.1 The TSF shall provide a mechanism for applications to request the TSF to perform the following cryptographic operations: - All mandatory and [ selected algorithms ] in FCS_CKM.2/LOCKED - The following algorithms in FCS_COP.1/ENCRYPT: AES-CBC, [ AES-GCM ] - All mandatory and selected algorithms in FCS_COP.1/SIGN - All mandatory and selected algorithms in FCS_COP.1/HASH - All mandatory and selected algorithms in FCS_COP.1/KEYHMAC - [ No other cryptographic operations ]. ##### 5.1.2.24 FCS_SRV_EXT.2: Cryptographic Algorithm Services ####### FCS_SRV_EXT.2.1 The TSF shall provide a mechanism for applications to request the TSF to perform the following cryptographic operations: - Algorithms in FCS_COP.1/ENCRYPT - Algorithms in FCS_COP.1/SIGN by keys stored in the secure key storage. ##### 5.1.2.25 FCS_STG_EXT.1: Cryptographic Key Storage ####### FCS_STG_EXT.1.1 The TSF shall provide [ mutable hardware (only available on select devices), softwarebased ] secure key storage for asymmetric private keys and [ symmetric keys ]. ####### FCS_STG_EXT.1.2 The TSF shall be capable of importing keys/secrets into the secure key storage upon request of [ the user, the administrator ] and [ applications running on the TSF ]. ####### FCS_STG_EXT.1.3 The TSF shall be capable of destroying keys/secrets in the secure key storage upon request of [ the user, the administrator ]. ####### FCS_STG_EXT.1.4 The TSF shall have the capability to allow only the application that imported the key/secret the use of the key/secret. Exceptions may only be explicitly authorized by [ a common application developer ]. ####### FCS_STG_EXT.1.5 The TSF shall allow only the application that imported the key/secret to request that the key/secret be destroyed. Exceptions may only be explicitly authorized by [ a common application developer ]. ##### 5.1.2.26 FCS_STG_EXT.2: Encrypted Cryptographic Key Storage FCS_STG_EXT.2.1 28 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ####### FCS_STG_EXT.2.2 DEKs, KEKs, [ Bluetooth and WPA3/WPA2 PSK long-term trusted channel key material and SecurityLogAgent properties (related to SE Android) ] and [ all software-based key storage ] shall be encrypted using one of the following methods: [ - o using a SP800-56B key establishment scheme, - o using AES in the [GCM, CBC mode] ]. ##### 5.1.2.27 FCS_STG_EXT.3: Integrity of Encrypted Key Storage ####### FCS_STG_EXT.3.1 The TSF shall protect the integrity of any encrypted DEKs and KEKs and [ long-term trusted channel key material, all software-based key storage ] by [ - [GCM] cipher mode for encryption according to FCS_STG_EXT.2 - a hash (FCS_COP.1/HASH) of the stored key that is encrypted by a key protected by FCS_STG_EXT.2 - a keyed hash (FCS_COP.1/KEYHMAC) using a key protected by a key protected by FCS_STG_EXT.2 ]. ####### FCS_STG_EXT.3.2 The TSF shall verify the integrity of the [ MAC ] of the stored key prior to use of the key. ##### 5.1.2.28 PKG_TLS_V1.1: FCS_TLS_EXT.1: TLS Protocol ####### FCS_TLS_EXT.1.1 The product shall implement [ - TLS as a client ]. ##### 5.1.2.29 PKG_TLS_V1.1: FCS_TLSC_EXT.1: TLS Client Protocol ####### FCS_TLSC_EXT.1.1 The product shall implement TLS 1.2 (RFC 5246) and [ no earlier TLS versions ] as a client that supports the cipher suites [ - TLS_RSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5288, - TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 as defined in RFC 5289, - TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289, - TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 as defined in RFC 5289, - TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289 ] Version: 0.3 Date: 10/22/2026 The TSF shall encrypt all DEKs, KEKs [ Wi-Fi, Bluetooth, VPN, and SecurityLogAgent properties (related to SE Android) ] and [ all software-based key storage ] by KEKs that are [ - Protected by the REK with [ - o encryption by a REK, - o encryption by a KEK that is derived from a REK], - Protected by the REK and the password with [ - o encryption by a REK and the password-derived KEK or biometric-unlocked KEK , - o encryption by a KEK that is derived from a REK and the password-derived or biometric-unlocked KEK] ]. 29 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target and also supports functionality for [ - mutual authentication - session renegotiation ]. ####### FCS_TLSC_EXT.1.2 The product shall verify that the presented identifier matches the reference identifier according to RFC 6125. ####### FCS_TLSC_EXT.1.3 The product shall not establish a trusted channel if the server certificate is invalid [ - with no exceptions ]. (TD0442 applied) ##### 5.1.2.30 MOD_WLANC_V1.0: FCS_TLSC_EXT.1/WLAN: TLS Client Protocol (EAP-TLS for WLAN) ####### FCS_TLSC_EXT.1.1/WLAN The TSF shall implement TLS 1.2 (RFC 5246) and [ TLS 1.1 (RFC 4346) ] in support of the EAPTLS protocol as specified in RFC 5216 supporting the following ciphersuites: [ - TLS_RSA_WITH_AES_128_CBC_SHA as defined in RFC 5246, - TLS_RSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5288, - TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 as defined in RFC 5289, - TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289, - TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 as defined in RFC 5289, - TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289 ]. ####### FCS_TLSC_EXT.1.2/WLAN The TSF shall generate random values used in the EAP-TLS exchange using the RBG specified in FCS_RBG_EXT.1. ####### FCS_TLSC_EXT.1.3/WLAN The TSF shall use X509 v3 certificates as specified in FIA_X509_EXT.1/WLAN. ####### FCS_TLSC_EXT.1.4/WLAN The TSF shall verify that the server certificate presented includes the Server Authentication purpose (id-kp 1 with OID 1.3.6.1.5.5.7.3.1) in the extendedKeyUsage field. ####### FCS_TLSC_EXT.1.5/WLAN The TSF shall allow an authorized administrator to configure the list of CAs that are allowed to sign authentication server certificates that are accepted by the TOE. ##### 5.1.2.31 PKG_TLS_V1.1: FCS_TLSC_EXT.2: TLS Client Support for Mutual Authentication ####### FCS_TLSC_EXT.2.1 The product shall support mutual authentication using X.509v3 certificates. ##### 5.1.2.32 MOD_WLANC_V1.0: FCS_TLSC_EXT.2/WLAN: TLS Client Support for Supported Groups Extension (EAP-TLS for WLAN) ####### FCS_TLSC_EXT.2.1/WLAN The TSF shall present the Supported Groups extension in the Client Hello with the following NIST curves: [ secp256r1, secp384r1 ]. Version: 0.3 Date: 10/22/2026 30 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ##### 5.1.2.33 PKG_TLS_V1.1:FCS_TLSC_EXT.4 TLS Client Support for Renegotiation ####### FCS_TLSC_EXT.4.1 The product shall support secure renegotiation through use of the 'renegotiation_info' TLS extension in accordance with RFC 5746. ##### 5.1.2.34 PKG_TLS_V1.1: FCS_TLSC_EXT.5: TLS Client Support for Supported Groups Extension ####### FCS_TLSC_EXT.5.1 The product shall present the Supported Groups Extension in the Client Hello with the supported groups: [ - secp256r1, - secp384r1 ]. ##### 5.1.2.35 MOD_WLANC_V1.0: FCS_WPA_EXT.1: Supported WPA Versions ####### FCS_WPA_EXT.1.1 The TSF shall support WPA3 and [ WPA2 ] security type. #### 5.1.3 User Data Protection (FDP) ##### 5.1.3.1 FDP_ACF_EXT.1: Access Control for System Services ####### FDP_ACF_EXT.1.1 The TSF shall provide a mechanism to restrict the system services that are accessible to an application. ####### FDP_ACF_EXT.1.2 The TSF shall provide an access control policy that prevents [ application, groups of applications ] from accessing [ all ] data stored by other [ application, groups of applications ]. Exceptions may only be explicitly authorized for such sharing by [ the administrator, a common application developer ]. ##### 5.1.3.2 FDP_ACF_EXT.2: Access Control for System Resources ####### FDP_ACF_EXT.2.1 The TSF shall provide a separate [ address book, calendar ] for each application group and only allow applications within that process group to access the resource. Exceptions may only be explicitly authorized for such sharing by [ the user ]. ##### 5.1.3.3 FDP_ACF_EXT.3: Security Attribute Based Access Control ####### FDP_ACF_EXT.3.1 The TSF shall enforce an access control policy that prohibits an application from granting both write and execute permission to a file on the device except for [ files stored in the application's private data folder ]. ##### 5.1.3.4 FDP_DAR_EXT.1: Protected Data Encryption ####### FDP_DAR_EXT.1.1 Encryption shall cover all protected data. Version: 0.3 Date: 10/22/2026 31 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ####### FDP_DAR_EXT.1.2 Encryption shall be performed using DEKs with AES in the [ CBC, XTS ] mode with key size [ 256 ] bits. ##### 5.1.3.5 FDP_DAR_EXT.2: Sensitive Data Encryption ####### FDP_DAR_EXT.2.1 The TSF shall provide a mechanism for applications to mark data and keys as sensitive. ####### FDP_DAR_EXT.2.2 The TSF shall use an asymmetric key scheme to encrypt and store sensitive data received while the product is locked. ####### FDP_DAR_EXT.2.3 The TSF shall encrypt any stored symmetric key and any stored private key of the asymmetric key(s) used for the protection of sensitive data according to FCS_STG_EXT.2.1 selection 2. ####### FDP_DAR_EXT.2.4 The TSF shall decrypt the sensitive data that was received while in the locked state upon transitioning to the unlocked state using the asymmetric key scheme and shall re-encrypt that sensitive data using the symmetric key scheme. ##### 5.1.3.6 FDP_IFC_EXT.1: Subset Information Flow Control ####### FDP_IFC_EXT.1.1 The TSF shall - provide a VPN client which can protect all IP traffic using IPsec as defined in the PPModule for VPN Client with the exception of IP traffic required to establish the VPN connection and [ captive portal traffic needed for correct functioning of the TOE ], when the VPN is enabled 4 . ##### 5.1.3.7 MOD_VPNC_V2.5: FDP_RIP.2: Full Residual Information Protection ####### FDP_RIP.2.1 The [ TOE ] shall ensure that any previous information content of a resource is made unavailable upon the [ allocation of the resource to ] all objects. ##### 5.1.3.8 FDP_STG_EXT.1: User Data Storage ####### FDP_STG_EXT.1.1 The TSF shall provide protected storage for the Trust Anchor Database. ##### 5.1.3.9 FDP_UPC_EXT.1/APPS: Inter-TSF User Data Transfer Protection (Applications) ####### FDP_UPC_EXT.1.1/APPS The TSF shall provide a means for non-TSF applications executing on the TOE to use - Mutually authenticated TLS as defined in the Functional Package for Transport Layer Security (TLS), version 1.1, - HTTPS, and [ 4 Modified as per MOD_VPNC_V2.5 Version: 0.3 Date: 10/22/2026 32 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 ####### · IPsec as defined in the PP-Module for Virtual Private Network (VPN) Clients, version 2.4 ] to provide a protected communication channel between the non-TSF application and another IT product that is logically distinct from other communication channels, provides assured identification of its end points, protects channel data from disclosure, and detects modification of the channel data. ####### FDP_UPC_EXT.1.2/APPS The TSF shall permit the non-TSF applications to initiate communication via the trusted channel. ##### 5.1.3.10 FDP_UPC_EXT.1/ BLUETOOTH: Inter-TSF User Data Transfer Protection (Bluetooth) ####### FDP_UPC_EXT.1.1/BLUETOOTH The TSF shall provide a means for non-TSF applications executing on the TOE to use - Bluetooth BR/EDR in accordance with the PP-Module for Bluetooth, and [ - Bluetooth LE in accordance with the PP-Module for Bluetooth, version 1.0 ] to provide a protected communication channel between the non-TSF application and another IT product that is logically distinct from other communication channels, provides assured identification of its end points, protects channel data from disclosure, and detects modification of the channel data. ####### FDP_UPC_EXT.1.2/BLUETOOTH The TSF shall permit the non-TSF applications to initiate communication via the trusted channel. ##### 5.1.3.11 MOD_VPNC_V2.5: FDP_VPN_EXT.1: Split Tunnel Prevention ####### FDP_VPN_EXT.1.1 The TSF shall ensure that all IP traffic (other than IP traffic required to establish the VPN connection) flow through the IPsec VPN client. #### 5.1.4 Identification and Authentication (FIA) ##### 5.1.4.1 FIA_AFL_EXT.1: Authentication Failure Handling ####### FIA_AFL_EXT.1.1 The TSF shall consider password and [ no other ] as critical authentication mechanisms. ####### FIA_AFL_EXT.1.2 The TSF shall detect when a configurable positive integer within [ 1-30 ] of [ non-unique ] unsuccessful authentication attempts occur related to last successful authentication for each authentication mechanism. ####### FIA_AFL_EXT.1.3 The TSF shall maintain the number of unsuccessful authentication attempts that have occurred upon power off. ####### FIA_AFL_EXT.1.4 When the defined number of unsuccessful authentication attempts has exceeded the maximum allowed for a given authentication mechanism, all future authentication attempts will be limited to other available authentication mechanisms, unless the given mechanism is designated as a critical authentication mechanism. 33 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ####### FIA_AFL_EXT.1.5 When the defined number of unsuccessful authentication attempts for the last available authentication mechanism or single critical authentication mechanism has been surpassed, the TSF shall perform a wipe of all protected data. ####### FIA_AFL_EXT.1.6 The TSF shall increment the number of unsuccessful authentication attempts prior to notifying the user that the authentication was unsuccessful. ##### 5.1.4.2 MOD_BT_V1.0: FIA_BLT_EXT.1: Bluetooth User Authorization ####### FIA_BLT_EXT.1.1 The TSF shall require explicit user authorization before pairing with a remote Bluetooth device. ##### 5.1.4.3 MOD_BT_V1.0: FIA_BLT_EXT.2: Bluetooth Mutual Authentication ####### FIA_BLT_EXT.2.1 The TSF shall require Bluetooth mutual authentication between devices prior to any data transfer over the Bluetooth link. ##### 5.1.4.4 MOD_BT_V1.0: FIA_BLT_EXT.3: Rejection of Duplicate Bluetooth Connections ####### FIA_BLT_EXT.3.1 The TSF shall discard pairing and session initialization attempts from a Bluetooth device address (BD_ADDR) to which an active session already exists. ##### 5.1.4.5 MOD_BT_V1.0: FIA_BLT_EXT.4: Secure Simple Pairing ####### FIA_BLT_EXT.4.1 The TOE shall support Bluetooth Secure Simple Pairing, both in the host and the controller. ####### FIA_BLT_EXT.4.2 The TOE shall support Secure Simple Pairing during the pairing process. ##### 5.1.4.6 MOD_BT_V1.0: FIA_BLT_EXT.6: Trusted Bluetooth Device User Authorization ####### FIA_BLT_EXT.6.1 The TSF shall require explicit user authorization before granting trusted remote devices access to services associated with the following Bluetooth profiles: [ OPP, MAP ] ##### 5.1.4.7 MOD_BT_V1.0: FIA_BLT_EXT.7: Untrusted Bluetooth Device User Authorization ####### FIA_BLT_EXT.7.1 The TSF shall require explicit user authorization before granting untrusted remote devices access to services associated with the following Bluetooth profiles: [ OPP ]. ##### 5.1.4.8 MOD_CPP_BIO_V1.1: FIA_MBE_EXT.1: Biometric enrolment ####### FIA_MBE_EXT.1.1 The TSF shall provide a mechanism to enrol an authenticated user to the biometric system. Version: 0.3 Date: 10/22/2026 34 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 ##### 5.1.4.9 MOD_CPP_BIO_V1.1: FIA_MBE_EXT.2 :Quality of biometric templates for biometric enrolment ####### FIA_MBE_EXT.2.1 The TSF shall only use biometric samples of sufficient quality for enrolment. Sufficiency of sample data shall be determined by measuring sample with [developer defined quality assessment method]. ##### 5.1.4.10 MOD_CPP_BIO_V1.1: FIA_MBV_EXT.1:BMFPS Biometric verification 5 ####### FIA_MBV_EXT.1.1/BMFPS The TSF shall provide a biometric verification mechanism using [fingerprint]. ####### FIA_MBV_EXT.1.2/BMFPS The TSF shall provide a biometric verification mechanism with the [FAR] not exceeding [1:50,000] for the upper bound of [95%] confidence interval and, [FRR] not exceeding [3%] for the upper bound of [95%] confidence interval. ##### 5.1.4.11 MOD_CPP_BIO_V1.1: FIA_MBV_EXT.1: UDFPS Biometric verification 6 ####### FIA_MBV_EXT.1.1/UDFPS The TSF shall provide a biometric verification mechanism using [fingerprint]. ####### FIA_MBV_EXT.1.2/UDFPS The TSF shall provide a biometric verification mechanism with the [FAR] not exceeding [1:50,000] for the upper bound of [95%] confidence interval and, [FRR] not exceeding [3%] for the upper bound of [95%] confidence interval. ##### 5.1.4.12 MOD_CPP_BIO_V1.1: FIA_MBV_EXT.2 Quality of biometric samples for biometric verification ####### FIA_MBV_EXT.2.1 The TSF shall only use biometric samples of sufficient quality for verification. Sufficiency of sample data shall be determined by measuring sample with [developer defined quality assessment method]. ##### 5.1.4.13 MOD_WLANC_V1.0: FIA_PAE_EXT.1: Port Access Entity Authentication ####### FIA_PAE_EXT.1.1 The TSF shall conform to IEEE Standard 802.1X for a Port Access Entity (PAE) in the 'Supplicant' role. ##### 5.1.4.14 FIA_PMG_EXT.1: Password Management ####### FIA_PMG_EXT.1.1 The TSF shall support the following for the Password Authentication Factor: 1. Passwords shall be able to be composed of any combination of [ upper and lower case letters ] , numbers, and special characters: [! @ # $ % ^ & * ( ) + = _ / - ' " : ; , ? ` ~ \ | < > { } [ ] ] ]; 2. Password length up to [ 16 ] characters shall be supported. 5 This applies to the Ultrasonic and optical sensors 6 This applies to Capacitive sensors. 35 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ##### 5.1.4.15 FIA_TRT_EXT.1: Authentication Throttling ####### FIA_TRT_EXT.1.1 The TSF shall limit automated user authentication attempts by [ enforcing a delay between incorrect authentication attempts ] for all authentication mechanisms selected in FIA_UAU.5.1. The minimum delay shall be such that no more than 10 attempts can be attempted per 500 milliseconds. ##### 5.1.4.16 FIA_UAU.5: Multiple Authentication Mechanisms ####### FIA_UAU.5.1 ####### FIA_UAU.5.2 Version: 0.3 Date: 10/22/2026 The TSF shall provide password and [ fingerprint, hybrid ] to support user authentication. The TSF shall authenticate any user's claimed identity according to the [ following rules: - Passwords - o Can be used at any time - Biometric - o Can only be used - When there is an enrolled biometric, - When the user enables the allow biometrics for unlock feature, - The non-critical biometric failed limit has not been reached, and - At device lock screen (not at the first lock screen after reboot/power-up) - Hybrid - o For work environments unlock and hybrid authentication factor configured by the user ]. ##### 5.1.4.17 FIA_UAU.6/CREDENTIAL: Re-authenticating (Credential Change) ####### FIA_UAU.6.1/CREDENTIAL The TSF shall re-authenticate the user via the Password Authentication Factor under the conditions attempted change to any supported authentication mechanisms. ##### 5.1.4.18 FIA_UAU.6/LOCKED: Re-authenticating (TSF Lock) ####### FIA_UAU.6.1/LOCKED The TSF shall re-authenticate the user via an authentication factor defined in FIA_UAU.5.1 under the conditions TSF-initiated lock, user-initiated lock, [ no other conditions ]. ##### 5.1.4.19 FIA_UAU.7: Protected Authentication Feedback ####### FIA_UAU.7.1 The TSF shall provide only obscured feedback to the device's display to the user while the authentication is in progress. ##### 5.1.4.20 FIA_UAU_EXT.1: Authentication for Cryptographic Operation ####### FIA_UAU_EXT.1.1 The TSF shall require the user to present the Password Authentication Factor prior to decryption of protected data and encrypted DEKs, KEKs and [ long-term trusted channel key material, all software-based key storage ] at startup. 36 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ##### 5.1.4.21 FIA_UAU_EXT.2: Timing of Authentication ####### FIA_UAU_EXT.2.1 The TSF shall allow [ [ - enter password or supply biometric authentication factor to unlock - make emergency calls - receive calls - take pictures and screen shots (automatically named and stored internally by the TOE) - see notifications - configure sound/vibrate/mute - set the volume (up and down) for various sound categories - see the configured banner, access Notification Panel functions (including toggles Always on Display - Flashlight - Do not disturb toggle - Auto rotate - Sound (on, mute, vibrate) - Access user configured Edge applications (Edge applications not available on Tab S6) ] ] on behalf of the user to be performed before the user is authenticated. ####### FIA_UAU_EXT.2.2 The TSF shall require each user to be successfully authenticated before allowing any other TSF-mediated actions on behalf of that user. ##### 5.1.4.22 FIA_UAU_EXT.4: Secondary User Authentication ####### FIA_UAU_EXT.4.1 The TSF shall provide a secondary authentication mechanism for accessing Enterprise applications and resources. The secondary authentication mechanism shall control access to the Enterprise application and shared resources and shall be incorporated into the encryption of protected and sensitive data belonging to Enterprise applications and shared resources. ####### FIA_UAU_EXT.4.2 The TSF shall require the user to present the secondary authentication factor prior to decryption of Enterprise application data and Enterprise shared resource data. ##### 5.1.4.23 FIA_X509_EXT.1: Validation of Certificates ####### FIA_X509_EXT.1.1 The TSF shall validate certificates in accordance with the following rules: - RFC 5280 certificate validation and certificate path validation - The certificate path must terminate with a certificate in the Trust Anchor Database - The TSF shall validate a certificate path by ensuring the presence of the basicConstraints extension, that the CA flag is set to TRUE for all CA certificates, and that any path constraints are met. - The TSF shall validate that any CA certificate includes caSigning purpose in the key usage field Version: 0.3 Date: 10/22/2026 37 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ####### FIA_X509_EXT.1.2 The TSF shall only treat a certificate as a CA certificate if the basicConstraints extension is present and the CA flag is set to TRUE. ##### 5.1.4.24 MOD_WLANC_V1.0: FIA_X509_EXT.1/WLAN: X.509 Certificate Validation ####### FIA_X509_EXT.1.1/WLAN The TSF shall validate certificates for EAP-TLS in accordance with the following rules: - RFC 5280 certificate validation and certificate path validation - The certificate path must terminate with a certificate in the Trust Anchor Database - The TSF shall validate a certificate path by ensuring the presence of the basicConstraints extension and that the CA flag is set to TRUE for all CA certificates - The TSF shall validate the extendedKeyUsage field according to the following rules: - o Server certificates presented for TLS shall have the Server Authentication purpose (id-kp 1 with OID 1.3.6.1.5.5.7.3.1) in the extendedKeyUsage field - o Client certificates presented for TLS shall have the Client Authentication purpose (id-kp 2 with OID 1.3.6.1.5.5.7.3.2) in the extendedKeyUsage field. ####### FIA_X509_EXT.1.2/WLAN The TSF shall only treat a certificate as a CA certificate if the basicConstraints extension is present and the CA flag is set to TRUE. ##### 5.1.4.25 FIA_X509_EXT.2: X.509 Certificate Authentication ####### FIA_X509_EXT.2.1 The TSF shall use X.509v3 certificates as defined by RFC 5280 to support authentication for mutually authenticated TLS as defined in the Package for Transport Layer Security, HTTPS, IPsec in accordance with the PP-Module for VPN Client , and [ no additional uses ]. 7 ####### FIA_X509_EXT.2.2 When the TSF cannot establish a connection to determine the revocation status of a certificate, the TSF shall [ not accept the certificate ]. 7 Modified as per MOD_VPNC_V2.5 Version: 0.3 Date: 10/22/2026 - The TSF shall validate the revocation status of the certificate using [ OCSP as specified in RFC 6960 (for TLS, HTTPS, EAP-TLS, IPsec), CRL as specified in RFC 8603 (for TLS, HTTPS) ]. - The TSF shall validate the extendedKeyUsage field according to the following rules: - o Certificates used for trusted updates and executable code integrity verification shall have the Code Signing purpose (id-kp 3 with OID 1.3.6.1.5.5.7.3.3) in the extendedKeyUsage field - o Server certificates presented for TLS shall have the Server Authentication purpose (id-kp 1 with OID 1.3.6.1.5.5.7.3.1) in the extendedKeyUsage field - o Server certificates presented for EST shall have the CMC Registration Authority (RA) purpose (id-kp-cmcRA with OID 1.3.6.1.5.5.7.3.28) in the extendedKeyUsage field. [conditional] - o Client certificates presented for TLS shall have the Client Authentication purpose (id-kp 2 with OID 1.3.6.1.5.5.7.3.2) in the EKU field. - o OCSP certificates presented for OCSP responses shall have the OCSP Signing purpose (id-dp 9 with OID 1.3.6.1.5.5.7.3.9) in the EKU field. [conditional] 38 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 ##### 5.1.4.26 MOD_WLANC_V1.0: FIA_X509_EXT.2/WLAN: X.509 Certificate Authentication (EAP-TLS for WLAN) ####### FIA_X509_EXT.2.1/WLAN The TSF shall use X.509v3 certificates as defined by RFC 5280 to support authentication for EAP-TLS exchanges. ##### 5.1.4.27 FIA_X509_EXT.3: Request Validation of Certificates ####### FIA_X509_EXT.3.1 The TSF shall provide a certificate validation service to applications. ####### FIA_X509_EXT.3.2 The TSF shall respond to the requesting application with the success or failure of the validation. ##### 5.1.4.28 MOD_WLANC_V1.0: FIA_X509_EXT.6: Certificate Storage and Management ####### FIA_X509_EXT.6.1 The TSF shall [ store and protect ] to store and protect certificate(s) from unauthorized deletion and modification. ####### FIA_X509_EXT.6.2 The TSF shall [ provide the capability for authorized administrators to load X.509v3 certificates into the TOE ] for use by the TSF. #### 5.1.5 Security Management (FMT) ##### 5.1.5.1 FMT_MOF_EXT.1: Management of Security Functions Behavior ####### FMT_MOF_EXT.1.1 The TSF shall restrict the ability to perform the functions in column 3 of Table 8 - Security Management Functions to the user. ####### FMT_MOF_EXT.1.2 The TSF shall restrict the ability to perform the functions in column 5 of Table 8 - Security Management Functions to the administrator when the device is enrolled and according to the administrator-configured policy. ##### 5.1.5.2 FMT_SMF.1: Specification of Management Functions ####### FMT_SMF.1.1 The TSF shall be capable of performing the functions in column 2 of Table 8 - Security Management Functions. 39 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 | Management Function Mandatory = M Implemented = I | Implemented | User Only | Admin | Admin Only | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------|---------|--------------| | 1. configure password policy: a. minimum password length b. minimum password complexity c. maximum password lifetime The administrator can configure the required password characteristics (minimum length, complexity, and lifetime) using the MDM APIs. There are distinct settings for the passwords used to unlock the personal and work profiles. Length: an integer value of characters (0 = no minimum) Complexity: Unspecified, Something, Numeric, Alphabetic, Alphanumeric, Complex. | M | | M | M | | maximum) | | | M | M | | Lifetime: an integer value of days (0 = no 2. configure session locking policy: a. screen-lock enabled/disabled b. screen lock timeout | | | M | M | | c. number of authentication failures The administrator can configure the session locking policy using the MDM APIs. There are distinct settings for personal and work profile inactivity. The user can also adjust each of the session locking policies for the personal and work profile; however, if set by the administrator, the user can only set a more restrictive policy | M | | M | M | | (e.g., setting the device to allow fewer authentication failures than configured by the administrator). Screen lock timeout: an integer number of minutes before the TOE locks (0 = no lock timeout) Authentication failures: an integer number (0 = no limit) 3. enable/disable the VPN protection: a. across device | | | | | | [ b. on a per-app basis, c. on a per-group of applications processes basis ] The user can configure and then enable the TOE's VPN to protect traffic across the entire device. The administrator (through an MDM Agent that utilizes the MDM APIs) can restrict the TOE's ability to connect to a VPN. The administrator can configure per-app and per-work profile VPN connections with the | M | | I | I | | work profile MDM APIs. 4. enable/disable [ NFC 8 , Bluetooth, Wi-Fi, and cellular radios ] The administrator can disable the radios using the TOE's MDM APIs . Once disabled, a user cannot enable the radio. The administrator cannot fully disable/restrict cellular voice capabilities. The TOE's radios operate at frequencies of 2.4 GHz (NFC/Bluetooth), 2.4/5 GHz (Wi-Fi), and 850 MHz (4G/LTE). | M | | I | I | 40 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 | Management Function | Mandatory = M Implemented = I | Implemented | User Only Admin | Admin Only | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|---------------|-------------------|--------------| | 5. enable/disable [ camera, microphone ]: a. across device [ d. no other method ] An administrator may configure the TOE (through an MDM agent utilizing to turn off the camera and or microphones. If the administrator has | the MDM APIs) disabled either the M | | I | I | | camera or the microphones, then the user cannot use those capture The administrator can also disable the use of the camera or microphone profile without affecting access to those devices when outside the work profile. 6. transition to the locked state Both users and administrators (using the MDM APIs) can transition the TOE into a locked state. | devices. inside a work M | | M | - | | 7. TSF wipe of protected data Both users and administrators (using the MDM APIs) can force the TOE to perform wipe (factory reset) of data. | a full M | | M | | | 8. configure application installation policy by: [ a. restricting the sources of applications b. specifying a set of allowed applications based on [application name, developer signature] (an application whitelist) c. denying installation of applications ] The administrator using the TOE's MDM APIs can configure the TOE so that applications cannot be installed and can also block the use of the Google Play Store. There are distinct | M | | M | M | | settings for disabling the installation of applications for the personal and 9. import keys/secrets into the secure key storage Both users and administrators (using the MDM APIs) can import secret keys into the secure key storage. | work profile. M | | I | | | 10. destroy imported keys/secrets and [ no other keys/secrets ] in the secure key storage Both users and administrators (using the MDM APIs) can destroy secret keys in the secure key storage. | M | | I | | | 11. import X.509v3 certificates into the Trust Anchor Database Both users and administrators (using the MDM APIs) can import X.509v3 certificates into the Trust Anchor Database. | M | | M | | | 12. remove imported X.509v3 certificates and [ default X.509v3 certificates ] in the Trust Anchor Database Both users and administrators (using the MDM APIs) can remove imported X.509v3 certificates from the Trust Anchor Database as well as disable any of the TOE's default Root CA certificates (in the latter case, the CA certificate still resides in the TOE's read -only system partition; however, the TOE will treat that Root CA certificate and any certificate chaining to it as untrusted). | M | | I | | 41 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 | Management Function Mandatory = M Implemented = | I Implemented | User Only | Admin | Admin Only | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|---------|--------------| | 13. enroll the TOE in management TOE users can enroll the TOE in management according to the instructions specific to a given MDM. Presumably any enrollment would involve at least some user functions (e.g., install an MDM agent application) on the TOE prior to enrollment. | M | I | | | | 14. remove applications Both users and administrators (using the MDM APIs) can uninstall user and administrator installed applications in the personal profile and applications inside a work profile. 15. update system software | M | | M | | | Users can check for updates and cause the device to update if an update is available. An administrator can use MDM APIs to query the version of the TOE and query the installed applications and an MDM agent on the TOE could issue pop-ups, initiate updates, block communication, etc. until any necessary updates are completed. Note that the system software covers the entire mobile device (including all work profile software). | M | | M | | | 16. install applications Both users and administrators (using the MDM APIs) can install applications in the personal profile and applications inside a work profile. Only administrators (using the MDM APIs) can specify to install applications in a Knox Separated Apps folder. | M | | M | | | 17. remove Enterprise applications Both users and administrators (using the MDM APIs) can uninstall user and administrator installed applications in the personal profile and applications inside a work profile. Applications installed within the work profile are marked as Enterprise (work) applications | M | | M | | | 18. enable/disable display notification in the locked state of: [ f. all notifications ] TOE users can configure the TOE to allow or disallow notifications while in a locked state. | M | | | | | 19. enable data-at rest protection The TOE always encrypts user data storage. | M | | | | | 20. enable removable media's data -at-rest protection The device does not support internally installed removable media.. | M | | | | | 21. enable/disable location services: a. across device [ d. no other method ] The administrator (using the MDM APIs) can disable location services. Unless disabled by the administrator, TOE users can enable and disable location services. | M | | I | I | | 22. enable/disable the use of [ Fingerprint Authentication Factor, Hybrid Authentication Factor ] The TOE supports disabling Biometric authentication for the both the TOE's normal device lock screen and for the TOE's work profile lock screen. The TOE's normal device lock screen supports biometrics, which the administrator can disable. The TOE's work profile supports hybrid authentication (combination of password and biometrics), which the administrator can also disable. | M | | I | I | 42 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 | Management Function Mandatory = M Implemented = | I Implemented | User Only | Admin | Admin Only | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|---------|--------------| | 23. configure whether to allow/disallow establishment of [ mutually authenticated TLS trusted channel ] if the peer/server certificate is deemed invalid. | I | | | | | 24. enable/disable all data signaling over [assignment: list of externally accessible hardware ports] 25. enable/disable [assignment: list of protocols where the device acts as a server] | | | | | | 26. enable/disable developer modes The administrator (using the MDM APIs) can disable Developer Mode. | I | | I | I | | Unless disabled by the administrator, TOE users can enable and disable Developer Mode. 27. enable/disable bypass of local user authentication | I | | I | I | | 28. wipe Enterprise data | I | | | | | The TOE work profile provides the ability to remove only Enterprise data versus user data. 29. approve [ selection: import, removal ] by applications of X.509v3 certificates in the | | | | | | Trust Anchor Database 30. configure whether to allow/disallow establishment of a trusted channel if the TSF cannot establish a connection to determine the validity of a certificate 31. enable/disable the cellular protocols used to connect to cellular network base stations | | | | | | 32. read audit logs kept by the TSF The administrator (using the MDM APIs) can view the TOE's audit records. | I | | I | | | 33. configure [ selection : certificate, public-key ] used to validate digital signature on applications | | | | | | 34. approve exceptions for shared use of keys/secrets by multiple applications 35. approve exceptions for destruction of keys/secrets by applications that did not import | | | | | | the key/secret 36. configure the unlock banner The administrator (using the MDM APIs) can define a banner of a maximum of 256 characters to be displayed while the TOE is locked. There is no method for the user to | I | | I | I | | change the banner. 37. configure the auditable items | | | | | | 38. retrieve TSF-software integrity verification values 39. enable/disable [ a. USB mass storage mode | I | | I | I | | ] The administrator (using the MDM APIs) can disable USB mass storage mode. | | | | | | 40. enable/disable backup of [ selection: all applications, selected applications, selected groups of applications, configuration data ] to [ selection: locally connected system, remote system ] | | | | | 43 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 Table 8 - Security Management Functions | Management Function 41. enable/disable | Mandatory = M Implemented = I Implemented | User Only | Admin | Admin Only | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|-------------|---------|--------------| | [ a. Hotspot functionality authenticated by [pre-shared key], b. USB tethering authenticated by [passcode] ] The administrator (using the MDM APIs) can disable the wireless hotspot tethering. If enabled by the administrator (and supported by the device 9 ), • A Wi-Fi hotspot with a pre-shared key • A Bluetooth hotspot with another device that has been Bluetooth pairing (establishing a pre-shared key) • A USB tethering connection when the user has first | and USB | | | | | TOE users can configure: successfully completed a authenticated to the device (the tethering connection will be maintained when the device locks, but initial setup requires the user to actively approve the connection via authentication to | I | | I | I | | the device) 42. approve exceptions for sharing data between [ groups of applications ] The TOE work profile and Knox Separated Apps folder provide separation between groups of application processes along with the ability to control the ability to share data between these groups | I | | | I | | 43. place applications into application process groups based on [ creating a Knox Separated Apps folder ] | I | | I | I | | 44. unenroll the TOE from management | I | | I | I | | 45. Enable/disable the Always On VPN protection 10 a. across device [ b. on a per-app basis, c. on a per-group of applications processes basis ] | M | | I | I | | The user can be required to use an Always On VPN | | | | | | 46. revoke Biometric template 47. additional management functions | | | | | | [ • enable/disable USB host storage • disable CC Mode • enable/disable manual Date/Time changes • enable/disable applications (including pre-installed) ] | I I I I | | I I I I | I I I I | | The user can always disable CC Mode by entirely wiping the device (factory reset), as this will return the phone to its factory state (in which CC Mode has not been enabled) | | | | | 9 Not all devices support all (or any) options for tethering. Many carriers require additional subscriptions/payments to enable tethering features on the device. The Tab S7 devices and the Tab S6 do not support tethering. 10 Modified as per MOD_VPNC_V2.5 44 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 ##### 5.1.5.3 MOD_BT_V1.0: FMT_SMF_EXT.1/BT: Specification of Management Functions (Bluetooth) ####### FMT_SMF_EXT.1.1/BT The TSF shall be capable of performing the following Bluetooth management functions: Table 9 - Bluetooth Security Management Functions | Management Function Mandatory = M Implemented = I | Management Function Mandatory = M Implemented = I | Implemented | User Only | Admin | Admin Only | |---------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|---------------|-------------|---------|--------------| | BT1. • | Configure the Bluetooth trusted channel. Disable/enable the Discoverable (for BR/EDR) and Advertising (for LE) modes; | M | | I | I | | BT2. | Change the Bluetooth device name (separately for BR/EDR and LE); | | | | | | BT3. | Provide separate controls for turning the BR/EDR and LE radios on and off; | | | | | | BT4. | Allow/disallow the following additional wireless technologies to be used with Bluetooth: [ NFC ]; | I | | I | I | | NFC can be disabled and so unable to be used for Bluetooth pairing. | NFC can be disabled and so unable to be used for Bluetooth pairing. | | | | | | BT5. | Configure allowable methods of Out of Band pairing (for BR/EDR and LE); | | | | | | BT6. | Disable/enable the Discoverable (for BR/EDR) and Advertising (for LE) modes separately; | | | | | | BT7. | Disable/enable the Connectable mode (for BR/EDR and LE); | | | | | | BT8. | Disable/enable the Bluetooth [ assignment: list of Bluetooth service and/or profiles available on the OS (for BR/EDR and LE)]; | | | | | | BT9. | Specify minimum level of security for each pairing (for BR/EDR and LE); | | | | | ##### 5.1.5.4 MOD_WLANC_V1.0: FMT_SMF.1/WLAN: Specification of Management Functions (WLAN Client) ####### FMT_SMF.1.1/WLAN The TSF shall be capable of performing the following management functions: | Management Function Mandatory = Implemented | Management Function Mandatory = Implemented | M = I Implemented | User Only | Admin | Admin Only | |-----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-------------|---------|--------------| | WL1. a. b. | configure security policy for each wireless network: [ specify the CA(s) from which the TSF will accept WLAN authentication server certificate(s) ] security type | M | | M | I | | c. d. WL2. | authentication protocol client credentials to be used for authentication; specify wireless networks (SSIDs) to which the TSF may connect; | M | | M | I | | WL3. | enable/disable disable wireless network bridging capability (for example, bridging a connection between the WLAN and cellular radios to function as a hotspot) authenticated by [ pre-shared key ] | M | | M | | | WL4. | enable/disable certificate revocation list checking; | | | | | | WL5. | disable ad hoc wireless client-to-client connection capability; | | | | | | WL6. | disable roaming capability | | | | | | WL7. | enable/disable IEEE 802.1X pre-authentication | | | | | | WL8. | loading X.509 certificates into the TOE | I | | | | SAMSUNG 45 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 Table 10 - WLAN Security Management Functions | Management Function | Mandatory Implemented | = M = I Implemented | User Only | Admin | Admin Only | |-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------|---------|--------------| | WL9. | revoke X.509 certificates loaded into the TOE | I | | | | | WL10. a. b. | enable/disable and configure PMK caching set the amount of time (in minutes) for which PMK entries are cached set the maximum number of PMK entries that can be cached | | | | | ##### 5.1.5.5 MOD_VPNC_V2.5: FMT_SMF.1/VPN: Specification of Management Functions - VPN ####### FMT_SMF.1.1/VPN The TSF shall be capable of performing the following management functions : Table 11 - VPN Security Management Functions | Management Function | Mandatory Implemented | = M = I Implemented | User Only | Admin | Admin Only | |-----------------------|--------------------------------------------------------------|-----------------------|-------------|---------|--------------| | VPN1. | Specify VPN gateways to use for connections | I | | | | | VPN2. | Specify IPsec VPN Clients to use for connections | | | | | | VPN3. | Specify IPsec-capable network devices to use for connections | | | | | | VPN4. | Specify client credentials to be used for connections | I | | | | | VPN5. | Configure the reference identifier of the peer | I | | | | | VPN6. | [any additional VPN management functions] | | | | | ##### 5.1.5.6 FMT_SMF_EXT.2: Specification of Remediation Actions ####### FMT_SMF_EXT.2.1 The TSF shall offer [ - wipe of protected data - wipe of sensitive data - remove Enterprise applications - remove all device-stored Enterprise resource data - remove Enterprise secondary authentication data ] upon unenrollment and [ no other triggers ]. ##### 5.1.5.7 FMT_SMF_EXT.3: Current Administrator ####### FMT_SMF_EXT.3.1 The TSF shall provide a mechanism that allows users to view a list of currently authorized administrators and the management functions that each administrator is authorized to perform. #### 5.1.6 Protection of the TSF (FPT) ##### 5.1.6.1 FPT_AEX_EXT.1: Application Address Space Layout Randomization ####### FPT_AEX_EXT.1.1 46 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 The TSF shall provide address space layout randomization ASLR to applications. ####### FPT_AEX_EXT.1.2 The base address of any user-space memory mapping will consist of at least 8 unpredictable bits. ##### 5.1.6.2 FPT_AEX_EXT.2: Memory Page Permissions ####### FPT_AEX_EXT.2.1 The TSF shall be able to enforce read, write, and execute permissions on every page of physical memory. ##### 5.1.6.3 FPT_AEX_EXT.3: Stack Overflow Protection ####### FPT_AEX_EXT.3.1 TSF processes that execute in a non-privileged execution domain on the application processor shall implement stack-based buffer overflow protection. ##### 5.1.6.4 FPT_AEX_EXT.4: Domain Isolation ####### FPT_AEX_EXT.4.1 The TSF shall protect itself from modification by untrusted subjects. ####### FPT_AEX_EXT.4.2 The TSF shall enforce isolation of address space between applications. ##### 5.1.6.5 FPT_AEX_EXT.5: Kernel Address Space Layout Randomization ####### FPT_AEX_EXT.5.1 The TSF shall provide address space layout randomization (ASLR) to the kernel. ####### FPT_AEX_EXT.5.2 The base address of any kernel-space memory mapping will consist of [ 6 ] unpredictable bits. ##### 5.1.6.6 FPT_AEX_EXT.6: Write or Execute Memory Page Permissions ####### FPT_AEX_EXT.6.1 The TSF shall prevent write and execute permissions from being simultaneously granted to any page of physical memory [ excluding memory used for JIT (just-in-time) compilation and memory allocated with mmap ]. ##### 5.1.6.7 FPT_BBD_EXT.1: Application Processor Mediation ####### FPT_BBD_EXT.1.1 The TSF shall prevent code executing on any baseband processor (BP) from accessing application processor (AP) resources except when mediated by the AP. ##### 5.1.6.8 MOD_CPP_BIO_V1.1:FPT_BDP_EXT.1: Biometric data processing ####### FPT_BDP_EXT.1.1 Processing of plaintext biometric data shall be inside the TEE in runtime. ####### FPT_BDP_EXT.1.2 Transmission of plaintext biometric data between the capture sensor and the TEE shall be isolated from the main computer operating system on the TSF in runtime. 47 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ##### 5.1.6.9 FPT_JTA_EXT.1: JTAG Disablement ####### FPT_JTA_EXT.1.1 The TSF shall [ control access by a signing key ] to JTAG. ##### 5.1.6.10 FPT_KST_EXT.1 & MOD_CPP_BIO_V1.1/FPT_KST_EXT.1: Key Storage ####### FPT_KST_EXT.1.1 The TSF shall not store any plaintext key material or biometric data in readable non-volatile memory. ##### 5.1.6.11 FPT_KST_EXT.2 & MOD_CPP_BIO_V1.1/FPT_KST_EXT.2: No Key Transmission ####### FPT_KST_EXT.2.1 The TSF shall not transmit any plaintext key material or biometric data outside the security boundary of the TOE. ##### 5.1.6.12 FPT_KST_EXT.3: No Plaintext Key Export ####### FPT_KST_EXT.3.1 The TSF shall ensure it is not possible for the TOE user(s) to export plaintext keys. ##### 5.1.6.13 FPT_NOT_EXT.1: Self-Test Notification ####### FPT_NOT_EXT.1.1 The TSF shall transition to non-operational mode and [ no other actions ] when the following types of failures occur: - failures of the self-test(s) - TSF software integrity verification failures - [ no other failures ]. ##### 5.1.6.14 MOD_CPP_BIO_V1.1/FPT_PBT_EXT.1: Protection of biometric template ####### FPT_PBT_EXT.1.1 The TSF shall protect the biometric template [using a password as an additional factor]. ##### 5.1.6.15 FPT_STM.1: Reliable time stamps ####### FPT_STM.1.1 The TSF shall be able to provide reliable time stamps for its own use. ##### 5.1.6.16 FPT_TST_EXT.1: TSF Cryptographic Functionality Testing ####### FPT_TST_EXT.1.1 The TSF shall run a suite of self-tests during initial start-up (on power on) to demonstrate the correct operation of all cryptographic functionality. ##### 5.1.6.17 MOD_WLANC_V1.0: FPT_TST_EXT.3/WLAN: TSF Cryptographic Functionality Testing (WLAN Client) ####### FPT_TST_EXT.3.1/WLAN The [ TOE platform ] shall run a suite of self-tests during initial start-up (on power on) to demonstrate the correct operation of the TSF. ####### FPT_TST_EXT.3.2/WLAN Version: 0.3 Date: 10/22/2026 48 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 The [ TOE platform ] shall provide the capability to verify the integrity of stored TSF executable code when it is loaded for execution through the use of the TSF-provided cryptographic services. ##### 5.1.6.18 MOD_VPNC_V2.5: FPT_TST_EXT.1/VPN: TSF Self-Test (VPN Client) ####### FPT_TST_EXT.1.1/VPN The [ TOE Platform ] shall run a suite of self -tests during initial start-up (on power on) to demonstrate the correct operation of the TSF. ####### FPT_TST_EXT.1.2/VPN The [ TOE ] shall provide the capability to verify the integrity of stored TSF executable code when it is loaded for execution through the use of the [ cryptographic signature and hash for integrity ]. ##### 5.1.6.19 FPT_TST_EXT.2/PREKERNEL: TSF Integrity Checking (Pre-Kernel) ####### FPT_TST_EXT.2.1/PREKERNEL The TSF shall verify the integrity of the bootchain up through the Application Processor OS kernel stored in mutable media prior to its execution through the use of [ an immutable hardware hash of an asymmetric key ]. ##### 5.1.6.20 FPT_TST_EXT.2/POSTKERNEL: TSF Integrity Checking (Post-Kernel) ####### FPT_TST_EXT.2.1/POSTKERNEL The TSF shall verify the integrity of [[ the /system and /vendor partitions ]], stored in mutable media prior to its execution through the use of [ hardware-protected hash ]. ##### 5.1.6.21 FPT_TUD_EXT.1: Trusted Update: TSF Version Query ####### FPT_TUD_EXT.1.1 The TSF shall provide authorized users the ability to query the current version of the TOE firmware/software. ####### FPT_TUD_EXT.1.2 The TSF shall provide authorized users the ability to query the current version of the hardware model of the device. ####### FPT_TUD_EXT.1.3 The TSF shall provide authorized users the ability to query the current version of installed mobile applications. ##### 5.1.6.22 FPT_TUD_EXT.2: TSF Update Verification ####### FPT_TUD_EXT.2.1 The TSF shall verify software updates to the Application Processor system software and [ [communications processor software, bootloader software, carrier specific configuration] ] using a digital signature verified by the manufacturer trusted key prior to installing those updates. ####### FPT_TUD_EXT.2.2 The TSF shall [ update only by verified software ] the TSF boot integrity [ key, hash ]. ####### FPT_TUD_EXT.2.3 The TSF shall verify that the digital signature verification key used for TSF updates [ matches an immutable hardware public key ]. 49 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ##### 5.1.6.23 FPT_TUD_EXT.3: Application Signing ####### FPT_TUD_EXT.3.1 The TSF shall verify mobile application software using a digital signature mechanism prior to installation. ##### 5.1.6.24 FPT_TUD_EXT.6: Trusted Update Verification ####### FPT_TUD_EXT.6.1 The TSF shall verify that software updates to the TSF are a current or later version than the current version of the TSF. #### 5.1.7 TOE Access (FTA) ##### 5.1.7.1 FTA_SSL_EXT.1: TSF- and User-initiated Locked State ####### FTA_SSL_EXT.1.1 The TSF shall transition to a locked state after a time interval of inactivity. ####### FTA_SSL_EXT.1.2 The TSF shall transition to a locked state after initiation by either the user or the administrator. ####### FTA_SSL_EXT.1.3 The TSF shall, upon transitioning to the locked state, perform the following operations: - a. clearing or overwriting display devices, obscuring the previous contents; - b. [ no other actions ]. ##### 5.1.7.2 FTA_TAB.1: Default TOE Access Banners ####### FTA_TAB.1.1 Before establishing a user session, the TSF shall display an advisory warning message regarding unauthorized use of the TOE. ##### 5.1.7.3 MOD_WLANC_V1.0: FTA_WSE_EXT.1: Wireless Network Access ####### FTA_WSE_EXT.1.1 The TSF shall be able to attempt connections only to wireless networks specified as acceptable networks as configured by the administrator in FMT_SMF.1.1/WLAN. #### 5.1.8 Trusted Path/Channels (FTP) ##### 5.1.8.1 MOD_BT_V1.0: FTP_BLT_EXT.1: Bluetooth Encryption ####### FTP_BLT_EXT.1.1 The TSF shall enforce the use of encryption when transmitting data over the Bluetooth trusted channel for BR/EDR and [ LE ]. ####### FTP_BLT_EXT.1.2 The TSF shall use key pairs per FCS_CKM_EXT.8 for Bluetooth encryption. ##### 5.1.8.2 MOD_BT_V1.0: FTP_BLT_EXT.2: Persistence of Bluetooth Encryption ####### FTP_BLT_EXT.2.1 The TSF shall [ terminate the connection ] if the remote device stops encryption while connected to the TOE. Version: 0.3 Date: 10/22/2026 50 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 ##### 5.1.8.3 MOD_BT_V1.0: FTP_BLT_EXT.3/BR: Bluetooth Encryption Parameters (BR/EDR) ####### FTP_BLT_EXT.3.1/BR The TSF shall set the minimum encryption key size to [ 128 bits ] for [ BR/EDR ] and not negotiate encryption key sizes smaller than the minimum size. ##### 5.1.8.4 MOD_BT_V1.0: FTP_BLT_EXT.3/LE: Bluetooth Encryption Parameters (LE) ####### FTP_BLT_EXT.3.1/LE The TSF shall set the minimum encryption key size to [ 128 bits ] for [ LE ] and not negotiate encryption key sizes smaller than the minimum size. ##### 5.1.8.5 FTP_ITC_EXT.1: Trusted Channel Communication ####### FTP_ITC_EXT.1.1 The TSF shall use - 802.11-2012 in accordance with the PP-Module for WLAN Clients, version 1.0, - 802.1X in accordance with the PP-Module for WLAN Clients, version 1.0, - EAP-TLS in accordance with the PP-Module for WLAN Clients, version 1.0, - mutually authenticated TLS as defined in the Package for Transport Layer Security, version 1.1 - IPsec in accordance with the PP-Module for VPN Client, and [ ####### · HTTPS ] protocols to provide a communication channel between itself and another trusted IT product that is logically distinct from other communication channels, provides assured identification of its end points, protects channel data from disclosure, and detects modification of the channel data. 11 ####### FTP_ITC_EXT.1.2 The TSF shall permit the TSF to initiate communication via the trusted channel. ####### FTP_ITC_EXT.1.3 The TSF shall initiate communication via the trusted channel for wireless access point connections, administrative communication, configured enterprise connections, and [ no other connections ]. ##### 5.1.8.6 MOD_WLANC_V1.0: FTP_ITC.1/WLAN: Trusted Channel Communication (Wireless LAN) ####### FTP_ITC.1.1/WLAN The TSF shall use 802.11-2012, 802.1X, and EAP-TLS to provide a trusted communication channel between itself and a wireless access point that is logically distinct from other communication channels and provides assured identification of its end points and protection of the channel data from modification or disclosure. ####### FTP_ITC.1.2/WLAN The TSF shall permit the TSF to initiate communication via the trusted channel. ####### FTP_ITC.1.3/WLAN The TSF shall initiate communication via the trusted channel for wireless access point connections. 11 Modified as per MOD_VPNC_V2.5 51 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 ### 5.2 TOE Security Assurance Requirements The SARs are as specified in Part 3 of the Common Criteria. Note that the SARs have effectively been refined with the assurance activities explicitly defined in association with both the SFRs and SARs. #### 5.2.1 Development (ADV) ##### 5.2.1.1 ADV_FSP.1: Basic Functional Specification | ADV_FSP.1.1d | The developer shall provide a functional specification. | |---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ADV_FSP.1.2d | The developer shall provide a tracing from the functional specification to the SFRs. | | ADV_FSP.1.1c | The functional specification shall describe the purpose and method of use for each SFR- enforcing and SFR-supporting TSFI. | | ADV_FSP.1.2c | The functional specification shall identify all parameters associated with each SFR-enforcing and SFR-supporting TSFI. | | ADV_FSP.1.3c | The functional specification shall provide rationale for the implicit categorization of interfaces as SFR-non-interfering. | | ADV_FSP.1.4c ADV_FSP.1.1e | The tracing shall demonstrate that the SFRs trace to TSFIs in the functional specification. The evaluator shall confirm that the information provided meets all requirements for content and presentation of evidence. | | ADV_FSP.1.2e | The evaluator shall determine that the functional specification is an accurate and complete instantiation of the SFRs. | #### 5.2.2 Guidance Documents (AGD) ##### 5.2.2.1 AGD_OPE.1: Operational User Guidance | | The developer shall provide operational user guidance. | |--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | AGD_OPE.1.1c | AGD_OPE.1.1c | | | The operational user guidance shall describe, for each user role, the user-accessible functions and privileges that should be controlled in a secure processing environment, including appropriate warnings. | | AGD_OPE.1.2c | AGD_OPE.1.2c | | | The operational user guidance shall describe, for each user role, how to use the available interfaces provided by the TOE in a secure manner. | | AGD_OPE.1.3c | AGD_OPE.1.3c | | | The operational user guidance shall describe, for each user role, the available functions and interfaces, in particular all security parameters under the control of the user, indicating secure values as appropriate. | | AGD_OPE.1.4c | AGD_OPE.1.4c | ####### SAMSUNG 52 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ####### AGD_OPE.1.5c ####### AGD_OPE.1.6c ####### AGD_OPE.1.7c ####### AGD_OPE.1.1e The evaluator shall confirm that the information provided meets all requirements for content and presentation of evidence. ##### 5.2.2.2 AGD_PRE.1: Preparative Procedures ####### AGD_PRE.1.1d ####### AGD_PRE.1.1c ####### AGD_PRE.1.2c ####### AGD_PRE.1.1e ####### AGD_PRE.1.2e The developer shall provide the TOE, including its preparative procedures. The preparative procedures shall describe all the steps necessary for secure acceptance of the delivered TOE in accordance with the developer's delivery procedures. The preparative procedures shall describe all the steps necessary for secure installation of the TOE and for the secure preparation of the operational environment in accordance with the security objectives for the operational environment as described in the ST. The evaluator shall confirm that the information provided meets all requirements for content and presentation of evidence. The evaluator shall apply the preparative procedures to confirm that the TOE can be prepared securely for operation. #### 5.2.3 Life-cycle Support (ALC) ##### 5.2.3.1 ALC_CMC.1: Labelling of the TOE ####### ALC_CMC.1.1d ####### ALC_CMC.1.1c ####### ALC_CMC.1.1e The developer shall provide the TOE and a reference for the TOE. The TOE shall be labelled with its unique reference. The evaluator shall confirm that the information provided meets all requirements for content and presentation of evidence. ##### 5.2.3.2 ALC_CMS.1: TOE CM Coverage ####### ALC_CMS.1.1d Version: 0.3 Date: 10/22/2026 The operational user guidance shall, for each user role, clearly present each type of security-relevant event relative to the user-accessible functions that need to be performed, including changing the security characteristics of entities under the control of the TSF. The operational user guidance shall identify all possible modes of operation of the TOE (including operation following failure or operational error), their consequences, and implications for maintaining secure operation. The operational user guidance shall, for each user role, describe the security measures to be followed in order to fulfill the security objectives for the operational environment as described in the ST. The operational user guidance shall be clear and reasonable. 53 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ####### ALC_CMS.1.1c ####### ALC_CMS.1.2c ####### ALC_CMS.1.1e The evaluator shall confirm that the information provided meets all requirements for content and presentation of evidence. ##### 5.2.3.3 ALC_TSU_EXT.1: Timely Security Updates ####### ALC_TSU_EXT.1.1d The developer shall provide a description in the TSS of how timely security updates are made to the TOE. ####### ALC_TSU_EXT.1.1c The description shall include the process for creating and deploying security updates for the TOE software. ####### ALC_TSU_EXT.1.2c The description shall express the time window as the length of time, in days, between public disclosure of a vulnerability and the public availability of security updates to the TOE. ####### ALC_TSU_EXT.1.3c The description shall include the mechanisms publicly available for reporting security issues pertaining to the TOE. ####### ALC_TSU_EXT.1.4c The description shall include where users can seek information about the availability of new updates including details (e.g. CVE identifiers) of the specific public vulnerabilities corrected by each update. ####### ALC_TSU_EXT.1.1e The evaluator shall confirm that the information provided meets all requirements for content and presentation of evidence. #### 5.2.4 Tests (ATE) ##### 5.2.4.1 ATE_IND.1: Independent Testing - sample ####### ATE_IND.1.1d ####### ATE_IND.1.1c ####### ATE_IND.1.1e ####### ATE_IND.1.2e The developer shall provide the TOE for testing. The TOE shall be suitable for testing. The evaluator shall confirm that the information provided meets all requirements for content and presentation of evidence. The evaluator shall test a subset of the TSF to confirm that the TSF operates as specified. The developer shall provide a configuration list for the TOE. The configuration list shall include the following: the TOE itself; and the evaluation evidence required by the SARs. The configuration list shall uniquely identify the configuration items. Version: 0.3 Date: 10/22/2026 54 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target #### 5.2.5 Vulnerability Assessment (AVA) ##### 5.2.5.1 AVA_VAN.1: Vulnerability Survey ####### AVA_VAN.1.1d ####### AVA_VAN.1.1c ####### AVA_VAN.1.1e ####### AVA_VAN.1.2e ####### AVA_VAN.1.3e The developer shall provide the TOE for testing. The TOE shall be suitable for testing. The evaluator shall confirm that the information provided meets all requirements for content and presentation of evidence. The evaluator shall perform a search of public domain sources to identify potential vulnerabilities in the TOE. The evaluator shall conduct penetration testing, based on the identified potential vulnerabilities, to determine that the TOE is resistant to attacks performed by an attacker possessing Basic attack potential. Version: 0.3 Date: 10/22/2026 55 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ## 6 TOE Summary Specification This chapter describes the security functions: - Security audit - Cryptographic support - User data protection - Identification and authentication - Security management - Protection of the TSF - TOE access - Trusted path/channels ## 6.1 Security Audit ####### FAU_GEN.1 TOE provides several distinct mechanisms for Security Audit logging - one introduced via KNOX APIs, and one introduced from mainline AOSP - Security Log (https://developer.android.com/reference/android/app/admin/SecurityLog). Some events might only be audited by one of these systems, so the client is encouraged to monitor both. Section 5.1 of the Administrator Guide describes the fields in the audit records. The following table enumerates the events that the TOE audits including the mechanisms logging it. Requirements marked with '(O)' are from the Additional Auditable Events table of the PP_MDF_V3.3. | Requirement | Audit Event | Content | Mechanism | |--------------------------------------------------------------------|----------------------------------------------|----------------------------------------------------------|-------------------| | FAU_GEN.1 Start-up and functions | shutdown of the audit | KNOX | | | All administrative actions | | KNOX/Security Log | FAU_GEN.1 | | Start-up and shutdown of the OS and kernel | | Security Log | FAU_GEN.1 | | Insertion or removal of removable media | | Knox | FAU_GEN.1 | | Failure of key generation activity authentication keys. | for | Security Log/K | FCS_CKM.1 | | FCS_CKM_EXT.1 None | | | | | FCS_CKM_EXT.5 None | | | | | FCS_STG_EXT.1 Import or destruction of key. | Identity of key. Role identity of requestor. | and | Security Log/Knox | | FCS_STG_EXT.3 Failure to verify integrity of | stored key. Identity of key | being verified. | Security Log | | FDP_DAR_EXT.1 [None] | | | | | FDP_DAR_EXT.2 None | | | | | FDP_STG_EXT.1 Addition or removal of certificate from Trust Anchor | Database. Subject | name of certificate. | Security Log | | FIA_X509_EXT.1 Failure to validate X.509v3 | certificate. | Reason for failure of validation. | KNOX | | FMT_SMF.1 (O) | Change of settings. | Role of user that changed setting. Value of new setting. | KNOX | | FPT_NOT_EXT.1 | None | | | Version: 0.3 Date: 10/22/2026 56 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ####### MOD_BT_V1.0: FAU_GEN.1/BT The following table enumerates the events that the TOE audits from Table 2: Auditable Events of the MOD_BT_V1.0 . Requirements marked with '(O)' are optional in the table. Table 13 - Bluetooth Audit Events | Requirement | Audit Event | Content | Mechanism | |---------------|-------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| | FIA_BLT_EXT.1 | Failed user authorization of Bluetooth device. Failed user authorization for local Bluetooth Service. | User authorization decision (e.g., user rejected connection, incorrect pin entry). Bluetooth address and name of device. Bluetooth profile. Identity of local service with [selection: profile name] | KNOX KNOX | | FIA_BLT_EXT.2 | Initiation of Bluetooth connection. | Bluetooth address and name of device. | KNOX | | FIA_BLT_EXT.2 | Failure of Bluetooth connection. | Reason for failure. | KNOX | ####### MOD_WLANC_V1.0: FAU_GEN.1/WLAN The following table enumerates the events that the TOE audits from Table 2: Auditable Events of the MOD_WLANC_V1.0. Table 14 - WLAN Client Audit Events | Requirement | Audit Event | Content | Mechanism | |---------------------|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|--------------| | FCS_TLSC_EXT.1/WLAN | Failure to establish an EAP-TLS session. | Reason for failure. | Security Log | | FCS_TLSC_EXT.1/WLAN | Establishment/termination of an EAP-TLS session. | Non-TOE endpoint of connection. | Security Log | | FIA_X509_EXT.1/WLAN | Failure to validate X.509v3 certificate | Reason for failure | KNOX | | FPT_TST_EXT.3/WLAN | Execution of this set of TSF self-tests. | None | KNOX | | FPT_TST_EXT.3/WLAN | [ none ]. | [ no additional information ]. | KNOX | | FTA_WSE_EXT.1 | All attempts to connect to access points. | For each access point record the [ Complete SSID and MAC ] of the MAC Address Success and failures (including reason for failure) | Security Log | | FTP_ITC.1/WLAN | All attempts to establish a trusted channel. | Identification of the non-TOE endpoint of the channel. | Security Log | ####### FAU_SAR.1 The TOE provides the ability for the administrator to export and read the audit log. ####### FAU_STG.1 The TOE stores audit records in a file within the file system accessible only to Linux processes with system permissions (effectively the TSF itself and MDM agents using the defined APIs). These restrictions prevent the unauthorized modification or deletion of the audit records stored in the audit files. Version: 0.3 Date: 10/22/2026 Table 12 - Audit Events | Requirement | Audit Event | Content | Mechanism | |--------------------------|--------------------------------------------------------------------|----------------------------------------------------------|--------------| | FPT_TST_EXT.1 | Initiation of self-test. Failure of self- test. | No additional Information | KNOX | | FPT_TST_EXT.2/ PREKERNEL | Start-up of TOE. [ none ] | No additional Information. [ no additional information ] | Security Log | | FPT_TUD_EXT.2 (O) | Success or failure of signature verification for software updates. | | KNOX | 57 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ####### FAU_STG.4 The TOE pre-allocates a file system area (between 10MB and 50MB in size, depending upon available storage on the device) by creating a /data/system/[admin_uid]_bubble/bubbleFile and directory (/data/system/[admin_uid]) in which to archive compressed audit logs. If the TOE lacks sufficient space (at least 10MB), then the TOE returns a failure code in response to the administrator's attempt to enable the AuditLog. Once enabled, the TOE writes audit events into nodes until they read a given size, and then compresses and archives the records. The TOE utilizes a circular buffer approach to handle when the accumulated, compressed audit events exceed the allocated file system size. When the limit is reached, the TOE removes the oldest audit logs, freeing space for new records. ## 6.2 Cryptographic Support ####### FCS_CKM.1 The TOE supports asymmetric key generation for all types in accordance with FIPS 186-5. The TOE generates RSA keys in its BoringSSL and SCrypto library and generates DH/ECDH/ECDSA (including P-256, P384 and P-521) keys in BoringSSL and ECDSA (including P-256, P384 and P-521) keys in SCrypto. The TOE supports generating keys with a security strength of 112-bits and larger, thus supports 2048-bit RSA and DH keys, and 256bit ECDH/ECDSA keys. The TOE's RSA and ECDSA implementations have the CAVP certificates described in the FCS_COP.1 section below. Table 15 - Asymmetric Key Generation per Module | Cryptographic Library | RSA Generation | DH (FFC) | ECDH (ECC) | EDCSA (ECC) | |-------------------------|------------------|------------|--------------|---------------| | BoringSSL (user space) | Yes | Yes | Yes | Yes | | Kernel Crypto (Kernel) | No | No | No | No | | SCrypto (TrustZone) | Yes | No | No | Yes | | Application Processor | No | No | No | No | ####### MOD_WLANC_V1.0: FCS_CKM.1/WPA The TOE adheres to IEEE 802.11-2012 and IEEE 802.11ac-2014 for key generation. The TOE's wpa_supplicant provides the PRF384 and PRF704 for WPA3/WPA2 derivation of 128-bit or 256-bit AES Temporal Key (using the HMAC implementation provided by BoringSSL) and employs its BoringSSL AES-256 DRBG when generating random values used in the EAP-TLS and 802.11 4-way handshake. The TOE supports the AES-128 CCMP encryption mode. ####### MOD_VPNC_V2.5: FCS_CKM.1/VPN The VPN uses the TOE cryptographic libraries to generate asymmetric keys (RSA or ECDSA) for authentication during the IKE key exchange. Note that ECDSA is only supported by IKEv2 connections. ####### FCS_CKM.2/UNLOCKED The TOE supports RSA (800-56B, as an initiator only), DHE (FFC 800-56A), and ECDHE (ECC 800-56A) methods in TLS key establishment/exchange. The TOE has CVL KAS and ECDSA CAVP algorithm certificates for Elliptic Curve key establishment and key generation respectively as described in the FCS_COP.1 section below. Samsung vendoraffirms that the TOE's RSA key establishment follows 800 -56B. The TOE implementation meets RFC 3526 Section 3. The user and administrator need take no special configuration of the TOE as the TOE automatically generates the keys needed for negotiated TLS ciphersuites. Because the TOE only acts as a TLS client, the TOE only performs 800-56B encryption (specifically the encryption of the PreMaster Secret using the Server's RSA public key) when participating in TLS_RSA_* based TLS handshakes. Thus, the TOE does not perform 80056B decryption. However, the TOE's TLS client correctly handles other cryptographic errors (for example, invalid checksums, incorrect certificate types, corrupted certificates) by sending a TLS fatal alert. As the TOE's RSA key exchange mechanism is used in the TLS Version: 0.3 Date: 10/22/2026 58 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 handshake process and during product development, the TOE's implementation undergoes testing to ensure TLS compatibility. ####### FCS_CKM.2/LOCKED For the S26, A57, A37, Tab Active5 Pro, and Tab Active 5 and their equivalent devices, the TOE provides a Sensitive Data Protection (SDP) library for applications that uses a hybrid crypto scheme based on 4096-bit RSA based key establishment. Applications can utilize this library to implement SDP that encrypts incoming data received while the phone is locked in a manner compliant with this requirement. For other devices, the TOE uses ECDH with a P-256 curve key establishment for protection of application sensitive data received while the device is locked. ####### MOD_WLANC_V1.0: FCS_CKM.2/WLAN The TOE adheres to RFC 3394, SP 800-38F, and 802.11-2012 standards and unwraps the GTK (sent encrypted with the WPA3/2 KEK using AES Key Wrap in an EAPOL-Key frame). The TOE, upon receiving an EAPOL frame, will subject the frame to a number of checks (frame length, EAPOL version, frame payload size, EAPOL-Key type, key data length, EAPOL-Key CCMP descriptor version, and replay counter) to ensure a proper EAPOL message and then decrypt the GTK using the KEK, thus ensuring that it does not expose the Group Temporal Key (GTK). ####### FCS_CKM_EXT.1 The TOE supports a Root Encryption Key (REK) within the main (application) processor. Requests for encryption or decryption chaining to the REK are only accessible through the Trusted Execution Environment, or TEE (TrustZone). The REK lies in a series of 256-bit fuses, programmed during manufacturing. The TEE does not allow direct access to the REK but provides services to derive a HEK (Hardware Encryption Key, which is derived from the REK through a KDF function) for encryption and decryption. The REK value is generated during manufacturing either by the TOE (if it detects that the REK fuses have not been set) using its hardware DRBG or is generated during fabrication using an external RBG that meets the requirements of this PP in that the process utilizes a SHA-256 Hash_DRBG seeded by a hardware entropy source identical in architecture to that within the TOE. The application processor loads the fuse value into an internal hardware crypto register and the Trusted Execution Environment (TEE) provides trusted applications the ability to derive KEKs from the REK (using an SP 800-108 KDF to combine the REK with a salt). Additionally, the when the REK is loaded, the fuses for the REK become locked, preventing any further changing or loading of the REK value. The TEE does not allow trusted applications to use the REK for encryption or decryption, only the ability to derive a KEK from the REK. The TOE includes a TEE application that calls into the TEE in order to derive a KEK from the 256-bit REK/fuse value and then only permits use of the derived KEK for encryption and decryption as part of the TOE key hierarchy. This fabrication process includes strict controls (including physical and logical access control to the manufacturing room where programming takes place as well as video surveillance and access only to specific, authorized, trusted individuals) to ensure that the fabricator cannot access any REK values between generation and programming. ####### FCS_CKM_EXT.2 (KMD) The TOE utilizes its approved RBGs to generate DEKs. When generating AES keys for itself (for example, the TOE's sensitive data encryption keys or for the Secure Key Storage), the TOE utilizes the RAND_bytes() API call from its BoringSSL AES-256 CTR_DRBG to generate a 256-bit AES key. The TOE also utilizes that same DRBG when servicing API requests from mobile applications wishing to generate AES keys (either 128 or 256-bit). In all cases, the TOE generates DEKs using a compliant RBG seeded with sufficient entropy so as to ensure that the generated key cannot be recovered with less work than a full exhaustive search of the key space. 59 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ####### FCS_CKM_EXT.3 (KMD) The TOE generates KEKs (which are always AES 256bit keys generated by one of the TOE's DRBGs) through a combination of methods. First, the TOE generates a KEK (the Keystore masterkey) for each user of the TOE. The TOE also generates encryption KEKs for FBE and work profile encryption (normal and sensitive). The TOE generates a number of different KEKs. In addition to the TSF KEKs, applications may request key generation (through either the Android APIs or SCrypto APIs within the TEE), and the TOE utilizes its BoringSSL/SCrypto CTR_DRBG and Kernel Crypto HMAC_DRBG to satisfy those requests. The requesting application ultimately chooses whether to use that key as a DEK or a KEK, but it is worth mentioning here, as an application can utilize such a key as a KEK, should it choose. ####### FCS_CKM_EXT.4 (KMD) The TOE destroys all the cryptographic keys (plaintext keys, authentication and biometric data, and other security parameters) when they are no longer in use by the system. The exceptions to this are public keys (that protect the boot chain and software updates) and the REK, which are never cleared. Keys stored in RAM during use are destroyed by a zero overwrite. Keys stored in Flash (i.e. eMMC) are destroyed by cryptographic erasure through a block erase call to the flash controller for the location where the FBE keys are stored. Once these are erased, all keys (and data) stored within the encrypted data partition of the TOE are considered cryptographically erased. ####### FCS_CKM_EXT.5 The TOE provides a TOE Wipe function that first erases the encrypted DEKs used to encrypt the data partition using a block erase and read verify command to ensure that the UFS blocks containing the encrypted DEKs (FBE) are now reported as empty. After the encrypted keys have been erased, the TOE will delete the entire user partition with a block erase command and then reformat the partition. Upon completion of reformatting the Flash partition holding user data, the TOE will perform a power-cycle. ####### FCS_CKM_EXT.6 The TOE creates salt and nonces (which are just salt values used in WPA3/WPA2) using its AES-256 CTR_DRBG. | ####### MOD_BT_V1.0:FCS_CKM_EXT.8 The TOE will generate new ECDH key pairs for every pairing attempt. FCS_COP.1/ENCRYPT FCS_COP.1/HASH FCS_COP.1/SIGN FCS_COP.1/KEYHMAC FCS_COP.1/CONDITION The TOE performs cryptographic algorithms in accordance with the following NIST standards and has received the following CAVP algorithm certificates. The BoringSSL v1.10 library (with both Processor Algorithm Accelerators (PAA) and without PAA) provides the following algorithms. Table 16 - Salt Creation | Salt value and size | RBG origin | Salt storage location | |--------------------------------------------------|------------------------------------------------------|-------------------------| | User password salt (256-bit) | BoringSSL's AES -256 CTR_DRBG | Flash file system | | TLS client_random (256-bit) | BoringSSL's AES -256 CTR_DRBG | N/A (ephemeral) | | TLS pre_master_secret (384-bit) | BoringSSL's AES -256 CTR_DRBG | N/A (ephemeral) | | TLS ECDHE private value (256, 384, 512) | BoringSSL's AES -256 CTR_DRBG | N/A (ephemeral) | | WPA3/2 4-way handshake supplicant nonce (SNonce) | BoringSSL's AES -256 CTR_DRBG through wpa_supplicant | N/A (ephemeral) | Version: 0.3 Date: 10/22/2026 60 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 Table 17 - BoringSSL Cryptographic Algorithms | Algorithm | NIST Standard | SFR Reference | Cert# | |---------------------------------------------------|--------------------------|---------------------------------------------------|---------------------------------------| | AES 128/256 CBC, GCM, KW | FIPS 197, SP 800-38A/D/F | FCS_COP.1/ENCRYPT | A7759 | | CVL ECC - P-256/384/521 | SP 800-56B | FCS_CKM.2/UNLOCKED FCS_CKM.2/LOCKED FCS_CKM_EXT.3 | A7759 | | DRBG CTR - 256 | SP 800-90A | FCS_RBG_EXT.1 | A7759 | | ECDSA KeyGen/KeyVer/SigGen/SigVer - P-256/384/521 | FIPS 186-5 | FCS_CKM.1 FCS_COP.1/SIGN | A7759 | | HMAC SHA-1/256/384/512 | FIPS 198-1 & 180-4 | FCS_COP.1/KEYHMAC | A7759 | | RSA KeyGen/SigGen/SigVer - 2048/3072/4096 | FIPS 186-5 | FCS_CKM.1 FCS_COP.1/SIGN | A7759 | | SHS SHA-1/256/384/512 | FIPS 180-4 | FCS_COP.1/HASH | A7759 | | RSA Key Establishment | SP 800-56B | FCS_CKM.2/UNLOCKED FCS_CKM.2/LOCKED | Tested with known good implementation | | FFC Safe Primes | SP 800-56A | FCS_CKM.1 FCS_CKM.2/UNLOCKED | Tested with known good implementation | The Android LockSettings service KBKDF version 77561fc30db9aedc1f50f5b07504aa65b4268b88 library provides the following algorithms. Table 18 - Samsung Crypto Extension Cryptographic Algorithms | Algorithm | NIST Standard | SFR Reference | Cert# | |---------------|-----------------|-----------------|---------| | Key-based KDF | SP 800-108 | FCS_CKM_EXT.3 | A7711 | The evaluated devices utilize the following kernels for the Samsung Kernel Cryptographic Module (Kernel Crypto). Table 19 - Kernel Versions | Device | Kernel Version | Kernel Crypto Version | |------------------------|------------------|-------------------------| | Galaxy S26 Ultra 5G | 6.12 | 2.6 | | Galaxy S26+ 5G | 6.12 | 2.6 | | Galaxy S26 5G | 6.12 | 2.6 | | Galaxy XCover 7 Pro | 5.4 | 2.2 | | Galaxy XCover6 Pro | 6.1 | 2.4 | | Galaxy Tab Active5 Pro | 5.15 | 2.3 | | Galaxy Tab Active5 | 6.1 | 2.4 | | Galaxy A37 5G | 6.12 | 2.6 | | Galaxy A57 5G | 5.10 | 2.2 | | Galaxy A53 5G | 6.12 | 2.6 | The Samsung Kernel Cryptographic ('Kernel Crypto') Module provides the following algorithms. Note that with and without PAA is equivalent to with and without crypto extensions. Table 20 - Samsung Kernel Cryptographic Algorithms | Algorithm | NIST Standard | SFR Reference | Cert# | |------------------------|----------------------|-------------------|----------------------------------| | AES 128/256 CBC | FIPS 197, SP 800-38A | FCS_COP.1/ENCRYPT | A8176, A5143, A3242 A1456, A1455 | | HMAC SHA-1/256 | FIPS 198-1 & 180-4 | FCS_COP.1/KEYHMAC | A8176, A5143, A3242 A1456, A1455 | | DRBG SHA-256 HMAC_DRBG | SP 800-90A | FCS_RBG_EXT.1 | A8176, A5143, A3242 A1456, A1455 | | SHS SHA-1/256 | FIPS 180-4 | FCS_COP.1/HASH | A8176, A5143, A3242 A1455 | 61 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 The evaluated devices utilize the Samsung SCrypto Cryptographic Module for cryptographic operations within the TEE on each device. The following table lists the TEE operating systems for each device. Table 21 - TEE Environments | Device | SoC | TEE OS Version | SCrypto Version | |------------------------|-----------------------------------|------------------|-------------------| | Galaxy S26 Ultra 5G | Snapdragon 8 Elite Gen 5 (SM8850) | QSEE 5.33 | 2.10 | | Galaxy S26+ 5G | Snapdragon 8 Elite Gen 5 (SM8850) | QSEE 533 | 2.10 | | | Exynos 2600 (S5E9965) | TEEGRIS 6.0.0 | 2.9 | | Galaxy S26 5G | Snapdragon 8 Elite Gen 5 (SM8850) | QSEE 5.33 | 2.10 | | Galaxy XCover 7 Pro | Snapdragon 7s Gen 3 (SM7635) | QSEE 5.28 | 2.9 | | Galaxy XCover6 Pro | Snapdragon 778G (SM7325) | QSEE 5.11 | 2.5 | | Galaxy Tab Active5 Pro | Snapdragon 7s Gen 3 (SM7635) | QSEE 5.18 | 2.9 | | Galaxy Tab Active5 | Exynos 1380 (S5E8835) | TEEGRIS 5.0.0 | 2.7 | | Galaxy A37 5G | Exynos 1480 (S5E8845) | TEEGRIS 5.0.0 | 2.7 | | Galaxy A57 5G | Exynos 1680 (S5E8865) | TEEGRIS 6.0.0 | 2.9 | | Galaxy A53 5G | Exynos 1280 (S5E8825) | TEEGRIS 4.2.1 | 2.6 | The Samsung SCrypto TEE library provides the following algorithms. Note that the TOE only performs RSA signing/decryption (using the private key) in the TEE, and performs public key verification/encryption in the normal world using BoringSSL. Table 22 - SCrypto TEE Cryptographic Algorithms | Algorithm | NIST Standard | SFR Reference | Cert# | |---------------------------------------------------|---------------------------|--------------------------|---------------------| | AES CBC/GCM 128/256 | FIPS 197, SP 800-38A/D | FCS_COP.1/ENCRYPT | A8175, A6892, A3243 | | AES CBC/GCM 128/256 | FIPS 197, SP 800-38A/D | FCS_COP.1/ENCRYPT | A915, A889 | | DRBG AES-256 CTR_DRBG | SP 800-90A | FCS_RBG_EXT.1 | A8175, A6892, A3243 | | DRBG AES-256 CTR_DRBG | SP 800-90A | FCS_RBG_EXT.1 | A915, A889 | | ECDSA KeyGen/KeyVer/SigGen/SigVer P-256/384/521 | FIPS 186-5 or FIPS 186- 4 | FCS_CKM.1 FCS_COP.1/SIGN | A8175, A6892, A3243 | | ECDSA KeyGen/KeyVer/SigGen/SigVer P-256/384/521 | FIPS 186-5 or FIPS 186- 4 | FCS_CKM.1 FCS_COP.1/SIGN | A915, A889 | | HMAC SHA-1/256/384/512 | FIPS 198-1 & 180-4 | FCS_COP.1/KEYHMAC | A8175, A6892, A3243 | | HMAC SHA-1/256/384/512 | FIPS 198-1 & 180-4 | FCS_COP.1/KEYHMAC | A915, A889 | | RSA KeyGen and SigGen (no verification) 2048 bits | FIPS 186-5 or FIPS 186- 4 | FCS_CKM.1 FCS_COP.1/SIGN | A8175, A6892, A3243 | | RSA KeyGen and SigGen (no verification) 2048 bits | FIPS 186-5 or FIPS 186- 4 | FCS_CKM.1 FCS_COP.1/SIGN | A915, A889 | | SHS SHA-1/256/384/512 | FIPS 180-4 | FCS_COP.1/HASH | A8175, A6892, A3243 | | SHS SHA-1/256/384/512 | FIPS 180-4 | FCS_COP.1/HASH | A915, A889 | | KBKDF | SP 800-108 | FCS_CKM_EXT.3 | A8175, A6892, A3243 | | KBKDF | SP 800-108 | FCS_CKM_EXT.3 | A915, A889 | The Chipset hardware for storage encryption has various modules that provide cryptographic functions. The modules and versions are listed here. Only discrete modules are listed here. | Device | SoC | Flash Crypto | |------------------------|-----------------------------------|-----------------------------------------| | Galaxy S26 Ultra 5G | Snapdragon 8 Elite Gen 5 (SM8850) | Qualcomm ICE v4.0.3 | | Galaxy S26+ 5G | Snapdragon 8 Elite Gen 5 (SM8850) | Qualcomm ICE v4.0.3 | | | Exynos 2600 (S5E9965) | Samsung sf_crypt_config_fmp_fx_sk_v3.01 | | Galaxy S26 5G | Snapdragon 8 Elite Gen 5 (SM8850) | Qualcomm ICE v4.0.3 | | Galaxy XCover 7 Pro | Snapdragon 7s Gen 3 (SM7635) | Qualcomm ICE v3.2.2 | | Galaxy XCover6 Pro | Snapdragon 778G (SM7325) | Qualcomm ICE v3.2.0 | | Galaxy Tab Active5 Pro | Snapdragon 7s Gen 3 (SM7635) | Qualcomm ICE v4.2.1 | | Galaxy Tab Active5 | Exynos 1380 (S5E8835) | Samsung sf_crypt_config_fmp_fx_sk_v2.00 | | Galaxy A37 5G | Exynos 1480 (S5E8845) | Samsung sf_crypt_config_fmp_fx_sk_v2.00 | | Galaxy A57 5G | Exynos 1680 (S5E8865) | Samsung sf_crypt_config_fmp_fx_sk_v3.01 | 62 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 Table 23 - Hardware Components | Device | SoC | Flash Crypto | |---------------|-----------------------|-----------------------------------------| | Galaxy A53 5G | Exynos 1280 (S5E8825) | Samsung sf_crypt_config_fmp_fx_sk_v1.00 | The storage encryption modules provide the following algorithms. Table 24 - Storage Hardware Algorithms | Algorithm | NIST Standard | SFR Reference | Cert# | |----------------------------|----------------------|-------------------|----------------------------| | XTS-AES 256 (Exynos FMP) | FIPS 197, SP 800-38E | FCS_COP.1/ENCRYPT | A7799, A5100 A2723 | | XTS-AES 128/256 (Qualcomm) | FIPS 197, SP 800-38E | FCS_COP.1/ENCRYPT | A6456, A6449, A1658, A1659 | The devices contain unique Wi-Fi chipsets based on the model of the device. The chipsets are listed here. Table 25 - Wi-Fi Hardware Components | Device | Wi-Fi Chipset | Wi-Fi Chipset Details | |------------------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------| | S26x (Qualcomm) | Qualcomm WCN7881 | Incorporates Qualcomm's Qualcomm Lithium AES engine- 256w core to provide WPA2/WPA3 AES encryption | | All S26x(Exynos) | Qualcomm WCN7851 | Incorporates Qualcomm's Qualcomm Lithium AES engine- 256w core to provide WPA2/WPA3 AES encryption | | Galaxy XCover 7 Pro | Qualcomm WCN6755 | Incorporates Qualcomm's Beryllium AES-256 engine IP core to provide WPA2/WPA3 AES encryption | | Galaxy XCover6 Pro | Qualcomm WCN6750 | Incorporates Qualcomm's Beryllium AES-256 engine IP core to provide WPA2/WPA3 AES encryption | | Galaxy Tab Active5 Pro | Qualcomm WCN6755 | Incorporates Qualcomm's Beryllium AES-256 engine IP core to provide WPA2/WPA3 AES encryption | | Galaxy Tab Active5 | S5N6566X01-6031 | The Samsung WLAN Cryptographic Accelerator is a hardware module that provides AES support for WLAN packet data in multiple Exynos products. | | Galaxy A37 5G | S5N6566X01-6031 | The Samsung WLAN Cryptographic Accelerator is a hardware module that provides AES support for WLAN packet data in multiple Exynos products. | | Galaxy A57 5G | S5M6568X01-6030 | The Samsung WLAN Cryptographic Accelerator is a hardware module that provides AES support for WLAN packet data in multiple Exynos products. | | Galaxy A53 5G | S5N5C20X00-6030 | The Samsung WLAN Cryptographic Accelerator is a hardware module that provides AES support for WLAN packet data in multiple Exynos products. | The Wi-Fi chipset hardware provides the following algorithms. Table 26 - Wi-Fi Chip Algorithms | Algorithm | NIST Standard | SFR Reference | Cert# | |------------------------------|----------------------|-------------------|-------------| | AES 128 CCM (Qualcomm Wi-Fi) | FIPS 197, SP 800-38C | FCS_COP.1/ENCRYPT | A3238, 5663 | | AES 128 CCM (Samsung Wi-Fi) | FIPS 197, SP 800-38C | FCS_COP.1/ENCRYPT | C1623 | Several devices provide a secure processor for mutable hardware key storage. The devices and chipsets are listed here. Table 27 - Mutable Key Storage Components | Device | Mutable Storage Chipset | |--------------------|----------------------------| | All S26x(Qualcomm) | Secure Processing Unit 1.3 | | All S26x(Samsung) | Smart Secure Platform 7.0 | The chipsets for the mutable hardware key storage provide the following algorithms. 63 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 Table 28 - Mutable Key Storage Cryptographic Algorithms | Algorithm | NIST Standard | SFR Reference | Cert# | |----------------------------------|--------------------------|-------------------|-----------------------------------------------------------------------------------------------| | AES CBC/GCM 128/256 | FIPS 197, SP 800- 38A/D | FCS_COP.1/ENCRYPT | A4780, A4779, A4445, A4444, A3029, A3030, A2211, A2212 A2148, A2149, A1007, A1006, A840, A836 | | DRBG Hash_DRBG (Qualcomm) | SP 800-90A | FCS_RBG_EXT.1 | A2840, A2028, A774 | | ECDSA SigGen/SigVer (P- 256/384) | FIPS 186-5 or FIPS 186-4 | FCS_COP.1/SIGN | A4780, A4445, A3030, A2212, A2149, A1006, A840 | | HMAC SHA-256/384/512 (Qualcomm) | FIPS 198-1 & 180-4 | FCS_COP.1/KEYHMAC | A4444, A3029, A2211, A1007 | | HMAC SHA-256 (Exynos) | FIPS 198-1 & 180-4 | FCS_COP.1/KEYHMAC | A4780, A2149, A840 | | RSA SigGen/SigVer - 2048 | FIPS 186-5 or FIPS 186-4 | FCS_COP.1/SIGN | A4780, A4445, A3030, A2212, A2149, A1006, A774 | | SHS SHA-256 | FIPS 180-4 | FCS_COP.1/HASH | A4779, A4444, A3029, A2840, A2211, A2028, A2149, A1007, A840, A774 | The SoC hardware provides the following algorithms. Table 29 - SoC Cryptographic Algorithms | Algorithm | NIST Standard | SFR Reference | Cert# | |-------------------------------------------------------------|------------------------|-------------------|---------------------| | KBKDF (Exynos) | SP 800-108 | FCS_CKM_EXT.3 | A8321, A6940 | | KBKDF (Exynos) | SP 800-108 | FCS_CKM_EXT.3 | A5162, A2536 | | AES 128/256 CBC/GCM (Exynos) | FIPS 197, SP 800-38A/D | FCS_COP.1/ENCRYPT | A8321, A6940 | | AES 128/256 CBC/GCM (Exynos) | FIPS 197, SP 800-38A/D | FCS_COP.1/ENCRYPT | A5162, A2536 | | SHS SHA-256 (Exynos) | FIPS 180-4 | FCS_COP.1/HASH | A8321, A6940 | | SHS SHA-256 (Exynos) | FIPS 180-4 | FCS_COP.1/HASH | A5162, A2536 | | HMAC SHA-256 (Exynos) | FIPS 198-1 & 180-4 | FCS_COP.1/KEYHMAC | A8321, A6940 | | HMAC SHA-256 (Exynos) | FIPS 198-1 & 180-4 | FCS_COP.1/KEYHMAC | A5162, A2536 | | AES 128/256 CBC (Qualcomm) | FIPS 197, SP 800-38A | FCS_COP.1/ENCRYPT | A7988, A805 | | DRBG SHA-256 Hash_DRBG or DRBG SHA-512 Hash_DRBG (Qualcomm) | SP 800-90A | FCS_RBG_EXT.1 | A8783, A3756, A2065 | | SHS SHA-256 (Qualcomm) | FIPS 180-4 | FCS_COP.1/HASH | A8772, A3756, A2065 | The TOE's application processors include hardware entropy implementations that supply random data within the TEE and to the Linux kernel RNG (primary input pool). Note that kernel-space system applications utilize the cryptographic algorithm implementations in the Samsung Kernel Cryptographic Module (Kernel Crypto) or in the Chipset hardware, while user-space system applications and mobile applications utilize the BoringSSL library (through the Android API). In the case of each cryptographic library, the library itself includes any algorithms required (for example, BoringSSL provides hash functions for use by HMAC and digital signature algorithms). Trusted Applications executing with the Trusted Execution Environment (TEE) utilize the SCrypto library. For example, the trusted application implementing the Android Keymaster that supports the Android Keystore utilizes the SCrypto library for all of its cryptographic functionality. For its HMAC implementations, the TOE accepts all key sizes of 160, 256, 384, & 512; supports all SHA sizes save 224 (e.g., SHA-1, 256, 384, & 512), utilizes the specified block size (512 for SHA-1 and 256, and 1024 for SHA-384 & 512); and outputs MAC lengths of 160, 256, 384, and 512. 64 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 The TOE conditions the user's password using a combination of functions to increase the memory required for derivation to thwart attacks. This combination of functions is embedded in the scrypt algorithm. Scrypt uses three steps to condition the password: 1. One PBKDF2 operation (NIST SP 800-132) 2. Several rounds of ROMix operations 3. One final PBKDF2 operation (NIST SP 800-132) This value is used as input for decrypting other keys that are tied to successful user authentication. To unlock the user's keystore, the value generated in the previous step us conditioned further using PBKDF2 (NIST SP 800-132). The key derivation function uses the value derived from the initial password conditioning and a randomly generated 128-bit salt in 8192 HMAC-SHA-256 iterations to generate a 256-bit KEK. In both cases of conditioning, the time needed to derive keying material does not impact or lessen the difficulty faced by an attacker's exhaustive guessing as the combination of the password derived KEK with REK value entirely prevents offline attacks and the TOE's maximum incorrect password login attempts (between 1 and 30 incorrect attempts with 4 character, minimum, passwords) prevents exhaustive online attacks. The TOE's algorithm certificates represent the BoringSSL library, Kernel Cryptographic module, SCrypto library, Crypto Extensions library and Chipset hardware implementations. These implementations have been tested upon Android 16 running atop both Exynos and Qualcomm ARMv8 chipsets. The TOE's Exynos processor devices include the Samsung Flash Memory Protector, while the TOE's Qualcomm processor devices include hardware XTS-AES (Inline Crypto Engine, ICE) implementations for internal storage encryption and decryption. ####### FCS_HTTPS_EXT.1 The TOE includes the ability to support the HTTPS protocol (compliant with RFC 2818) so that (mobile and system client) applications executing on the TOE can securely connect to external servers using HTTPS. Administrators have no credentials and cannot use HTTPS or TLS to establish administrative sessions with the TOE as the TOE does not provide any such capabilities. ####### MOD_VPNC_V2.5: FCS_IPSEC_EXT.1 The TOE's VPN Client implements the IPsec protocol as specified in RFC 4301; however, the VPN Client presents as few configuration options as possible to the User in order to minimize the possibility of misconfiguration and relies upon the Gateway to enforce organizational policies, for things like the specific cipher suites and selection of traffic to protect. For this reason, the VPN Client does not support editing of its SPD entries. The VPN Client will insert a PROTECT rule to IPsec encrypt and send all TOE traffic to the VPN GW (as the VPN Client ignores the IKEv2 Traffic Selector negotiated between the client and gateway and always sends all traffic). The VPN Client routes all packets through the kernel's IPsec interface (ipsec0) when the VPN is active. The kernel compares packets routed through this interface to the SPDs configured for the VPN to determine whether to PROTECT, BYPASS, or DISCARD each pa cket. The vendor designed the TOE's VPN Client, when operating in CC Mode, to allow no SPD configuration and always force all traffic through the VPN. The VPN Client ignores any IKEv2 traffic selector negotiations with the VPN GW and will always create an SPD PROTECT rule that matches all traffic. Thus, the kernel will match all packets, subsequently encrypt those packets, and finally forward them to the VPN Gateway. The VPN Client supports tunnel mode for its IPsec connections. The VPN Client provides IKEv2 key establishment as part of its IPsec implementation. The IKEv2 implementation is conformant with RFCs 7296 with mandatory support for NAT traversal as specified in section 2.23, RFC 8247 and RFC 4868 for hash functions. 65 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 The TOE provides RFC 4106 conformant AES-GCM-128 and AES-GCM-256, and RFC 3602 conformant AESCBC-128 and AES-CBC-256 as encryption algorithms. The TOE Platform also provides SHA-1, SHA-256, SHA384, and SHA-512 in addition to HMAC-SHA1, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 as integrity/authentication algorithms (producing message digests of 160, 256, 384, and 512-bits in length) as well as Diffie-Hellman Groups 14, 15, 16, 19, 20, 21, and 24. The VPN utilizes the algorithms from the BoringSSL and Kernel Cryptographic modules as part of the IKEv2 and IPsec protocols. The encrypted payload for IKEv2 uses AES-CBC-128, AES-CBC-256 as specified in RFC 6379 and AES-GCM-128 and AESGCM-256 as specified in RFC 5282. The TOE relies upon the VPN Gateway to ensure that by default the strength of the symmetric algorithm (in terms of the number of bits in the key) negotiated to protect the IKEv2 /IKE_SA connection is greater than or equal to the strength of the symmetric algorithm (in terms of the number of bits in the key) negotiated to protect the IKEv2 CHILD_SA connection. An administrator can configure the VPN Gateway to limit SA lifetimes based on length of time to values that include 24 hours for IKE SAs and 8 hours for IPsec SAs. The TOE includes hardcoded limits of 10 hours for an IKE SA and 3 hours for an IPsec SA. The TOE and VPN Gateway will rekey their IKE and IPsec SAs after the shorter of either 10 hours or 3 hours respectively (the TOE's fixed lifetimes) or the administrator specified lifetime configured on the VPN Gateway. The VPN Client generates the secret value x used in the IKEv2 Diffie-Hellman key exchange ('x' in g x mod p) using the FIPS validated RBG specified in FCS_RBG_EXT.1 and having possible lengths of 224, 256, or 384 bits. When a random number is needed for a nonce, the probability that a specific nonce value will be repeated during the life of a specific IPsec SA is less than 1 in 2 112 , 2 128 , or 2 192 . The VPN Client implements peer authentication using RSA certificates or ECDSA certificates that conform to RFC 4945 and FIPS 186-5. If certificates are used, the VPN Client ensures that the IP address or Fully Qualified Distinguished Name (FQDN) contained in a certificate matches the expected IP Address or FQDN for the entity attempting to establish a connection and ensures that the certificate has not been revoked (using the Online Certificate Status Protocol [OCSP] in accordance with RFC 2560). The TOE supports a number of different Diffie-Hellman (DH) groups for use in SA negotiation including DH Groups 14 (2048-bit MODP), 15 (3072-bit MODP), 16 (4096-bit MODP), 19 (256-bit Random ECP), 20 (384bit Random ECP), 21 (521-bit Random ECP), and 24 (2048-bit MODP with 256-bit POS). The TOE selects the DH group by selecting the largest group configured by an administrator that is offered by the VPN gateway. During the Peer Authentication stage of IPsec, the TOE Platform will verify the authenticity of the VPN gateway's X.509v3 certificate by validating the certificate, validating the certificate path, validating the certificate's revocation status using OCSP, validating that the certificate path terminates in a trusted CA certificate, and validating that the CA certificate has the basicConstraints extension present and the CA flag set to true. The TOE will also ensure that the Subject Alternative Name IP address or DNS name in the VPN gateway's certificate matches the IP address or DNS name configured in the VPN profile. If the configured IP addres s or DNS name does not match a Subject Alternative Name in the VPN gateway's certificate, the TOE will refuse to establish an IPsec connection with the VPN gateway. The VPN Client relies upon the VPN Gateway to ensure that the cryptographic algorithms and key sizes negotiated during the IKEv2 negotiation ensure that the security strength of the Phase 1/IKE_SA are greater than or equal to that of the Phase 2/CHILD_SA. ####### FCS_IV_EXT.1 (KMD) The TOE generates IVs for data storage encryption and for key storage encryption. The TOE uses XTS-AES and AES-CBC mode for data encryption and AES-GCM for key storage. 66 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target ####### FCS_RBG_EXT.1 (KMD) The TOE provides a number of different RBGs including: - An AES-256 CTR_DRBG w/ Block_Cipher_df provided by BoringSSL. The TOE provides mobile applications access (through an Android API) to random data drawn from its AES-256 CTR_DRBG - An AES-256 CTR_DRBG w/ Block_Cipher_df provided by SCrypto in the TEE - A SHA-256 HMAC_DRBG HMAC_DRBG provided by Kernel Crypto in the Android kernel (/dev/random or get_random_bytes()) - A hardware SHA-256 or SHA-512 Hash_DRBG provided by the Qualcomm Application Processor hardware The TOE ensures that it initializes each RBG with sufficient entropy ultimately accumulated from a TOEhardware-based noise source or the software-based Jitterentropy noise source. The TOE seeds each of its software AES-256 CTR_DRBGs using at least 384-bits of data originating from the hardware noise source after passing the seeding data through an appropriate derivation function. The TOE seeds its Kernel Crypto DRBG using a combination of a 512-bit seed from the hardware noise source and 384 bits of data from the Jitterentropy software noise source. Each of these RBGs are ensured to have at least 256 bits of security strength, however all are capable of providing other amounts of entropy (such as 128-bits) to any requesting application. The TOE itself always uses 256-bits of entropy, but other applications or services are not subject to this limitation, and can request 128-bits or 256-bits of entropy subject its own requirements. The SHA-256/512 Hash_DRBG in the Qualcomm AP is used to generate the REK on first boot. ####### FCS_SRV_EXT.1 FCS_SRV_EXT.2 (KMD) The TOE provides applications access to the cryptographic operations including encryption (AES), hashing (SHA), signing and verification (RSA & ECDSA), key hashing (HMAC), password-based key-derivation functions (PKBDFv2 HMAC-SHA-512), generating asymmetric keys for key establishment (RSA and ECDH), and generating asymmetric keys for signature generation and verification (RSA, ECDSA). T he hashing functions are implemented in byte-oriented mode. The TOE also provides access through Android API methods and through the kernel. The vendor also developed testing applications to enable execution of the NIST algorithm test suite in order to verify the correctness of the algorithm implementations. ####### FCS_STG_EXT.1 The TOE provides users, administrators and applications running on the TOE the ability to generate, import, and securely store symmetric and asymmetric keys through the TOE's Android Keystore. The TOE allows a user or administrator (via the MDM) to import a certificate (in PKCS#12 [PFX] format) and provides applications running on the TOE an API to import a certificate or secret key. In either case, the TOE will place the key into the user's keystore (and the TOE will remove the PKCS#12 password -based protection if the imported key is a certificate) and doubly encrypt the imported key with DEKs, which in turn are encrypted by a KEK derived from the user's DKEK and a KEK derived from the REK. All user and application keys placed into the user's keystore are s ecured in this fashion. The user of the TOE can elect to delete keys from the keystore, as well as to wipe the entire device securely. The administrator can only delete keys from the keystore that have been deployed to the TOE by the administrator. The TOE affords applications control (control over use and destruction) of keys that they create or import, and only the common application developer can explicitly authorize access, use, or destruction of one application's key by any other applica tion. Version: 0.3 Date: 10/22/2026 67 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 Table 30 - Key Management Matrix | Entity | Can Import? | Can Destroy? | Allow Other App to Use? | Allow Other App to Destroy? | |------------------------------|---------------|----------------|---------------------------|-------------------------------| | User | Yes | Yes | | | | Administrator | Yes | Yes | | | | Mobile application | Yes | Yes | | | | Common application developer | | | Yes | Yes | On the devices with support for mutable hardware storage (see see Error! Reference source not found. ) the TOE provides both software-based (the Android Keystore) and mutable hardware-based (the StrongBox Keystore) key storage. The key storage is implemented in a separate hardware chipset that is part of the SoC, providing additional protection beyond that normally provided by the Android Keystore which is implemented in the TEE. The hardware module implements its own cryptographic services internally to the module. By default, all key storage is handled with the Android Keystore, but an application developer can use the StrongBox keystore by setting a preference to use the hardware keystore instead. When the preference is set to the hardware keystore, the keys will be stored in the mutable hardware and all operations on the keys will be handled inside the hardware. ####### FCS_STG_EXT.2 (KMD) The TOE provides protection for all stored keys (i.e. those written to storage media for persistent storage) chained to both the user's password and the REK. All keys are encrypted with AES -GCM. All KEKs are 256bit, ensuring that the TOE encrypts every key with another key of equal or greater strength/size. In the case of Wi-Fi, the TOE utilizes the 802.11-2012 KCK and KEK keys to unwrap (decrypt) the WPA3/WPA2 Group Temporal Key received from the access point. Additionally, the TOE protects persistent Wi-Fi keys (user certificates) by storing them in the Android Keystore. The TOE also stores the SecurityLogAgent (properties related to the SE Android configuration) in the same manner as the long-term trusted channel key materials. ####### FCS_STG_EXT.3 The key hierarchy shows AES-256-GCM is used to encrypt all KEKs and the GCM encryption mode itself ensures integrity as authenticated decryption operations fail if the encrypted KEK becomes corrupted. PKG_TLS_V1.1: FCS_TLS_EXT.1 PKG_TLS_V1.1: FCS_TLSC_EXT.1 PKG_TLS_V1.1: FCS_TLSC_EXT.2 PKG_TLS_V1.1: FCS_TLSC_EXT.4 PKG_TLS_V1.1: FCS_TLSC_EXT.5 The TOE provides mobile applications (through its Android API) the use of TLS version 1.2 only as a client, including support for the selected ciphersuites in the selections in section 5.1.2.29. The TOE supports Subject Alternative Name (SAN) (DNS and IP address) as reference identifiers. The TOE supports client (mutual) authentication. The TOE inherently (without requiring any configuration) supports the supported ciphersuites and evaluated elliptic curves (P-256 and P-384); neither the user nor the administrator need configure anything in order for the TOE to support these ciphersuites or curves. The TOE supports the use of wildcards in X.509 reference identifiers (SAN), and the TOE supports certificate pinning through Android's Network security configuration. This configuration allows a mobile application to specify one or more certificate public key hashes (SHA-1 or SHA-256) along with the domain and optionally an expiry. With such a configuration, the application will only establish a TLS connection if one of the public keys in the certificate path matches a 'pinned' key hash. After t he optional expiry, Android disregards the pinned 68 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 certificates and performs no pinning (to prevent connectivity issues in apps that have not been updated). The TOE includes the 'renegotiation_info' TLS extension in its TLS client hello message . ####### MOD_WLANC_V1.0: FCS_TLSC_EXT.1/WLAN MOD_WLANC_V1.0: FCS_TLSC_EXT.2/WLAN MOD_WLANC_V1.0: FCS_WPA_EXT.1 The TSF supports TLS versions 1.2, and 1.1 with client (mutual) authentication and supports the ciphersuites in the selections in section 5.1.2.30 for use with EAP-TLS as part of WPA3/2. The TOE, by design, supports the evaluated elliptic curves (P-256 and P-384) and requires/allows no configuration of the supported curves. ## 6.3 User Data Protection ####### FDP_ACF_EXT.1 FDP_ACF_EXT.2 ####### FDP_ACF_EXT.3 (KMD) The TOE provides protection for high-level services like location, email, calendar in addition to providing individual permissions to which mobile applications can request access. The TOE provides the following base permissions to applications (for API Level 34): 1. Normal - A lower-risk permission that gives an application access to isolated application-level features, with minimal risk to other applications, the system, or the user. The system automatically grants this type of permission to a requesting application at installation, without asking for the user's explicit approval (though the user always has the option to review these permissions before installing). 2. Dangerous - A higher-risk permission that would give a requesting application access to private user data or control over the device that can negatively impact the user. Because this type of permission introduces potential risk, the system cannot automatically grant it to the requesting application. For example, any dangerous permissions requested by an application will be displayed to the user and require confirmation before proceeding or some other approach can be taken to avoid the user automatically allowing the use of such facilities. 3. Signature - A permission that the system is to grant only if the requesting application is signed with the same certificate as the application that declared the permission. If the certificates match, the system automatically grants the permission without notifying the user or asking for the user's explicit approval. 4. Internal - a permission that is managed internally by the system and only granted according to the protection flags. An example of a normal permission is the ability to vibrate the device: android.permission.VIBRATE. This permission allows an application to make the device vibrate, and an application that does not request (or declare) this permission would have its vibration requests ignored. An example of a dangerous privilege would be access to location services to determine the location of the mobile device: android.permission.ACCESS_FINE_LOCATION. The TOE controls access to Dangerous permissions during the running of the application. The TOE prompts the user to review the application's requested permissions (by displaying a description of each permission group, into which individual permissions map, that an application requested access to). If the user approves, then the application is allowed to continue running. If the user disapproves, the devices continues to run, but cannot use the services protected by the denied permissions. Thereafter, the mobile device grants that application during execution access to the set of permissions declared in its Manifest file 12 . 69 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 An example of a signature permission is the android.permission.BIND_VPN_SERVICE that an application must declare in order to utilize the VpnService APIs of the device. Because the permission is a Signature permission, the mobile device only grants this permission to an application (2nd installed app) that requests this permission and that has been signed with the same developer key used to sign the application (1st installed app) declaring the permission (in the case of the example, the Android Framework itself). ####### An example of an internal permission is the android.permission.SET_DEFAULT_ACCOUNT_FOR_CONTACTS, which is only granted to system applications fulfilling the Contacts app role to allow the default account for new contacts to be set. Additionally, Android includes the following flags that layer atop the base categories: 1. privileged - this permission can also be granted to any applications installed as privileged apps on the system image. Please avoid using this option, as the signature protection level should be sufficient for most needs and works regardless of exactly where applications are installed. This permission flag is used for certain special situations where multiple vendors have applications built in to a system image which need to share specific features explicitly because they are being built together. 2. system - Old synonym for 'privileged'. 3. development - this permission can also (optionally) be granted to development applications (e.g., to allow additional location reporting during beta testing). 4. appop - this permission is closely associated with an app op for controlling access. 5. pre23 - this permission can be automatically granted to apps that target API levels below API level 23 (Android 6.0). 6. installer - this permission can be automatically granted to system apps that install packages. 7. verifier - this permission can be automatically granted to system apps that verify packages. 8. preinstalled - this permission can be automatically granted to any application pre-installed on the system image (not just privileged apps) (the TOE does not prompt the user to approve the permission). The Android 16 (Level 35) API (details found here https://developer.android.com/reference/packages) provides services to mobile applications. While Android provides a large number of individual permissions, they are grouped into categories or features that provide similar functionality for the simplicity of the user interaction. These groupings do not affect the permissions themselves; it is only a way to group them together for the user presentation. Table 31 shows a series of functional categories centered on common functionality. | Service Features | Description | |-----------------------------------------|--------------------------------------------------------| | Sensitive I/O Devices & Sensors | Location services, Audio & Video capture, Body sensors | | User Personal Information & Credentials | Contacts, Calendar, Call logs, SMS | | Metadata & Device ID Information | IMEI, Phone Number | 70 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 Table 31 - Access Control Categories | Service Features | Description | |-------------------------------------------|--------------------------------------------------------------------------------------| | Data Storage Protection | App data, App cache | | System Settings & Application Management | Date time, Reboot/Shutdown, Sleep, Force-close application, Administrator Enrollment | | Wi-Fi, Bluetooth, USB Access | Wi-Fi, Bluetooth, USB tethering, debugging and file transfer | | Mobile Device Management & Administration | MDM APIs | | Peripheral Hardware | NFC, Camera, Headphones | | Security & Encryption | Certificate/Key Management, Password, Revocation rules | Only applications with a common application developer are able to allow sharing of data between the applications. Common applications are those signed by a common certificate or key by the developer that have permissions to allow data sharing in their manifest. Application data can only be shared under this scenario. The TOE provides the ability to create a Knox Separated Apps folder. A Knox Separated Apps folder provides an administrator with the ability to isolate applications from the broader system. Access to applications placed into the folder does not require separate authentication. Applications within the folder are restricted from accessing services provided outside the folder, such as sharing services (intents) and data storage. ####### FDP_DAR_EXT.1 The TOE provides encryption of all data (which includes both user data and TSF data) stored on the data partition of the TOE. The TOE uses FBE to encrypt data using XTS-AES-256 using a unique File Content Encryption Key (FCEK) for each file. File metadata (such as filenames) is encrypted separately with AES-CBC-CTS with a unique File Name Encryption Key (FNEK) for each file. FBE supports two separate classes of protection, credentialed and device. While each class is encrypted, the difference is whether the encryption is chained to the user's credentials. By default, all data is stored in the credential class, and applications that will store data in the device class are defined during the installation of the application. Device class data can be accessed as soon as the device has started, including prior to the first user authentication. The TOE's system executables, libraries, and their configuration data reside in a read -only file system outside the data partition. ####### FDP_DAR_EXT.2 (KMD) For the S26x, and their equivalent devices, the TOE provides the NIAPSEC library for Sensitive Data Protection (SDP) that application developers must use to opt-in for sensitive data protection. When developer's opt -in for SDP, all data that is received on the device destined for that application is treated as sensitive. This library calls into the TOE to generate an RSA key that acts as a master KEK for the SDP encryption process. When an application that has opted-in for SDP receives incoming data while the device is locked, an AES symmetric DEK is generated to encrypt that data. The public key from the master RSA KEK above is then used to encrypt the AES DEK. Once the device is unlocked, the RSA KEK private key is rederived and can be used to decrypt the AES DEK for each piece of information that was stored while the device was locked. The TOE then takes that decrypted data and re-encrypts it following FDP_DAR_EXT.1. For all other devices, the TOE as a part of the Knox Platform for Enterprise, provides mobile applications the ability to store sensitive data and have the TOE encrypt it accordingly. This functionality is controlled by the administrator through the apps that support sensitive data storage, and is only available for apps that have been designed to support sensitive data. When an application stores data as sensitive data, the file will be marked as sensitive in the metadata. Based on the environment lock-state, sensitive data protected by this mechanism will be encrypted when locked (either directly by the user or via timeout). An application can determine whether sensitive data should remain encrypted in this manner or if it should be re-encrypted (such as by a symmetric key for better performance). Applications can use this to receive and store data securely while the environment is locked (such as an email application). 71 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 ####### FDP_IFC_EXT.1 MOD_VPNC_V2.5: FDP_IFC_EXT.1 FDP_VPN_EXT.1 The TOE supports the installation of VPN Client applications, which can make use of the provided VPN APIs in order to configure the TOE's routing functionality to direct all traffic through the VPN. The TOE also includes an IPsec VPN Client that ensures all traffic other than traffic necessary to establish the VPN connection (for example, ARP, 802.11-2012 traffic, and IKEv2) flows through the VPN. The TOE routes all packets through the kernel's IPsec interface (ipsec0) when the VPN is active. The kernel com pares packets routed through this interface to the SPDs configured for the VPN to determine whether to PROTECT, BYPASS, or DISCARD each packet. The vendor developed the TOE's VPN, when operating in CC Mode, to allow no configuration and always force all traffic through the VPN. The TOE ignores any IKEv2 traffic selector negotiations with the VPN GW and will always create an SPD PROTECT rule that matches all traffic. Thus, the kernel will match all packets, subsequently encrypt those packets, and finally forward them to the VPN Gateway. ####### MOD_VPNC_V2.5: FDP_RIP.2 The TOE has been designed to ensure that no residual information exists in network packets when the VPN is turned on. When the TOE allocates a new buffer for either an incoming or outgoing a network packet, the new packet data will be used to overwrite any previous data in the buffer. If an allocated buffer exceeds the size of the packet, any additional space will be overwritten (padded) with zeros before the packet is forwarded (to the external network or delivered to the appropriate internal application). ####### FDP_STG_EXT.1 The TOE's Trusted Anchor Database consists of the built -in certificates (individually stored in /system/etc/security/cacerts ) and any additional user or admin/MDM loaded certificates. The user can disable the built-in certificates or add new certificates using the TOE's Android user interface [Settings->Security and privacy->More security settings->Credential storage]. The admin is able to load new certificates using the MDM. Disabled default certificates and user added certificates reside in the /data/misc/user/0/cacerts-removed and /data/misc/user/0/cacerts-added directories respectively. The builtin ones are protected, as they are part of the TSF's read only system partition, while the TOE protects user-loaded certificates by storing them with appropriate permissions to prevent modification by mobile applications. The TOE also stores the userloaded certificates in the user's keystore. ####### FDP_UPC_EXT.1/APPS The TOE provides APIs allowing non-TSF applications (mobile applications) the ability to establish a secure channel using IPsec, TLS, and HTTPS. Google provides the NIAPSEC library for application developers to use for Hostname Checking, Revocation Checking, and TLS Ciphersuite restriction. Application developers must utilize this library to ensure the device behaves in the evaluated configuration. Mobile applications can use the following Android APIs for IPsec, TLS and HTTPS respectively: android.net.VpnService [https://developer.android.com/reference/android/net/VpnService.html](https://developer.android.com/reference/android/net/VpnService.html) com.samsung.android.knox.net.vpn 72 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 https://docs.samsungknox.com/devref/knox-sdk/reference/com/samsung/android/knox/net/vpn/package-summary.html javax.net.ssl.SSLContext: [https://developer.android.com/reference/javax/net/ssl/SSLSocket](https://developer.android.com/reference/javax/net/ssl/SSLSocket) Developers then need to swap SocketFactory for SecureSocketFactory, part of a private library provided by Google. Developers can request this library by emailing: niapsec@google.com ####### FDP_UPC_EXT.1/BLUETOOTH The TOE provides APIs allowing non-TSF applications (mobile applications) the ability to establish a secure channel using Bluetooth BR/EDR and Bluetooth LE. Mobile applications can use the following Android APIs for Bluetooth: android.bluetooth [http://developer.android.com/reference/android/bluetooth/package-summary.html](http://developer.android.com/reference/android/bluetooth/package-summary.html) ## 6.4 Identification and Authentication ####### FIA_AFL_EXT.1 The TOE maintains two separate lock screens: the device (Android) lock screen and a lock screen for the work profile. Each lock screen maintains individually stored (in separate Flash locations) failed login attempt counters. The TOE maintains, for each lock screen, the number of failed logins since the last successful login, and upon reaching the maximum number of incorrect logins the TOE performs a full wipe of all protected data. For the device lock screen, this would mean a full wipe of all data on the device (a factory reset), while for the work profile lock screen this would remove all data associated with the work profile. The TOE maintains the number of failed logins across power-cycles (so for example, assuming a configured maximum retry of ten incorrect attempts, if one were to enter five incorrect passwords and power cycle the phone, the phone would only allow five more incorrect login attempts before wiping) by storing the number of logins remaining within its Flash file system. An administrator can adjust the number of failed logins to a value between one and 30 through an MDM. For users with biometrics enabled, biometric authentication attempts are maintained along with the password attempts. In all cases, biometric or hybrid authentication mechanisms are non-critical and cannot be the authentication method that triggers an action (device or work profile wipe). The maximum number of incorrect password authentication attempts can be configured to a value between 1 and 30. The maximum number of biometric attempts is 20 (this cannot be configured separately and this limit only applies to the device lock screen, not the work profile lock screen). The user can attempt 10 biometric attempts followed by the maximum number of password attempts before the TOE will wipe itself. For example, if the counter were set to 15, 10 biometric attempts would be followed by 15 password attempts before the device was wiped. Alternatively, the user might enter 14 incorrect passwords, and then twenty failed biometric authentication attempts followed by a final incorrect password attempt. The TOE's work profile provides its own lock screen, which allows password authentication or hybrid authentication (biometric and password). The hybrid authentication method requires the user to authenticate with a biometric and a password in sequential order. To login, the user must first enter his or her Knox biometric and only upon successfully verifying the user's biometric, the TOE prompts the User for 73 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 their Knox password, and the user must enter their password. Knox will count the number of incorrect passwords attempted, and wipe the work profile (and its associated data) after the user reaches the configured number of incorrect attempts. The TOE validates passwords by providing them to Android's Gatekeeper (which runs in the Trusted Execution Environment), and if the presented password fails to validate, the TOE increments the failed attempt counter before displaying a visual error to the user. The TOE validates biometric attempts through the biometric service (which runs in the Trusted Execution Environment), and if the presented biometric does not match the registered templates, the TOE increments the failed attempt counter before displaying a visual error to the user. ####### MOD_BT_V1.0: FIA_BLT_EXT.1 The TOE requires explicit user authorization before it will pair with a remote Bluetooth device. When pairing with another device, the TOE requires that the user either confirm that a displayed numeric passcode matches between the two devices or that the user enter (or choose) a numeric passcode that the peer device generates (or must enter). ####### MOD_BT_V1.0: FIA_BLT_EXT.2 The TOE requires explicit user authorization or user authorization before data transfers over the link. When transferring data with another device, the TOE requires that the user must confirm an authorization popup displayed allowing data transfer (Obex Object Push) or confirm the user passkey displayed numeric passcode matches between the two devices (RFCOMM). ####### MOD_BT_V1.0: FIA_BLT_EXT.3 The TOE tracks active connections and actively ignores connection attempts from Bluetooth device addresses for which the TOE already has an active connection. ####### MOD_BT_V1.0: FIA_BLT_EXT.4 The TOE 's Bluetooth host and controller support Bluetooth Secure Simple Pairing and the TOE utilizes this pairing method when the remote host also supports it. ####### MOD_BT_V1.0: FIA_BLT_EXT.6 The TOE requires that OPP and MAP profile connections have explicit user authorization before granting access to trusted remote devices on a per service basis (as opposed to a per app basis). ####### MOD_BT_V1.0: FIA_BLT_EXT.7 The TOE requires that untrusted devices have explicit user authorization before granting access to untrusted remote devices for the OPP Bluetooth profile on a per service basis (as opposed to a per app basis). FIA_MBE_EXT.1 FIA_MBE_EXT.2 FIA_MBV_EXT.1/BMFPS FIA_MBV_EXT.1/UDFPS (KMD) The TOE provides fingerprint biometric authentication. Table 32 shows which biometric subsystems are available on each device. | Device | Sensors | |----------------------------------------------------------------------------------|------------| | Galaxy S26(Ultra 5G, S26+5G, S26 5G), | Ultrasonic | | Galaxy Tab S9 (Ultra, Tab S9+, Tab S9) Galaxy A53 5G Galaxy A37 5G Galaxy A57 5G | Optical | 74 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Table 32 - Device biometric sensor The TOE provides a mechanism to enroll user biometrics for authentication. The enrollment process requires the user to have a password set and to be authenticated successfully prior to being able to start the enrollment process. The TSF determines the quality of a sample before using it to enroll or verify a user. The fingerprint systems utilize different sensors to capture the data, but the data analysis of the quality is common. Fingerprint sample quality is determined using three measures - completeness, clarity, and minutia. In the evaluated configuration, the maximum number of authentication attempts is 40 before a wipe event is triggered. This is broken down into a maximum of 10 biometric attempts and 30 password attempts that could be made before a wipe occurs. Using this as the worst-case scenario leads to a maximum of 10 biometric attempts that can be made for the System Authentication False Accept Rate (SAFAR) calculations. All devices or configurations provide for fewer attempts (both password and biometric), and so any resulting SAFAR would be lower than this scenario. The last attempt before a wipe must be a password attempt. For a password-only configuration, the SAFAR claim would be 1:1,000,000 when set for 10 attempts. The password minimum length is 4 characters and there are 93 possible characters that can be used in the password. This is not claimed since this configuration (i.e. no biometric authentication allowed) would not require FIA_BME_EXT.1, but is shown here for the overall SAFAR calculations. The False Accept Rate (FAR) for fingerprint is 1:50,000 and the False Reject Rate (FRR) is 3%. The SAFAR when a fingerprint is in use is 1:1,000 based on a maximum of 10 attempts of the biometric as noted in the worst-case scenario. For all SAFAR calculations the password is considered a critical factor for all combined factor SAFARany calculations as detailed in PP_MDF_V3.3 section G.4. The values are accepted because they are within the 1% margin allowed by MOD_BIO_11. For devices which support fingerprint biometrics, SAFARfingerprint can be used for the calculation of a worstcase scenario. The Knox Platform for Enterprise provides hybrid (multi-factor: password and biometric) authentication. When using the hybrid authentication mechanism, the user must enter a correct biometric factor and then a correct password in order to successfully unlock the work profile. Version: 0.3 Date: 10/22/2026 75 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 The SAFAR when a hybrid mechanism is in use is equal to SAFARpassword. The maximum number of biometric attempts when using hybrid is 50, but eventually the biometric factor must be entered correctly and then one must always enter a correct password. Given the potential maximum 50 biometric attempts, although that could take a very long time given some imposed delays, that factor is discounted in calculating the SAFAR. The password minimum length is 4 characters and there are 93 possible characters that can be used in the password. The biometric FAR/FRR values are tested internally by two independent groups using different methodologies. The first set of tests are 'offline' in that a specially configured device is connected to a test harness and used to enroll biometric samples for storage. The test harness then uses the samples to run through numerous combinations of the samples to determine FAR/FRR results that are used to tune the algorithms controlling the biometric system. Once testing is complete a second set of tests are performed in an 'online' manner where the testing is done with users directly testing on a live device. All devices with different hardware combinations that could affect the biometric subsystem are tested. For example, both the Exynos and Qualcomm versions of the mobile devices are tested individually since the TrustZone components in each device are different. These tests are integrated into the production process and so are repeated continually during the development process. ####### MOD_WLANC_V1.0: FIA_PAE_EXT.1 The TOE can join WPA2-802.1X (802.11i) and WPA3-Enterprise wireless networks requiring EAP-TLS authentication, acting as a client/supplicant (and in that role connect to the 802.11 access point and communicate with the 802.1X authentication server). ####### FIA_PMG_EXT.1 The TOE supports user passwords consisting of basic Latin characters (upper and lower case, numbers, and the special characters noted in the selection (see section 5.1.4.14)) for authentication to all lock screens (see Table 33). On devices with a boot lock screen, the TOE uses the same configuration for both the boot and device lock screens (i.e. there is one setting that applies to both). The TOE can support a minimum password length of as few as four (4) characters and a maximum of no more than sixteen (16) characters. The TOE defaults to requiring passwords to have a minimum of four characters that contain at least one letter and one number. An MDM application can change these defaults and impose password restrictions (like quality, specify another minimum length, the minimum number of letters, numeric characters, lower case letters, upper case letters, symbols, and non-letters). ####### FIA_TRT_EXT.1 The TOE allows users to authenticate through external ports (either a USB keyboard or a Bluetooth keyboard paired in advance of the login attempt). If not using an external keyboard, a user must authenticate through the standard User Interface (using the TOE touchscreen). The TOE limits the number of authentication attempts through the UI to no more than five attempts within 30 seconds (irrespective of what keyboard the operator uses). Thus if the current [the n th ] and prior four authentication attempts have failed, and the n-4 th attempt was less than 30 second ago, the TOE will prevent any further authentication attempts until 30 seconds has elapsed. Note as well that the TOE will wipe itself when it reaches the maximum number of unsuccessful authentication attempts (as described in FIA_AFL_EXT.1 above). ####### FIA_UAU.5 The TOE allows the following authentication methods at the different lock screens in CC mode. The available biometrics are dependent on the lock screen being used, MDM configuration and enrolled templates. Table 33 shows which authentication methods are available at each lock screen. 76 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Table 33 - Allowed Lock Screen Authentication Methods The TOE prohibits other authentication mechanisms such as pattern or swipe. Use of Smart Lock mechanisms (on-body detection, trusted places, trusted devices, trusted face, and trusted voice) and PIN can be blocked through management controls. Upon restart or power-up the user can only use a password for authentication at the first lock screen. Once past this initial authentication screen the user is able to use one of the configured methods at the device lock screen to login and the work profile lock screen. ####### FIA_UAU.6/CREDENTIAL FIA_UAU.6/LOCKED The TOE requires the user to enter their password or supply their biometric in order to unlock the TOE. Additionally, the TOE requires the user to confirm their current password when accessing the ' Settings>Lock screen and AOD->Screen lock and biometrics ' menu in the TOE's user interface . The TOE can disable Smart Lock through management controls. Only after entering their current user password can the user then elect to change their password. ####### FIA_UAU.7 The TOE's two lock screens (device lock screen, and work profile lock screen), by default, briefly display the most recently entered password character and then obscures the character by replacing the displayed character with a dot symbol. The user can con figure the TOE's behavior for the device lock screen so that it does not briefly display the last typed character; however, the TOE always briefly displays the last entered character for the work profile lock screen. Additionally, the TOE's device lock scr een does not provide any feedback other than a notification of a failed biometric (fingerprint) authentication attempt ('not recognized'). Similarly, the TOE's work profile lock screen, when configured for hybrid authentication, displays only an indication ('no match') of a failed biometric att empt. ####### FIA_UAU_EXT.1 The TOE's Key Hierarchy requires the user's password in order to derive the sHEK in order to decrypt other KEKs and DEKs. Thus, until it has the user's password, the TOE cannot decrypt the DEK utilized by FBE to decrypt protected data. ####### FIA_UAU_EXT.2 The TOE, when configured to require user authentication (as is the case in CC mode), allows only those actions described in section 5.1.4.21. Beyond those actions, a user cannot perform any other actions other than observing notifications displayed on the lock screen until after successfully authenticating. The Galaxy Tab S6 devices do not support Edge applications, and are not available on these devices. ####### FIA_X509_EXT.1 ####### MOD_WLANC_V1.0: FIA_X509_EXT.1/WLAN The TOE checks the validity of all imported CA certificates by checking for the presence of the basicConstraints extension and that the CA flag is set to TRUE as the TOE imports the certificate into the TOE's Trust Anchor Database . If the TOE detects the absence of either the extension or flag, the TOE will import the certificate as a user public key and add it to the keystore (not the Trust Anchor Database). The TOE also checks for the presence of the basicConstraints extension and CA flag in each CA certificate presented in a peer server's certificate chain . Similarly, the TOE verifies the extendedKeyUsage Server Authentication purpose during certificate validation. The TOE's certificate validation algorithm examines each certificate in the path (starting with the peer's certificate) and first checks for validity of that Version: 0.3 Date: 10/22/2026 77 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 certificate (e.g., has the certificate expired? or is it not yet valid? whether the certificate contains the appropriate X.509 extensions [e.g., the CA flag in the basic constraints extension for a CA certificate, or that a server certificate contains the Server Authentication purpose in the extendedKeyUsage field]), then verifies each certificate in the chain (applying the same rules as above, but also ensuring that the Issuer of each certificate matches the Subject in the next rung 'up' in the chain and that the chain ends in a self - signed certificate present in ei ther the TOE's trusted anchor database or matches a specified Root CA), and finally the TOE performs revocation checking for all certificates in the chain. ####### FIA_X509_EXT.2 MOD_WLANC_V1.0: FIA_X509_EXT.2/WLAN MOD_WLANC_V1.0: FIA_X509_EXT.6 The TOE uses X.509v3 certificates as part of EAP-TLS, TLS, HTTPS and IPsec authentication. The TOE comes with a built-in set of default Trusted Credentials (Android's set of trusted CA certificates). While the user cannot remove any of the built-in default CA certificates, the user can disable any of those certificates through the user interface so that certificates issued by disabled CA's cannot validate successfully. In addition, a user can import a new trusted CA certificate into the Keystore or an administrator can install a new certificate through an MDM. The TOE does not establish TLS or HTTPS connections itself (beyond EAP-TLS used for WPA3/WPA2 Wi-Fi connections), but provides a series of APIs that mobile applications can use to check the validity of a peer certificate. When establishing an EAP-TLS connection, the TOE does not check for certificate revocation as the revocation servers are not available until after the EAP-TLS connection is established. The mobile application, after correctly using the specified APIs, can be assured as to the validity of the peer certificate and will not establish the trusted connection if the peer certificate cannot be verified (including validity, certification path, and revocation [through CRL and OCSP]). The VPN requires that for each VPN profile, the user specify the client certificate the TOE will use (the certificate must have been previously imported into the keystore) and specify the CA certificate to which the server's certificate must chain . The VPN thus uses the specified certificate when attempting to establish that VPN connection. When establishing a connection to a VPN server, the VPN first compares the Identification (ID) Payload received from the server against the certificate sent by the server, and if the DN of the certificate does not match the ID, then the TOE does not establish the connection. The TOE supports both CRL and OCSP configurations for revocation checking. Only one of these will be used at a time (even if both are configured). OCSP takes precedence over CRL if a certificate provides information for checking both. The process of checking the revocation status of a certificate depends on the configuration on the device set by the admin. If OCSP is configured (and if the Authority Information Access, AIA, extension is present), OCSP will be used to check the status. If the certificate lacks AIA, or if OCSP is not configured on the device the TOE attempts to determine revocation status using CRLs, if the certificate includes a CRL Distribution Point (CDP). If the TOE cannot establish a connection with the server acting as the CDP or OCSP server, or does not receive a positive confirmation from the OCSP server , the TOE will deem the server's certificate as invalid and not establish a TLS connection with the server. Note that the VPN only checks OCSP for revocation (if it is configured on the device). ####### FIA_X509_EXT.3 The TOE's Android operating system provides applications the java.security.cert.CertPathValidator API Class of methods for validating certificates and certification paths (certificate chains establishing a trust chain from a certificate to a trust anchor). This class is also recommended to be used by third-party Android developers for certificate validation. However, TrustedCertificateStore must be used to chain certificates to the Android System Trust Anchor Database (anchors should be retrieved and provided to PKIXParameters used by CertPathValidator). The available APIs may be found here: 78 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 [http://developer.android.com/reference/java/security/cert/package-summary.html](http://developer.android.com/reference/java/security/cert/package-summary.html) ## 6.5 Security Management ####### FMT_MOF_EXT.1 FMT_SMF.1 The TOE provides the management functions described in Table 8 - Security Management Functions. The table includes annotations describing the roles that have access to each service and how to access the service. The TOE enforces administrative configured restrictions by rejecting user configuration (through the UI) when attempted. It is worth noting that the TOE's ability to specify authorized application repositories takes the form of allowing enterprise applications (i.e., restricting applications to only those applications installed by an MDM Agent). ####### MOD_BT_V1.0: FMT_SMF_EXT.1/BT The TOE provides the management functions described in Table 9 - Bluetooth Security Management Functions. The table includes annotations describing the roles that have access to each service and how to access the service. The TOE enforces administrative configured restrictions by rejecting user configuration (through the UI) when attempted. Wi-Fi Direct can be blocked to prevent Bluetooth High Speed access between devices and NFC access can be blocked to prevent out of band pairing. ####### MOD_WLANC_V1.0: FMT_SMF.1/WLAN The TOE provides the management functions described in Table 10 - WLAN Security Management Functions. The table includes annotations describing the roles that have access to each service and how to access the service. The TOE enforces administrative configured restrictions by rejecting user configuration (through the UI) when attempted. ####### MOD_VPNC_V2.5: FMT_SMF.1/VPN The TOE provides the management functions described in Table 11 - VPN Security Management Functions. In addition, the VPN Gateway, acting as administrator, can specify the IKE algorithms, protocols and authentication techniques, and the crypto period for session keys. The TOE provides users the ability to specify an X.509v3 certificate (previously loaded into the TOE Platform's keystore) for the TOE to use to authenticate to the VPN gateway during IPsec peer authentication as well as an X.509v3 certificate to use as the CA certificate. ####### FMT_SMF_EXT.2 A user can unenroll an MDM agent from the device in one of two ways. First, a user can revoke the MDM agent's administrative privileges through the Settings app ( Settings->Security and privacy->More security settings->Device admin apps) and then uninstall the agent. This method assumes that the MDM agent does block the user from revoking the agent's administrator privileges. When unenrolled in this fashion, the device will remove the work profile, the work profile's applications and dat a. In effect, this translates to the selections of wiping all sensitive data (all work profile data), removing all Enterprise applications (all work profile applications), removing all device-stored Enterprise application data (all work profile application data), and removing Enterprise secondary authentication data (Knox password and/or fingerprint). In the case where an MDM agent blocks the user from revoking the agent's administrative privileges, a user can only unenroll by wiping the entire device. By doing this, the user causes the device to wipe all protected 79 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 data (wiping all data, including both the user's protected data and any Enterprise/work profile data) as well as remove MDM policies and disabling CC mode (as the device returns to factory defaults). ####### FMT_SMF_EXT.3 The TOE provides the user with the ability to see all apps installed on the device that have administrative capabilities. Each app listing also shows the status of the app privileges for administration (enabled or disabled) and the permissions the app has on the device. ## 6.6 Protection of the TSF ####### FPT_AEX_EXT.1 The Linux kernel of the TOE's Android operating system provides address space layout randomization utilizing a non-cryptographic kernel random function to provide 8 unpredictable bits to the base address of any user-space memory mapping. The random function, though not cryptographic, ensures that one cannot predict the value of the bits. ####### FPT_AEX_EXT.2 FPT_AEX_EXT.6 The TOE's Android 16 operating system utilizes 6.12/6.1/5.15/5.4 Linux kernels, whose memory management unit (MMU) enforces read, write, and execute permissions on all pages of virtual memory and ensures that write and execute permissions are not simultaneously granted on all memory (exceptions are only made for Dalvik JIT compilation and memory allocated with mmap). The Android operating system sets the ARM eXecute Never (XN) bit on memory pages and the MMU circuitry of the TOE's ARMv 8 Application Processor enforces the XN bits. From Android's security documentation (https://source.android.com/security/), Android supports 'Hardware -based No eXecute (NX) to prevent code execution on the stack and heap' . Section D.5 of the ARM v8 Architecture Reference Manual contains additional details about the MMU of ARM-based processors: [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0487a.f/index.html.](http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0487a.f/index.html) ####### FPT_AEX_EXT.3 The TOE's Android operating system provides explicit mechanisms to prevent stack buffer overruns (enabling -fstack-protector) in addition to taking advantage of hardware-based No eXecute to prevent code execution on the stack and heap. Samsung requires and applies these protections to all TSF executable binaries and libraries. ####### FPT_AEX_EXT.4 The TOE protects itself from modification by untrusted subjects using a variety of methods. The first protection employed by the TOE is a Secure Boot process that uses cryptographic signatures to ensure the authenticity and integrity of the bootloader and kernels using data fused into the device processor. The TOE's Secure Boot process employs a series of public keys to form a chain of trust that operates as follows. The Application Processor (AP) contains the hash of the Secure Boot Public Key (a key embedded in the end of the signed bootloader image), and upon verifying the SBPK attached to the bootloader produces the expected hash, the AP uses this public key to verify the signature of the bootloader image, to ensure its integrity and authenticity before transitioning execution to the bootloader. The bootloader, in turn, contains the Image Signing Public Key (ISPK), which the bootloader will use to verify the signature on either kernel image (primary kernel image or recovery kernel image). The signing key type and hash type used are listed in Table 34 - Secure Boot Public Keys. Table 34 - Secure Boot Public Keys | Device | Signing Key | Hash | |---------------------------|---------------|---------| | All S26x (all processors) | ECDSA P384 | SHA-256 | | All other devices | RSA 2048 | SHA-256 | 80 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 Note that when configured for Common Criteria mode, the TOE only accepts updates to the TOE via FOTA; however, when not configured for CC mode, the TOE allows updates through the bootloader's ODIN mode. The primary kernel includes an embedded FOTA Public Key, which the TOE uses to verify the authenticity and integrity of FOTA update signatures (which contain a PKCS 2.1 PSS RSA 2048 w/ SHA-256 signature). The TOE protects access to the REK and derived HEK to only trusted applications 13 within the TEE (TrustZone). The TOE key manager includes a TEE module that utilizes the HEK to protect all other keys in the key hierarchy. All TEE applications are cryptographically signed, and when invoked at runtime (at the behest of an untrusted application), the TEE will only load the trusted application after successfully verifying its cryptographic signature. Furthermore, the device encryption library checks the integrity of the system by checking the result from both Secure Boot/SecurityManager and from the Integrity Check Daemon before servicing any requests. Without this TEE application, no keys within the TOE (including keys for ScreenLock, the keystore, and user data) can be successfully decrypted, and thus are useless. The TOE protects biometric data by separating it from the Android operating system. The biometric sensor is tied to the TEE such that it cannot be accessed directly from Android but can only be done through the biometric software inside the TEE. All biometric data is maintained within the TEE such that Android is only able to know the result of a biometric process (such as enrollment or verification), and not any of the data used in that process itself. The third protection is the TOE's internal SecurityManager watchdog service. The SecurityManager manages the CC mode of the TOE by looking for unsigned kernels or failures from other, non-cryptographic checks on system integrity, and upon detection of a failure in either, disables the CC mode and notifies the TEE application. The TEE application then locks itself, again rendering all TOE keys useless. Finally, the TOE's Android OS provides 'sandboxing' that ensures each non -system mobile application executes with the file permissions of a unique Linux user ID in a different virtual memory space. This ensures that applications cannot access each other's memory space (it is possible for two processes to utilize shared memory, but not directly access the memory of another application) or files and cannot access the memory space or files of system-level applications. ####### FPT_AEX_EXT.5 The TOE provides Kernel Address Space Layout Randomization to ensure that the base address of kernelspace memory mappings consist of six (6) unpredictable bits. This ensures that at each boot, the location of kernel data structures including the core kernel begins at a random physical address, mapping the core kernel at a random virtual address in the vmalloc area, loading kernel modules at a random virtual address in the vmalloc area, and mapping system memory at a random virtual address in the linear area. ####### FPT_BBD_EXT.1 The TOE's hardware and software architecture ensures separation of the application processor (AP) from the baseband or communications processor (CP). While the AP and CP are part of the same SoC, they are separate physical components within the SoC with no shared components between them (such as memory) and communicate via a non-shared bus (i.e. no other chips can communicate via this bus). From a software perspective, the AP and CP communicate logically through the Android Radio Interface Layer (RIL) daemon. This daemon, which executes on the AP, coordinates all communication between the AP and CP. It makes requests of the CP and accepts the response from the CP; however, the RIL daemon does not provide any reciprocal mechanism for the CP to make requests of the AP. Because the mobile architecture provides only the RIL daemon interface, the CP has no method to access the resources of the software executing on the AP. 13 A TrustZone application is a trusted application that executes in a hardware-isolated domain. 81 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 ####### MOD_CPP_BIO_V1.1:FPT_BDP_EXT.1 (KMD) The complete biometric authentication process happens inside the TEE (including image capture, all processing and match determination). All software in the biometric system is inside the TEE boundary, while the sensors are accessible from within Android. The TEE handles calls for authentication made from Android with only the success or failure of the match provided back to Android (and when applicable, to the calling app). The image taken by the capture sensor is processed by the biometric service to check the enrolled templates for a match to the captured image. ####### FPT_JTA_EXT.1 The TOE prevents access to its processor's JTAG interface by only enabling JTAG when the TOE has a special image written to its bootloader/TEE partitions. That special image must be signed by the appropriate key (corresponding to the public key that has its SHA-25 6 hash programmed into the processor's fuses). ####### FPT_KST_EXT.1 (KMD) The TOE does not store any plaintext key material in its internal Flash; instead, the TOE encrypts all keys and biometric data before storing them. This ensures that irrespective of how the TOE powers down (e.g., a user commands the TOE to power down, the TOE reboots itself, or battery is removed), all keys and biometric data stored in internal Flash are wrapped with a KEK. Please refer to section 6.2 for further information (including the KEK used) regarding the encryption of keys stored in the internal Flash. As the TOE encrypts all keys stored in Flash, upon boot-up, the TOE must first decrypt and utilize keys. Note as well that the TOE does not use a user's biometric fingerprint to encrypt/protect key material. Rather the TOE always requires the user enter his or her password after a reboot (in order to derive the necessary keys to decrypt the user data partition and other keys in the key hierarchy). ####### FPT_KST_EXT.2 (KMD) The TOE utilizes a cryptographic library consisting of an implementation of BoringSSL, the Kernel Crypto module, the SCrypto module, and the following system-level executables that utilize KEKs: fscrypt, eCryptfs, wpa_supplicant, and the keystore. The TOE ensures that plaintext key material is not exported by not allowing the REK to be exported and by ensuring that only authenticated entities can request utilization of the REK. Furthermore, the TOE only allows the system-level executables access to plaintext DEK values needed for their operation. The TSF software (the system-level executables) protects those plaintext DEK values in memory both by not providing any access to these values and by clearing them when no longer needed (in compliance with FCS_CKM_EXT.4) . Note again that the TOE does not use the user's biometric fingerprint to encrypt/protect key material (and instead only relies upon the user's password). The TOE also ensures that biometric data used for enrolling and authenticating users cannot be exported. During authentication or enrollment, the calling program (the TSF or an app) is able to request biometric actions, but the data resulting from that action is not provided back to the calling program. The calling program only receives a notice of success of failure about the process. ####### FPT_KST_EXT.3 (KMD) The TOE does not provide any way to export plaintext DEKs or KEKs (including all keys stored in the keystore) as the TOE chains all KEKs to the HEK/REK. ####### FPT_NOT_EXT.1 When the TOE encounters a self-test failure or when the TOE software integrity verification fails, the TOE transitions to a non-operational mode. The user may attempt to power-cycle the TOE to see if the failure condition persists, and if it does persist, the user may attempt to boot to the recovery mode/kernel to wipe data and perform a factory reset in order to recover the device. MOD_CPP_BIO_V1.1:FPT_PBT_EXT.1 (KMD) 82 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 The TOE requires the user to enter their password to enroll, re-enroll or unenroll any biometric templates. When the user attempts biometric authentication to the TOE, the biometric sensor takes an image of the presented biometric for comparison to the enrolled templates. The biometric system compares the captured image to all the stored templates on the device to determine if there is a match. ####### FPT_STM.1 The TOE requires time for the Package Manager, FOTA image verifier, TLS certificate validation, wpa_supplicant, audit system and keystore applications. These TOE components obtain time from the TOE using system API calls [e.g., time() or gettimeofday()]. An application cannot modify the system time as mobile applications need the A ndroid 'SET_TIME' permission to do so . Likewise, only a process with system privileges can directly modify the system time using system-level APIs. The TOE uses the Cellular Carrier time (obtained through the Carrier's network timeserver) as a trusted source; however, the user can also manually set the time through the TOE's user interface. ####### FPT_TST_EXT.1 The TOE performs known answer power on self-tests (POST) on its cryptographic algorithms to ensure that they are functioning correctly. The kernel itself performs known answer tests on its cryptographic algorithms to ensure they are working correctly and the SecurityManager service invokes the self-tests of BoringSSL at start-up to ensure that those cryptographic algorithms are working correctly. The Chipset hardware performs a power-up self-test to ensure that its AES implementation is working, as does the TEE SCrypto cryptographic library. Should any of the tests fail, the TOE will reboot to see if that will clear the error. Table 35 - Power-up Cryptographic Algorithm Self-Tests | Algorithm | Implemented in | Description | |----------------------------|-----------------------------------------------------|-------------------------------------------------| | AES encryption/ decryption | BoringSSL, SCrypto, Kernel Crypto, Chipset hardware | Comparison of known answer to calculated valued | | ECDH key agreement | BoringSSL | Comparison of known answer to calculated valued | | DRBG random bit generation | BoringSSL, SCrypto, Kernel Crypto | Comparison of known answer to calculated valued | | ECDSA sign/verify | BoringSSL, SCrypto | Sign operation followed by verify | | HMAC-SHA | BoringSSL, SCrypto, Kernel Crypto | Comparison of known answer to calculated valued | | RSA sign/verify | BoringSSL, SCrypto | Comparison of known answer to calculated valued | | SHA hashing | BoringSSL, SCrypto, Kernel Crypto | Comparison of known answer to calculated valued | ####### MOD_WLANC_V1.0: FPT_TST_EXT.3/WLAN MOD_VPNC_V2.5: FPT_TST_EXT.1/VPN The TOE platform performs the previously mentioned self-tests to ensure the integrity of the WLAN client (wpa_supplicant) and the VPN client (libcharon.so) in addition to the cryptographic libraries used by the clients. ####### FPT_TST_EXT.2/PREKERNEL ####### FPT_TST_EXT.2/POSTKERNEL The TOE ensures a secure boot process in which the TOE verifies the digital signature of the bootloader software for the Application Processor (using a public key whose hash resides in the processor's internal fuses) before transferring control. The bootloader, in turn, verifies the signature of the Linux kernel (either the primary or the recovery kernel) it loads. For any boot mode, once the kernel has been loaded, the TOE uses dm-verity in EIO mode to protect the integrity of the system partition. After verifying the digital signature of the dm-verity hash tree (using the 83 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 same public key that verifies the kernel image), the TOE will reject the loading of file system blocks where the integrity does not match, and return an I/O error (as if the block were unreadable). ####### FPT_TUD_EXT.1 The TOE's user interface provides a method to query the current version of the TOE software/firmware (Android version, baseband version, kernel version, build number, and security software version) and hardware (model and version). Additionally, the TOE provides users the ability to review the currently installed apps (including 3 rd party 'built - in' applications) and their version. ####### FPT_TUD_EXT.2 (KMD) When in CC mode, the TOE verifies all updates to the TOE software using a public key (FOTA public key) chaining ultimately to the Secure Boot Public Key (SBPK), a hardware protected key whose SHA-256 hash resides inside the application processor (note that when not in CC mode, the TOE allows updates to the TOE software through the Download mode of the bootloader). After verifying an update's FOTA signature, the TOE will then install those updates to the TOE. The application processing verifies the bootloader's authenticity and integrity (thus tying the bootloader and subsequent stages to a hardware root of trust: the SHA-256 hash of the SBPK, which cannot be reprogrammed after the 'write - enable' fuse, has been blown). The Android OS on the TOE requires that all applications bear a valid signature before Android will install the application. ####### FPT_TUD_EXT.3 The TOE requires that all applications be signed before they can be installed. Android uses a file format called APK to package the application installation. The contents of the APK are hashed and then signed, with the resulting APK Signing Block then inserted into the APK or saved as a separate file (depending on the APK Signature Scheme in use). Once an application has been downloaded, the Signing Block information is used to verify the software before installation. The app contents are verified against the hash values that have been calculated and signed before approving the installation. In addition to the hash check, there are several rules related to the contents of the Signing Block which can be found here: https://source.android.com/security/apksigning/v3. ####### FPT_TUD_EXT.6 (KMD) The TOE maintains a monotonic version counter for the TOE software. Before a new update can be installed, the version of the new software is verified to the version counter. If the new image is older than the current version, the update will be rejected and not installed; only version numbers that are equal to or greater than the currently set number can be installed on the device. ####### ALC_TSU_EXT Samsung utilizes industry best practices to ensure their devices are patched to mitigate security flaws. Samsung provides a web portal for reporting potential security issues (https://security.samsungmobile.com/securityReporting.smsb) with instructions about how to securely contact and communicate with Samsung. As an Android OEM, also works with Google on reported Android issues (https://source.android.com/source/report-bugs.html) to ensure customer devices are secure. Samsung will create updates and patches to resolve reported issues as quickly as possible, at which point the update is provided to the wireless carriers. The delivery time for resolving an issue depends on the severity, and can be as rapid as a few days before the carrier handoff for high priority cases. The wireless carriers perform additional tests to ensure the updates will not adversely impact their networks and then plan device rollouts once that testing is complete. Carrier updates usually take at least two weeks to as 84 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 much as two months (depending on the type and severity of the update) to be rolled out to customers. However, the Carriers also release monthly Maintenance Releases in order to address security-critical issues, and Samsung itself maintains a security blog (https://security.samsungmobile.com) in order to disseminate information directly to the public. Samsung communicates with the reporting party to inform them of the status of the reported issue. Further information about updates is handled through the carrier release notes. Issues reported to Google directly are handled through Google's notification processes. ## 6.7 TOE Access ####### FTA_SSL_EXT.1 The TOE transitions to its locked state either immediately after a user initiates a lock by pressing the power button or after a configurable period of inactivity. As part of that transition, the TOE will display a lock screen to obscure the previous conte nts; however, the TOE's lock screen still allows a user to perform the functions listed in section 5.1.4.21 before authenticating. However, without authenticating first, a user cannot perform any related actions based upon these notifications (for example, they cannot respond to emails, calendar appointment requests, or text messages) other than answering an incoming phone call. On power up the TOE boots to the device lock screen. On the first boot, the user can only make emergency calls, receive calls, enter their password or see notifications from apps that do not require user authentication (apps that have requested the use of Device Encrypted `storage during installation). ####### FTA_TAB.1 The TOE can be configured by an administrator to display a message on the lock screen using an MDM. ####### MOD_WLANC_V1.0: FTA_WSE_EXT.1 The TOE allows an administrator to specify (using an MDM) a list of wireless networks (SSIDs) to which the user may direct the TOE to connect. When not enrolled with an MDM, the TOE allows the user to control to which wireless networks the TOE should connect, but does not provide an explicit list of such networks, rather the user may scan for available wireless network (or directly enter a specific wireless network), and then connect. Once a user has connected to a wireless network, the TOE will automatically reconnect to that network when in range and the user has enabled the TOE's Wi -Fi radio. ## 6.8 Trusted Path/Channels ####### MOD_BT_V1.0: FTP_BLT_EXT.1 MOD_BT_V1.0: FTP_BLT_EXT.3/BR ####### MOD_BT_V1.0: FTP_BLT_EXT.3/LE The TOE provides support for both Bluetooth BR/EDR and Bluetooth LE connections. The TSF ensures that all connections are encrypted by default using keys of at least 128-bits (regardless of the type of connection). ####### MOD_BT_V1.0: FTP_BLT_EXT.2 Since the TOE requires an encrypted connection between itself and another Bluetooth device, if the remote device stops encryption, the TSF will force the termination of the connection. A new connection should reestablish the encrypted channel (and if not, the connection will not be successful). ####### FTP_ITC_EXT.1 ####### MOD_WLANC_V1.0: FTP_ITC.1/WLAN The TOE provides secured (encrypted and mutually authenticated) communication channels between itself and other trusted IT products through the use of 802.11-2012, 802.1X, and EAP-TLS, TLS, HTTPS and IPsec. 85 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 The TOE permits itself and applications to initiate communications via the trusted channel, and the TOE initiates communication via the trusted channel for connection to a wireless access point. The TOE provides access to TLS and HTTPS via published APIs that are accessible to any application that needs an encrypted end-to-end trusted channel. The TOE also meets the PP-Module for Virtual Private Network (VPN) Clients. ### 6.9 Work Profile Functionality This section specifically enumerates the functionality specifically provided when a work profile has been created. ####### FDP_ACF_EXT.1.2 The TOE, through a combination of Android's multi -user capabilities and Security Enhancements (SE) for Android, provides the ability to create an isolated profile within the device. Within a work profile a group of applications can be installed, and access to those applications is then restricted to usage solely within the work profile. The work profile boundary restricts the ability of sharing data such that applications outside the work profile cannot see, share or even copy data to those inside the work profile and vice versa. Exceptions to the boundary (such as allowing a copy operation) must be configured by the administrator via policy. Furthermore, the work profile boundary policy can control access to hardware features, such as the camera or microphone, and restrict the ability of applications within the work profile to access those services. ####### FIA_AFL_EXT.1 The work profile maintains, in flash, the number of failed logins since the last successful login, and upon reaching the maximum number of incorrect logins, the work profile performs a full wipe of data protected by Knox (i.e. data inside the work profile). An administrator can adjust the number of failed logins for the hybrid and password login mechanism from the default of twenty failed logins to a value between one and thirty through an MDM. ####### FIA_UAU_EXT.4 (KMD) The TOE requires a separate password or hybrid authentication for its work profile, thus protecting all Enterprise application data and shared resource data. The user must enter either their password or both their password and biometric (if the user has configured hybrid authentication and enrolled a biometric) in order to access any of the Enterprise application data. ####### FIA_UAU.5 The work profile allows the user to authenticate using a password, or a hybrid method requiring both a biometric and the password at the same time. The TOE prohibits other authentication mechanisms, such as pattern, PIN, or biometric by themselves. ####### FIA_UAU.6/LOCKED The work profile requires the user to enter their password in order to unlock the work profile. Additionally, the work profile requires the user to confirm their current password when accessing the ' Knox Settings -> Knox unlock method ' menu in the work profile user interface. Only after entering their current user password can the user then elect to change their password. ####### FIA_UAU.7 The work profile allows the user to enter the user's password from the lock screen. The work profile will, by default display the most recently entered character of the password briefly or until the user enters the next character in the password, at which point the work profile obscures the character by replacing the character with a dot symbol. The work profile can also be configured for hybrid authentication. In this case the user is prompted to first scan their biometric successfully before being prompted to enter their password. If the biometric attempt is 86 of 87 Samsung Electronics Co., Ltd. Samsung Galaxy Devices on Android 16 - Spring Security Target Version: 0.3 Date: 10/22/2026 unsuccessful, the user is prompted again to enter the biometric. To successfully login, both a valid biometric and the correct password must be entered. ####### FMT_MOF_EXT.1 & FMT_SMF_EXT.1 The work profile grants the admin additional controls over the work profile beyond those available to the device as a whole. The primary additional control is over sharing data to and from the work profile. The control over the camera and microphone within the work profile only affects access to those resources inside the work profile, not outside the work profile. If either of these is disabled outside the work profile then they will not be available within the work profile, even if they are enabled. In general, the management functions for the work profile are the same as those of the device as a whole. Specific differences of the impact of a work profile function are noted in Table 8 - Security Management Functions. ####### FTA_SSL_EXT.1 The work profile transitions to its locked state either immediately after a user initiates a lock by pressing the work profile lock button from the notification bar or after a configurable period of inactivity, and as part of that transition, the work profile will display a lock screen to obscure the previous contents. When the work profile is locked, it can still display calendar appointments and other notifications allowed by the administrator to be shown outside the work profile (in the notification area). However, without authenticating first to the work profile, a user cannot perform any related actions based upon these work profile notifications (they cannot respond to emails, calendar appointments, or text messages). The work profile timeout is independent of the TOE timeout and as such can be set to different values. 87 of 87