Difference between revisions of "Key Management Cheat Sheet"
(→Introduction) |
(→Algorithm Selection) |
||
Line 6: | Line 6: | ||
== Algorithm Selection == | == Algorithm Selection == | ||
+ | |||
+ | |||
+ | |||
+ | 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. | ||
+ | |||
+ | <table> | ||
+ | <tr> | ||
+ | </tr> | ||
== Key Strength == | == Key Strength == |
Revision as of 15:04, 15 April 2015
- 1 DRAFT CHEAT SHEET - WORK IN PROGRESS
- 2 Introduction
- 3 Key Management General Guidelines and Considerations
- 4 Key Management Lifecycle Best Practices
- 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
Introduction
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
Algorithm Selection
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.