Revision as of 16:04, 15 April 2015

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.

Key Strength

Selecting

Enforcing

Maintaining

Memory Management Considerations

Perfect Forward Secrecy

Proxy Handling

Key Management Lifecycle Best Practices

Generation

Distribution

EndPoint Authentication

Algorithms and Protools

Integrity and Confidentiality

Storage

Software-based Storage

Hardware Storage

Escrow and Backup

Key Escrow

Key Backup

Tracking and Audit

Key Compromise and Recovery

Trust Stores

Population

Secure Update

Cryptographic Module Topics

Standards

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

Other Cheatsheets

OWASP Cheat Sheets Project Homepage

OWASP Cheat Sheet Series

V - T - E Cheat Sheets
Developer / Builder	3rd Party Javascript Management Access Control AJAX Security Cheat Sheet Authentication (ES) Bean Validation Cheat Sheet Choosing and Using Security Questions Clickjacking Defense Credential Stuffing Prevention Cheat Sheet Cross-Site Request Forgery (CSRF) Prevention Cryptographic Storage C-Based Toolchain Hardening CSS Security Deserialization DOM based XSS Prevention Forgot Password HTML5 Security HTTP Strict Transport Security Injection Prevention Cheat Sheet Injection Prevention Cheat Sheet in Java JSON Web Token (JWT) Cheat Sheet for Java Input Validation Insecure Direct Object Reference Prevention JAAS Key Management LDAP Injection Prevention Logging Mass Assignment Cheat Sheet .NET Security OS Command Injection Defense Cheat Sheet OWASP Top Ten Password Storage Pinning Query Parameterization REST Security Ruby on Rails Session Management SAML Security SQL Injection Prevention Transaction Authorization Transport Layer Protection TLS Cipher String Configuration Unvalidated Redirects and Forwards User Privacy Protection Web Service Security XSS (Cross Site Scripting) Prevention XML External Entity (XXE) Prevention Cheat Sheet
Assessment / Breaker	Attack Surface Analysis REST Assessment Web Application Security Testing XML Security Cheat Sheet XSS Filter Evasion
Mobile	Android Testing IOS Developer Mobile Jailbreaking
OpSec / Defender	Virtual Patching Vulnerability Disclosure
Draft and Beta	Application Security Architecture Business Logic Security Content Security Policy Denial of Service Cheat Sheet Grails Secure Code Review IOS Application Security Testing PHP Security Regular Expression Security Cheatsheet Secure Coding Secure SDLC Threat Modeling
All Pages In This Category

This project is part of the OWASP Builders community.
Feel free to browse other projects within the Defenders, Builders, and Breakers communities.

@@ Line 6: / Line 6: @@
 == 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 ==

Difference between revisions of "Key Management Cheat Sheet"