ST33TPHF20SPI datasheet(38/47 Pages) STMICROELECTRONICS

38 / 47 page

FIPS140-2 SECURITY POLICY

Page 38 of 47

NON-PROPRIETARY DOCUMENT

SELF-TESTS

Self-tests run by the cryptographic module are split in three categories:



Power-up self-tests



Full self-tests



Conditional self-tests

The power-on self-tests do not require operator intervention in order to run. Power-on self-

tests execution completes all tests except KATs on asymmetric algorithms (RSA, ECDSA,

ECDH). Completion of power-on self-tests allows the TPM to be in a limited approved mode

allowing to process only a subset of TPM commands (see §1.7.2.1).

To switch from limited approved mode to full approved mode, operator shall execute

TPM_SelfTestFull command. This command requests the module to switch mode by

executing all self-tests listed in Table 22 : Asymmetric cryptography self-tests list (power-up

self-tests plus the remaining self-tests, that mainly concern asymmetric cryptography).

The security module

outputs an “error” Return Code via the status interface when the error

state is entered due to a failed self-test. While in error state, security module does not perform

any cryptographic functions and all data output via the data output interface are inhibited.

If power-on self-tests have passed successfully, no status is indicated but commands that

require self-tests to be completed can be successfully executed.

4.1

Power-up tests list

Table 21 : Power-up self-tests list

Algorithm

tested

Test description

SHA1

SHA1 computation on known data (16 bytes) and comparison of output to the expected

digest (20 bytes)

SHA256

SHA256 computation on known data (16 bytes) and comparison of output to the expected

digest (32 bytes)

HMAC

SHA256

HMAC-SHA256 computation on known data (16 bytes) / known key (16 bytes, same value

as data) and comparison of output to the expected MAC (32 bytes). Self-test allows

validating the secure SHA algorithm also used in standalone (out of HMAC context).

KDF SP800-

108

KDF (based on SHA1) computation on known data (16 bytes) / known label (“TEST”) and

comparison of output to the expected value (32 bytes).

Hash-

DRBG

Instantiate, Generate and Reseed API are tested in a single test sequence in accordance

with §11.3 of [SP800-90A]. Output of HDRBG (55 bytes) is compared to a reference value.

AES

AES CFB encryption is done on known data (32 bytes) / known key (16 bytes) and known IV

(16 bytes, same value as key). The 32 bytes output data are compared to the expected

reference data. If comparison succeeds, AES CFB decryption is done on encrypted data

with same key & same IV as encryption. 32 bytes output are compared to the initial

plaintext data.

Triple-DES

Triple-DES CFB encryption is done on known data (32 bytes) / known key (24 bytes) and

known IV (8 bytes). The 32 bytes output data are compared to the expected reference

data. If comparison succeeds, Triple-DES CFB decryption is done on encrypted data with

same key & same IV as encryption. 32 bytes output are compared to the initial plaintext

data.

ST33TPHF20SPI датащи(PDF) 38 Page - STMicroelectronics

ST33TPHF20SPI датащи(HTML) 38 Page - STMicroelectronics

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47

датащи скачать

ссылки URL