Qualcomm Technologies, Inc. ### Qualcomm® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy Document Version: 1.0 Last Update: 2026-10-02 Prepared by: atsec information security corporation 4516 Seton Center Pkwy, Suite 250 Austin, TX 78759 https://www.atsec.com Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## Table of Contents | 1 General ....................................................................................................................................................................... | 5 | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| | 1.1 Overview ............................................................................................................................................................ | 5 | | 1.2 Security Levels .................................................................................................................................................... | 5 | | 1.3 Additional Information ...................................................................................................................................... | 5 | | 2 Cryptographic Module Specification ........................................................................................................................ | 7 | | 2.1 Description ......................................................................................................................................................... | 7 | | 2.2 Tested and Vendor Affirmed Module Version and Identification .................................................................. | 9 | | 2.3 Excluded Components ....................................................................................................................................... | 9 | | 2.4 Modes of Operation............................................................................................................................................ | 9 | | 2.5 Algorithms ........................................................................................................................................................ | 10 | | 2.6 Security Function Implementations ................................................................................................................ | 12 | | 2.7 Algorithm Specific Information ...................................................................................................................... | 13 | | 2.7.1 AES XTS .................................................................................................................................................... | 13 | | 2.7.2 Use of TDES .............................................................................................................................................. | 13 | | 2.7.3 Use of SHA-1 ............................................................................................................................................. | 14 | | 2.8 RBG and Entropy ............................................................................................................................................. | 14 | | 2.9 Key Generation ................................................................................................................................................ | 14 | | 2.10 Key Establishment .......................................................................................................................................... | 14 | | 2.11 Industry Protocols .......................................................................................................................................... | 14 | | 3 Cryptographic Module Interfaces ........................................................................................................................... | 15 | | 3.1 Ports and Interfaces .......................................................................................................................................... | 15 | | 4 Roles, Services, and Authentication ....................................................................................................................... | 16 | | 4.1 Authentication Methods .................................................................................................................................. | 16 | | 4.2 Roles .................................................................................................................................................................. 4.3 Approved Services ............................................................................................................................................ | 16 16 | | 4.4 Non-Approved Services ................................................................................................................................... | 20 | | 4.5 External Software/Firmware Loaded ............................................................................................................... | 21 | | 5 Software/Firmware Security ................................................................................................................................... | 22 | | 5.1 Integrity Techniques ........................................................................................................................................ | 22 | | 6 Operational Environment ....................................................................................................................................... | 23 | | 6.1 Operational Environment Type and Requirements ....................................................................................... | 23 | | 6.2 Configuration Settings and Restrictions .......................................................................................................... | 23 | | 7 Physical Security ..................................................................................................................................................... | 24 | 7.1 Mechanisms and Actions Required ................................................................................................................. 24 Page 2 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy 8 Non-Invasive Security ............................................................................................................................................. 25 8.1 Mitigation Techniques ..................................................................................................................................... 25 9 Sensitive Security Parameters Management .......................................................................................................... 26 9.1 Storage Areas .................................................................................................................................................... 26 9.2 SSP Input-Output Methods ............................................................................................................................. 26 9.3 SSP Zeroization Methods ................................................................................................................................. 26 9.4 SSPs ................................................................................................................................................................... 27 9.5 Transitions ........................................................................................................................................................ 28 10 Self-Tests ................................................................................................................................................................ 29 10.1 Pre-Operational Self-Tests ............................................................................................................................. 29 10.2 Conditional Self-Tests .................................................................................................................................... 29 10.3 Periodic Self-Test Information ...................................................................................................................... 30 10.4 Error States ..................................................................................................................................................... 30 10.5 Operator Initiation of Self-Tests .................................................................................................................... 31 11 Life-Cycle Assurance ............................................................................................................................................. 32 11.1 Installation, Initialization, and Startup Procedures ...................................................................................... 32 11.2 Administrator Guidance ................................................................................................................................ 32 11.3 Non-Administrator Guidance ........................................................................................................................ 32 11.4 Design and Rules ............................................................................................................................................ 32 11.5 Maintenance Requirements ........................................................................................................................... 32 11.6 End of Life ...................................................................................................................................................... 32 12 Mitigation of Other Attacks .................................................................................................................................. 34 12.1 Attack List....................................................................................................................................................... 34 Appendix A: Glossary and Abbreviations ................................................................................................................. 35 Appendix B: References ............................................................................................................................................. 36 Page 3 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ### List of Tables Table 1: Security Levels ................................................................................................................................................ 5 Table 2: Tested Module Identification - Hardware .................................................................................................... 9 Table 3: Modes List and Description ......................................................................................................................... 10 Table 4: Approved Algorithms ................................................................................................................................... 11 Table 5: Non-Approved, Not Allowed Algorithms ................................................................................................... 12 Table 6: Security Function Implementations ............................................................................................................ 13 Table 7: Ports and Interfaces ...................................................................................................................................... 15 Table 8: Roles .............................................................................................................................................................. 16 Table 9: Approved Services ........................................................................................................................................ 20 Table 10: Non-Approved Services ............................................................................................................................. 21 Table 11: Mechanisms and Actions Required ........................................................................................................... 24 Table 12: Storage Areas .............................................................................................................................................. 26 Table 13: SSP Input-Output Methods ....................................................................................................................... 26 Table 14: SSP Zeroization Methods ........................................................................................................................... 26 Table 15: SSP Table 1 ................................................................................................................................................. 27 Table 16: SSP Table 2 ................................................................................................................................................. 28 Table 17: Conditional Self-Tests ................................................................................................................................ 30 Table 18: Conditional Periodic Information ............................................................................................................. 30 Table 19: Error States ................................................................................................................................................. 30 ### List of Figures Figure 1: Cryptographic boundary and physical perimeter ........................................................................................ 7 Figure 2: Qualcomm Dragonwing TM Q-6690 with modem ........................................................................................ 8 Figure 3: Qualcomm Dragonwing TM Q-6690 without modem ................................................................................... 8 Figure 4: Snapdragon 6 Gen 4 Mobile Platform .......................................................................................................... 8 Figure 5: Snapdragon 7s Gen 3 Mobile Platform ........................................................................................................ 9 Page 4 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## 1 General ### 1.1 Overview This Security Policy describes the features and design of the module named Qualcomm ® Crypto Engine Core 1 using the terminology contained in the FIPS 140-3 specification. The FIPS 140-3 Security Requirements for Cryptographic Modules specifies the security requirements that will be satisfied by a cryptographic module utilized within a security system protecting sensitive but unclassified information. The NIST/CCCS Cryptographic Module Validation Program (CMVP) validates cryptographic modules to FIPS 140-3. Validated products are accepted by the Federal agencies of both the USA and Canada for the protection of sensitive or designated information. This Non-Proprietary Security Policy may be reproduced and distributed, but only whole and intact and including this notice. Other documentation is proprietary to their authors. ### 1.2 Security Levels Table 1: Security Levels | Section | Title | Security Level | |-----------|-----------------------------------------|------------------| | 1 | General | 1 | | 2 | Cryptographic module specification | 1 | | 3 | Cryptographic module interfaces | 1 | | 4 | Roles, services, and authentication | 1 | | 5 | Software/Firmware security | N/A | | 6 | Operational environment | N/A | | 7 | Physical security | 2 | | 8 | Non-invasive security | N/A | | 9 | Sensitive security parameter management | 1 | | 10 | Self-tests | 1 | | 11 | Life-cycle assurance | 2 | | 12 | Mitigation of other attacks | N/A | | | Overall Level | 1 | ### 1.3 Additional Information In preparing the Security Policy document, the laboratory formatted the vendor-supplied documentation for consolidation without altering the technical statements therein contained. The further refining of the Security Policy document was conducted iteratively throughout the conformance testing, wherein the Security Policy was submitted to the vendor, who would then edit, modify, and add technical contents. The vendor would also supply additional documentation, which the laboratory formatted into the existing Security Policy, and resubmitted to the vendor for their final editing. 1 Qualcomm branded products are products of Qualcomm Technologies, Inc. and/or its subsidiaries. Page 5 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy This document is the non-proprietary FIPS 140-3 Security Policy for version 5.8.2 of the Qualcomm Crypto Engine Core. It has a one-to-one mapping to the [SP 800140B] starting with section B.2.1 named 'General' that maps to section 1 in this document and ending with section B.2.12 named 'Mitigation of other attacks' that maps to section 12 in this document. Page 6 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## 2 Cryptographic Module Specification ### 2.1 Description ####### Purpose and Use: The Qualcomm Crypto Engine Core cryptographic module is a sub-chip hardware module in a single chip embodiment for the purpose of FIPS 140-3 validation. Module Type: Hardware Module Embodiment: Single Chip Module Characteristics: SubChip ####### Cryptographic Boundary: Figure 1: Cryptographic boundary and physical perimeter ####### Tested Operational Environment's Physical Perimeter ( TOEPP): The tested operational environment's physical perimeter is the single chip. Page 7 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy Figure 2: Qualcomm Dragonwing TM Q-6690 with modem Figure 3: Qualcomm Dragonwing TM Q-6690 without modem Figure 4: Snapdragon 6 Gen 4 Mobile Platform Page 8 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy Figure 5: Snapdragon 7s Gen 3 Mobile Platform ### 2.2 Tested and Vendor Affirmed Module Version and Identification ####### Tested Module Identification - Hardware: | Model and/or Part Number | Hardware Version | Firmware Version | Processors | Features | |----------------------------------------------|--------------------|--------------------|--------------|------------| | Qualcomm Dragonwing(TM) Q-6690 with modem | 5.8.2 | N/A | N/A | N/A | | Qualcomm Dragonwing(TM) Q-6690 without modem | 5.8.2 | N/A | N/A | N/A | | Snapdragon® 6 Gen 4 Mobile Platform | 5.8.2 | N/A | N/A | N/A | | Snapdragon® 7s Gen 3 Mobile Platform | 5.8.2 | N/A | N/A | N/A | Table 2: Tested Module Identification - Hardware ### 2.3 Excluded Components There are no excluded components. ### 2.4 Modes of Operation ####### Modes List and Description: | Mode Name | Description | Types of Services | Status Indicator | |----------------------------|-----------------------------------------------------------------|---------------------|------------------------------------------------------| | Approved mode of operation | Automatically entered whenever an approved service is requested | Approved | Equivalent to the indicator of the requested service | Page 9 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy Table 3: Modes List and Description | Mode Name | Description | Types of Services | Status Indicator | |--------------------------------|--------------------------------------------------------------------|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------| | Non-approved mode of operation | Automatically entered whenever a non-approved service is requested | Non- Approved | Non-approved services are not explicitly indicated. The absence of an explicit indicator is an implicit indicator of non- approved services. | The Qualcomm Crypto Engine Core supports two modes of operation: approved mode and a non-approved mode. All CSPs are kept separate between the two modes through the use of a key policy management system. ####### Mode Change Instructions and Status: The switching of modes of operation is implicit depending on the service invoked, but the approved services are explicitly identified by an indicator. The Qualcomm Crypto Engine Core enters the approved mode after successful completion of the conditional algorithm self-tests. When the operator invokes a non-approved service, the Qualcomm Crypto Engine Core implicitly switches to its non-approved mode. ### 2.5 Algorithms ####### Approved Algorithms: | Algorithm | CAVP Cert | Properties | Reference | |------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| | AES-CBC-CS2 | A6506 | Direction - decrypt, encrypt Key Length - 128, 256 Payload Length - Payload Length: 128- 65536 Increment 8 | SP 800-38A | | AES-CBC, AES-ECB | A6506 | Direction - Decrypt, Encrypt Key Length - 128, 256 | SP 800-38A | | AES-CCM | A6506 | Key Length - 128, 256 Tag Length - 112, 128, 32, 48, 64, 80, 96 IV Length - IV Length: 56, 64, 72, 80, 88, 96, 104 Payload Length - Payload Length: 0, 256 AAD Length - AAD Length: 256, 65536 | SP 800-38C | | AES-CMAC | A6506 | Direction - Generation, Verification Key Length - 128, 256 MAC Length - MAC Length: 128 Message Length - Message Length: 8- 524288 Increment 8 | SP 800-38B | | AES-CTR | A6506 | Direction - Decrypt, Encrypt Key Length - 128, 256 Payload Length - Payload Length: 128 Supports Counter larger than maximum | SP 800-38A | Page 10 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy | Algorithm | CAVP Cert | Properties | Reference | |-----------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------| | | | value - Yes Incremental Counter - Yes Counter Tests Performed - Yes | | | AES-XTS Testing Revision 2.0 | A6506 | Direction - Decrypt, Encrypt Key Length - 128, 256 Payload Length - Payload Length: 128- 65536 Increment 8 Tweak Mode - Hex Data Unit Length Matches Payload Length - Yes | SP 800-38E | | HMAC-SHA-1 | A6506 | MAC - MAC: 160 Key Length - Key Length: 512 | FIPS 198-1 | | HMAC-SHA2-256, HMAC- SHA3-256 | A6506 | MAC - MAC: 256 Key Length - Key Length: 512 | FIPS 198-1 | | HMAC-SHA2-384, HMAC- SHA3-384 | A6506 | MAC - MAC: 384 Key Length - Key Length: 512 | FIPS 198-1 | | HMAC-SHA2-512, HMAC- SHA3-512 | A6506 | MAC - MAC: 512 Key Length - Key Length: 512 | FIPS 198-1 | | HMAC-SHA3-224 | A6506 | MAC - MAC: 224 Key Length - Key Length: 512 | FIPS 198-1 | | SHA-1, SHA2-256, SHA2-384, SHA2-512 | A6506 | Message Length - Message Length: 0- 65536 Increment 8 | FIPS 180-4 | | SHA3-224, SHA3-256, SHA3- 384, SHA3-512 | A6506 | Message Length - Message Length: 0- 65536 Increment 8 | FIPS 202 | | TDES-CBC, TDES-ECB | A6506 | Direction - Decrypt, Encrypt Keying Option - 1 | SP 800-67 Rev. 2 | ####### Vendor-Affirmed Algorithms: N/A for this module. ####### Non-Approved, Allowed Algorithms: N/A for this module. ####### Non-Approved, Allowed Algorithms with No Security Claimed: N/A for this module. ####### Non-Approved, Not Allowed Algorithms: Page 11 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy Table 5: Non-Approved, Not Allowed Algorithms | Name | Use and Function | |--------------------------------------------------|-----------------------------------------------------------| | AES-GCM (external IV) | encryption, decryption | | DES-CBC | encryption, decryption | | DES-ECB | encryption, decryption | | TDES (two independent keys) | encryption, decryption | | TDES Encryption (three independent keys) | encryption | | HMAC SHA-1 with key size other than 512 bits | message authentication code | | HMAC SHA2-256 with key sizes other than 512 bits | message authentication code | | HMAC SHA2-384 with key sizes other than 512 bits | message authentication code | | HMAC SHA2-512 with key sizes other than 512 bits | message authentication code | | HMAC SHA3-224 with key sizes other than 512 bits | message authentication code | | HMAC SHA3-256 with key sizes other than 512 bits | message authentication code | | HMAC SHA3-384 with key sizes other than 512 bits | message authentication code | | HMAC SHA3-512 with key sizes other than 512 bits | message authentication code | | AEAD-SHA-1 AES-CBC | encryption, decryption (with message authentication code) | | AEAD-SHA-1 AES-CTR | encryption, decryption (with message authentication code) | | AEAD-SHA-1 DES-CBC | encryption, decryption (with message authentication code) | | AEAD-SHA-1 TDES-CBC | encryption, decryption (with message authentication code) | | SM3 | hashing | | SM4 | encryption, decryption | ### 2.6 Security Function Implementations | Name | Type | Description | Properties | Algorithms | |--------------|-----------|---------------------|--------------|---------------------------------------| | AES-CBC | BC-UnAuth | AES in CBC mode | | AES-CBC: (A6506) | | AES-CBC- CS2 | BC-UnAuth | AES in CBC-CS2 mode | | AES-CBC-CS2: (A6506) | | AES-CCM | BC-Auth | AES in CCM mode | | AES-CCM: (A6506) | | AES-CMAC | MAC | AES in CMAC mode | | AES-CMAC: (A6506) | | AES-CTR | BC-UnAuth | AES in CTR mode | | AES-CTR: (A6506) | | AES-ECB | BC-UnAuth | AES in ECB mode | | AES-ECB: (A6506) | | AES-XTS | BC-UnAuth | AES in XTS mode | | AES-XTS Testing Revision 2.0: (A6506) | Page 12 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy | Name | Type | Description | Properties | Algorithms | |-----------------------|-------------------|--------------------------------------|----------------------|------------------------| | HMAC-SHA- 1 | MAC | HMAC with SHA-1 | | HMAC-SHA-1: (A6506) | | HMAC- SHA2-256 | MAC | HMAC with SHA2- 256 | | HMAC-SHA2-256: (A6506) | | HMAC- SHA2-384 | MAC | HMAC with SHA2- 384 | | HMAC-SHA2-384: (A6506) | | HMAC- SHA2-512 | MAC | HMAC with SHA2- 512 | | HMAC-SHA2-512: (A6506) | | HMAC- SHA3-224 | MAC | HMAC with SHA3- 224 | | HMAC-SHA3-224: (A6506) | | HMAC- SHA3-256 | MAC | HMAC with SHA3- 256 | | HMAC-SHA3-256: (A6506) | | HMAC- SHA3-384 | MAC | HMAC with SHA3- 384 | | HMAC-SHA3-384: (A6506) | | HMAC- SHA3-512 | MAC | HMAC with SHA3- 512 | | HMAC-SHA3-512: (A6506) | | SHA-1 | SHA | SHA-1 | | SHA-1: (A6506) | | SHA2-256 | SHA | SHA2-256 | | SHA2-256: (A6506) | | SHA2-384 | SHA | SHA2-384 | | SHA2-384: (A6506) | | SHA2-512 | SHA | SHA2-512 | | SHA2-512: (A6506) | | SHA3-224 | SHA | SHA3-224 | | SHA3-224: (A6506) | | SHA3-256 | SHA | SHA3-256 | | SHA3-256: (A6506) | | SHA3-384 | SHA | SHA3-384 | | SHA3-384: (A6506) | | SHA3-512 | SHA | SHA3-512 | | SHA3-512: (A6506) | | TDES-ECB (Legacy Use) | BC- UnAuthDecrypt | TDES-ECB with three independent keys | Direction:Decryption | TDES-ECB: (A6506) | | TDES-CBC (Legacy Use) | BC- UnAuthDecrypt | TDES-CBC with three independent keys | Direction:Decryption | TDES-CBC: (A6506) | Table 6: Security Function Implementations ### 2.7 Algorithm Specific Information #### 2.7.1 AES XTS The AES algorithm in XTS mode is only used for the cryptographic protection of data on storage devices, in compliance with [SP800-38E]. The module ensures that the length of a single data unit encrypted with the XTS-AES does not exceed 2² ⁰ AES blocks, that is 16MB of data. To meet the requirement stated in IG C.I, the module implements a check that ensures, before performing any cryptographic operation, that the two AES keys used in AES XTS mode are not identical. #### 2.7.2 Use of TDES Page 13 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy Threekey TDES decryption is approved only for Legacy Use. Algorithms designated as 'Legacy' can only be used on data that was generated prior to the Legacy Date specified in FIPS 140-3 IG C.M. #### 2.7.3 Use of SHA-1 The SHA1 algorithm is available 'as is' in Approved mode. Its use is approved only for message digests and HMAC-based message authentication. The module does not support any other approved use of SHA-1. Starting in 2031, all uses of SHA-1 will be non-approved. ### 2.8 RBG and Entropy N/A for this module. ### 2.9 Key Generation The module does not provide any key generation services. ### 2.10 Key Establishment The module does not provide any key establishment services. ### 2.11 Industry Protocols The module does not implement any industry protocols, or provide services designed to be used as part of any industry protocol. Page 14 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## 3 Cryptographic Module Interfaces ### 3.1 Ports and Interfaces | Physical Port | Logical Interface(s) | Data That Passes | |----------------------------|------------------------|-------------------------------------------| | Data In FIFO and Registers | Data Input | All input data | | Data Out FIFO | Data Output | All data output except Status information | | Registers | Control Input | Command input | | Registers | Status Output | Status information | | Physical power connector | Power | Power from SoC power port | Table 7: Ports and Interfaces The Qualcomm Crypto Engine Core does not implement a Control Output interface. Page 15 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## 4 Roles, Services, and Authentication ### 4.1 Authentication Methods N/A for this module. ### 4.2 Roles | Name | Type | Operator Type | Authentication Methods | |----------------|--------|-----------------|--------------------------| | Crypto Officer | Role | CO | None | Table 8: Roles The module only supports the Crypto Officer (CO) role that is assumed implicitly when a service is requested from the module. ### 4.3 Approved Services | Name | Description | Indicator | Inputs | Outputs | Securi ty Funct ions | SSP Acc ess | |-----------------|-------------------------|---------------------------------------------|----------------------|--------------------------|--------------------------------------------------------|---------------------------------| | AES Encrypti on | Perform data encryption | CRYPTO0_CRYPT O_STATUS4 bits 16-18 set to 0 | AES Key, Plaint ext | Ciphertext, Success/Fail | AES- CBC AES- CBC- CS2 AES- CCM AES- CTR AES- ECB AES- | Cry pto Offi cer - AES key: W,E | | AES Decrypti on | Perform data decryption | CRYPTO0_CRYPT O_STATUS4 bits 16-18 set to 0 | AES Key, Cipher text | Plaintext, Success/Fail | XTS AES- CBC AES- CBC- CS2 AES- CCM AES- CTR AES- | Cry pto Offi cer - AES key: W,E | Page 16 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy | Name | Description | Indicator | Inputs | Outputs | Securi ty Funct ions | SSP Acc ess | |--------------------------------|-----------------------------------------------------------------------------------------------|---------------------------------------------|------------------------------|--------------------------|--------------------------------------------|------------------------------------------| | | | | | | ECB AES- XTS | | | AES Authenti cated Encrypti on | Perform data encryption | CRYPTO0_CRYPT O_STATUS4 bits 16-18 set to 0 | AES Key, Plaint ext | Ciphertext, Success/Fail | AES- CCM | Cry pto Offi cer - AES key: W,E | | AES Authenti cated Decrypti on | Perform data decryption | CRYPTO0_CRYPT O_STATUS4 bits 16-18 set to 0 | AES Key, Cipher text | Plaintext, Success/Fail | AES- CCM | Cry pto Offi cer - AES key: W,E | | CMAC Message Authenti cation | Message Authentication | CRYPTO0_CRYPT O_STATUS4 bit 29 set to 0 | AES Key, Input data | CMAC value | AES- CMA C | Cry pto Offi cer - AES key: W,E | | TDES Decrypti on (Legacy Use) | Decrypt data which was encrypted with 3- key TDES prior to the sunset date provided in IG C.M | CRYPTO0_CRYPT O_STATUS4 bit 19 set to 0 | Triple -DES key, cipher text | Plaintext | TDES -ECB (Lega cy Use) TDES -CBC (Lega cy | Cry pto Offi cer - Trip le- DES Key: W,E | | HMAC Message Authenti cation | Message Authentication | CRYPTO0_CRYPT O_STATUS4 bits 25-28 set to 0 | HMA C Key, input data | HMAC value | Use) HMA C- SHA- 1 HMA C- SHA2 | Cry pto Offi cer - HM AC | Page 17 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy | Name | Description | Indicator | Inputs | Outputs | Securi ty Funct ions | SSP Acc ess | |-------------|---------------------------------------------------|---------------------------------------------|------------|----------------------------------------|------------------------------------------------------------------------------------------------------------|------------------| | | | | | | -256 HMA C- SHA2 -384 HMA C- SHA2 -512 HMA C- SHA3 -224 HMA C- SHA3 -256 HMA C- SHA3 -384 HMA C- SHA3 -512 | key: W,E | | Hash | Hashing | CRYPTO0_CRYPT O_STATUS4 bits 21-24 set to 0 | Input data | Hash output | SHA- 1 SHA2 -256 SHA2 -384 SHA2 -512 SHA3 -224 SHA3 -256 SHA3 -384 SHA3 -512 | Cry pto Offi cer | | Show Status | Return code read from CRYPTO0_CRYPTO_B IST_STATUS | None | N/A | Zero (operational) or non-zero (error) | None | Cry pto Offi cer | Page 18 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy | Name | Description | Indicator | Inputs | Outputs | Securi ty Funct ions | SSP Acc ess | |----------------------------|--------------------------------------------------------------------------|-------------|---------------------|------------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------------------| | Self-Test | Self-Tests are executed automatically when device is booted or restarted | None | None | Self-test Success/Fail | AES- CCM AES- CMA C AES- ECB HMA C- SHA- 1 HMA C- SHA2 -256 HMA C- SHA2 -512 HMA C- SHA3 -512 TDES -ECB (Lega cy Use) | Cry pto Offi cer | | Zeroizati on | Zeroizes all SSPs | None | None | None | None | Cry pto Offi cer - AES key: Z - HM | | Configur e keys for use by | Configures the keys for Crypto Officer role | None | AES Key, HMA C Key, | Success/Fail | None | AC key: Z Cry pto Offi cer | Page 19 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy Table 9: Approved Services | Name | Description | Indicator | Inputs | Outputs | Securi ty Funct ions | SSP Acc ess | |-----------------------------|------------------------------------------|-------------|-----------------|-------------------------------------------------------------------------------------------------------|------------------------|---------------------------------------------------| | Crypto Officer | | | Triple -DES Key | | | - AES key: W - HM AC key: W - Trip le- DES Key: W | | Show identifier and version | Show the module's identifier and version | None | None | Module identifier and version read from registers CRYPTO0_CRYPT O_FIPS_ID and CRYPTO0_CRYPT O_VERSION | None | Cry pto Offi cer | - G = Generate: The module generates or derives the SSP. - E = Execute: The module uses the SSP in performing a cryptographic operation. - R = Read: The SSP is read from the module (e.g., the SSP is output). - W = Write: The SSP is updated, imported, or written to the module. - Z = Zeroize: The module zeroizes the SSP. ### 4.4 Non-Approved Services | Name | Description | Algorithms | Role | |------------|--------------------------------------------|----------------------------------------------------------------------------------------------------------------|--------| | Encryption | Encrypts data using symmetric cryptography | AES-GCM (external IV) DES-CBC DES-ECB TDES (two independent keys) TDES Encryption (three independent keys) SM4 | CO | | Decryption | Decrypts data using symmetric cryptography | AES-GCM (external IV) DES-CBC DES-ECB | CO | Page 20 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy Table 10: Non-Approved Services | Name | Description | Algorithms | Role | |--------------------------------------------|--------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| | | | TDES (two independent keys) SM4 | | | Hash | Hashing algorithm | SM3 | CO | | Message Authentication | Computes the MAC value of data | HMAC SHA-1 with key size other than 512 bits HMAC SHA2-256 with key sizes other than 512 bits HMAC SHA2-384 with key sizes other than 512 bits HMAC SHA2-512 with key sizes other than 512 bits HMAC SHA3-224 with key sizes other than 512 bits HMAC SHA3-256 with key sizes other than 512 bits HMAC SHA3-384 with key sizes other than 512 bits HMAC SHA3-512 with key sizes other than 512 bits | CO | | Authenticated Encryption/Decryption [AEAD] | Encrypts or decrypts data using symmetric cryptography | AEAD-SHA-1 AES-CBC AEAD-SHA-1 AES-CTR AEAD-SHA-1 DES-CBC AEAD-SHA-1 TDES-CBC | CO | ### 4.5 External Software/Firmware Loaded Not Applicable. No external software or firmware is loaded. Page 21 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## 5 Software/Firmware Security ### 5.1 Integrity Techniques The Qualcomm Crypto Engine Core does not have any software or firmware components. Therefore, this section is not applicable. Page 22 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## 6 Operational Environment ### 6.1 Operational Environment Type and Requirements ####### Type of Operational Environment: Non-Modifiable How Requirements are Satisfied: The Qualcomm Crypto Engine Core is a single chip hardware module. The procurement, build and configuring procedure are controlled. Therefore, the operational environment is considered non-modifiable. ### 6.2 Configuration Settings and Restrictions N/A for this module. Page 23 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## 7 Physical Security ### 7.1 Mechanisms and Actions Required Table 11: Mechanisms and Actions Required | Mechanism | Inspection Frequency | Inspection Guidance | |------------------------|------------------------|-----------------------| | Tamper evident coating | N/A | N/A | The Qualcomm Crypto Engine Core is a sub-chip enclosed in the platforms that are listed in Table 2 that are made up of production grade component and conform to the Level 2 requirements for physical security. At the time of manufacturing, the die is embedded within a printed circuit board (PCB), which prevents visibility into the internal circuity of the Qualcomm Crypto Engine Core. The layering process which is used to embed the die into the PCB also prevents tampering of the physical components without leaving tamper evidence. The Qualcomm Crypto Engine Core is further protected by being enclosed in commercial off the shelf mobile device utilizing production grade commercially available components and that the mobile device enclosure that completely surrounds the Qualcomm Crypto Engine Core. There are no steps required to ensure that physical security is maintained. Page 24 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## 8 Non-Invasive Security ### 8.1 Mitigation Techniques The Qualcomm Crypto Engine Core does not support any non-invasive security techniques. Therefore, this section is not applicable. Page 25 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## 9 Sensitive Security Parameters Management ### 9.1 Storage Areas Table 12: Storage Areas | Storage Area Name | Description | Persistence Type | |---------------------|----------------------------------------------------------------------------|--------------------| | Hardware FIFO | Temporary storage for SSPs used by the module as part of service execution | Dynamic | | Registers | Temporary storage for SSPs used by the module as part of service execution | Dynamic | The Qualcomm Crypto Engine Core stores all SSPs internally (the storage is non-persistent). In addition, all SSPs are stored write-only and are not readable outside of the Qualcomm Crypto Engine Core. Therefore, any attempt to read SSPs are blocked by the Qualcomm Crypto Engine Core control logic, which will return zeros instead of an SSP. ### 9.2 SSP Input-Output Methods Table 13: SSP Input-Output Methods | Name | From | To | Format Type | Distribution Type | Entry Type | SFI or Algorithm | |-----------------|--------------------------------------|-----------------------------|---------------|---------------------|--------------|--------------------| | Input parameter | Caller within the physical perimeter | Hardware FIFO and Registers | Plaintext | N/A | N/A | | The SSPs are provided from the caller within the tested operation environment's physical perimeter (TOEPP) hardware via a single-chip TOEPP path, which is not considered SSP establishment by Table 1 of FIPS 140-3 IG 9.5.A. SSPs can only be written to the Qualcomm Crypto Engine Core by a caller within the TOEPP writing either to the key registers or to the FIFOs assigned to the particular use case. Any attempt to write to a non-assigned FIFO is blocked. The Qualcomm Crypto Engine Core ensures that there is no means to obtain CSP or key data from the Qualcomm Crypto Engine Core by placing the CSPs into registers which are write-only for outside entities. This action prevents an entity interacting with the Qualcomm Crypto Engine Core from being able to read the CSPs. ### 9.3 SSP Zeroization Methods Table 14: SSP Zeroization Methods | Zeroization Method | Description | Rationale | Operator Initiation | |----------------------|---------------------------|------------------------------------------------------|--------------------------------------------------------------------------| | Power-off | All SSPs will be zeroized | The registers holding the SSPs are set to all zeroes | Operator can initiate this zeroization method by powering off the module | The successful power-off indicates that all SSPs have been zeroized. Data output is inhibited during this zeroization process. Page 26 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ### 9.4 SSPs | Name | Description | Size - Strength | Type - Category | Generated By | Established By | Used By | |-----------------|---------------------------------------------------------------------------|-----------------------------------|---------------------|----------------|------------------|----------------------------------------------------------------------------------------------------------------------| | AES key | Symmetric key used for encryption, decryption, and message authentication | 128 or 256 bits - 128 or 256 bits | Symmetric key - CSP | | | AES-CBC AES-CBC- CS2 AES-CCM AES- CMAC AES-CTR AES-ECB AES-XTS | | HMAC key | Symmetric key used for message authentication | 512 bits - 256 bits | Symmetric key - CSP | | | HMAC- SHA-1 HMAC- SHA2-256 HMAC- SHA2-384 HMAC- SHA2-512 HMAC- SHA3-224 HMAC- SHA3-256 HMAC- SHA3-384 HMAC- SHA3-512 | | Triple- DES Key | Symmetric key used for legacy data decryption | 168 bits - 112 bits | Symmetric key - CSP | | | TDES-ECB (Legacy Use) TDES- CBC (Legacy Use) | Table 15: SSP Table 1 | Name | Input - Output | Storage | Storage Duration | Zeroization | Related SSPs | |----------|------------------|---------------------------------------------|-----------------------------|---------------|----------------| | AES key | Input parameter | Registers:Plaintext Hardware FIFO:Plaintext | Until module is powered off | Power-off | | | HMAC key | Input parameter | Registers:Plaintext Hardware FIFO:Plaintext | Until module is powered off | Power-off | | Page 27 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy | Name | Input - Output | Storage | Storage Duration | Zeroization | Related SSPs | |----------------|------------------|---------------------------------------------|-----------------------------|---------------|----------------| | Triple-DES Key | Input parameter | Hardware FIFO:Plaintext Registers:Plaintext | Until module is powered off | Power-off | | Table 16: SSP Table 2 ### 9.5 Transitions Beginning in 2031, - keys providing 112 bits of security strength shall no longer be used to apply cryptographic protection and are limited to legacy use for processing, as specified in Table 4 of NIST SP 800-57 Part 1 Rev. 5. - The SHA-1 algorithm as implemented by the module will be non-approved for all purposes. Page 28 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## 10 Self-Tests ### 10.1 Pre-Operational Self-Tests N/A for this module. The Qualcomm Crypto Engine Core is solely implemented in hardware and does not have any software or firmware components. As such, the module does not perform any pre-operational software/firmware integrity test. Instead, the module performs the CASTs listed in Conditional Self-tests section. ### 10.2 Conditional Self-Tests | Algorithm or Test | Test Properties | Test Method | Test Type | Indicator | Details | Conditions | |------------------------------|-------------------|---------------|-------------|---------------------------------------------------------------|--------------------------------------|----------------------------------| | AES-CCM (A6506) - Encryption | 256 bit key | KAT | CAST | Module becomes operational and services are available for use | Encryption | Performed during module power-up | | AES-CCM (A6506) - Decryption | 256 bit key | KAT | CAST | Module becomes operational and services are available for use | Decryption | Performed during module power-up | | AES-ECB (A6506) - Encryption | 256 bit key | KAT | CAST | Module becomes operational and services are available for use | Encryption | Performed during module power-up | | AES-ECB (A6506) - Decryption | 256 bit key | KAT | CAST | Module becomes operational and services are available for use | Decryption | Performed during module power-up | | AES-CMAC (A6506) | 256 bit key | KAT | CAST | Module becomes operational and services are available for use | MAC tag computation and verification | Performed during module power-up | | HMAC-SHA-1 (A6506) | 512 bit key | KAT | CAST | Module becomes operational and services are available for use | MAC tag computation and verification | Performed during module power-up | | HMAC-SHA2- 256 (A6506) | 512 bit key | KAT | CAST | Module becomes operational and services are available for use | MAC tag computation and verification | Performed during module power-up | | HMAC-SHA2- 512 (A6506) | 512 bit key | KAT | CAST | Module becomes operational and services are available for use | MAC tag computation and verification | Performed during module power-up | Page 29 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy Table 17: Conditional Self-Tests | Algorithm or Test | Test Properties | Test Method | Test Type | Indicator | Details | Conditions | |------------------------|-------------------|---------------|-------------|---------------------------------------------------------------|--------------------------------------|----------------------------------| | HMAC-SHA3- 512 (A6506) | 512 bit key | KAT | CAST | Module becomes operational and services are available for use | MAC tag computation and verification | Performed during module power-up | | TDES-ECB (A6506) | 168 bit key | KAT | CAST | Module becomes operational and services are available for use | Decryption (Legacy) | Performed during module power-up | Cryptographic algorithm self-tests (CASTs) are automatically performed during power-up of the Qualcomm Crypto Engine Core without any operator intervention. During CAST execution, no services are available, and data input and output are inhibited by the Qualcomm Crypto Engine Core control logic. If any CAST fails, the module will enter the error state. ### 10.3 Periodic Self-Test Information N/A for this module. Table 18: Conditional Periodic Information | Algorithm or Test | Test Method | Test Type | Period | Periodic Method | |------------------------------|---------------|-------------|-----------|---------------------------| | AES-CCM (A6506) - Encryption | KAT | CAST | On demand | Manually by power cycling | | AES-CCM (A6506) - Decryption | KAT | CAST | On demand | Manually by power cycling | | AES-ECB (A6506) - Encryption | KAT | CAST | On demand | Manually by power cycling | | AES-ECB (A6506) - Decryption | KAT | CAST | On demand | Manually by power cycling | | AES-CMAC (A6506) | KAT | CAST | On demand | Manually by power cycling | | HMAC-SHA-1 (A6506) | KAT | CAST | On demand | Manually by power cycling | | HMAC-SHA2-256 (A6506) | KAT | CAST | On demand | Manually by power cycling | | HMAC-SHA2-512 (A6506) | KAT | CAST | On demand | Manually by power cycling | | HMAC-SHA3-512 (A6506) | KAT | CAST | On demand | Manually by power cycling | | TDES-ECB (A6506) | KAT | CAST | On Demand | Manually by power cycling | ### 10.4 Error States Table 19: Error States | Name | Description | Conditions | Recovery Method | Indicator | |--------|-----------------------------------------------------------------------------------|--------------|-------------------|-------------------------------------------------| | Error | No cryptographic operation can be performed. No data input or output is possible. | KAT failure | Power cycling | CRYPTO0_CRYPTO_BIST_STATUS register is non-zero | Page 30 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy While in the error state, all data input and output are prohibited, and no further cryptographic operation is allowed. The Qualcomm Crypto Engine Core control logic enforces this prohibition by preventing external usage and inhibiting data output while the module is in the error state. In addition, neither caller-induced nor internal errors reveal any sensitive material to callers. Once the Qualcomm Crypto Engine Core is in the error state, it will only respond to a reset signal, which an external operator may invoke by power cycling the SoC which contains the module. A reset will cause the Qualcomm Crypto Engine Core to re-execute its CASTs. The Qualcomm Crypto Engine Core will remain unavailable until it passes its CASTs. ### 10.5 Operator Initiation of Self-Tests The operator can initiate the cryptographic algorithm self-tests by power cycling the module. Page 31 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## 11 Life-Cycle Assurance ### 11.1 Installation, Initialization, and Startup Procedures The Qualcomm ® Crypto Engine Core is a sub-chip module that runs on the chips listed in Table 2. The vendor uses a trusted delivery courier to transport the SoC to their customers. On the reception of the SoC, the operator shall first check all sides of the box to verify that it has not been tampered with during the shipment. Then, after opening the box the operator shall verify that the moisture barrier bag is still sealed and does not present any trace of tampering. Finally, after retrieving the SoC, the operator shall perform a visual inspection of the external package of the module; it should look like the picture in Figure 2. If one of these verifications fails, the operator shall contact their Qualcomm Technologies' representative who released the delivery before operating the module. Once the product is received by the customer and powered up, the tests defined in the Self-Tests section will be executed automatically and without operator intervention. ### 11.2 Administrator Guidance To verify the module's name and version, an administrator may invoke the module's 'Show identifier and version' service by reading the CRYPTO0_CRYPTO_FIPS_ID and CRYPTO0_CRYPTO_VERSION registers. The CRYPTO0_CRYPTO_FIPS_ID register must hold the value 0x00000001, which identifies the module as the Qualcomm Crypto Engine Core. The CRYPTO0_CRYPTO_VERSION register must hold the value 0x05080002, representing the module version 5.8.2. For using the cryptographic services of the Qualcomm Crypto Engine Core, the manual for the Qualcomm Crypto Engine Core covers the description of the register set as well as the use of the FIFOs channels should be used. ### 11.3 Non-Administrator Guidance There is no specific non-Administrator guidance required for the module. ### 11.4 Design and Rules N/A Therefore no specific design or rules to be followed. ### 11.5 Maintenance Requirements N/A There are no maintenance requirements. ### 11.6 End of Life Page 32 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy Because the module does not have persistent storage, all SSPs are zeroized and the module is securely sanitized when powered down. Thus, the module may be distributed to other operators or disposed of after each power off. Page 33 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## 12 Mitigation of Other Attacks ### 12.1 Attack List The Qualcomm Crypto Engine Core does not implement security mechanisms to mitigate other attacks. Page 34 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## Appendix A: Glossary and Abbreviations AES Advanced Encryption Standard CBC Cipher Block Chaining CCCS Canadian Centre for Cybersecurity CCM Counter with Cipher Block Chaining-Message Authentication Code CMVP Cryptographic Module Validation Program CSP Critical Security Parameter DES Data Encryption Standard FIFO First In, First Out FIPS Federal Information Processing Standards Publication HMAC Hash Message Authentication Code KAT Known Answer Test NIST National Institute of Science and Technology OTP One-Time Programmable SHA Secure Hash Algorithm SoC System on a Chip XTS XEX Tweakable Block Cipher with Ciphertext Stealing Page 35 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. Qualcomm ® Crypto Engine Core FIPS 140-3 Non-Proprietary Security Policy ## Appendix B: References | FIPS 140-3 | FIPS PUB 140-3 - Security Requirements For Cryptographic Modules March 2019 https://doi.org/10.6028/NIST.FIPS.140-3 | |---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | FIPS 140-3 IG | Implementation Guidance for FIPS PUB 140-3 and the Cryptographic Module Validation Program April 2025 https://csrc.nist.gov/Projects/cryptographic-module-validation-program/fips-140-3-ig- announcements | | FIPS 197 | Advanced Encryption Standard (AES) May 2023 https://doi.org/10.6028/NIST.FIPS.197-upd1 | | SP 800-38A | Recommendation for Block Cipher Modes of Operation Methods and Techniques December 2001 https://doi.org/10.6028/NIST.SP.800-38A | | SP 800-38B | Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication May 2005 https://doi.org/10.6028/NIST.SP.800-38B | | SP 800-38C | Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality May 2004 https://doi.org/10.6028/NIST.SP.800-38C | | SP 800-38E | Recommendation for Block Cipher Modes of Operation: The XTS-AES Mode for Confidentiality of Storage Devices January 2010 https://doi.org/10.6028/NIST.SP.800-38E | | SP 800-67r2 | Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher November 2017 https://doi.org/10.6028/NIST.SP.800-67r2 | | FIPS 180-4 | Secure Hash Standard (SHS) August 2015 https://doi.org/10.6028/NIST.FIPS.180-4 | | FIPS 202 | SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions August 2015 https://doi.org/10.6028/NIST.FIPS.202 | | FIPS 198-1 | The Keyed-Hash Message Authentication Code (HMAC) July 2008 https://doi.org/10.6028/NIST.FIPS.198-1 | Page 36 of 36 © 2025 Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved.