doc: security-overview: Update cryptographic information

Zephyr's transition to PSA Crypto API and demoting TinyCrypt.
Lets not promote TinyCrypt in the overview.

Signed-off-by: Flavio Ceolin <flavio.ceolin@intel.com>
This commit is contained in:
Flavio Ceolin 2024-05-23 10:43:08 -07:00 committed by Anas Nashif
parent cabeaf1436
commit 9751f78ce5

View file

@ -122,14 +122,12 @@ Security Functionality
The security functionality in Zephyr hinges mainly on the inclusion of The security functionality in Zephyr hinges mainly on the inclusion of
cryptographic algorithms, and on its monolithic system design. cryptographic algorithms, and on its monolithic system design.
The cryptographic features are provided through a set of cryptographic The cryptographic features are provided through PSA Crypto, with
libraries. Applications can choose TinyCrypt2 or Mbed TLS based on their mbedTLS as the underlying implementation. Applications leverage PSA
needs. TinyCrypt2 supports key cryptographic algorithms required by the Crypto APIs, ensuring a standardized and secure approach to
connectivity stacks. TinyCrypt2, however, only provides a limited set of cryptographic operations. mbedTLS, as the implementation of PSA
algorithms. Mbed TLS supports a wider range of algorithms, but at the Crypto, supports a wide range of cryptographic algorithms, making it
cost of additional requirements such as malloc support. Applications can suitable for various application requirements.
choose the solution that matches their individual requirements. Future
work may include APIs to abstract the underlying crypto library choice.
APIs for vendor specific cryptographic IPs in both hardware and software APIs for vendor specific cryptographic IPs in both hardware and software
are planned, including secure key storage in the form of secure access are planned, including secure key storage in the form of secure access