This page was not yet optimized for use on mobile devices.

ST Engineering & i-Engine SSID Applet on NXP P71D600

Certificate details

Certificate ID	#5360
Status	active
Validation dates	30.06.2026
Sunset date	29-06-2031
Standard	FIPS 140-3
Security level	3
Type	Hardware
Embodiment	SingleChip
Caveat	No assurance of minimum security of SSPs (e.g., keys, bit strings) that are externally loaded, or of SSPs established with externally loaded SSPs.
Exceptions	Operational environment: N/A Physical security: Level 4
Description	The Module is composed of a GlobalPlatform operational environment and a single Java Card applet – the SSID, running on the NXP P71D600 chip.
Vendor	ST Engineering Urban Solutions Ltd. and i-Engine Pte Ltd. http://www.stengg.com
Lab	Acumen Security
Algorithms	AES-CBCA2713 AES-CCMA2713 AES-CMACA2713 AES-CTRA2713 AES-ECBA2713 Counter DRBGA2713 ECDSA KeyGen (FIPS186-5)A6534 ECDSA SigGen (FIPS186-5)A6534 ECDSA SigVer (FIPS186-5)A6534 HMAC-SHA-1A2713 KAS-ECC-SSC Sp800-56Ar3A2713 KDA HKDF Sp800-56Cr1A2713 KDF SP800-108A2713 RSA Decryption Primitive Sp800-56Br2A5911 RSA KeyGen (FIPS186-5)A6536 RSA SigGen (FIPS186-5)A6535 RSA SigVer (FIPS186-5)A6535 SHA-1A2713 SHA2-256A2713 SHA2-512A2713
References	This certificate's webpage directly references 0 certificates, transitively this expands into 0 certificates.

Certificate

Webpage

Security policy

Security policy PDF TXT

Extracted keywords

Symmetric Algorithms

AES-256, AES, AES-, AES-128, CAST, Triple-DES, SEED, HMAC, KMAC, CMAC

Asymmetric Algorithms

ECDH, ECDSA, ECC

Hash functions

SHA-1, SHA1

Schemes

MAC, Key Agreement

Randomness

DRBG, RBG

Elliptic Curves

P-224, P-256, P-384, P-521

Block cipher modes

ECB, CBC

Operating System name

JCOP 4

Trusted Execution Environments

PSP, SSC

Vendor

NXP, NXP Semiconductors

Security level

Level 3, Level 4

Side-channel analysis

SPA, DPA, Fault Induction, fault induction

Standards

FIPS 140-3, FIPS140-3, FIPS186-5, FIPS 186-5, FIPS 198-1, FIPS 180-4, SP 800-38A, SP 800-38C, SP 800-38B, SP 800-90A, SP 800-56A, SP 800-56C, SP 800-108, SP 800-56B, SP 800-38F, SP 800-140C, NIST SP 800-90B, PKCS1, RFC 3394, SCP03

Author	Prasiddhi Tembulkar Intertek
Creation date	D:20260626082852-04'00'
Modification date	D:20260626082852-04'00'
Pages	61
Creator	Microsoft® Word for Microsoft 365
Producer	Microsoft® Word for Microsoft 365

Automated analysis

Automated inference - use with caution

All attributes shown in this section (e.g., links between certificates, products, vendors, and known CVEs) are generated by automated heuristics and have not been reviewed by humans. These methods can produce false positives or false negatives and should not be treated as definitive without independent verification. This applies equally to the Cross-references section below. If you want to know more about how this data is computed and how reliable it is, see our documentation on automated analysis. If you believe any information here is inaccurate or harmful, please submit feedback.

No automatically derived data are available in this section.

Cross-references

No references are available for this certificate.

Processing updates

06.10.2026

The certificate data changed.
Certificate changed

The PDF extraction data was updated.

The keywords property was updated, with the {'fips_security_level': {'__update__': {'Level': {'__update__': {'Level 3': 3}}}}, 'crypto_scheme': {'__update__': {'KA': {'__update__': {'Key Agreement': 4}}}}, 'randomness': {'__update__': {'PRNG': {'__update__': {'DRBG': 20}}}}} data.
05.10.2026

The certificate data changed.
Certificate changed

The PDF extraction data was updated.

The keywords property was updated, with the {'fips_security_level': {'__update__': {'Level': {'__update__': {'Level 3': 2}}}}, 'crypto_scheme': {'__update__': {'KA': {'__update__': {'Key Agreement': 5}}}}, 'randomness': {'__update__': {'PRNG': {'__update__': {'DRBG': 21}}}}} data.
24.09.2026

The certificate data changed.
Certificate changed

The PDF extraction data was updated.

The keywords property was updated, with the {'fips_security_level': {'__update__': {'Level': {'__update__': {'Level 3': 3}}}}, 'crypto_scheme': {'__update__': {'KA': {'__update__': {'Key Agreement': 4}}}}, 'randomness': {'__update__': {'PRNG': {'__update__': {'DRBG': 20}}}}} data.

The is_br1_format property was set to True.

The br1_tables property was set to {'_type': 'sec_certs.heuristics.br1.table_parsing.model.br1_tables.BR1Tables', 'security_levels': {'section': 1, 'subsection': 2, 'found': True, 'entries': [{'section': '1', 'title': 'General', 'level': '3'}, {'section': '2', 'title': 'Cryptographic module specification', 'level': '3'}, {'section': '3', 'title': 'Cryptographic module interfaces', 'level': '3'}, {'section': '4', 'title': 'Roles, services, and authentication', 'level': '3'}, {'section': '5', 'title': 'Software/Firmware security', 'level': '3'}, {'section': '6', 'title': 'Operational environment', 'level': 'N/A'}, {'section': '7', 'title': 'Physical security', 'level': '4'}, {'section': '8', 'title': 'Non-invasive security', 'level': '3'}, {'section': '9', 'title': 'Sensitive security parameter management', 'level': '3'}, {'section': '10', 'title': 'Self-tests', 'level': '3'}, {'section': '11', 'title': 'Life-cycle assurance', 'level': '3'}, {'section': '12', 'title': 'Mitigation of other attacks', 'level': '3'}, {'section': '', 'title': 'Overall Level', 'level': '3'}]}, 'tested_module_id_hw': {'section': 2, 'subsection': 2, 'found': True, 'entries': [{'modelPartNum': 'P71D600', 'hwVersion': 'N7122 A1', 'fwVersion': 'Platform ID: J3R6000373181200 ROM ID: B3375FE9B5508BC4;', 'processors': 'MRK3-SC 16/32-bit RISC CPU', 'features': 'The GlobalPlatform operational environment is identified with the Platform ID, the ROM ID,'}, {'modelPartNum': '', 'hwVersion': '', 'fwVersion': 'Patch ID: 00000000 00000000; SSID v3.0.0.1.1', 'processors': '', 'features': 'the Patch ID, and other information, describing the content in ROM, NVM and loaded patches. The Platform ID is a data string that allows the identification of the P71D600 Card'}]}, 'tested_module_id_sw_fw_hy': {'section': 2, 'subsection': 2, 'found': False, 'entries': []}, 'tested_module_id_hw_hy': {'section': 2, 'subsection': 2, 'found': False, 'entries': []}, 'tested_op_env_sw_fw_hy': {'section': 2, 'subsection': 2, 'found': False, 'entries': []}, 'vendor_affirmed_op_env_sw_fw_hy': {'section': 2, 'subsection': 2, 'found': False, 'entries': []}, 'modes_of_operation': {'section': 2, 'subsection': 4, 'found': True, 'entries': [{'name': 'Approved mode', 'description': 'The module supports the Approved mode of operation after following the initialization instructions outlined in Section 11.1', 'type': 'Approved', 'statusIndicator': "To verify that the GlobalPlatform operational environment runs in the Approved mode of operation, use the IDENTIFY APDU. The DF28 file tag '05' contains the status of the Approved mode compliancy, where '00' identifies Approved mode not active and '01' - Approved mode active. The Lifecycle service (GET STATUS APDU/command) can be used to verify that the SSID applet is in the Approved mode of operation (it is in this mode by default post initialization): Command: 00 CA DF 66 00; Output Data: 01; Status: 90 00"}]}, 'approved_algorithms': {'section': 2, 'subsection': 5, 'found': True, 'entries': [{'algorithm': 'AES-CBC', 'cavpCertName': 'A2713', 'properties': 'Direction - Decrypt, Encrypt Key Length - 128, 192, 256', 'reference': 'SP 800-38A'}, {'algorithm': 'AES-CCM', 'cavpCertName': 'A2713', 'properties': 'Key Length - 128, 192, 256', 'reference': 'SP 800-38C'}, {'algorithm': 'AES-CMAC', 'cavpCertName': 'A2713', 'properties': 'Direction - Generation, Verification Key Length - 128, 192, 256', 'reference': 'SP 800-38B'}, {'algorithm': 'AES-CTR', 'cavpCertName': 'A2713', 'properties': 'Direction - Decrypt, Encrypt Key Length - 128, 192, 256', 'reference': 'SP 800-38A'}, {'algorithm': 'AES-ECB', 'cavpCertName': 'A2713', 'properties': 'Direction - Decrypt, Encrypt Key Length - 128, 192, 256', 'reference': 'SP 800-38A'}, {'algorithm': 'Counter DRBG', 'cavpCertName': 'A2713', 'properties': 'Prediction Resistance - No, Yes Mode - AES-256 Derivation Function Enabled - Yes', 'reference': 'SP 800-90A Rev. 1'}, {'algorithm': 'ECDSA KeyGen (FIPS186-5)', 'cavpCertName': 'A6534', 'properties': 'Curve - P-224, P-256, P-384, P-521 Secret Generation Mode - testing candidates', 'reference': 'FIPS 186-5'}, {'algorithm': 'ECDSA SigGen (FIPS186-5)', 'cavpCertName': 'A6534', 'properties': 'Curve - P-224, P-256, P-384, P-521 Hash Algorithm - SHA2-224, SHA2-256, SHA2-384, SHA2-512 Component - No', 'reference': 'FIPS 186-5'}, {'algorithm': 'ECDSA SigVer (FIPS186-5)', 'cavpCertName': 'A6534', 'properties': 'Curve - P-224, P-256, P-384, P-521 Hash Algorithm - SHA2-224, SHA2-256, SHA2-384, SHA2-512', 'reference': 'FIPS 186-5'}, {'algorithm': 'HMAC-SHA-1', 'cavpCertName': 'A2713', 'properties': 'Key Length - Key Length: 112-2048 Increment 8', 'reference': 'FIPS 198-1'}, {'algorithm': 'KAS-ECC-SSC Sp800- 56Ar3', 'cavpCertName': 'A2713', 'properties': 'Domain Parameter Generation Methods - P-256 Scheme - onePassDh - KAS Role - initiator, responder', 'reference': 'SP 800-56A Rev. 3'}, {'algorithm': 'KDA HKDF Sp800- 56Cr1', 'cavpCertName': 'A2713', 'properties': 'Derived Key Length - 2048 Shared Secret Length - Shared Secret Length: 224-4096 Increment 8 HMAC Algorithm - SHA-1, SHA2-256, SHA2-384, SHA2-512', 'reference': 'SP 800-56C Rev. 2'}, {'algorithm': 'KDF SP800-108', 'cavpCertName': 'A2713', 'properties': 'KDF Mode - Counter, Feedback Supported Lengths - Supported', 'reference': 'SP 800-108 Rev. 1'}, {'algorithm': '', 'cavpCertName': '', 'properties': 'Lengths: 112-4096 Increment 8, Supported Lengths: 128', 'reference': ''}, {'algorithm': 'RSA Decryption Primitive Sp800-56Br2 (CVL)', 'cavpCertName': 'A5911', 'properties': 'Modulo - 2048, 3072, 4096', 'reference': 'SP 800-56B Rev. 2'}, {'algorithm': 'RSA KeyGen (FIPS186-5)', 'cavpCertName': 'A6535', 'properties': 'Key Generation Mode - probable Modulo - 2048, 3072, 4096 Primality Tests - 2pow100 Private Key Format - standard', 'reference': 'FIPS 186-5'}, {'algorithm': 'RSA KeyGen (FIPS186-5)', 'cavpCertName': 'A6536', 'properties': 'Key Generation Mode - probable Modulo - 2048, 3072, 4096 Primality Tests - 2pow100 Private Key Format - crt', 'reference': 'FIPS 186-5'}, {'algorithm': 'RSA SigGen (FIPS186- 5)', 'cavpCertName': 'A6535', 'properties': 'Modulo - 2048, 3072, 4096 Signature Type - pkcs1v1.5, pss', 'reference': 'FIPS 186-5'}, {'algorithm': 'RSA SigVer (FIPS186- 5)', 'cavpCertName': 'A6535', 'properties': 'Modulo - 2048, 3072, 4096 Signature Type - pkcs1v1.5, pss', 'reference': 'FIPS 186-5'}, {'algorithm': 'SHA-1', 'cavpCertName': 'A2713', 'properties': 'Message Length - Message Length: 0- 65536 Increment 8', 'reference': 'FIPS 180-4'}, {'algorithm': 'SHA2-256', 'cavpCertName': 'A2713', 'properties': 'Message Length - Message Length: 0- 65536 Increment 8', 'reference': 'FIPS 180-4'}, {'algorithm': 'SHA2-512', 'cavpCertName': 'A2713', 'properties': 'Message Length - Message Length: 0- 65536 Increment 8', 'reference': 'FIPS 180-4'}]}, 'vendor_affirmed_algos': {'section': 2, 'subsection': 5, 'found': True, 'entries': [{'name': 'CKG SP800- 133r2 Section 4', 'algoPropList': 'Key Type:Symmetric and Asymmetric', 'implName': 'N/A', 'reference': 'NIST SP800-133r2 Section 4: Symmetric keys and seeds for asymmetric key generation are generated using methods described in Section 4 of SP800-133r2 (example 1). The module supports the following per NIST SP 800-133r2: 1. Section 5.1: Key Pairs for Digital Signature Schemes 2. Section 6.2.1: Symmetric Keys Generated Using Key-Agreement Schemes 3. Section 6.2.2: Symmetric Keys Derived from a Pre-existing Key 4. Section 6.4: Distributing the Generated Symmetric Key'}, {'name': 'CKG SP 800- 133r2 Section 6.3', 'algoPropList': 'Key Type :Symmetric', 'implName': 'N/A', 'reference': 'NIST SP 800-133r2 Section 6.3 Symmetric Keys Produced by Combining (Multiple) Keys and Other Data (approach/method 2. Exclusive-Oring one'}, {'name': '', 'algoPropList': '', 'implName': '', 'reference': 'or more symmetric keys and possibly one or more other items of data)'}]}, 'non_approved_allowed_algos': {'section': 2, 'subsection': 5, 'found': False, 'entries': []}, 'non_approved_allowed_NSC': {'section': 2, 'subsection': 5, 'found': True, 'entries': [{'name': 'RSA Encryption using PKCS1.5 padding', 'caveat': 'no security claimed', 'use': 'Used to encrypt and protect keys; Per IG 2.4.A example 1.'}]}, 'non_approved_not_allowed': {'section': 2, 'subsection': 5, 'found': False, 'entries': []}, 'ports_interfaces': {'section': 3, 'subsection': 1, 'found': True, 'entries': [{'physicalPort': 'VSS, VDD', 'logicalInterface': 'Power', 'data': 'These interfaces are used to supply power to the module in contact mode; The module starts when interface is powered'}, {'physicalPort': 'VIN, VOUT', 'logicalInterface': 'Power', 'data': 'These interfaces are used to supply power to the module in contact, contactless and I2C mode'}, {'physicalPort': 'RST_N', 'logicalInterface': 'Control Input', 'data': 'If a signal is sent on this interface on contact mode, the module will reboot (active low)'}, {'physicalPort': 'CLK', 'logicalInterface': 'Control Input', 'data': 'The interface is used by an external device (ex: smartcard reader) to provide a clock signal to the IC in contact mode; The IC will derive its own clock from this signal'}, {'physicalPort': 'IO1', 'logicalInterface': 'Data Input Data Output Control Input Status Output', 'data': 'The interface is used to communicate with an external entity (ex: SmartCard reader) in contact mode; It also functions as I2C master SDA in I2C mode'}, {'physicalPort': 'IO2', 'logicalInterface': 'Data Input Data Output Control Input', 'data': 'The interface is used to communicate with an external entity (ex: SmartCard reader) in contact mode; It also functions as I2C master SCL in I2C mode or as SPI interface'}, {'physicalPort': '', 'logicalInterface': 'Status Output', 'data': ''}, {'physicalPort': 'LA, LB', 'logicalInterface': 'Data Input Data Output Control Input Status Output Power', 'data': 'The interface is used to communicate with an external entity (ex: smartcard reader) in contactless mode; This interface is also used to set the internal clock and to supply power to the module'}, {'physicalPort': 'SDA', 'logicalInterface': 'Data Input Data Output Control Input Status Output', 'data': 'The interface is used to communicate with an external entity such as a host controller'}, {'physicalPort': 'SCL', 'logicalInterface': 'Control Input', 'data': 'The interface is used by an external device (ex: host controller) to provide a clock signal to the I2C HW'}]}, 'authentication_methods': {'section': 4, 'subsection': 1, 'found': True, 'entries': [{'name': 'Platform Authentica tion (Secure Channel Protocol 03 Authentica tion Method)', 'description': 'The Secure Channel Protocol authentica tion method is provided by the Secure Channel service; The SD- KENC and SD-KMAC keys are used to', 'mechanism': 'The external entity participati ng in the mutual authentica tion sends a 64-bit challenge to the Secure Element; The Secure Element generates', 'strength': "1/(2^128) = 2.9E - 39 (MAC||cryptogram) using a 128 - bit block for authentication; This authentication method includes a counter of failed authentication called 'velocity checking' by GlobalPlatform; The counter is decremented prior to any attempt to authenticate and is only reset to its threshold (maximum value) upon successful authentication", 'perMinute': 'The module enforces a maximum of 60 failed Global Platform SCP03 authentication attempts before permanently blocking the card; The probability that a random attempt will succeed over a one-minute interval is (with the assumption here that one'}, {'name': '', 'description': 'derive the SD- SENC, SD- SMAC, and SD- RMAC session keys; These sessions keys are used with AES-CBC and AES- CMAC to provide an end-to- end confidenti al and authentica ted protected channel (Approved KTS) between the external entity (User) and the module', 'mechanism': 'its own challenge and computes a 64-bit cryptogra m with SD-SMAC key and both challenge s; The Secure Element cryptogra m and challenge are sent to the external entity which checks the Secure Element cryptogra m and creates its own 64-bit cryptogra m with both challenge s; A 64-bit message authentica tion code (MAC) is also computed on the command containing the external entity cryptogra', 'strength': '', 'perMinute': 'attempt is possible per second): 60/(2^128) = 1.7E-37 (MAC||cryptogra m), using a 128 - bit block for authentication'}, {'name': '', 'description': '', 'mechanism': 'm with AES- CMAC and SD- SMAC key; The MAC is concatena ted to the command, and the command is sent to the Secure Element; The Secure Element checks the message authentica tion code and compares the received cryptogra m to the calculated cryptogra m; If all of this succeeds, the two participant s are mutually authentica ted (the external entity is authentica ted to the Module)', 'strength': '', 'perMinute': ''}, {'name': 'Owner PIN', 'description': '8 bytes PIN used', 'mechanism': '-', 'strength': 'The probability that a random- access attempt will succeed when', 'perMinute': 'Probability of Success: The'}, {'name': '', 'description': 'for authentica tion', 'mechanism': '', 'strength': 'using a PIN of size 8 bytes depends on the total number of possible PIN combinations. 1. PIN Size: 8 bytes means there are 8 * 8 = 64 bits (since 1 byte = 8 bits). 2. Possible Combinations: The number of possible PIN combinations is 2^64, as each bit can be either 0 or 1. Therefore, the total number of combinations is: 2^64=18,446,744,073,709,551,61 6 If a random-access attempt means choosing one of these combinations, and assuming all combinations are equally likely, the probability of a successful attempt is: Probability of success=1/2^64 This is an extremely small probability, roughly: 1/118,446,744,073,709,551,616≈ 5.4×10^-19 So, the probability of a successful random-access attempt with an 8-byte PIN is extraordinarily low', 'perMinute': 'probability of success for any single random- access attempt with a 8-byte PIN, is ≈ 5.4 x 10^ -19 Probability of Failure for One Attempt: The probability of a failure on any single random access attempt is: Pfailure=1-Psucc ess≈1 (Since the success probability is so small, the failure probability is practically 1.) Probability of Failure for All Attempts in One Minute: If 60N attempts are made in one minute, the probability of failing on all attempts is: Pfailure (all)=(Pfailure)^ 60N ≈1^(60N) =1 (Again, this approximation assumes the success probability is negligible.) Probability of At Least One Success in One Minute: The probability of having at least one success is the complement of the probability'}, {'name': '', 'description': '', 'mechanism': '', 'strength': '', 'perMinute': 'of failing on all attempts: Psuccess (at least one)=1-Pfailure (all)=1-(Pfailure)^ (60N) Since Pfailure is extremely close to 1, we can estimate this probability as: Psuccess (at least one)≈ 60N×Psuccess So, the probability of success within one minute, given N attempts per second, is: Psuccess (at least one)≈ 60N×6.8×10^-49 Assuming 1 million attempts can be made per second = 10^6, the number of attemper per minute is: 60x10^6 = 60, 000, 000 attempts The probability of at least one success in one minute is: Psuccess (at least one)≈ 60, 000, 000 attempts x 5.4×10^-19 ~ 3.24 x 10 ^-11'}, {'name': 'Marriage code', 'description': '20 bytes PIN used for authentica tion', 'mechanism': '-', 'strength': 'The probability that a random- access attempt will succeed when using a PIN of size 8 bytes depends on the total number of possible PIN combinations. 1. PIN Size: 20 bytes means there are 20 * 8 = 160 bits (since 1 byte = 8', 'perMinute': 'Probability of Success: The probability of success for any single random- access attempt with a 20-byte'}, {'name': 'Method Name', 'description': 'Descripti on', 'mechanism': 'Security Mechanis', 'strength': 'Strength Each Attempt', 'perMinute': 'Strength per Minute'}, {'name': '', 'description': '', 'mechanism': 'm', 'strength': 'bits). 2. Possible Combinations: The number of possible PIN combinations is 2^160, as each bit can be either 0 or 1. Therefore, the total number of combinations is: 2^160= 1,461,501,637,330,901,217,467,9 99,448 If a random-access attempt means choosing one of these combinations, and assuming all combinations are equally likely, the probability of a successful attempt is: Probability of success=1/2^160 This is an extremely small probability, roughly: 1/ 1,461,501,637,330,901,217,467,9 99,448 ≈ 6.8×10^-49 So, t he probability of a successful random-access attempt with an 20-byte PIN is extraordinarily low', 'perMinute': 'PIN, is ≈6.8×10^-49 Probability of Failure for One Attempt: The probability of a failure on any single random access attempt is: Pfailure=1-Psucc ess≈1 (Since the success probability is so small, the failure probability is practically 1.) Probability of Failure for All Attempts in One Minute: If 60N attempts are made in one minute, the probability of failing on all attempts is: Pfailure (all)=(Pfailure)^ 60N ≈1^(60N) =1 (Again, this approximation assumes the success probability is negligible.) Probability of At Least One Success in One Minute: The probability of having at least one success is the complement of the probability of failing on all attempts: Psuccess (at least'}, {'name': '', 'description': '', 'mechanism': '', 'strength': '', 'perMinute': 'one)=1-Pfailure (all)=1-(Pfailure)^ (60N) Since Pfailure is extremely close to 1, we can estimate this probability as: Psuccess (at least one)≈ 60N×Psuccess So, the probability of success within one minute, given N attempts per second, is: Psuccess (at le ast one)≈ 60N×6.8×10^-49 Assuming 1 million attempts can be made per second = 10^6, the number of attemper per minute is: 60x10^6 = 60, 000, 000 attempts The probability of at least one success in one minute is: Psuccess (at least one)≈ 60, 000, 000 attempts x 6.8×10^-49 ~ 4.08 x 10^-41'}, {'name': 'Passive Authentica tion', 'description': 'ECDSA P- 384 SHA2-384', 'mechanism': 'EC Crypto Operation s', 'strength': 'The private key is a random number in the range { 0 , 1 , 2 , … , 𝑛 - 1 } {0,1,2,…,n-1}, where 𝑛 n is the order of the elliptic curve (approximately 2^384 for P-384); Since the key space is approximately 2^384, the probability of successfully forging a valid signature (i.e., a random- access attempt succeeding) is', 'perMinute': 'The probability of a single attempt succeeding is 3.5×10^(-116); The probability of at least one successful attempt per second can be approximated as: 10^12 x 1/'}, {'name': '', 'description': '', 'mechanism': '', 'strength': 'around: 1/(2^384) = ~ 3.5×10^(- 116)', 'perMinute': '(2^384) = ~3.5 x 10 ^(-104); Since there are 60 seconds in a minute, multiply the probability per second by 60 to get the probability per minute: 60×3.5x10^(-104) = 2.1 x 10^(-102)'}, {'name': 'Active Authentica tion', 'description': 'AES 256- bit key used (mode: ECB) to send random nonces to the SAM (an external applet). The SSID encrypts the nonce using this key, if the SAM can decrypt it, mutual authentica tion succeeds', 'mechanism': 'Symmetric Cipher Crypto Operation s', 'strength': 'To successfully decrypt the ciphertext and authenticate, the attacker would need to know the AES-256 key used for encryption; AES-256 bit key has a space of 2^256, so the probability of randomly guessing the correct key i.e. random access is = 1/(2^256) = ~8.63×10^(-78)', 'perMinute': 'The probability of a successful random access is: 8.63×10^(-78); The probability of success per minute is: 60×8.63x10^(-78) = 5.18 x 10^(-76)'}]}, 'roles': {'section': 4, 'subsection': 2, 'found': True, 'entries': [{'name': 'Cryptographic Officer', 'type': 'Identity', 'operatorType': 'Cryptographic Officer', 'authMethodList': 'Platform Authentication (Secure Channel Protocol 03 Authentication Method) Owner PIN Marriage code Passive Authentication Active Authentication'}, {'name': 'User', 'type': 'Identity', 'operatorType': 'User', 'authMethodList': 'Platform Authentication (Secure Channel Protocol 03 Authentication Method) Owner PIN Marriage code Passive Authentication Active Authentication'}]}, 'approved_services': {'section': 4, 'subsection': 3, 'found': True, 'entries': [{'name': 'Manage Content (ISD Services)', 'description': 'Load keys and data; APDU(s) used: DELETE, LOAD, INSTALL, MANAGE CHANNEL', 'indicator': "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag '05' contains the status of", 'inputs': 'Comman d paramete rs (data objects, SSPs)', 'outputs': 'Status Word (Respons e APDU 9000)', 'secFunImpl': 'KTS-1', 'rolesSspAccess': 'Cryptographi c Officer - OS-SKEK: W,E,Z - SD-KENC: W,E,Z - SD-KMAC: W,E,Z - SD-KDEK: W,E,Z - DAP-DAPK: E'}, {'name': '', 'description': '', 'indicator': "the Approve d mode complian cy ( '01' signifies that Approve d mode is active))", 'inputs': '', 'outputs': '', 'secFunImpl': '', 'rolesSspAccess': ''}, {'name': 'Lifecycle (Show status and Perform zeroisation ) (SSD Services)', 'description': 'Get or modify the card or applet life cycle status; APDU(s) used: SET STATUS, GET STATUS, TERMINATE (Zeroise)', 'indicator': "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag '05' contains the status of the Approve d mode complian cy ( '01' signifies that Approve d mode is active))", 'inputs': 'Target status', 'outputs': 'Status Word (Respons e APDU 9000)', 'secFunImpl': 'KTS-1', 'rolesSspAccess': 'Cryptographi c Officer - OS-DRBG- EI: E,Z - OS- DRBG- KEY: E,Z - OS-DRBG- V: E,Z - OS-SKEK: E,Z - OS-MKEK: E,Z - SD-KENC: E,Z - SD-KMAC: E,Z - SD-KDEK: E,Z - SD-SENC: E,Z - SD-SMAC: E,Z - SD-RMAC: E,Z - DAP-DAPK: Z - RSA-PRIV- KEY: E,Z - EC-PRIV- KEY: E,Z - EC-KAS-Z: E,Z - RSA-PUB- KEY: E,Z - EC-PUB- KEY: E,Z - EC-KAS- PUB: E,Z'}, {'name': 'Name', 'description': 'Description', 'indicator': 'Indicato', 'inputs': 'Inputs', 'outputs': 'Outputs', 'secFunImpl': 'Security Functions', 'rolesSspAccess': 'SSP Access'}, {'name': 'Manage Content (SSD Services)', 'description': 'Load keys and data; APDU(s) used: PUT KEY, STORE DATA', 'indicator': "r Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag '05' contains the status of the Approve d mode complian cy ( '01' signifies that Approve d mode is active))", 'inputs': 'Comman d paramete rs (data objects, SSPs)', 'outputs': 'Status Word (Respons e APDU 9000)', 'secFunImpl': 'KTS-1', 'rolesSspAccess': 'Cryptographi c Officer - OS-SKEK: W,E,Z - SD-KENC: W,E,Z - SD-KMAC: W,E,Z - SD-KDEK: W,E,Z - DAP-DAPK: E'}, {'name': 'Secure Channel (SSD Services)', 'description': 'Establish and use a secure communicatio n channel; APDU(s) used: INITIALIZE, UPDATE, EXTERNAL AUTHENTICA TE', 'indicator': "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag '05' contains", 'inputs': 'Comman d paramete rs (data objects, SSPs)', 'outputs': 'Status Word (Respons e APDU 9000)', 'secFunImpl': 'Counter DRBG SCP03/sec ure channel KTS-1 Entropy Source OS-MKEK Generation', 'rolesSspAccess': 'Cryptographi c Officer - OS-DRBG- EI: G,E,Z - OS- DRBG- KEY: G,E,Z - OS-DRBG- V: G,E,Z - OS-MKEK: G,E,Z - SD-KENC: G,E,Z - SD-KMAC: G,E,Z - SD-SENC: G,E,Z - SD-SMAC: G,E,Z'}, {'name': '', 'description': '', 'indicator': "the status of the Approve d mode complian cy ( '01' signifies that Approve d mode is active))", 'inputs': '', 'outputs': '', 'secFunImpl': '', 'rolesSspAccess': '- SD-RMAC: G,E,Z - OS-DRBG- SEED: G,E,Z'}, {'name': "Privileged Info (Show module's versioning information ) (SSD Services)", 'description': 'Read Module data (privileged data objects, but no CSPs); APDU(s) used: GET DATA', 'indicator': "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag '05' contains the status of the Approve d mode complian cy ( '01' signifies that Approve d mode is active))", 'inputs': 'Comman d: IDENTIF Y APDU', 'outputs': 'Requeste d informati on; Status Word (Respons e APDU 9000)', 'secFunImpl': 'KTS-1', 'rolesSspAccess': 'Cryptographi c Officer - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E'}, {'name': 'Card Reset', 'description': 'Power cycle or reset the module; APDU(s) used: N/A', 'indicator': 'Status Word (Respon se APDU 9000);', 'inputs': 'Power cycle or reset the module', 'outputs': 'Status Word (Respons e APDU 9000)', 'secFunImpl': 'KTS-1', 'rolesSspAccess': 'Cryptographi c Officer - OS-SKEK: E - SD-KENC:'}, {'name': '', 'description': '', 'indicator': "Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag '05' contains the status of the Approve d mode complian cy ( '01' signifies that Approve d mode is active))", 'inputs': '', 'outputs': '', 'secFunImpl': '', 'rolesSspAccess': 'E - SD-KMAC: E - SD-KDEK: E User - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E Unauthentica ted'}, {'name': 'Context', 'description': 'Select an applet or manage logical channels; APDU(s) used: SELECT, MANAGE CHANNEL', 'indicator': "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag '05' contains the status of the Approve d mode", 'inputs': 'Comman d paramete rs (data objects, SSPs)', 'outputs': 'Status Word (Respons e APDU 9000)', 'secFunImpl': 'KTS-1', 'rolesSspAccess': 'Cryptographi c Officer - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E User - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E Unauthentica ted'}, {'name': '', 'description': '', 'indicator': "complian cy ( '01' signifies that Approve d mode is active))", 'inputs': '', 'outputs': '', 'secFunImpl': '', 'rolesSspAccess': ''}, {'name': 'Info (Show status and Perform self-tests)', 'description': 'Read unprivileged data objects, e.g., module configuration or status information (Show Status). This service includes the Pre- operational Self-Test on- demand; APDU(s) used: GET DATA', 'indicator': "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag '05' contains the status of the Approve d mode complian cy ( '01' signifies that Approve d mode is active))", 'inputs': 'Comman d paramete rs (data objects, SSPs)', 'outputs': 'Status Word (Respons e APDU 9000)', 'secFunImpl': 'Perform Self-Tests', 'rolesSspAccess': 'Cryptographi c Officer - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E User - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E Unauthentica ted'}, {'name': 'Get Applet Version', 'description': 'Retrieve firmware version of the applet', 'indicator': 'Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY', 'inputs': 'Comman d: Read Applet Version APDU (00 CA DF 65 00)', 'outputs': 'Status Word (Respons e APDU 9000)', 'secFunImpl': 'None', 'rolesSspAccess': 'Cryptographi c Officer - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E'}, {'name': '', 'description': '', 'indicator': "APDU can be used where the DF28 file tag '05' contains the status of the Approve d mode complian cy ( '01' signifies that Approve d mode is active))", 'inputs': '', 'outputs': '', 'secFunImpl': '', 'rolesSspAccess': '- Marriage Code: W,E - Owner PIN: W,E - Passive Authenticatio n Key: E - Active Authenticatio n: E User - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E - Marriage Code: W,E - Owner PIN: W,E - Passive Authenticatio n Key: E - Active Authenticatio n: E'}, {'name': 'Create data group', 'description': 'Inject keys (AES, ECDSA, RSA)', 'indicator': "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag '05' contains the status of", 'inputs': 'Comman d paramete rs (data objects, SSPs)', 'outputs': 'Status Word (Respons e APDU 9000)', 'secFunImpl': 'KTS-1', 'rolesSspAccess': 'Cryptographi c Officer - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E - RSA-PRIV- KEY: W - RSA-PUB- KEY: W - EC-PUB- KEY: W - EC-PRIV- KEY: W - Application AES'}, {'name': 'Name', 'description': 'Description', 'indicator': 'Indicato r', 'inputs': 'Inputs', 'outputs': 'Outputs', 'secFunImpl': 'Security', 'rolesSspAccess': 'SSP Access'}, {'name': '', 'description': '', 'indicator': "the Approve d mode complian cy ( '01' signifies that Approve d mode is active))", 'inputs': '', 'outputs': '', 'secFunImpl': 'Functions', 'rolesSspAccess': 'Communicati on : W - Marriage Code: W,E - Owner PIN: W,E - Passive Authenticatio n Key: E - Active Authenticatio n: E User - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E - RSA-PRIV- KEY: W - RSA-PUB- KEY: W - EC-PRIV- KEY: W - EC-PUB- KEY: W - Application AES Communicati on : W - Marriage Code: W,E - Owner PIN: W,E - Passive Authenticatio n Key: E - Active Authenticatio n: E'}, {'name': 'Perform Cryptograp hy', 'description': 'Perform AES Encrypt, Decrypt, RSA Sign, Verify, Decrypt, ECDSA Verify', 'indicator': 'Status Word (Respon se APDU 9000); Approve', 'inputs': 'Comman d paramete rs (data objects, SSPs)', 'outputs': 'Status Word (Respons e APDU 9000)', 'secFunImpl': 'Asymmetric Key Generation EC Crypto Operations RSA Crypto', 'rolesSspAccess': 'Cryptographi c Officer - RSA-PRIV- KEY: G,E - RSA-PUB- KEY: G,E'}, {'name': '', 'description': '', 'indicator': "d mode indicator (IDENTI FY APDU can be used where the DF28 file tag '05' contains the status of the Approve d mode complian cy ( '01' signifies that Approve d mode is active))", 'inputs': '', 'outputs': '', 'secFunImpl': 'Operations Symmetric Cipher Crypto Operations', 'rolesSspAccess': '- EC-PRIV- KEY: G,E - EC-PUB- KEY: G,E - Application AES Communicati on : E - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E - Marriage Code: W,E - Owner PIN: W,E - Passive Authenticatio n Key: E - Active Authenticatio n: E User - RSA-PRIV- KEY: G,E - EC-PRIV- KEY: G,E - RSA-PUB- KEY: G,E - EC-PUB- KEY: G,E - Application AES Communicati on : E - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E - Marriage Code: W,E'}, {'name': '', 'description': '', 'indicator': '', 'inputs': '', 'outputs': '', 'secFunImpl': '', 'rolesSspAccess': '- Owner PIN: W,E - Passive Authenticatio n Key: E - Active Authenticatio n: E'}, {'name': 'ECDH Key Agreement', 'description': 'Key Agreement', 'indicator': "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag '05' contains the status of the Approve d mode complian cy ( '01' signifies that Approve d mode is active))", 'inputs': 'Key identifier, Mechani sm identifier, Host ECC public key', 'outputs': 'Status Word (Respons e APDU 9000)', 'secFunImpl': 'KAS-1', 'rolesSspAccess': 'User - EC-KAS-Z: G,E,Z - EC-KAS- PUB: W,E,Z - EC-PRIV- KEY: G,E,Z'}]}, 'non_approved_services': {'section': 4, 'subsection': 4, 'found': False, 'entries': []}, 'mechanisms_actions': {'section': 7, 'subsection': 1, 'found': True, 'entries': [{'mechanism': 'Hard, tamper evident coating', 'inspectFreq': 'N/A', 'inspectGuidance': 'N/A'}]}, 'storage_areas': {'section': 9, 'subsection': 1, 'found': True, 'entries': [{'name': 'Temporarily stored in RAM', 'description': 'plaintext (does not persist beyond a power cycle); object identifier to entity association', 'persistance': 'Dynamic'}, {'name': 'Stored in NVM', 'description': 'plaintext; object identifier to entity association', 'persistance': 'Static'}, {'name': 'Stored in NVM - Encrypted', 'description': 'encrypted with Approved AES CBC with OSMKEK; key version to entity association', 'persistance': 'Static'}, {'name': 'Plaintext: Persistent', 'description': 'plaintext (persists beyond a power cycle); identity- based authentication data', 'persistance': 'Static'}]}, 'ssp_io_methods': {'section': 9, 'subsection': 2, 'found': True, 'entries': [{'name': 'Imported in secure channel specified by GP- Amd-I', 'source': 'External endpoint', 'dest': 'Stored in NVM - Encrypt ed', 'format': 'Encrypt ed', 'distribution': 'Automated', 'entry': 'Electron ic', 'sfiAlgo': 'KTS-1'}, {'name': 'Encrypted using AES-CBC (using SD- KDEK) (RFC 3394 method) and transported', 'source': 'External endpoint', 'dest': 'Stored in NVM encrypte d with Approve d AES', 'format': 'Encrypt ed', 'distribution': 'Automated', 'entry': 'Electron ic', 'sfiAlgo': 'KTS-1'}, {'name': 'using platform SCP03', 'source': '', 'dest': 'CBC with OS- MKEK', 'format': '', 'distribution': '', 'entry': '', 'sfiAlgo': ''}, {'name': 'Entered encrypted with the previous SD-KDEK', 'source': 'External endpoint', 'dest': 'Stored in NVM - Encrypt ed', 'format': 'Encrypt ed', 'distribution': 'Automated', 'entry': 'Electron ic', 'sfiAlgo': 'KTS-1'}, {'name': 'Not Imported', 'source': 'N/A', 'dest': 'N/A', 'format': 'Plaintext', 'distribution': 'N/A', 'entry': 'N/A', 'sfiAlgo': ''}, {'name': 'Not Exported', 'source': 'N/A', 'dest': 'N/A', 'format': 'Plaintext', 'distribution': 'N/A', 'entry': 'N/A', 'sfiAlgo': ''}, {'name': 'Exported using Approved KTS', 'source': 'Stored in NVM - Encrypted', 'dest': 'External Endpoin t', 'format': 'Encrypt ed', 'distribution': 'Automated', 'entry': 'Electron ic', 'sfiAlgo': 'KTS-1'}, {'name': 'Entered during manufacturing/p re- personalization', 'source': 'Vendor generated at manufacture/duri ng pre- personalization', 'dest': 'Stored in NVM - Encrypt ed', 'format': 'Encrypt ed', 'distribution': 'N/A', 'entry': 'N/A', 'sfiAlgo': ''}, {'name': 'Entered during manufacturing/ pre- personalization - plaintext storage', 'source': 'Vendor generated at manufacture/duri ng pre- personalization', 'dest': 'Stored in NVM', 'format': 'Plaintext', 'distribution': 'N/A', 'entry': 'N/A', 'sfiAlgo': ''}]}, 'ssp_zeroization_methods': {'section': 9, 'subsection': 3, 'found': True, 'entries': [{'method': 'Power-off', 'description': 'Ephemeral parameter', 'rationale': 'Cleared upon power cycling the module', 'operatorId': 'Operator initiation'}, {'method': 'Destroyed by termination of the module (LifeCycle/Perform Zeroisation service)', 'description': 'Overwritten with zeroes', 'rationale': 'Setting the module to the TERMINATE state triggers zeroisation and renders the module unusable', 'operatorId': 'Operator initiation'}, {'method': 'Destroyed because of OS- MKEK zeroisation', 'description': '-', 'rationale': 'Zeroising the root of trust causes zeroisation of SSPs derived from it', 'operatorId': 'Module initiation'}, {'method': 'Cleared immediately following return to the caller', 'description': 'Ephemeral shared secret', 'rationale': 'Shared secret computed is zeroised post being returned to caller (for use internal to the module)', 'operatorId': 'Module initiation'}]}, 'self_tests': {'section': 10, 'subsection': 1, 'found': True, 'entries': [{'algorithmOrTest': 'Firmware Integrity', 'testProps': '32-bit CRC performed over all code located in Flash', 'testMethod': '32-bit CRC', 'type': 'SW/FW Integrity', 'indicator': '9000', 'details': '-'}]}, 'cond_self_tests': {'section': 10, 'subsection': 2, 'found': True, 'entries': [{'algorithmOrTest': 'AES-CBC (A2713) - Encrypt', 'testProps': '128-bit', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Encrypt', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'AES-CBC (A2713) - Decrypt', 'testProps': '128-bit', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Decrypt', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'AES-CMAC (A2713) - Encrypt', 'testProps': '128-bit', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Encrypt', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'AES-CMAC (A2713) - Decrypt', 'testProps': '128-bit', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Decrypt', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'Counter DRBG (A2713)', 'testProps': '256-bit', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Health Tests: Generate, Reseed, Instantiate functions per Section 11 in NIST SP800- 90Ar1', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'ECDSA SigGen (FIPS186- 5) (A6534)', 'testProps': 'P-521 SHA- 256', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Signature Generation', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'ECDSA SigVer (FIPS186- 5) (A6534)', 'testProps': 'P-521 SHA- 256', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Signature Verification', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'KAS-ECC- SSC Sp800-', 'testProps': 'P-256 Scheme: onePassDh: KAS Role:', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000', 'details': 'Shared Secret Computation (Z)', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': '56Ar3 (A2713)', 'testProps': 'initiator, responder', 'testMethod': '', 'type': '', 'indicator': 'signifies success', 'details': '', 'condition': ''}, {'algorithmOrTest': 'KDA HKDF Sp800- 56Cr1 (A2713)', 'testProps': 'SHA-1, SHA2-256, SHA2-384, SHA2-512', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Key Derivation Function per NIST SP 800- 56Cr1', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'KDF SP800-108 (A2713) - AES-128', 'testProps': 'Counter mode with AES-128', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Key Derivation Function per NIST SP 800- 108r1 (Counter mode)', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'KDF SP800-108 (A2713) - HMAC- SHA1', 'testProps': 'Feedback Mode with HMAC-SHA1', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Key Derivation Function per NIST SP 800- 108r1 (Counter mode)', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'RSA SigGen (FIPS186- 5) (A6535)', 'testProps': '2048-bit SHA2-256', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Signature Generation', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'RSA SigVer (FIPS186- 5) (A6535)', 'testProps': '2048-bit SHA2-256', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Signature Verification', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'SHA-1 (A2713)', 'testProps': 'SHA-1', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Hash generation', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'SHA2-256 (A2713)', 'testProps': 'SHA2-256', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Hash generation', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'SHA2-512 (A2713)', 'testProps': 'SHA2-512', 'testMethod': 'KAT', 'type': 'CAST', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Hash generation', 'condition': 'Performed automatically on every boot'}, {'algorithmOrTest': 'Generate PCT', 'testProps': 'Pairwise consistency test performed when an asymmetric key pair is generated for RSA or ECC.', 'testMethod': 'PCT', 'type': 'PCT', 'indicator': 'The APDU code 9000 signifies success', 'details': '-', 'condition': 'Performed automatically on generation of keypairs'}, {'algorithmOrTest': 'Signature PCT', 'testProps': 'Pairwise consistency test performed when a signature is generated for RSA or ECDSA', 'testMethod': 'PCT', 'type': 'PCT', 'indicator': 'The APDU code 9000 signifies success', 'details': '-', 'condition': 'Performed automatically on generation of keypairs'}, {'algorithmOrTest': 'Firmware Load Test', 'testProps': 'ECDSA P- 256 with SHA2-256', 'testMethod': 'Load Test', 'type': 'SW/FW Load', 'indicator': 'The APDU code 9000 signifies success', 'details': 'Signature Verification based on ECDSA P- 256 with SHA2-256', 'condition': 'Upon loading of the SSID applet'}, {'algorithmOrTest': 'NIST SP800-90B ENT (P) Repetition Count Test (RCT)', 'testProps': '-', 'testMethod': 'NIST SP 800- 90B Health Test', 'type': 'CAST', 'indicator': 'Implicit, based on output of entropy', 'details': '-', 'condition': 'Performed continuously by the entropy source'}, {'algorithmOrTest': 'NIST SP800-90B ENT (P) Developer Defined Heath Test Transition Count Test', 'testProps': '-', 'testMethod': 'NIST SP 800- 90B Health Test', 'type': 'CAST', 'indicator': 'Implicit, based on output of entropy', 'details': '-', 'condition': 'Performed continuously by the entropy source'}, {'algorithmOrTest': 'NIST SP800-90B ENT (P) Developer', 'testProps': '-', 'testMethod': 'NIST SP 800- 90B', 'type': 'CAST', 'indicator': 'Implicit, based on output of entropy', 'details': '-', 'condition': 'Performed continuously by the'}, {'algorithmOrTest': 'Defined Heath Test Chi - Square Test', 'testProps': '', 'testMethod': 'Health Test', 'type': '', 'indicator': '', 'details': '', 'condition': 'entropy source'}, {'algorithmOrTest': 'NIST SP800-90B ENT (P) Developer Defined Heath Test Amplitude Limiter Analog Test', 'testProps': '-', 'testMethod': 'NIST SP 800- 90B Health Test', 'type': 'CAST', 'indicator': 'Implicit, based on output of entropy', 'details': '-', 'condition': 'Performed continuously by the entropy source'}]}, 'error_states': {'section': 10, 'subsection': 4, 'found': True, 'entries': [{'name': 'Hard Error (MUTE) state', 'description': 'All the Self-Tests can be performed on-demand with the GET DATA APDU command (Info service) with the following parameters: CLA = 80, INS = CA, P1 = 00, P2 = FE, Lc = 04, Incoming Data = DF4B0120, and Le = 00. The expected result is FE04DF4B0120. The return code 9000 signifies success. In case of a failure, the module', 'conditions': 'In case of failure of a pre- operational, conditional self- test or NIST SP 800-90B compliant entropy source health test.', 'recoveryMethod': 'A reset of the module can be attempted but in the event that the error persists, the module must be returned to the vendor', 'indicator': '66A7'}, {'name': '', 'description': 'enters a hard error (MUTE) state and returns a code/status indicator', 'conditions': '', 'recoveryMethod': '', 'indicator': ''}]}}.
23.09.2026

The certificate data changed.
Certificate changed

The PDF extraction data was updated.

The following values were inserted: {'is_br1_format': False, 'br1_deviations': 0, 'br1_tables': None}.

The keywords property was updated, with the {'fips_security_level': {'__update__': {'Level': {'__update__': {'Level 3': 2}}}}, 'crypto_scheme': {'__update__': {'KA': {'__update__': {'Key Agreement': 5}}}}, 'randomness': {'__update__': {'PRNG': {'__update__': {'DRBG': 21}}}}} data.
21.09.2026

The certificate data changed.
Certificate changed

The PDF extraction data was updated.

The following values were inserted: {'module_algorithms': {'_type': 'Set', 'elements': ['RSA SigVer (FIPS186-5)A6535', 'ECDSA KeyGen (FIPS186-5)A6534', 'KAS-ECC-SSC Sp800-56Ar3A2713', 'KDA HKDF Sp800-56Cr1A2713', 'SHA2-512A2713', 'SHA2-256A2713', 'SHA-1A2713', 'RSA Decryption Primitive Sp800-56Br2A5911', 'AES-CMACA2713', 'AES-CCMA2713', 'RSA KeyGen (FIPS186-5)A6536', 'AES-CBCA2713', 'HMAC-SHA-1A2713', 'AES-CTRA2713', 'ECDSA SigGen (FIPS186-5)A6534', 'AES-ECBA2713', 'KDF SP800-108A2713', 'ECDSA SigVer (FIPS186-5)A6534', 'RSA SigGen (FIPS186-5)A6535', 'Counter DRBGA2713']}, 'policy_algorithms': {'_type': 'Set', 'elements': ['#A5911', '#A6536', '#A2713', '#A6534', '#A6535']}}.

The keywords property was updated, with the {'fips_security_level': {'__update__': {'Level': {'__delete__': ['Level 1']}}}, 'standard_id': {'__update__': {'NIST': {'__update__': {'SP 800-108': 2}}}}} data.

The computed heuristics were updated.

The algorithms property was updated, with the {'_type': 'Set', 'elements': ['#A5911', '#A6536', '#A2713', '#A6534', '#A6535']} values added.

The state was updated.

The policy property was updated, with the {'txt_hash': 'ce376fe06b225a8722d4aeed443ed89fa0d4a8ebbf408f050ef1c1fcb7a5d40e', 'json_hash': 'fbd36ae284a5ff5e4da66051fb0ff810825f00d5e5401005c5cb603d2b9ecaf6'} data.
31.08.2026

The certificate data changed.
Certificate changed

The computed heuristics were updated.

The algorithms property was set to {'_type': 'Set', 'elements': ['RSA SigVer (FIPS186-5)A6535', 'ECDSA KeyGen (FIPS186-5)A6534', 'KAS-ECC-SSC Sp800-56Ar3A2713', 'KDA HKDF Sp800-56Cr1A2713', 'SHA2-512A2713', 'SHA2-256A2713', 'SHA-1A2713', 'RSA Decryption Primitive Sp800-56Br2A5911', 'AES-CMACA2713', 'AES-CCMA2713', 'RSA KeyGen (FIPS186-5)A6536', 'AES-CBCA2713', 'HMAC-SHA-1A2713', 'AES-CTRA2713', 'ECDSA SigGen (FIPS186-5)A6534', 'AES-ECBA2713', 'KDF SP800-108A2713', 'ECDSA SigVer (FIPS186-5)A6534', 'RSA SigGen (FIPS186-5)A6535', 'Counter DRBGA2713']}.
20.07.2026

The certificate data changed.
Certificate changed

The web extraction data was updated.

The certificate_pdf_url property was set to https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/certificates/June 2026_080726_0648.pdf.
06.07.2026

The certificate was first processed.

Raw data

{
  "_type": "sec_certs.sample.fips.FIPSCertificate",
  "cert_id": 5360,
  "dgst": "c702d852a09d5ac8",
  "heuristics": {
    "_type": "sec_certs.sample.fips.FIPSCertificate.Heuristics",
    "algorithms": {
      "_type": "Set",
      "elements": [
        "ECDSA KeyGen (FIPS186-5)A6534",
        "#A6534",
        "#A6535",
        "SHA2-256A2713",
        "#A6536",
        "AES-CCMA2713",
        "Counter DRBGA2713",
        "ECDSA SigGen (FIPS186-5)A6534",
        "RSA SigGen (FIPS186-5)A6535",
        "SHA2-512A2713",
        "SHA-1A2713",
        "RSA SigVer (FIPS186-5)A6535",
        "#A5911",
        "KDF SP800-108A2713",
        "RSA Decryption Primitive Sp800-56Br2A5911",
        "AES-CTRA2713",
        "#A2713",
        "AES-CBCA2713",
        "AES-ECBA2713",
        "RSA KeyGen (FIPS186-5)A6536",
        "KAS-ECC-SSC Sp800-56Ar3A2713",
        "ECDSA SigVer (FIPS186-5)A6534",
        "AES-CMACA2713",
        "KDA HKDF Sp800-56Cr1A2713",
        "HMAC-SHA-1A2713"
      ]
    },
    "cpe_matches": null,
    "direct_transitive_cves": null,
    "extracted_versions": {
      "_type": "Set",
      "elements": [
        "-"
      ]
    },
    "indirect_transitive_cves": null,
    "module_processed_references": {
      "_type": "sec_certs.sample.certificate.References",
      "directly_referenced_by": null,
      "directly_referencing": null,
      "indirectly_referenced_by": null,
      "indirectly_referencing": null
    },
    "module_prunned_references": {
      "_type": "Set",
      "elements": []
    },
    "policy_processed_references": {
      "_type": "sec_certs.sample.certificate.References",
      "directly_referenced_by": null,
      "directly_referencing": null,
      "indirectly_referenced_by": null,
      "indirectly_referencing": null
    },
    "policy_prunned_references": {
      "_type": "Set",
      "elements": []
    },
    "related_cves": null,
    "verified_cpe_matches": null
  },
  "pdf_data": {
    "_type": "sec_certs.sample.fips.FIPSCertificate.PdfData",
    "br1_deviations": 0,
    "br1_tables": {
      "_type": "sec_certs.heuristics.br1.table_parsing.model.br1_tables.BR1Tables",
      "approved_algorithms": {
        "entries": [
          {
            "algorithm": "AES-CBC",
            "cavpCertName": "A2713",
            "properties": "Direction - Decrypt, Encrypt Key Length - 128, 192, 256",
            "reference": "SP 800-38A"
          },
          {
            "algorithm": "AES-CCM",
            "cavpCertName": "A2713",
            "properties": "Key Length - 128, 192, 256",
            "reference": "SP 800-38C"
          },
          {
            "algorithm": "AES-CMAC",
            "cavpCertName": "A2713",
            "properties": "Direction - Generation, Verification Key Length - 128, 192, 256",
            "reference": "SP 800-38B"
          },
          {
            "algorithm": "AES-CTR",
            "cavpCertName": "A2713",
            "properties": "Direction - Decrypt, Encrypt Key Length - 128, 192, 256",
            "reference": "SP 800-38A"
          },
          {
            "algorithm": "AES-ECB",
            "cavpCertName": "A2713",
            "properties": "Direction - Decrypt, Encrypt Key Length - 128, 192, 256",
            "reference": "SP 800-38A"
          },
          {
            "algorithm": "Counter DRBG",
            "cavpCertName": "A2713",
            "properties": "Prediction Resistance - No, Yes Mode - AES-256 Derivation Function Enabled - Yes",
            "reference": "SP 800-90A Rev. 1"
          },
          {
            "algorithm": "ECDSA KeyGen (FIPS186-5)",
            "cavpCertName": "A6534",
            "properties": "Curve - P-224, P-256, P-384, P-521 Secret Generation Mode - testing candidates",
            "reference": "FIPS 186-5"
          },
          {
            "algorithm": "ECDSA SigGen (FIPS186-5)",
            "cavpCertName": "A6534",
            "properties": "Curve - P-224, P-256, P-384, P-521 Hash Algorithm - SHA2-224, SHA2-256, SHA2-384, SHA2-512 Component - No",
            "reference": "FIPS 186-5"
          },
          {
            "algorithm": "ECDSA SigVer (FIPS186-5)",
            "cavpCertName": "A6534",
            "properties": "Curve - P-224, P-256, P-384, P-521 Hash Algorithm - SHA2-224, SHA2-256, SHA2-384, SHA2-512",
            "reference": "FIPS 186-5"
          },
          {
            "algorithm": "HMAC-SHA-1",
            "cavpCertName": "A2713",
            "properties": "Key Length - Key Length: 112-2048 Increment 8",
            "reference": "FIPS 198-1"
          },
          {
            "algorithm": "KAS-ECC-SSC Sp800- 56Ar3",
            "cavpCertName": "A2713",
            "properties": "Domain Parameter Generation Methods - P-256 Scheme - onePassDh - KAS Role - initiator, responder",
            "reference": "SP 800-56A Rev. 3"
          },
          {
            "algorithm": "KDA HKDF Sp800- 56Cr1",
            "cavpCertName": "A2713",
            "properties": "Derived Key Length - 2048 Shared Secret Length - Shared Secret Length: 224-4096 Increment 8 HMAC Algorithm - SHA-1, SHA2-256, SHA2-384, SHA2-512",
            "reference": "SP 800-56C Rev. 2"
          },
          {
            "algorithm": "KDF SP800-108",
            "cavpCertName": "A2713",
            "properties": "KDF Mode - Counter, Feedback Supported Lengths - Supported",
            "reference": "SP 800-108 Rev. 1"
          },
          {
            "algorithm": "",
            "cavpCertName": "",
            "properties": "Lengths: 112-4096 Increment 8, Supported Lengths: 128",
            "reference": ""
          },
          {
            "algorithm": "RSA Decryption Primitive Sp800-56Br2 (CVL)",
            "cavpCertName": "A5911",
            "properties": "Modulo - 2048, 3072, 4096",
            "reference": "SP 800-56B Rev. 2"
          },
          {
            "algorithm": "RSA KeyGen (FIPS186-5)",
            "cavpCertName": "A6535",
            "properties": "Key Generation Mode - probable Modulo - 2048, 3072, 4096 Primality Tests - 2pow100 Private Key Format - standard",
            "reference": "FIPS 186-5"
          },
          {
            "algorithm": "RSA KeyGen (FIPS186-5)",
            "cavpCertName": "A6536",
            "properties": "Key Generation Mode - probable Modulo - 2048, 3072, 4096 Primality Tests - 2pow100 Private Key Format - crt",
            "reference": "FIPS 186-5"
          },
          {
            "algorithm": "RSA SigGen (FIPS186- 5)",
            "cavpCertName": "A6535",
            "properties": "Modulo - 2048, 3072, 4096 Signature Type - pkcs1v1.5, pss",
            "reference": "FIPS 186-5"
          },
          {
            "algorithm": "RSA SigVer (FIPS186- 5)",
            "cavpCertName": "A6535",
            "properties": "Modulo - 2048, 3072, 4096 Signature Type - pkcs1v1.5, pss",
            "reference": "FIPS 186-5"
          },
          {
            "algorithm": "SHA-1",
            "cavpCertName": "A2713",
            "properties": "Message Length - Message Length: 0- 65536 Increment 8",
            "reference": "FIPS 180-4"
          },
          {
            "algorithm": "SHA2-256",
            "cavpCertName": "A2713",
            "properties": "Message Length - Message Length: 0- 65536 Increment 8",
            "reference": "FIPS 180-4"
          },
          {
            "algorithm": "SHA2-512",
            "cavpCertName": "A2713",
            "properties": "Message Length - Message Length: 0- 65536 Increment 8",
            "reference": "FIPS 180-4"
          }
        ],
        "found": true,
        "section": 2,
        "subsection": 5
      },
      "approved_services": {
        "entries": [
          {
            "description": "Load keys and data; APDU(s) used: DELETE, LOAD, INSTALL, MANAGE CHANNEL",
            "indicator": "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag \u002705\u0027 contains the status of",
            "inputs": "Comman d paramete rs (data objects, SSPs)",
            "name": "Manage Content (ISD Services)",
            "outputs": "Status Word (Respons e APDU 9000)",
            "rolesSspAccess": "Cryptographi c Officer - OS-SKEK: W,E,Z - SD-KENC: W,E,Z - SD-KMAC: W,E,Z - SD-KDEK: W,E,Z - DAP-DAPK: E",
            "secFunImpl": "KTS-1"
          },
          {
            "description": "",
            "indicator": "the Approve d mode complian cy ( \u002701\u0027 signifies that Approve d mode is active))",
            "inputs": "",
            "name": "",
            "outputs": "",
            "rolesSspAccess": "",
            "secFunImpl": ""
          },
          {
            "description": "Get or modify the card or applet life cycle status; APDU(s) used: SET STATUS, GET STATUS, TERMINATE (Zeroise)",
            "indicator": "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag \u002705\u0027 contains the status of the Approve d mode complian cy ( \u002701\u0027 signifies that Approve d mode is active))",
            "inputs": "Target status",
            "name": "Lifecycle (Show status and Perform zeroisation ) (SSD Services)",
            "outputs": "Status Word (Respons e APDU 9000)",
            "rolesSspAccess": "Cryptographi c Officer - OS-DRBG- EI: E,Z - OS- DRBG- KEY: E,Z - OS-DRBG- V: E,Z - OS-SKEK: E,Z - OS-MKEK: E,Z - SD-KENC: E,Z - SD-KMAC: E,Z - SD-KDEK: E,Z - SD-SENC: E,Z - SD-SMAC: E,Z - SD-RMAC: E,Z - DAP-DAPK: Z - RSA-PRIV- KEY: E,Z - EC-PRIV- KEY: E,Z - EC-KAS-Z: E,Z - RSA-PUB- KEY: E,Z - EC-PUB- KEY: E,Z - EC-KAS- PUB: E,Z",
            "secFunImpl": "KTS-1"
          },
          {
            "description": "Description",
            "indicator": "Indicato",
            "inputs": "Inputs",
            "name": "Name",
            "outputs": "Outputs",
            "rolesSspAccess": "SSP Access",
            "secFunImpl": "Security Functions"
          },
          {
            "description": "Load keys and data; APDU(s) used: PUT KEY, STORE DATA",
            "indicator": "r Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag \u002705\u0027 contains the status of the Approve d mode complian cy ( \u002701\u0027 signifies that Approve d mode is active))",
            "inputs": "Comman d paramete rs (data objects, SSPs)",
            "name": "Manage Content (SSD Services)",
            "outputs": "Status Word (Respons e APDU 9000)",
            "rolesSspAccess": "Cryptographi c Officer - OS-SKEK: W,E,Z - SD-KENC: W,E,Z - SD-KMAC: W,E,Z - SD-KDEK: W,E,Z - DAP-DAPK: E",
            "secFunImpl": "KTS-1"
          },
          {
            "description": "Establish and use a secure communicatio n channel; APDU(s) used: INITIALIZE, UPDATE, EXTERNAL AUTHENTICA TE",
            "indicator": "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag \u002705\u0027 contains",
            "inputs": "Comman d paramete rs (data objects, SSPs)",
            "name": "Secure Channel (SSD Services)",
            "outputs": "Status Word (Respons e APDU 9000)",
            "rolesSspAccess": "Cryptographi c Officer - OS-DRBG- EI: G,E,Z - OS- DRBG- KEY: G,E,Z - OS-DRBG- V: G,E,Z - OS-MKEK: G,E,Z - SD-KENC: G,E,Z - SD-KMAC: G,E,Z - SD-SENC: G,E,Z - SD-SMAC: G,E,Z",
            "secFunImpl": "Counter DRBG SCP03/sec ure channel KTS-1 Entropy Source OS-MKEK Generation"
          },
          {
            "description": "",
            "indicator": "the status of the Approve d mode complian cy ( \u002701\u0027 signifies that Approve d mode is active))",
            "inputs": "",
            "name": "",
            "outputs": "",
            "rolesSspAccess": "- SD-RMAC: G,E,Z - OS-DRBG- SEED: G,E,Z",
            "secFunImpl": ""
          },
          {
            "description": "Read Module data (privileged data objects, but no CSPs); APDU(s) used: GET DATA",
            "indicator": "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag \u002705\u0027 contains the status of the Approve d mode complian cy ( \u002701\u0027 signifies that Approve d mode is active))",
            "inputs": "Comman d: IDENTIF Y APDU",
            "name": "Privileged Info (Show module\u0027s versioning information ) (SSD Services)",
            "outputs": "Requeste d informati on; Status Word (Respons e APDU 9000)",
            "rolesSspAccess": "Cryptographi c Officer - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E",
            "secFunImpl": "KTS-1"
          },
          {
            "description": "Power cycle or reset the module; APDU(s) used: N/A",
            "indicator": "Status Word (Respon se APDU 9000);",
            "inputs": "Power cycle or reset the module",
            "name": "Card Reset",
            "outputs": "Status Word (Respons e APDU 9000)",
            "rolesSspAccess": "Cryptographi c Officer - OS-SKEK: E - SD-KENC:",
            "secFunImpl": "KTS-1"
          },
          {
            "description": "",
            "indicator": "Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag \u002705\u0027 contains the status of the Approve d mode complian cy ( \u002701\u0027 signifies that Approve d mode is active))",
            "inputs": "",
            "name": "",
            "outputs": "",
            "rolesSspAccess": "E - SD-KMAC: E - SD-KDEK: E User - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E Unauthentica ted",
            "secFunImpl": ""
          },
          {
            "description": "Select an applet or manage logical channels; APDU(s) used: SELECT, MANAGE CHANNEL",
            "indicator": "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag \u002705\u0027 contains the status of the Approve d mode",
            "inputs": "Comman d paramete rs (data objects, SSPs)",
            "name": "Context",
            "outputs": "Status Word (Respons e APDU 9000)",
            "rolesSspAccess": "Cryptographi c Officer - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E User - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E Unauthentica ted",
            "secFunImpl": "KTS-1"
          },
          {
            "description": "",
            "indicator": "complian cy ( \u002701\u0027 signifies that Approve d mode is active))",
            "inputs": "",
            "name": "",
            "outputs": "",
            "rolesSspAccess": "",
            "secFunImpl": ""
          },
          {
            "description": "Read unprivileged data objects, e.g., module configuration or status information (Show Status). This service includes the Pre- operational Self-Test on- demand; APDU(s) used: GET DATA",
            "indicator": "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag \u002705\u0027 contains the status of the Approve d mode complian cy ( \u002701\u0027 signifies that Approve d mode is active))",
            "inputs": "Comman d paramete rs (data objects, SSPs)",
            "name": "Info (Show status and Perform self-tests)",
            "outputs": "Status Word (Respons e APDU 9000)",
            "rolesSspAccess": "Cryptographi c Officer - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E User - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E Unauthentica ted",
            "secFunImpl": "Perform Self-Tests"
          },
          {
            "description": "Retrieve firmware version of the applet",
            "indicator": "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY",
            "inputs": "Comman d: Read Applet Version APDU (00 CA DF 65 00)",
            "name": "Get Applet Version",
            "outputs": "Status Word (Respons e APDU 9000)",
            "rolesSspAccess": "Cryptographi c Officer - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E",
            "secFunImpl": "None"
          },
          {
            "description": "",
            "indicator": "APDU can be used where the DF28 file tag \u002705\u0027 contains the status of the Approve d mode complian cy ( \u002701\u0027 signifies that Approve d mode is active))",
            "inputs": "",
            "name": "",
            "outputs": "",
            "rolesSspAccess": "- Marriage Code: W,E - Owner PIN: W,E - Passive Authenticatio n Key: E - Active Authenticatio n: E User - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E - Marriage Code: W,E - Owner PIN: W,E - Passive Authenticatio n Key: E - Active Authenticatio n: E",
            "secFunImpl": ""
          },
          {
            "description": "Inject keys (AES, ECDSA, RSA)",
            "indicator": "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag \u002705\u0027 contains the status of",
            "inputs": "Comman d paramete rs (data objects, SSPs)",
            "name": "Create data group",
            "outputs": "Status Word (Respons e APDU 9000)",
            "rolesSspAccess": "Cryptographi c Officer - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E - RSA-PRIV- KEY: W - RSA-PUB- KEY: W - EC-PUB- KEY: W - EC-PRIV- KEY: W - Application AES",
            "secFunImpl": "KTS-1"
          },
          {
            "description": "Description",
            "indicator": "Indicato r",
            "inputs": "Inputs",
            "name": "Name",
            "outputs": "Outputs",
            "rolesSspAccess": "SSP Access",
            "secFunImpl": "Security"
          },
          {
            "description": "",
            "indicator": "the Approve d mode complian cy ( \u002701\u0027 signifies that Approve d mode is active))",
            "inputs": "",
            "name": "",
            "outputs": "",
            "rolesSspAccess": "Communicati on : W - Marriage Code: W,E - Owner PIN: W,E - Passive Authenticatio n Key: E - Active Authenticatio n: E User - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E - RSA-PRIV- KEY: W - RSA-PUB- KEY: W - EC-PRIV- KEY: W - EC-PUB- KEY: W - Application AES Communicati on : W - Marriage Code: W,E - Owner PIN: W,E - Passive Authenticatio n Key: E - Active Authenticatio n: E",
            "secFunImpl": "Functions"
          },
          {
            "description": "Perform AES Encrypt, Decrypt, RSA Sign, Verify, Decrypt, ECDSA Verify",
            "indicator": "Status Word (Respon se APDU 9000); Approve",
            "inputs": "Comman d paramete rs (data objects, SSPs)",
            "name": "Perform Cryptograp hy",
            "outputs": "Status Word (Respons e APDU 9000)",
            "rolesSspAccess": "Cryptographi c Officer - RSA-PRIV- KEY: G,E - RSA-PUB- KEY: G,E",
            "secFunImpl": "Asymmetric Key Generation EC Crypto Operations RSA Crypto"
          },
          {
            "description": "",
            "indicator": "d mode indicator (IDENTI FY APDU can be used where the DF28 file tag \u002705\u0027 contains the status of the Approve d mode complian cy ( \u002701\u0027 signifies that Approve d mode is active))",
            "inputs": "",
            "name": "",
            "outputs": "",
            "rolesSspAccess": "- EC-PRIV- KEY: G,E - EC-PUB- KEY: G,E - Application AES Communicati on : E - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E - Marriage Code: W,E - Owner PIN: W,E - Passive Authenticatio n Key: E - Active Authenticatio n: E User - RSA-PRIV- KEY: G,E - EC-PRIV- KEY: G,E - RSA-PUB- KEY: G,E - EC-PUB- KEY: G,E - Application AES Communicati on : E - OS-SKEK: E - SD-KENC: E - SD-KMAC: E - SD-KDEK: E - Marriage Code: W,E",
            "secFunImpl": "Operations Symmetric Cipher Crypto Operations"
          },
          {
            "description": "",
            "indicator": "",
            "inputs": "",
            "name": "",
            "outputs": "",
            "rolesSspAccess": "- Owner PIN: W,E - Passive Authenticatio n Key: E - Active Authenticatio n: E",
            "secFunImpl": ""
          },
          {
            "description": "Key Agreement",
            "indicator": "Status Word (Respon se APDU 9000); Approve d mode indicator (IDENTI FY APDU can be used where the DF28 file tag \u002705\u0027 contains the status of the Approve d mode complian cy ( \u002701\u0027 signifies that Approve d mode is active))",
            "inputs": "Key identifier, Mechani sm identifier, Host ECC public key",
            "name": "ECDH Key Agreement",
            "outputs": "Status Word (Respons e APDU 9000)",
            "rolesSspAccess": "User - EC-KAS-Z: G,E,Z - EC-KAS- PUB: W,E,Z - EC-PRIV- KEY: G,E,Z",
            "secFunImpl": "KAS-1"
          }
        ],
        "found": true,
        "section": 4,
        "subsection": 3
      },
      "authentication_methods": {
        "entries": [
          {
            "description": "The Secure Channel Protocol authentica tion method is provided by the Secure Channel service; The SD- KENC and SD-KMAC keys are used to",
            "mechanism": "The external entity participati ng in the mutual authentica tion sends a 64-bit challenge to the Secure Element; The Secure Element generates",
            "name": "Platform Authentica tion (Secure Channel Protocol 03 Authentica tion Method)",
            "perMinute": "The module enforces a maximum of 60 failed Global Platform SCP03 authentication attempts before permanently blocking the card; The probability that a random attempt will succeed over a one-minute interval is (with the assumption here that one",
            "strength": "1/(2^128) = 2.9E - 39 (MAC||cryptogram) using a 128 - bit block for authentication; This authentication method includes a counter of failed authentication called \u0027velocity checking\u0027 by GlobalPlatform; The counter is decremented prior to any attempt to authenticate and is only reset to its threshold (maximum value) upon successful authentication"
          },
          {
            "description": "derive the SD- SENC, SD- SMAC, and SD- RMAC session keys; These sessions keys are used with AES-CBC and AES- CMAC to provide an end-to- end confidenti al and authentica ted protected channel (Approved KTS) between the external entity (User) and the module",
            "mechanism": "its own challenge and computes a 64-bit cryptogra m with SD-SMAC key and both challenge s; The Secure Element cryptogra m and challenge are sent to the external entity which checks the Secure Element cryptogra m and creates its own 64-bit cryptogra m with both challenge s; A 64-bit message authentica tion code (MAC) is also computed on the command containing the external entity cryptogra",
            "name": "",
            "perMinute": "attempt is possible per second): 60/(2^128) = 1.7E-37 (MAC||cryptogra m), using a 128 - bit block for authentication",
            "strength": ""
          },
          {
            "description": "",
            "mechanism": "m with AES- CMAC and SD- SMAC key; The MAC is concatena ted to the command, and the command is sent to the Secure Element; The Secure Element checks the message authentica tion code and compares the received cryptogra m to the calculated cryptogra m; If all of this succeeds, the two participant s are mutually authentica ted (the external entity is authentica ted to the Module)",
            "name": "",
            "perMinute": "",
            "strength": ""
          },
          {
            "description": "8 bytes PIN used",
            "mechanism": "-",
            "name": "Owner PIN",
            "perMinute": "Probability of Success: The",
            "strength": "The probability that a random- access attempt will succeed when"
          },
          {
            "description": "for authentica tion",
            "mechanism": "",
            "name": "",
            "perMinute": "probability of success for any single random- access attempt with a 8-byte PIN, is \u2248 5.4 x 10^ -19 Probability of Failure for One Attempt: The probability of a failure on any single random access attempt is: Pfailure=1-Psucc ess\u22481 (Since the success probability is so small, the failure probability is practically 1.) Probability of Failure for All Attempts in One Minute: If 60N attempts are made in one minute, the probability of failing on all attempts is: Pfailure (all)=(Pfailure)^ 60N \u22481^(60N) =1 (Again, this approximation assumes the success probability is negligible.) Probability of At Least One Success in One Minute: The probability of having at least one success is the complement of the probability",
            "strength": "using a PIN of size 8 bytes depends on the total number of possible PIN combinations. 1. PIN Size: 8 bytes means there are 8 * 8 = 64 bits (since 1 byte = 8 bits). 2. Possible Combinations: The number of possible PIN combinations is 2^64, as each bit can be either 0 or 1. Therefore, the total number of combinations is: 2^64=18,446,744,073,709,551,61 6 If a random-access attempt means choosing one of these combinations, and assuming all combinations are equally likely, the probability of a successful attempt is: Probability of success=1/2^64 This is an extremely small probability, roughly: 1/118,446,744,073,709,551,616\u2248 5.4\u00d710^-19 So, the probability of a successful random-access attempt with an 8-byte PIN is extraordinarily low"
          },
          {
            "description": "",
            "mechanism": "",
            "name": "",
            "perMinute": "of failing on all attempts: Psuccess (at least one)=1-Pfailure (all)=1-(Pfailure)^ (60N) Since Pfailure is extremely close to 1, we can estimate this probability as: Psuccess (at least one)\u2248 60N\u00d7Psuccess So, the probability of success within one minute, given N attempts per second, is: Psuccess (at least one)\u2248 60N\u00d76.8\u00d710^-49 Assuming 1 million attempts can be made per second = 10^6, the number of attemper per minute is: 60x10^6 = 60, 000, 000 attempts The probability of at least one success in one minute is: Psuccess (at least one)\u2248 60, 000, 000 attempts x 5.4\u00d710^-19 ~ 3.24 x 10 ^-11",
            "strength": ""
          },
          {
            "description": "20 bytes PIN used for authentica tion",
            "mechanism": "-",
            "name": "Marriage code",
            "perMinute": "Probability of Success: The probability of success for any single random- access attempt with a 20-byte",
            "strength": "The probability that a random- access attempt will succeed when using a PIN of size 8 bytes depends on the total number of possible PIN combinations. 1. PIN Size: 20 bytes means there are 20 * 8 = 160 bits (since 1 byte = 8"
          },
          {
            "description": "Descripti on",
            "mechanism": "Security Mechanis",
            "name": "Method Name",
            "perMinute": "Strength per Minute",
            "strength": "Strength Each Attempt"
          },
          {
            "description": "",
            "mechanism": "m",
            "name": "",
            "perMinute": "PIN, is \u22486.8\u00d710^-49 Probability of Failure for One Attempt: The probability of a failure on any single random access attempt is: Pfailure=1-Psucc ess\u22481 (Since the success probability is so small, the failure probability is practically 1.) Probability of Failure for All Attempts in One Minute: If 60N attempts are made in one minute, the probability of failing on all attempts is: Pfailure (all)=(Pfailure)^ 60N \u22481^(60N) =1 (Again, this approximation assumes the success probability is negligible.) Probability of At Least One Success in One Minute: The probability of having at least one success is the complement of the probability of failing on all attempts: Psuccess (at least",
            "strength": "bits). 2. Possible Combinations: The number of possible PIN combinations is 2^160, as each bit can be either 0 or 1. Therefore, the total number of combinations is: 2^160= 1,461,501,637,330,901,217,467,9 99,448 If a random-access attempt means choosing one of these combinations, and assuming all combinations are equally likely, the probability of a successful attempt is: Probability of success=1/2^160 This is an extremely small probability, roughly: 1/ 1,461,501,637,330,901,217,467,9 99,448 \u2248 6.8\u00d710^-49 So, t he probability of a successful random-access attempt with an 20-byte PIN is extraordinarily low"
          },
          {
            "description": "",
            "mechanism": "",
            "name": "",
            "perMinute": "one)=1-Pfailure (all)=1-(Pfailure)^ (60N) Since Pfailure is extremely close to 1, we can estimate this probability as: Psuccess (at least one)\u2248 60N\u00d7Psuccess So, the probability of success within one minute, given N attempts per second, is: Psuccess (at le ast one)\u2248 60N\u00d76.8\u00d710^-49 Assuming 1 million attempts can be made per second = 10^6, the number of attemper per minute is: 60x10^6 = 60, 000, 000 attempts The probability of at least one success in one minute is: Psuccess (at least one)\u2248 60, 000, 000 attempts x 6.8\u00d710^-49 ~ 4.08 x 10^-41",
            "strength": ""
          },
          {
            "description": "ECDSA P- 384 SHA2-384",
            "mechanism": "EC Crypto Operation s",
            "name": "Passive Authentica tion",
            "perMinute": "The probability of a single attempt succeeding is 3.5\u00d710^(-116); The probability of at least one successful attempt per second can be approximated as: 10^12 x 1/",
            "strength": "The private key is a random number in the range { 0 , 1 , 2 , \u2026 , \ud835\udc5b - 1 } {0,1,2,\u2026,n-1}, where \ud835\udc5b n is the order of the elliptic curve (approximately 2^384 for P-384); Since the key space is approximately 2^384, the probability of successfully forging a valid signature (i.e., a random- access attempt succeeding) is"
          },
          {
            "description": "",
            "mechanism": "",
            "name": "",
            "perMinute": "(2^384) = ~3.5 x 10 ^(-104); Since there are 60 seconds in a minute, multiply the probability per second by 60 to get the probability per minute: 60\u00d73.5x10^(-104) = 2.1 x 10^(-102)",
            "strength": "around: 1/(2^384) = ~ 3.5\u00d710^(- 116)"
          },
          {
            "description": "AES 256- bit key used (mode: ECB) to send random nonces to the SAM (an external applet). The SSID encrypts the nonce using this key, if the SAM can decrypt it, mutual authentica tion succeeds",
            "mechanism": "Symmetric Cipher Crypto Operation s",
            "name": "Active Authentica tion",
            "perMinute": "The probability of a successful random access is: 8.63\u00d710^(-78); The probability of success per minute is: 60\u00d78.63x10^(-78) = 5.18 x 10^(-76)",
            "strength": "To successfully decrypt the ciphertext and authenticate, the attacker would need to know the AES-256 key used for encryption; AES-256 bit key has a space of 2^256, so the probability of randomly guessing the correct key i.e. random access is = 1/(2^256) = ~8.63\u00d710^(-78)"
          }
        ],
        "found": true,
        "section": 4,
        "subsection": 1
      },
      "cond_self_tests": {
        "entries": [
          {
            "algorithmOrTest": "AES-CBC (A2713) - Encrypt",
            "condition": "Performed automatically on every boot",
            "details": "Encrypt",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "128-bit",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "AES-CBC (A2713) - Decrypt",
            "condition": "Performed automatically on every boot",
            "details": "Decrypt",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "128-bit",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "AES-CMAC (A2713) - Encrypt",
            "condition": "Performed automatically on every boot",
            "details": "Encrypt",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "128-bit",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "AES-CMAC (A2713) - Decrypt",
            "condition": "Performed automatically on every boot",
            "details": "Decrypt",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "128-bit",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "Counter DRBG (A2713)",
            "condition": "Performed automatically on every boot",
            "details": "Health Tests: Generate, Reseed, Instantiate functions per Section 11 in NIST SP800- 90Ar1",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "256-bit",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "ECDSA SigGen (FIPS186- 5) (A6534)",
            "condition": "Performed automatically on every boot",
            "details": "Signature Generation",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "P-521 SHA- 256",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "ECDSA SigVer (FIPS186- 5) (A6534)",
            "condition": "Performed automatically on every boot",
            "details": "Signature Verification",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "P-521 SHA- 256",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "KAS-ECC- SSC Sp800-",
            "condition": "Performed automatically on every boot",
            "details": "Shared Secret Computation (Z)",
            "indicator": "The APDU code 9000",
            "testMethod": "KAT",
            "testProps": "P-256 Scheme: onePassDh: KAS Role:",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "56Ar3 (A2713)",
            "condition": "",
            "details": "",
            "indicator": "signifies success",
            "testMethod": "",
            "testProps": "initiator, responder",
            "type": ""
          },
          {
            "algorithmOrTest": "KDA HKDF Sp800- 56Cr1 (A2713)",
            "condition": "Performed automatically on every boot",
            "details": "Key Derivation Function per NIST SP 800- 56Cr1",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "SHA-1, SHA2-256, SHA2-384, SHA2-512",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "KDF SP800-108 (A2713) - AES-128",
            "condition": "Performed automatically on every boot",
            "details": "Key Derivation Function per NIST SP 800- 108r1 (Counter mode)",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "Counter mode with AES-128",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "KDF SP800-108 (A2713) - HMAC- SHA1",
            "condition": "Performed automatically on every boot",
            "details": "Key Derivation Function per NIST SP 800- 108r1 (Counter mode)",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "Feedback Mode with HMAC-SHA1",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "RSA SigGen (FIPS186- 5) (A6535)",
            "condition": "Performed automatically on every boot",
            "details": "Signature Generation",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "2048-bit SHA2-256",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "RSA SigVer (FIPS186- 5) (A6535)",
            "condition": "Performed automatically on every boot",
            "details": "Signature Verification",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "2048-bit SHA2-256",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "SHA-1 (A2713)",
            "condition": "Performed automatically on every boot",
            "details": "Hash generation",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "SHA-1",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "SHA2-256 (A2713)",
            "condition": "Performed automatically on every boot",
            "details": "Hash generation",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "SHA2-256",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "SHA2-512 (A2713)",
            "condition": "Performed automatically on every boot",
            "details": "Hash generation",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "KAT",
            "testProps": "SHA2-512",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "Generate PCT",
            "condition": "Performed automatically on generation of keypairs",
            "details": "-",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "PCT",
            "testProps": "Pairwise consistency test performed when an asymmetric key pair is generated for RSA or ECC.",
            "type": "PCT"
          },
          {
            "algorithmOrTest": "Signature PCT",
            "condition": "Performed automatically on generation of keypairs",
            "details": "-",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "PCT",
            "testProps": "Pairwise consistency test performed when a signature is generated for RSA or ECDSA",
            "type": "PCT"
          },
          {
            "algorithmOrTest": "Firmware Load Test",
            "condition": "Upon loading of the SSID applet",
            "details": "Signature Verification based on ECDSA P- 256 with SHA2-256",
            "indicator": "The APDU code 9000 signifies success",
            "testMethod": "Load Test",
            "testProps": "ECDSA P- 256 with SHA2-256",
            "type": "SW/FW Load"
          },
          {
            "algorithmOrTest": "NIST SP800-90B ENT (P) Repetition Count Test (RCT)",
            "condition": "Performed continuously by the entropy source",
            "details": "-",
            "indicator": "Implicit, based on output of entropy",
            "testMethod": "NIST SP 800- 90B Health Test",
            "testProps": "-",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "NIST SP800-90B ENT (P) Developer Defined Heath Test Transition Count Test",
            "condition": "Performed continuously by the entropy source",
            "details": "-",
            "indicator": "Implicit, based on output of entropy",
            "testMethod": "NIST SP 800- 90B Health Test",
            "testProps": "-",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "NIST SP800-90B ENT (P) Developer",
            "condition": "Performed continuously by the",
            "details": "-",
            "indicator": "Implicit, based on output of entropy",
            "testMethod": "NIST SP 800- 90B",
            "testProps": "-",
            "type": "CAST"
          },
          {
            "algorithmOrTest": "Defined Heath Test Chi - Square Test",
            "condition": "entropy source",
            "details": "",
            "indicator": "",
            "testMethod": "Health Test",
            "testProps": "",
            "type": ""
          },
          {
            "algorithmOrTest": "NIST SP800-90B ENT (P) Developer Defined Heath Test Amplitude Limiter Analog Test",
            "condition": "Performed continuously by the entropy source",
            "details": "-",
            "indicator": "Implicit, based on output of entropy",
            "testMethod": "NIST SP 800- 90B Health Test",
            "testProps": "-",
            "type": "CAST"
          }
        ],
        "found": true,
        "section": 10,
        "subsection": 2
      },
      "error_states": {
        "entries": [
          {
            "conditions": "In case of failure of a pre- operational, conditional self- test or NIST SP 800-90B compliant entropy source health test.",
            "description": "All the Self-Tests can be performed on-demand with the GET DATA APDU command (Info service) with the following parameters: CLA = 80, INS = CA, P1 = 00, P2 = FE, Lc = 04, Incoming Data = DF4B0120, and Le = 00. The expected result is FE04DF4B0120. The return code 9000 signifies success. In case of a failure, the module",
            "indicator": "66A7",
            "name": "Hard Error (MUTE) state",
            "recoveryMethod": "A reset of the module can be attempted but in the event that the error persists, the module must be returned to the vendor"
          },
          {
            "conditions": "",
            "description": "enters a hard error (MUTE) state and returns a code/status indicator",
            "indicator": "",
            "name": "",
            "recoveryMethod": ""
          }
        ],
        "found": true,
        "section": 10,
        "subsection": 4
      },
      "mechanisms_actions": {
        "entries": [
          {
            "inspectFreq": "N/A",
            "inspectGuidance": "N/A",
            "mechanism": "Hard, tamper evident coating"
          }
        ],
        "found": true,
        "section": 7,
        "subsection": 1
      },
      "modes_of_operation": {
        "entries": [
          {
            "description": "The module supports the Approved mode of operation after following the initialization instructions outlined in Section 11.1",
            "name": "Approved mode",
            "statusIndicator": "To verify that the GlobalPlatform operational environment runs in the Approved mode of operation, use the IDENTIFY APDU. The DF28 file tag \u002705\u0027 contains the status of the Approved mode compliancy, where \u002700\u0027 identifies Approved mode not active and \u002701\u0027 - Approved mode active. The Lifecycle service (GET STATUS APDU/command) can be used to verify that the SSID applet is in the Approved mode of operation (it is in this mode by default post initialization): Command: 00 CA DF 66 00; Output Data: 01; Status: 90 00",
            "type": "Approved"
          }
        ],
        "found": true,
        "section": 2,
        "subsection": 4
      },
      "non_approved_allowed_NSC": {
        "entries": [
          {
            "caveat": "no security claimed",
            "name": "RSA Encryption using PKCS1.5 padding",
            "use": "Used to encrypt and protect keys; Per IG 2.4.A example 1."
          }
        ],
        "found": true,
        "section": 2,
        "subsection": 5
      },
      "non_approved_allowed_algos": {
        "entries": [],
        "found": false,
        "section": 2,
        "subsection": 5
      },
      "non_approved_not_allowed": {
        "entries": [],
        "found": false,
        "section": 2,
        "subsection": 5
      },
      "non_approved_services": {
        "entries": [],
        "found": false,
        "section": 4,
        "subsection": 4
      },
      "ports_interfaces": {
        "entries": [
          {
            "data": "These interfaces are used to supply power to the module in contact mode; The module starts when interface is powered",
            "logicalInterface": "Power",
            "physicalPort": "VSS, VDD"
          },
          {
            "data": "These interfaces are used to supply power to the module in contact, contactless and I2C mode",
            "logicalInterface": "Power",
            "physicalPort": "VIN, VOUT"
          },
          {
            "data": "If a signal is sent on this interface on contact mode, the module will reboot (active low)",
            "logicalInterface": "Control Input",
            "physicalPort": "RST_N"
          },
          {
            "data": "The interface is used by an external device (ex: smartcard reader) to provide a clock signal to the IC in contact mode; The IC will derive its own clock from this signal",
            "logicalInterface": "Control Input",
            "physicalPort": "CLK"
          },
          {
            "data": "The interface is used to communicate with an external entity (ex: SmartCard reader) in contact mode; It also functions as I2C master SDA in I2C mode",
            "logicalInterface": "Data Input Data Output Control Input Status Output",
            "physicalPort": "IO1"
          },
          {
            "data": "The interface is used to communicate with an external entity (ex: SmartCard reader) in contact mode; It also functions as I2C master SCL in I2C mode or as SPI interface",
            "logicalInterface": "Data Input Data Output Control Input",
            "physicalPort": "IO2"
          },
          {
            "data": "",
            "logicalInterface": "Status Output",
            "physicalPort": ""
          },
          {
            "data": "The interface is used to communicate with an external entity (ex: smartcard reader) in contactless mode; This interface is also used to set the internal clock and to supply power to the module",
            "logicalInterface": "Data Input Data Output Control Input Status Output Power",
            "physicalPort": "LA, LB"
          },
          {
            "data": "The interface is used to communicate with an external entity such as a host controller",
            "logicalInterface": "Data Input Data Output Control Input Status Output",
            "physicalPort": "SDA"
          },
          {
            "data": "The interface is used by an external device (ex: host controller) to provide a clock signal to the I2C HW",
            "logicalInterface": "Control Input",
            "physicalPort": "SCL"
          }
        ],
        "found": true,
        "section": 3,
        "subsection": 1
      },
      "roles": {
        "entries": [
          {
            "authMethodList": "Platform Authentication (Secure Channel Protocol 03 Authentication Method) Owner PIN Marriage code Passive Authentication Active Authentication",
            "name": "Cryptographic Officer",
            "operatorType": "Cryptographic Officer",
            "type": "Identity"
          },
          {
            "authMethodList": "Platform Authentication (Secure Channel Protocol 03 Authentication Method) Owner PIN Marriage code Passive Authentication Active Authentication",
            "name": "User",
            "operatorType": "User",
            "type": "Identity"
          }
        ],
        "found": true,
        "section": 4,
        "subsection": 2
      },
      "security_levels": {
        "entries": [
          {
            "level": "3",
            "section": "1",
            "title": "General"
          },
          {
            "level": "3",
            "section": "2",
            "title": "Cryptographic module specification"
          },
          {
            "level": "3",
            "section": "3",
            "title": "Cryptographic module interfaces"
          },
          {
            "level": "3",
            "section": "4",
            "title": "Roles, services, and authentication"
          },
          {
            "level": "3",
            "section": "5",
            "title": "Software/Firmware security"
          },
          {
            "level": "N/A",
            "section": "6",
            "title": "Operational environment"
          },
          {
            "level": "4",
            "section": "7",
            "title": "Physical security"
          },
          {
            "level": "3",
            "section": "8",
            "title": "Non-invasive security"
          },
          {
            "level": "3",
            "section": "9",
            "title": "Sensitive security parameter management"
          },
          {
            "level": "3",
            "section": "10",
            "title": "Self-tests"
          },
          {
            "level": "3",
            "section": "11",
            "title": "Life-cycle assurance"
          },
          {
            "level": "3",
            "section": "12",
            "title": "Mitigation of other attacks"
          },
          {
            "level": "3",
            "section": "",
            "title": "Overall Level"
          }
        ],
        "found": true,
        "section": 1,
        "subsection": 2
      },
      "self_tests": {
        "entries": [
          {
            "algorithmOrTest": "Firmware Integrity",
            "details": "-",
            "indicator": "9000",
            "testMethod": "32-bit CRC",
            "testProps": "32-bit CRC performed over all code located in Flash",
            "type": "SW/FW Integrity"
          }
        ],
        "found": true,
        "section": 10,
        "subsection": 1
      },
      "ssp_io_methods": {
        "entries": [
          {
            "dest": "Stored in NVM - Encrypt ed",
            "distribution": "Automated",
            "entry": "Electron ic",
            "format": "Encrypt ed",
            "name": "Imported in secure channel specified by GP- Amd-I",
            "sfiAlgo": "KTS-1",
            "source": "External endpoint"
          },
          {
            "dest": "Stored in NVM encrypte d with Approve d AES",
            "distribution": "Automated",
            "entry": "Electron ic",
            "format": "Encrypt ed",
            "name": "Encrypted using AES-CBC (using SD- KDEK) (RFC 3394 method) and transported",
            "sfiAlgo": "KTS-1",
            "source": "External endpoint"
          },
          {
            "dest": "CBC with OS- MKEK",
            "distribution": "",
            "entry": "",
            "format": "",
            "name": "using platform SCP03",
            "sfiAlgo": "",
            "source": ""
          },
          {
            "dest": "Stored in NVM - Encrypt ed",
            "distribution": "Automated",
            "entry": "Electron ic",
            "format": "Encrypt ed",
            "name": "Entered encrypted with the previous SD-KDEK",
            "sfiAlgo": "KTS-1",
            "source": "External endpoint"
          },
          {
            "dest": "N/A",
            "distribution": "N/A",
            "entry": "N/A",
            "format": "Plaintext",
            "name": "Not Imported",
            "sfiAlgo": "",
            "source": "N/A"
          },
          {
            "dest": "N/A",
            "distribution": "N/A",
            "entry": "N/A",
            "format": "Plaintext",
            "name": "Not Exported",
            "sfiAlgo": "",
            "source": "N/A"
          },
          {
            "dest": "External Endpoin t",
            "distribution": "Automated",
            "entry": "Electron ic",
            "format": "Encrypt ed",
            "name": "Exported using Approved KTS",
            "sfiAlgo": "KTS-1",
            "source": "Stored in NVM - Encrypted"
          },
          {
            "dest": "Stored in NVM - Encrypt ed",
            "distribution": "N/A",
            "entry": "N/A",
            "format": "Encrypt ed",
            "name": "Entered during manufacturing/p re- personalization",
            "sfiAlgo": "",
            "source": "Vendor generated at manufacture/duri ng pre- personalization"
          },
          {
            "dest": "Stored in NVM",
            "distribution": "N/A",
            "entry": "N/A",
            "format": "Plaintext",
            "name": "Entered during manufacturing/ pre- personalization - plaintext storage",
            "sfiAlgo": "",
            "source": "Vendor generated at manufacture/duri ng pre- personalization"
          }
        ],
        "found": true,
        "section": 9,
        "subsection": 2
      },
      "ssp_zeroization_methods": {
        "entries": [
          {
            "description": "Ephemeral parameter",
            "method": "Power-off",
            "operatorId": "Operator initiation",
            "rationale": "Cleared upon power cycling the module"
          },
          {
            "description": "Overwritten with zeroes",
            "method": "Destroyed by termination of the module (LifeCycle/Perform Zeroisation service)",
            "operatorId": "Operator initiation",
            "rationale": "Setting the module to the TERMINATE state triggers zeroisation and renders the module unusable"
          },
          {
            "description": "-",
            "method": "Destroyed because of OS- MKEK zeroisation",
            "operatorId": "Module initiation",
            "rationale": "Zeroising the root of trust causes zeroisation of SSPs derived from it"
          },
          {
            "description": "Ephemeral shared secret",
            "method": "Cleared immediately following return to the caller",
            "operatorId": "Module initiation",
            "rationale": "Shared secret computed is zeroised post being returned to caller (for use internal to the module)"
          }
        ],
        "found": true,
        "section": 9,
        "subsection": 3
      },
      "storage_areas": {
        "entries": [
          {
            "description": "plaintext (does not persist beyond a power cycle); object identifier to entity association",
            "name": "Temporarily stored in RAM",
            "persistance": "Dynamic"
          },
          {
            "description": "plaintext; object identifier to entity association",
            "name": "Stored in NVM",
            "persistance": "Static"
          },
          {
            "description": "encrypted with Approved AES CBC with OSMKEK; key version to entity association",
            "name": "Stored in NVM - Encrypted",
            "persistance": "Static"
          },
          {
            "description": "plaintext (persists beyond a power cycle); identity- based authentication data",
            "name": "Plaintext: Persistent",
            "persistance": "Static"
          }
        ],
        "found": true,
        "section": 9,
        "subsection": 1
      },
      "tested_module_id_hw": {
        "entries": [
          {
            "features": "The GlobalPlatform operational environment is identified with the Platform ID, the ROM ID,",
            "fwVersion": "Platform ID: J3R6000373181200 ROM ID: B3375FE9B5508BC4;",
            "hwVersion": "N7122 A1",
            "modelPartNum": "P71D600",
            "processors": "MRK3-SC 16/32-bit RISC CPU"
          },
          {
            "features": "the Patch ID, and other information, describing the content in ROM, NVM and loaded patches. The Platform ID is a data string that allows the identification of the P71D600 Card",
            "fwVersion": "Patch ID: 00000000 00000000; SSID v3.0.0.1.1",
            "hwVersion": "",
            "modelPartNum": "",
            "processors": ""
          }
        ],
        "found": true,
        "section": 2,
        "subsection": 2
      },
      "tested_module_id_hw_hy": {
        "entries": [],
        "found": false,
        "section": 2,
        "subsection": 2
      },
      "tested_module_id_sw_fw_hy": {
        "entries": [],
        "found": false,
        "section": 2,
        "subsection": 2
      },
      "tested_op_env_sw_fw_hy": {
        "entries": [],
        "found": false,
        "section": 2,
        "subsection": 2
      },
      "vendor_affirmed_algos": {
        "entries": [
          {
            "algoPropList": "Key Type:Symmetric and Asymmetric",
            "implName": "N/A",
            "name": "CKG SP800- 133r2 Section 4",
            "reference": "NIST SP800-133r2 Section 4: Symmetric keys and seeds for asymmetric key generation are generated using methods described in Section 4 of SP800-133r2 (example 1). The module supports the following per NIST SP 800-133r2: 1. Section 5.1: Key Pairs for Digital Signature Schemes 2. Section 6.2.1: Symmetric Keys Generated Using Key-Agreement Schemes 3. Section 6.2.2: Symmetric Keys Derived from a Pre-existing Key 4. Section 6.4: Distributing the Generated Symmetric Key"
          },
          {
            "algoPropList": "Key Type :Symmetric",
            "implName": "N/A",
            "name": "CKG SP 800- 133r2 Section 6.3",
            "reference": "NIST SP 800-133r2 Section 6.3 Symmetric Keys Produced by Combining (Multiple) Keys and Other Data (approach/method 2. Exclusive-Oring one"
          },
          {
            "algoPropList": "",
            "implName": "",
            "name": "",
            "reference": "or more symmetric keys and possibly one or more other items of data)"
          }
        ],
        "found": true,
        "section": 2,
        "subsection": 5
      },
      "vendor_affirmed_op_env_sw_fw_hy": {
        "entries": [],
        "found": false,
        "section": 2,
        "subsection": 2
      }
    },
    "is_br1_format": true,
    "keywords": {
      "asymmetric_crypto": {
        "ECC": {
          "ECC": {
            "ECC": 3
          },
          "ECDH": {
            "ECDH": 5
          },
          "ECDSA": {
            "ECDSA": 24
          }
        }
      },
      "certification_process": {},
      "cipher_mode": {
        "CBC": {
          "CBC": 4
        },
        "ECB": {
          "ECB": 3
        }
      },
      "cplc_data": {},
      "crypto_engine": {},
      "crypto_library": {},
      "crypto_protocol": {},
      "crypto_scheme": {
        "KA": {
          "Key Agreement": 4
        },
        "MAC": {
          "MAC": 5
        }
      },
      "device_model": {},
      "ecc_curve": {
        "NIST": {
          "P-224": 8,
          "P-256": 24,
          "P-384": 18,
          "P-521": 10
        }
      },
      "eval_facility": {},
      "fips_cert_id": {},
      "fips_certlike": {
        "Certlike": {
          "AES- 128": 1,
          "AES-128": 2,
          "AES-256": 4,
          "HMAC- SHA1": 1,
          "HMAC-SHA-1": 2,
          "HMAC-SHA1": 4,
          "PKCS1": 2,
          "SHA- 256": 2,
          "SHA-1": 8,
          "SHA1": 1,
          "SHA2-224": 2,
          "SHA2-256": 13,
          "SHA2-384": 5,
          "SHA2-512": 8
        }
      },
      "fips_security_level": {
        "Level": {
          "Level 3": 3,
          "Level 4": 1
        }
      },
      "hash_function": {
        "SHA": {
          "SHA1": {
            "SHA-1": 8,
            "SHA1": 1
          }
        }
      },
      "ic_data_group": {},
      "javacard_api_const": {},
      "javacard_packages": {},
      "javacard_version": {},
      "os_name": {
        "JCOP": {
          "JCOP 4": 4
        }
      },
      "pq_crypto": {},
      "randomness": {
        "PRNG": {
          "DRBG": 20
        },
        "RNG": {
          "RBG": 2
        }
      },
      "side_channel_analysis": {
        "FI": {
          "Fault Induction": 4,
          "fault induction": 2
        },
        "SCA": {
          "DPA": 1,
          "SPA": 1
        }
      },
      "standard_id": {
        "FIPS": {
          "FIPS 140-3": 11,
          "FIPS 180-4": 3,
          "FIPS 186-5": 8,
          "FIPS 198-1": 1,
          "FIPS140-3": 1,
          "FIPS186-5": 19
        },
        "NIST": {
          "NIST SP 800-90B": 1,
          "SP 800-108": 2,
          "SP 800-140C": 1,
          "SP 800-38A": 3,
          "SP 800-38B": 1,
          "SP 800-38C": 1,
          "SP 800-38F": 1,
          "SP 800-56A": 1,
          "SP 800-56B": 1,
          "SP 800-56C": 1,
          "SP 800-90A": 1
        },
        "PKCS": {
          "PKCS1": 1
        },
        "RFC": {
          "RFC 3394": 3
        },
        "SCP": {
          "SCP03": 6
        }
      },
      "symmetric_crypto": {
        "AES_competition": {
          "AES": {
            "AES": 17,
            "AES-": 3,
            "AES-128": 2,
            "AES-256": 4
          },
          "CAST": {
            "CAST": 40
          }
        },
        "DES": {
          "3DES": {
            "Triple-DES": 3
          }
        },
        "constructions": {
          "MAC": {
            "CMAC": 4,
            "HMAC": 3,
            "KMAC": 1
          }
        },
        "miscellaneous": {
          "SEED": {
            "SEED": 2
          }
        }
      },
      "tee_name": {
        "AMD": {
          "PSP": 3
        },
        "IBM": {
          "SSC": 1
        }
      },
      "tls_cipher_suite": {},
      "vendor": {
        "NXP": {
          "NXP": 7,
          "NXP Semiconductors": 1
        }
      },
      "vulnerability": {}
    },
    "module_algorithms": {
      "_type": "Set",
      "elements": [
        "ECDSA KeyGen (FIPS186-5)A6534",
        "SHA2-256A2713",
        "AES-CCMA2713",
        "Counter DRBGA2713",
        "ECDSA SigGen (FIPS186-5)A6534",
        "RSA SigGen (FIPS186-5)A6535",
        "SHA2-512A2713",
        "SHA-1A2713",
        "RSA SigVer (FIPS186-5)A6535",
        "KDF SP800-108A2713",
        "RSA Decryption Primitive Sp800-56Br2A5911",
        "AES-CTRA2713",
        "AES-CBCA2713",
        "AES-ECBA2713",
        "RSA KeyGen (FIPS186-5)A6536",
        "KAS-ECC-SSC Sp800-56Ar3A2713",
        "ECDSA SigVer (FIPS186-5)A6534",
        "AES-CMACA2713",
        "KDA HKDF Sp800-56Cr1A2713",
        "HMAC-SHA-1A2713"
      ]
    },
    "policy_algorithms": {
      "_type": "Set",
      "elements": [
        "#A5911",
        "#A6534",
        "#A6535",
        "#A6536",
        "#A2713"
      ]
    },
    "policy_metadata": {
      "/Author": "Prasiddhi Tembulkar  Intertek",
      "/CreationDate": "D:20260626082852-04\u002700\u0027",
      "/Creator": "Microsoft\u00ae Word for Microsoft 365",
      "/ModDate": "D:20260626082852-04\u002700\u0027",
      "/Producer": "Microsoft\u00ae Word for Microsoft 365",
      "pdf_file_size_bytes": 782022,
      "pdf_hyperlinks": {
        "_type": "Set",
        "elements": [
          "https://csrc.nist.gov/projects/cryptographic-module-validation-program",
          "https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/entropy/E148_PublicUse.pdf"
        ]
      },
      "pdf_is_encrypted": false,
      "pdf_number_of_pages": 61
    }
  },
  "state": {
    "_type": "sec_certs.sample.fips.InternalState",
    "module": {
      "_type": "sec_certs.sample.document_state.DocumentState",
      "convert_ok": true,
      "download_ok": true,
      "extract_ok": true,
      "json_hash": null,
      "source_hash": null,
      "txt_hash": null
    },
    "policy": {
      "_type": "sec_certs.sample.document_state.DocumentState",
      "convert_ok": true,
      "download_ok": true,
      "extract_ok": true,
      "json_hash": "fbd36ae284a5ff5e4da66051fb0ff810825f00d5e5401005c5cb603d2b9ecaf6",
      "source_hash": "05a4f05ed2d2e6d68dfce13411a450741758d82bf316ae5335a519a028780acd",
      "txt_hash": "ce376fe06b225a8722d4aeed443ed89fa0d4a8ebbf408f050ef1c1fcb7a5d40e"
    }
  },
  "web_data": {
    "_type": "sec_certs.sample.fips.FIPSCertificate.WebData",
    "caveat": "No assurance of minimum security of SSPs (e.g., keys, bit strings) that are externally loaded, or of SSPs established with externally loaded SSPs.",
    "certificate_pdf_url": "https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/certificates/June 2026_080726_0648.pdf",
    "date_sunset": "2031-06-29",
    "description": "The Module is composed of a GlobalPlatform operational environment and a single Java Card applet \u2013 the SSID, running on the NXP P71D600 chip.",
    "embodiment": "SingleChip",
    "exceptions": [
      "Operational environment: N/A",
      "Physical security: Level 4"
    ],
    "fw_versions": null,
    "historical_reason": null,
    "hw_versions": null,
    "level": 3,
    "mentioned_certs": {},
    "module_name": "ST Engineering \u0026 i-Engine SSID Applet on NXP P71D600",
    "module_type": "Hardware",
    "revoked_link": null,
    "revoked_reason": null,
    "standard": "FIPS 140-3",
    "status": "active",
    "sw_versions": null,
    "tested_conf": null,
    "validation_history": [
      {
        "_type": "sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry",
        "date": "2026-06-30",
        "lab": "Acumen Security",
        "validation_type": "Initial"
      }
    ],
    "vendor": "ST Engineering Urban Solutions Ltd. and i-Engine Pte Ltd.",
    "vendor_url": "http://www.stengg.com"
  }
}

Sections

ST Engineering & i-Engine SSID Applet on NXP P71D600

Certificate details

Security policy

Extracted keywords

Symmetric Algorithms

Asymmetric Algorithms

Hash functions

Schemes

Randomness

Elliptic Curves

Block cipher modes

Operating System name

Trusted Execution Environments

Vendor

Security level

Side-channel analysis

Standards

File metadata

Automated analysis

Automated inference - use with caution

Cross-references

Processing updates

Certificate changed

Certificate changed

Certificate changed

Certificate changed

Certificate changed

Certificate changed

Certificate changed

New certificate

Raw data

Sections

ST Engineering & i-Engine SSID Applet on NXP P71D600

Certificate details

Security policy

Extracted keywords

Cryptography

Symmetric Algorithms

Asymmetric Algorithms

Hash functions

Schemes

Randomness

Elliptic Curves

Block cipher modes

Device

Operating System name

Trusted Execution Environments

Vendor

Security

Security level

Side-channel analysis

Other

Standards

File metadata

Automated analysis

Automated inference - use with caution

Cross-references

Processing updates

Raw data

Toggle raw data