The Platform Security Architecture initiative defines a set of common APIs meant to level the field around secure services offered by a Root of Trust. Those APIs cover a minimal set of services that should be included into all devices like cryptography, secure storage, attestation, and firmware update.
Crypto vendors may also be interested in adopting just the Crypto API part for their crypto libraries or hardware.
PSA Certified delivers compliance badges for both device-level vendors who want to check their compliance agains the whole API set, and Crypto compliance badges for crypto vendors who want to check their compliance against all or a subset of the Crypto API.
The official name for those APIs is PSA Certified APIs. API specifications are placed in PSA API github site.
Other common ways to refer to those APIs are: PSA APIs, PSA functional APIs.
PSA Certified Crypto API is often shortened to Crypto API in documentation.
PSA Certification aims at grading the robustness of Root of Trust implementations.
PSA Certification does not mandate the implementation of the PSA Certified APIs. Root of Trust implementers are free to choose whatever interfaces they want to offer to their users, the certification process only looks at security properties and robustness offered by implementations.
PSA API compliance aims at measuring adoption for the APIs, by delivering compliance badges to implementers of those APIs. PSA API implementations do not need to be certified by PSA at any level to receive a compliance badge.
In summary: you can PSA-certify a product without implementing PSA Certified APIs, and you can implement PSA Certified APIs and seek the compliance badge without applying for PSA Certification.
No. PSA certification is about estimating the robustness of Root of Trust implementations. The PSA Certified initiative came to the conclusion that standardization of Root of Trust service APIs would be a helpful tool to help democratize security on as many devices as possible, and thus the PSA Certified APIs were born out of the PSA Certified initiative. They are part of the same initiative but serve different purposes.
The general API compliance badge is meant for Device vendors who provide access to their Root of Trust services through PSA APIs: Crypto, Secure Storage, and Attestation.
For device vendors, obtaining the API compliance badge is a way to communicate to their customers that they can rely on the presence of standardized APIs to access Root of Trust services. The minimum requirement to pass general API compliance is to support:
- Enough Crypto APIs to support TF-M Profile Small, i.e.
crypto_hash,crypto_cipher, andcrypto_rng. - At least one Secure Storage service: ITS (Internal Trusted Storage) or PS (Protected Storage), or both.
- The Attestation service API.
Once you get your badge, your product will be displayed on PSA Certified products.
The Crypto API compliance badge is meant for pure crypto players who provide access to their crypto software or hardware through PSA Certified Crypto APIs.
Product examples include open-source and commercial crypto libraries, crypto hardware accelerators, secure elements, smart cards, TPM equivalents, TrustZone-based services, and anything that offers high-level cryptography services like hash, signature, or encryption.
For pure crypto players, obtaining the Crypto API compliance badge is a way to communicate to their customers:
- Compliance with the Crypto API standard, implying no need for developers to re-learn yet another proprietary API.
- How many high-level crypto services are supported by a given crypto product.
Ideally, it should be possible for developers to determine at a glance whether a crypto engine (hardware or software) has enough functionality to implement their use cases. This is exactly what the Crypto API compliance badge is trying to achieve.
High-level crypto services describe the main operations offered by a crypto engine (hardware or software) like encrypt/decrypt, sign/verify, hash, generate random, and key derivation and agreement protocols. Most crypto use cases can be described by combining those high-level functions.
Announcing high-level crypto services is useful for developers looking for ways to develop cryptography-based use cases like secure network connections, secure storage, or authentication protocols. For example, establishing a handshake in a mutually-authenticated protocol may require key agreement, key generation, symmetric ciphers, and hash functions.
| High-level Crypto services | Crypto badge mention |
|---|---|
| Hash | crypto_hash |
| MAC | crypto_mac |
| Symmetric and stream ciphers | crypto_cipher |
| Asymmetric signature and verification | crypto_asym_sign |
| Asymmetric encryption/decryption | crypto_asym_crypt |
| Authenticated Encryption with Associated Data | crypto_aead |
| Key derivation | crypto_derivation |
| Key agreement | crypto_agreement |
| Random Number Generation | crypto_rng |
| PAKE algorithm support | crypto_pake |
Functions that need to be implemented for each badge:
| Badge mention | Functions |
|---|---|
| All badges | initimport_keyexport_keydestroy_keykey_attributes_set_getgenerate_keycopy_key |
crypto_hash |
hash_setuphash_updatehash_verifyhash_finishhash_aborthash_cloneoptional: hash_computehash_comparehash_suspendhash_resume |
crypto_mac |
mac_sign_setupmac_updatemac_sign_finishmac_verify_setupmac_verify_finishmac_abortoptional: mac_computemac_verifymac_sign_multipartmac_verify_multipart |
crypto_asym_sign |
sign_hashverify_hashsign_messageverify_message |
crypto_asym_crypt |
asymmetric_encryptasymmetric_decrypt |
crypto_cipher |
cipher_encryptcipher_decryptcipher_encrypt_setupcipher_decrypt_setupcipher_generate_ivcipher_set_ivcipher_updatecipher_finishcipher_abort |
crypto_aead |
aead_encryptaead_decryptoptional: aead_encrypt_setupaead_decrypt_setupaead_generate_nonceaead_set_nonceaead_set_lengthsaead_update_adaead_updateaead_finishaead_abortaead_verify |
crypto_derivation |
key_derivation_setupkey_derivation_input_byteskey_derivation_input_integerkey_derivation_input_keykey_derivation_key_agreementkey_derivation_output_byteskey_derivation_output_keykey_derivation_abortkey_derivation_set_get_capacitykey_derivation_verify_byteskey_derivation_verify_key |
crypto_agreement |
raw_key_agreement |
crypto_rng |
generate_random |
crypto_pake |
A consistent set of PAKE operations needed to complete a PAKE key exchange. |
This list is probably not exhaustive. Crypto vendors are expected to use common sense to determine which functions of a given subset are interesting for their own users.
The API compliance badge only shows what kind of high-level crypto services are offered by compatible products. Low-level crypto primitives like AES, RSA, SHA, or specific elliptic curves are already always clearly announced by crypto vendors on their product datasheets. The API compliance badge is about functional compliance with a promise of portability, rather than about low-level crypto primitive support.
The Crypto API part of the compliance kit expects a minimal set of crypto primitives to be present to pass test cases. See test cases for more details about which primitives are tested.
To pass general PSA API compliance tests you need to:
- Download the compliance kit from this repository.
- Possibly adapt the test suite to reflect which tests you want to pass or skip.
- Run the tests on a device that runs the Root of Trust you want to apply for.
- Send the logs to
psacertified@arm.comand mention you want to apply for General PSA API compliance. You should pass at least enough Crypto API to satisfy a TF-M Profile Small use case, at least one secure storage service, and implement the (small) Attestation API. You can also apply for compliance without the Attestation API and the badge you will receive will mention exactly what tests you passed.
To pass Crypto API compliance tests you need to:
- Download the compliance kit from this repository.
- Possibly adapt the test suite to reflect which tests you want to pass or skip.
- Run the tests on any compatible platform.
- Send the logs to
psacertified@arm.comand mention you want to apply for Crypto API compliance.
It is possible to apply for Crypto API compliance even when implementing very restricted subsets of Crypto. For example, a hardware hash accelerator that offers compatible hash APIs could apply and obtain a PSA Certified API compliance badge that would only mention crypto_hash.
Nothing.
Delivering a badge usually takes a few working days, please bear with us if any delays occur.
Copyright (c) 2023-2024, Arm Limited and Contributors. All rights reserved.