Published: 14 September 2011
This Decision Point covers the choices to be made once an organization has determined to use cryptography for encryption or authentication. Situations examined include how much information should be encrypted under a single key; how often to change keys and how long to trust keys; how to select key lengths, hash sizes, and cryptographic algorithms and protocols; whether to use hardware or software; requirements for cryptographic validations; and whether to run the system in a validated cryptographic configuration mode.
Table Of Contents
- Requirements and Constraints
- Time Frames and Surety Levels
- Speed vs. Security vs. Modularity and Compatibility (in Both Key Length and Algorithm Choice)
- Strength of the Environment
- Vetted vs. Unvetted Algorithms and Protocols
- FIPS Validation
- FIPS-Compliant Configuration
- Algorithm and Protocol Choice
- Key Length and Hash Size
- Key Granularity
- Key Rotation
- Protection of Keys
- Hardware vs. Software
- Vetted vs. Unvetted Solutions Position
- Consider vetted and unvetted algorithms, protocols, and implementations based on analysis of risks, costs, and benefits.
- Always use vetted algorithms, protocols, and implementations.
- FIPS Validation Position
- Choose FIPS 140-2-validated systems or modules over noncertified ones.
- Consider systems or modules validated at FIPS 140-2 level 3.
- Consider systems or modules validated at FIPS 140-2 level 4.
- FIPS-Compliant Configuration Position
- Make a risk-based decision to keep or change the system and re-evaluate.
- Run the system in an appropriately secure configuration.
- Run the system in FIPS mode.
- Algorithm and Protocol Choice Position
- Use an appropriate implementation of the specified algorithm or protocol.
- Make a risk-based decision to keep the system and implement compensating controls, or to not use the system.
- Choose an appropriate implementation of a current algorithm or protocol that meets system requirements.
- Key Length and Hash Size Position
- Focus on resistance against password brute force attacks before deciding on key length and hash size.
- Choose the largest possible key length or hash size for the algorithm.
- Choose a key length or hash size with an expected strength equal to or greater than the confidentiality and/or authenticity requirements of the information.
- Choose a key length with an expected strength equal to or greater than the validity or rotation period of the authentication key.
- Key Granularity Position
- Select a key granularity based on risk, performance, and manageability considerations.
- Key Rotation Position
- Key rotation is based on risk and manageability requirements.
- Protection of Keys Position
- Protect keys at least to the level of the information.
- Hardware vs. Software Position
- Use hardware.
- Use software.
©2019 Gartner, Inc. and/or its affiliates.
All rights reserved.
Gartner is a registered trademark of Gartner, Inc. and its affiliates.
This publication may not be reproduced or distributed in any form without Gartner’s prior written permission.
It consists of the opinions of Gartner’s research organization, which should not be construed as statements of fact.
While the information contained in this publication has been obtained from sources believed to be reliable, Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information.
Although Gartner research may address legal and financial issues, Gartner does not provide legal or investment advice and its research should not be construed or used as such.
Your access and use of this publication are governed by Gartner’s Usage Policy.
Gartner prides itself on its reputation for independence and objectivity.
Its research is produced independently by its research organization without input or influence from any third party.
For further information, see
Guiding Principles on Independence and Objectivity.