Crypto Agility

Crypto Agility

This glossary provides explanations of various keywords to help you understand the concepts necessary for successful data utilization and digital transformation (DX).
This time, we will introduce the concept of crypto agility, which is necessary to keep IT systems and products safe and secure.

Crypto Agility is

Crypto agility refers to the ability of an IT system or product to quickly switch between different cryptographic technologies.

Here, cryptography refers not only to cryptographic techniques in the narrow sense (such as symmetric-key cryptography and public-key cryptography) that convert plaintext into ciphertext, but also to technologies used to ensure the security of IT systems, such as digital signatures used for electronic declarations of intent and ownership, and cryptographic hash functions.
The ability to quickly switch between technologies used to ensure the security of these IT systems as needed is increasingly recognized as an important concept for maintaining safety and security. For example, if a vulnerability is found in one of the technologies being used, security can be maintained by quickly switching to an alternative technology.

An idea that has begun to gain attention in response to the threat of quantum computers.

Concepts and approaches equivalent to cryptoagility already existed in the application of cryptographic technology in the 20th century, and the term "cryptogility" itself seems to have come into use around the beginning of the 21st century. However, it is only very recently that cryptoagility has become a widely discussed new concept in security. The catalyst for this was the recent need to address the threat of quantum computers.

Against the backdrop of the ongoing research and development of quantum computers, efforts are underway to switch the cryptographic technologies currently in use to "post-quantum cryptography," which will maintain security even after quantum computers become fully practical. Cryptoagility has become widely known as a recommended practice in these efforts.

For more information on post-quantum cryptography, please click here.
⇒ Post-Quantum Cryptography (PQC) / Quantum Computer / Cryptogility / Harvest Attack | Glossary

To add further, while the practical application of quantum computers with sufficient capabilities is still considered to be a long way off, it is already possible to carry out time-delayed attacks that involve "collecting and storing encrypted data at the present time and decrypting its contents in the future." Because such "harvest attacks (HNDL: Harvest Now, Decrypt Later)" are a real threat, a global response is urgently needed.

For more information about "Harvest attacks," please click here.
⇒ Harvest Attack (HNDL: Harvest Now, Decrypt Later) | Glossary

The events surrounding the transition from DES encryption to AES encryption due to its insufficient strength.

Currently (as of this writing in 2026), it has become widely known for its application to quantum computers, but the concept itself is not limited to quantum computers.

In the late 1990s and early 2000s, just before the turn of the 21st century, a situation similar to the present day arose where "the encryption technologies that had been widely used up to that point could no longer maintain security." The background to this situation is as follows:

Cryptographic technology has long been used in intelligence gathering and military operations throughout human history. However, in the computer age, there was a need for cryptographic technology that could be widely used by the public as a "foundation for the safety and security of civilian economic activities," and in 1977, the "DES encryption" standard was established by the U.S. government.

Subsequently, DES encryption became widely used around the world. However, while computer processing power advanced dramatically, DES encryption only had a key length of 56 bits. Furthermore, advancements in cryptography (such as linear decryption) meant that it was becoming possible to crack it in a realistic amount of time using brute-force methods or new decryption techniques, bringing the security of DES encryption closer to being compromised.

Therefore, while introducing "Triple DES," which temporarily increased strength by processing existing DES encryption three times, as a transitional technology, the standardization of "AES encryption," a next-generation encryption technology that is stronger and superior in many aspects, was completed in 2001.

For more details on the background of this matter, please see here.

⇒ Symmetric-key cryptography / DES / AES (Advanced Encryption Standard) | Glossary

AES encryption remains the de facto global standard for symmetric-key cryptography, and AES-256 is considered to be sufficiently strong even in the age of quantum computing, and will continue to support our safety and security in the future.

This is how AES encryption came about, but DES/Triple DES could not be completely phased out for a long time. The transition to the new technology was difficult and time-consuming.

  • 1977: The former NBS (National Bureau of Standards), now NIST (National Institute of Standards and Technology), standardizes DES.
  • 1999: Triple DES is introduced.
  • 2001: AES is standardized by NIST.
  • 2005: Standardization of DES was withdrawn.
  • 2024: Triple DES is finally banned.

It took a full 23 years after the AES encryption method was created before a declaration banning the use of Triple DES could be made.

There are other similar examples. One is the situation with the once widely used cryptographic hash function "SHA-1." More than 20 years have passed since it was found to be insufficiently secure, yet it still hasn't been phased out.

  • 1995: NIST standardizes SHA-1.
  • 2005: The theoretical possibility of colliding hash values is discovered.
  • 2017: Successfully created a hash value collision.
  • It has not yet been completely abolished (although they have declared that they plan to abolish it by the end of 2030).

Why has crypto agility become so important?

The concept of crypto agility has become important after experiencing situations like these.

DES encryption was a well-designed technology at the time of its standardization. However, subsequent technological advancements, such as the assumption of a 56-bit key length becoming outdated, resulted in insufficient security. This loss of security in an encryption technology that was once considered secure is called vulnerability.

A similar situation can be seen in the age of quantum computers, where public-key cryptography based on prime factorization and discrete logarithms, which has been widely used until now, is now in danger of being cracked.

For more information about public-key cryptography, please click here.
⇒ Public-key cryptography / Digital signatures / One-way functions | Glossary

Neither 56-bit key-length DES encryption nor prime factorization-based RSA encryption was sufficiently secure. This situation led to the development of successor encryption technologies. Formerly AES encryption, now post-quantum cryptography. However, despite the creation of the secure successor technology, AES encryption, it took 23 years before Triple DES was banned.

In other words, simply providing secure new technologies was insufficient to address the situation where cryptographic technology was compromised. What went wrong? The reason this happened was that, due to various circumstances, the process of switching from currently used cryptographic technologies to new ones as needed could not be done immediately (there wasn't enough agility).
This important lesson learned can be put into words as "cryptoagility."

Cryptogility may become more important in addressing the threat posed by quantum computers.

Furthermore, ensuring crypto agility is likely to become even more important in addressing the threat posed by quantum computers, a task currently underway worldwide.

AES encryption was standardized in 2001, and to this day, researchers worldwide continue to study it for any potential problems. It is also used in practical applications, and yet no major problems have been found (although minor issues have been discovered). It continues to play a vital role today as a foundation for the security and safety of data worldwide.

Regarding post-quantum cryptography, it is a crucial technology for supporting security and safety in the quantum computing era, and proposals from around the world have been accepted, leading to the standardization of superior technologies. However, because it employs a new type of technology, it does not have the security and safety backed by a long track record (it is not a mature technology).

There are concerns that a major, unexpected problem could be discovered in the encryption technology at a later date, leading to a situation where it's deemed "no longer secure and should not be used in the future."

Such a situation has already been considered, and alternative cryptographic technologies with different technical foundations (to prevent serious problems from occurring simultaneously) have been prepared. However, even with secure alternative technologies, it's useless if you can't switch between the cryptographic technologies you're using.

It is believed that there is a significant risk that one day, the post-quantum cryptography currently in use may suddenly be found to be insecure. This is why "cryptoagility is important" in post-quantum cryptography countermeasures.

The concept is similar to achieving "loose coupling."

So how can crypto agility, or the ability to respond to risk with the power to change rather than strength, be achieved? In fact, it's related to the concept of "loose coupling," which is familiar in the "connecting" aspect of IT and data utilization. In other words, crypto agility can be considered the act of maintaining a loosely coupled relationship between "IT systems" and "the cryptographic technologies used," rather than tightly coupled ones.

For more information on loose coupling, please see here.
⇒ Loose coupling | Glossary

Alternatively, it might be easier to understand if we think of it as "tight coupling should be avoided." For example, in a clearly tightly coupled state where the cryptographic techniques used are integrated at the program code level, it naturally becomes difficult to replace them with new technologies.

However, simply having a software-based, modularized, and interchangeable cryptographic technology is not always sufficient.

  • To make it possible to understand where and what kind of cryptographic technology is being used.
  • The architecture used will be software-interchangeable for the cryptographic technologies employed.
  • To enable a realistic transition from old technologies to new technologies.
    • If parallel operation of new and old technologies is necessary, then it should be possible to use them together.

Many other factors also need to be considered. For example, switching to a different encryption technology can significantly alter the supported encryption key length, the length of the encrypted data, the amount of computing resources required for encryption, and the time it takes to complete the encryption process. It's also necessary to have room to handle situations where the computational load for encryption increases significantly with the alternative encryption technology.

Furthermore, even if a technical switch can be made immediately, if prior coordination between related systems is required, or if it takes time to notify and coordinate with relevant organizations, then it cannot be said that agility has been ensured.

A method of entrusting things to those that have "adequate measures in place."

If it is difficult for you to proactively work towards achieving crypto agility on your own, you can entrust the technical layers related to cryptography to those that "already have adequate support in place and are expected to continue to provide adequate support in the future," rather than managing them yourself.

For example, web browsers are already making progress in supporting post-quantum cryptography through daily version updates, even without our conscious effort. As of this writing, support is progressing in the key exchange portion, while support for digital signatures and certificates is still in progress (and support on the web server side is also required). However, we can expect that major web browsers will continue to provide appropriate support in the future.

In any case, you need to either technically achieve crypto agility yourself, or adopt foundational technologies that are expected to ensure the level of crypto agility you need in the future.

HULFT is working on post-quantum cryptography.

Finally, if I may be so bold, I would like to introduce an example of a foundation that is expected to continue to receive adequate support.

HULFT, file transfer middleware, has long been supported as a de facto standard for reliable system integration in areas where errors are unacceptable and extremely high levels of "security and reliability" are required, particularly in corporate IT systems, especially banking IT systems.

Initially, it was widely used as a means of reliably coordinating between mainframes and UNIX, which are fundamentally different environments. Since then, as Linux and Windows have emerged as new environments, support for reliable integration with those environments has also been developed.

Furthermore, in the age of cloud computing, the very concept of system architecture is different from before. Cloud Native As the use of IT has spread throughout the world, "HULFT" container A new product that can be used naturally even in microservice architectures using this technology. HULFT 10 for Container Services) is being added.

⇒ HULFT Series | Services

As a collaborative platform that has supported crucial IT systems that underpin Japanese society itself, we have adapted to the changing times and the needs that arise. Currently, we are continuing to work on what will be required in the coming era of quantum computing.

HULFT will continue to address user needs and strive to provide a safe and secure foundation for continued use. We will also be fully committed to addressing post-quantum cryptography.

Ensuring agility "in addition to many other circumstances"

The reason we are ensuring crypto agility is to take into account future risks related to cryptographic technology and to ensure future safety and security even if those risks materialize.

If the goal is to ensure safety and security, then naturally there are other things that must be addressed to achieve that. In addition to continuing to address those things as before, there is also the difficulty of "addressing crypto agility."

As demonstrated by HULFT example I presented, we have implemented advanced features required for file transfer platform that can be used safely, securely, and reliably in a wide variety of environments, and we are also working on crypto agility. Our goal is comprehensive security and peace of mind, including crypto agility.

In a situation where "there are many other things to consider," any attempt to implement a new initiative is likely to be met with cumbersome responses such as "such changes would cause operational problems for us" or "if you're going to do anything, please get our approval beforehand." Nevertheless, what needs to be ensured is "agility (speed)."

Considering this, it becomes clear that ensuring agility isn't simply a matter of having interchangeable cryptographic software modules. It requires not only addressing technical interchangeability but also considering organizational aspects such as operation and coordination.

Related keywords (for further understanding)

Are you interested in "iPaaS" and "connecting" technologies?

Try out our products that enable you to seamlessly integrate various data and systems, from on-premises IT systems to cloud services, and successfully leverage IT.

The ultimate "connecting" tool: data integration software "DataSpider" and data integration platform "HULFT Square"

"DataSpider," data integration tool developed and sold by our company, is a "connecting" tool with a long history of success. "HULFT Square," a data integration platform, is a "connecting" cloud service developed using DataSpider technology.

Another feature is that development can be done using only the GUI (no code) without writing code like in regular programming, so business staff who have a good understanding of their company's business can take the initiative to use it.

Try out DataSpider/ HULFT Square 's "connecting" technology:

There are many simple collaboration tools on the market, but this tool can be used with just a GUI, is easy enough for even non-programmers to use, and has "high development productivity" and "full-fledged performance that can serve as the foundation for business (professional use)."

This solution smoothly resolves the problem of "connecting disparate systems and data," which often hinders the success of IT utilization. We regularly hold free trial sessions and hands-on workshops where you can try it out for free, so we encourage you to give it a try.


Why not try a PoC to see if "HULFT Square" can transform your business?

Why not try verifying how "connecting" can be utilized in your business, the feasibility of solving problems using data integration, and the benefits that can be obtained?

  • I want to automate data integration with SaaS, but I want to confirm the feasibility of doing so.
  • We want to move forward with data utilization, but there are challenges in system integration.
  • I want to consider data integration platform to achieve DX.

Glossary Column List

Alphanumeric characters and symbols

A row

Ka row

Sa row

Ta row

Na row

Ha row

Ma row

Ya row

Ra row

Wa row

»Data Utilization Column List

Recommended Content