From 8b357b3ddf64ba5b90256625ac18d2a9ae44c6f6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20B=C3=B8e?= Date: Mon, 13 May 2024 14:10:29 +0200 Subject: [PATCH] doc: nrf_security: Be more precise about prioritization MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Be more precise about prioritization. Signed-off-by: Sebastian Bøe --- doc/nrf/security/security.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/nrf/security/security.rst b/doc/nrf/security/security.rst index d5e5800a832e..db593ca33d73 100644 --- a/doc/nrf/security/security.rst +++ b/doc/nrf/security/security.rst @@ -145,7 +145,7 @@ The module can be enabled through the :kconfig:option:`CONFIG_NRF_SECURITY` Kcon The :ref:`nrf_security` acts as an orchestrator for the different cryptographic libraries available in the system. These libraries include the binary versions of accelerated cryptographic libraries listed in :ref:`nrfxlib:crypto`, and the open source Mbed TLS implementation in |NCS| located in `sdk-mbedtls`_. -The Kconfig option :kconfig:option:`CONFIG_NRF_SECURITY` prioritizes the usage of the accelerated libraries by default when this is supported by the platform. +HW accelerated libraries are prioritized over SW libraries when both are enabled. For more information about the configuration and usage of the :ref:`nrf_security`, see the :ref:`nrf_security_config` page. See also :ref:`crypto_samples` for examples of how to configure and perform different cryptographic operations in the |NCS|.