Cryptographic agility

From HandWiki

In cryptographic protocol design, cryptographic agility or crypto-agility is the ability to switch between multiple cryptographic primitives. Then the systems implementing a particular standard can choose which combination of primitives they want to use. The primary goal of cryptographic agility was to enable rapid adaptations of new cryptographic primitives and algorithms without making disruptive changes to the systems' infrastructure.

Cryptographic agility acts as a safety measure or an incident response mechanism when a cryptographic primitive of a system is discovered to be vulnerable.[1] A security system is considered crypto agile if its cryptographic algorithms or parameters can be replaced with ease and is at least partly automated.[2][3] The impending arrival of a quantum computer that can break existing asymmetric cryptography is raising awareness of the importance of cryptographic agility.[4][5]

Example

The X.509 public key certificate illustrates crypto-agility. A public key certificate has cryptographic parameters including key type, key length, and a hash algorithm. X.509 version v.3, with key type RSA, a 1024-bit key length, and the SHA-1 hash algorithm were found by NIST to have a key length that made it vulnerable to attacks, thus prompting the transition to SHA-2.[6]

Importance

With the rise of secure transport layer communication in the end of the 1990s, cryptographic primitives and algorithms have been increasingly more popular; as an example, by 2019 more than 80% of all websites employed some form of security measures.[7] Furthermore, cryptographic techniques are widely incorporated to protect applications and business transactions.

However, as cryptographic algorithms are deployed, researching their security intensifies, and new attacks against cryptographic primitives (old and new alike) are discovered in short intervals. Crypto-agility tries to tackle the implied threat to information security by allowing swift deprecation of vulnerable primitives and replacement by new ones.

This threat is not merely theoretical; many algorithms that were once considered secure (DES, 512 bit RSA, RC4) are now known to be vulnerable, some even to amateur attackers. On the other hand, new algorithms (AES, Elliptic Curve Cryptography) are often both more secure and faster in comparison to old ones. Systems designed to meet crypto-agility criteria are expected to be less affected should current primitives are found vulnerable, and may enjoy better latency or battery usage by using new and improved primitives.

As an example, quantum computing, if feasible, is expected to be able to defeat existing public key cryptography algorithms. The overwhelming majority of the existing public key infrastructure rely on the computational hardness of problems such as large integer factorization and discrete logarithm problems (which includes elliptic-curve cryptography as a special case). Quantum computers running Shor's algorithm can solve these problems exponentially faster than the best known algorithms for conventional computers.[8] Post-quantum cryptography is the subfield of cryptography that aims to replace algorithms broken with new ones that are believed hard to break even for a quantum computer. The main families of post-quantum alternatives to factoring and discrete logarithm include lattice-based cryptography, multivariate cryptography, hash-based cryptography and code-based cryptography.

Awareness

System evolution and crypto-agility are not the same. System evolution progresses on the basis of emerging business and technical requirements. Crypto-agility is related instead to computing infrastructure and requires consideration by security experts, system designers and application developers.[9]

Best practices

Best practices about dealing with crypto-agility include:[10]

  • All business applications involving any sort of cryptographic technology should incorporate the latest algorithms and techniques.
  • Crypto-agility requirements must be disseminated to all hardware, software and service suppliers, who must comply on a timely basis; suppliers who cannot address these requirements must be replaced.
  • Suppliers must provide timely updates and identify the crypto technology they employ.
  • Quantum-resistant solutions should be taken in mind.[11]
  • Symmetric-key algorithm should be flexible in their key lengths.
  • Hash algorithms should support different lengths of outputs.
  • Digital certificate and private key rotations must be automated. [12]
  • Comply with standards and regulations.[13]
  • The names of the algorithms used should be communicated and not assumed or defaulted.

References

  1. ↑ Henry, Jasmine. "What is Crypto-Agility?". Cryptomathic. https://www.cryptomathic.com/news-events/blog/what-is-crypto-agility. Retrieved 26 November 2018. 
  2. ↑ Patterson, Kenny. "Key Reuse: Theory and Practice (Workshop on Real-World Cryptography)". Stanford University. https://crypto.stanford.edu/RealWorldCrypto/slides/kenny.pdf. Retrieved 26 November 2018. 
  3. ↑ Sullivan, Bryan. "Cryptographic Agility". Microsoft Corporation on Blackhat.com. http://media.blackhat.com/bh-us-10/whitepapers/Sullivan/BlackHat-USA-2010-Sullivan-Cryptographic-Agility-wp.pdf. Retrieved 26 November 2018. 
  4. ↑ "Better Safe Than Sorry: Preparing for Crypto-Agility" (in en). https://www.gartner.com/en/documents/3645384/better-safe-than-sorry-preparing-for-crypto-agility. 
  5. ↑ Steel, Graham (2019-01-21). "Achieving Crypto Agility" (in en-US). https://cryptosense.com/blog/achieving-crypto-agility/. 
  6. ↑ Grimes, Roger A. (2017-07-06). "All you need to know about the move from SHA1 to SHA2 encryption" (in en). https://www.csoonline.com/article/2879073/all-you-need-to-know-about-the-move-from-sha1-to-sha2-encryption.html. 
  7. ↑ "How Let's Encrypt doubled the internet's percentage of secure websites in four years". 13 November 2019. https://news.umich.edu/how-lets-encrypt-doubled-the-internets-percentage-of-secure-websites-in-four-years/. 
  8. ↑ Bl, Stephanie; a (2014-05-01). "Shor's Algorithm – Breaking RSA Encryption" (in en-US). https://blogs.ams.org/mathgradblog/2014/04/30/shors-algorithm-breaking-rsa-encryption/. 
  9. ↑ Henry, Jasmine. "3DES is Officially Being Retired". Cryptomathic. https://www.cryptomathic.com/news-events/blog/3des-is-officially-being-retired. Retrieved 26 November 2018. 
  10. ↑ Mehmood, Asim. "What is crypto-agility and how to achieve it?". Utimaco. https://content.hsm.utimaco.com/blog/what-is-crypto-agility-and-how-to-achieve-it. Retrieved 26 November 2018. 
  11. ↑ Chen, Lily; Jordan, Stephen; Liu, Yi-Kai; Moody, Dustin; Peralta, Rene; Perlner, Ray; Smith-Tone, Daniel. "Report on Post-Quantum Cryptography (NISTIR 8105)". National Institute of Standards and Technology NIST. https://nvlpubs.nist.gov/nistpubs/ir/2016/nist.ir.8105.pdf. Retrieved 26 November 2018. 
  12. ↑ "Digital certificate and private key rotations must be automated.". https://zoom.us/webinar/register/WN_c_zTCRI0QZ6SI01MazDbNg. [yes|permanent dead link|dead link}}]
  13. ↑ Macaulay, Tyson. "Cryptographic Agility in Practice". InfoSec Global. https://uploads-ssl.webflow.com/5bd73d456f7b3f2db2bbbb95/5c76a740dcc2cc4646a06805_ISG_AgilityUseCases_Whitepaper-FINAL.pdf. Retrieved 5 March 2019. 



Retrieved from "https://handwiki.org/wiki/index.php?title=Cryptographic_agility&oldid=3371919"