Crypto: AES CCM
The AES CCM sample demonstrates how to use the PSA Crypto API to perform authenticated encryption and decryption operations using the CCM AEAD algorithm with a 128-bit AES key. The sample uses additional authenticated data (AAD) and a random nonce.
Requirements
The sample supports the following development kits:
Hardware platforms |
PCA |
Board name |
|
|---|---|---|---|
PCA10153 |
|
||
PCA10090 |
|
||
PCA10171 |
|
||
nRF7120 DK |
nrf7120dk |
|
|
nRF54LV10 DK |
PCA10188 |
|
|
nRF54LS05 DK |
PCA10214 |
nrf54ls05dk |
|
PCA10184 |
|
||
nRF54LC10 DK |
PCA10226 |
nrf54lc10dk |
|
PCA10156 |
|
||
PCA10156 |
|
||
PCA10156 |
|
||
PCA10175 |
|
||
PCA10095 |
|
||
PCA10056 |
|
For more security, it is recommended to use the */ns variant of the board target.
When built for this variant, the sample is configured to compile and run as a non-secure application using security by separation.
Therefore, it automatically includes Trusted Firmware-M that prepares the required peripherals and secure services to be available for the application.
Overview
The sample enables PSA Crypto API and configures the following Kconfig options for the cryptographic features:
CONFIG_PSA_WANT_KEY_TYPE_AES- Used to enable support for AES key types from among the supported cryptographic operations for Key types and key management.CONFIG_PSA_WANT_ALG_CCM- Used to enable support for the CCM AEAD algorithm from among the supported cryptographic operations for AEAD algorithms.CONFIG_PSA_WANT_GENERATE_RANDOM- Used to enable random number generation for key generation from among the supported cryptographic operations for RNG algorithms.
The sample also configures the cryptographic drivers for each board target using Kconfig options in the overlay files in the boards directory.
These Kconfig options are then used by the build system to compile the required cryptographic PSA directives and make the configured cryptographic drivers available at runtime. See Driver selection for more information about this process.
Once built and run, the sample performs the following operations:
Initialization:
The PSA Crypto API is initialized using
psa_crypto_init().A random 128-bit AES key is generated using
psa_generate_key()and stored in the PSA crypto keystore. The key is configured with usage flags for both encryption and decryption.
Authenticated encryption and decryption of a sample plaintext:
Authenticated encryption is performed using
psa_aead_encrypt()with thePSA_ALG_CCMalgorithm. This function encrypts the plaintext with the provided nonce and additional authenticated data, and appends an authentication tag to the ciphertext.Authenticated decryption is performed using
psa_aead_decrypt(). This function decrypts the ciphertext, verifies the authentication tag, and authenticates the additional data.The decrypted text is compared with the original plaintext to verify correctness.
Cleanup:
The AES key is removed from the PSA crypto keystore using
psa_destroy_key().
Building and running
This sample can be found under samples/crypto/aes_ccm in the nRF Connect SDK folder structure.
For more security, it is recommended to use the */ns variant of the board target (see the Requirements section above.)
When built for this variant, the sample is configured to compile and run as a non-secure application using security by separation.
Therefore, it automatically includes Trusted Firmware-M that prepares the required peripherals and secure services to be available for the application.
To build the sample, follow the instructions in Building an application for your preferred building environment. See also Programming an application for programming steps and Testing and optimization for general information about testing and debugging in the nRF Connect SDK.
Note
When building repository applications in the SDK repositories, building with sysbuild is enabled by default.
If you work with out-of-tree freestanding applications, you need to manually pass the --sysbuild parameter to every build command or configure west to always use it.
Testing
After programming the sample to your development kit, complete the following steps to test it:
Connect to the kit with a terminal emulator (for example, the Serial Terminal app). See Testing and optimization for the required settings and steps.
Build and program the application.
Observe the logs from the application using the terminal emulator. For example, the log output should look like this:
*** Booting nRF Connect SDK v3.1.0-6c6e5b32496e ***
*** Using Zephyr OS v4.1.99-1612683d4010 ***
[00:00:00.251,159] <inf> aes_ccm: Starting AES CCM example...
[00:00:00.251,190] <inf> aes_ccm: Generating random AES key...
[00:00:00.251,342] <inf> aes_ccm: AES key generated successfully!
[00:00:00.251,373] <inf> aes_ccm: Encrypting using the AES CCM mode...
[00:00:00.251,708] <inf> aes_ccm: Encryption successful!
[00:00:00.251,708] <inf> aes_ccm: ---- Nonce (len: 13): ----
[00:00:00.251,739] <inf> aes_ccm: Content:
SAMPLE NONCE
[00:00:00.251,770] <inf> aes_ccm: ---- Nonce end ----
[00:00:00.251,800] <inf> aes_ccm: ---- Additional data (len: 35): ----
[00:00:00.251,831] <inf> aes_ccm: Content:
Example string of additional data
[00:00:00.251,831] <inf> aes_ccm: ---- Additional data end ----
[00:00:00.251,861] <inf> aes_ccm: ---- Encrypted text (len: 115): ----
[00:00:00.251,892] <inf> aes_ccm: Content:
c4 36 60 2b 45 59 5b 12 35 00 00 00 00 00 00 00 |.6.+EY[..5.......
b3 5d 47 06 89 a5 08 3b e6 54 57 25 b9 49 02 50 |.]G....;.TW%.I.P
d1 55 49 58 11 00 00 00 00 00 00 00 00 00 00 00 |.UX.............
[00:00:00.251,922] <inf> aes_ccm: ---- Encrypted text end ----
[00:00:00.251,953] <inf> aes_ccm: Decrypting using the AES CCM mode...
[00:00:00.252,166] <inf> aes_ccm: ---- Decrypted text (len: 100): ----
[00:00:00.252,197] <inf> aes_ccm: Content:
Example string to demonstrate basic usage of AES CCM mode.
[00:00:00.252,227] <inf> aes_ccm: ---- Decrypted text end ----
[00:00:00.252,258] <inf> aes_ccm: Decryption and authentication successful!
[00:00:00.252,288] <inf> aes_ccm: Example finished successfully!