AN1412: Zigbee Security Manager
●This document is mainly focused on describing the components and APIs used to interact with security functionality since Zigbee EmberZNet SDK 7.2.
●KEY POINTS
■The Zigbee Security Manager components are now used by the Zigbee stack to manage access to security keys and operations performed with them.
■On parts with Secure Vault-High support, the underlying implementation of the APIs is provided by the PSA Crypto implementation in Secure Vault.
■The new APIs replace legacy Zigbee security API functionality and separate fetching of key data from key metadata.
●Introduction
■Versions of EmberZNet since 7.2 have offered the ability to use AN1271: Secure Key Storage on supported parts, with the PSA Crypto APIs in Secure Engine being used to implement this. As not all parts support key wrapping, the existing methods of key storage in plaintext NVM3 tokens continue to be maintained. Such builds do not call the PSA Crypto APIs for key storage. The Zigbee Security Manager components were therefore introduced to have a unified set of APIs for the stack to use that more closely aligned with the setup of the PSA Crypto APIs.
■This document describes some of the changes involved in using these new APIs to manage key storage and cryptographic operations.
■Previous APIs are callable in versions through 7.3 with their implementations now routing through Zigbee Security Manager APIs but are scheduled for removal in a future release
|
|
Application note & Design Guide |
|
|
|
Please see the document for details |
|
|
|
|
|
|
|
English Chinese Chinese and English Japanese |
|
2023/9/29 |
|
Rev. 0.1 |
|
AN1412 |
|
1.2 MB |
- +1 Like
- Add to Favorites
Recommend
All reproduced articles on this site are for the purpose of conveying more information and clearly indicate the source. If media or individuals who do not want to be reproduced can contact us, which will be deleted.