Key Management Cheat Sheet
- 1 DRAFT CHEAT SHEET - WORK IN PROGRESS
- 2 Introduction
- 3 Key Management General Guidelines and Considerations
- 4 Key Management Lifecycle Best Practices
- 4.1 Generation
- 4.2 Distribution
- 4.3 Storage
- 4.4 Escrow and Backup
- 4.5 Tracking and Audit
- 4.6 Key Compromise and Recovery
- 5 Trust Stores
- 6 Cryptographic Module Topics
- 7 Standards
- 8 Cryptographic Key Management Libraries
- 9 Authors and Primary Editors
- 10 Other Cheatsheets
DRAFT CHEAT SHEET - WORK IN PROGRESS
This Key Management Cheat Sheet provides developers with guidance for implementation of cryptographic key management within application in a secure manner.
Key Management General Guidelines and Considerations
Selection of the cryptographic and key management algorithms to use within a given application should begin with an understanding of the objectives of the application. For example, if the application is required to store data securely, then the developer should select an algorithm suite that supports the objective of Data-At-Rest (DAR) security. Applications that are required to transmit and receive data would select an algorithm suite that supports the objective of Data-in-Transit security. We have provided recommendations on the selection of crypto suites within an application based on application and security objectives.
Application developers oftentimes begin the development of crypto and key management capabilities by examining what is available in a library. However, an analysis of the real needs of the application should be conducted to determine the optimal key management approach. Begin by understanding the security objectives of the application which will then drive a determination of the cryptographic protocols that should be used.
For example, the objectives of the application may be: - Confidentiality of data at rest - Confidentiality of data in use - authenticity of data origin - authenticity of the end device - Integrity of data in transit - Confidentiality of data in transit
Once the understanding of the security needs of the application is achieved, developers can determine what protocols and algorithms are required. Once the protocols and algorithms are understood, you can you can begin to define the different types of keys that will need support the application's objectives. There are a diverse set of key types to consider, for example:
Encryption: - Symmetric encryption keys - Asymmetric encryption keys
Authentication of End Devices: - Pre-shared symmetric keys - Trusted certificates - Trust Anchors
Data Origin Authentication - HMAC
Integrity Protection - Message Authentication Codes (MACs)
Aside from the keys that the application supports, it will also likely be required to support certificates.
Authentication keys Key Encryption Keys (KEKs)
- Digital certificates - Asymmetric public key (and privates)
Memory Management Considerations
Perfect Forward Secrecy
Key Management Lifecycle Best Practices
Algorithms and Protools
Integrity and Confidentiality
Escrow and Backup
Tracking and Audit
Key Compromise and Recovery
Cryptographic Module Topics
Cryptographic Key Management Libraries
This article is focused on providing application security testing professionals with a guide to assist in managing cryptographic keys.
Authors and Primary Editors
Brian Russell - russellbri[at]leidos.com
Drew Van Duren - drew.f.van.duren[at]leidos.com
OWASP Cheat Sheets Project Homepage
| This project is part of the OWASP Builders community. |
Feel free to browse other projects within the Defenders, Builders, and Breakers communities.