Does your encryption strategy take the quantum computing era into consideration?

Are you experiencing any of the following situations regarding daily file transfer and security measures?

Important business data on a daily basis
file transfer is enabled.

The data exchanged daily, such as data integration with business partners and file transfer between internal systems, contains information that needs to be protected over the long term.

We do not know if current encryption measures will be effective against future threats.

Even if current security requirements are met, future advancements in computing technology are not taken into account.

Countermeasures against quantum computers are,
I think that's still a long way off.

A concrete plan for addressing PQC (Post-Quantum Cryptography) has not yet been decided.

Current data could potentially become a future risk.

In recent years, concerns have been raised that the practical application of quantum computers will undermine the security of currently widely used public-key cryptography, and discussions on transitioning to PQC (Primary Quantum Computing) have begun both domestically and internationally. In parallel with these concerns, the risk of harvest attacks, in which current communications are intercepted and stored for future decryption, is also being discussed.

The Cabinet Secretariat's National Cyber Security Division decided at the "Inter-Ministerial Liaison Conference on the Use of PQC in Government Agencies, etc." to complete the transition to PQC for encryption systems of government agencies, etc., by 2035 in principle. The Financial Services Agency is also discussing with a wide range of stakeholders at the "Study Group on Responding to Post-Quantum Cryptography by Deposit-Taking Financial Institutions," and it has been determined that it is desirable for high-priority systems in the financial sector to be able to use PQC encryption technology by the mid-2030s.

In addition to financial industries such as banks, securities firms, and insurance companies, which are already required to take action, companies involved in domestic social infrastructure where data confidentiality is paramount, as well as Manufacturing, are among the critical issues that require immediate attention in addressing PQC compliance for their corporate systems.

Let's not just wait for future solutions, but take action now.

- Three steps to prepare for future PQC compliance -

STEP 1
Enhanced protection of file transfer data

We will utilize HULFT 's encryption option, which employs the AES method, to implement measures to ensure confidentiality.

STEP 2
Consideration based on the existing system environment

We will review the operating system, connection destinations, and integration methods currently in use, and organize the requirements for implementation and operation.

STEP 3
Prepare for future changes in cryptographic technology

In anticipation of the transition to cryptographic technologies, we will begin the necessary considerations for future system updates and security plans.

Let's start with the encryption measures we can implement now.
Data protection is provided by HULFT 's encryption option, which uses the AES method.

A crucial step in preparing for harvest attacks is to properly encrypt data that needs to be protected for the future, right now.
HULFT ensures data protection against decryption (confidentiality) during file transfer transfers by combining it with an encryption option that employs AES-256 encryption technology, thus protecting data from harvest attacks. You can.
Not only HULFT 10, You can also use the "HULFT AES encryption option" in HULFT8.

What is HULFT 's AES encryption option?

HULFT 's AES encryption option is optional product for HULFT that uses the AES encryption method.
By utilizing HULFT 's AES encryption option, you can achieve file transfer with higher encryption strength than the standard HULFT Encryption Scheme across various platforms supported by HULFT.
AES (Advanced Encryption Standard) is an encryption algorithm defined in "FIPS 197," an encryption standard established by the U.S. National Institute of Standards and Technology (NIST), and has also been selected as a recommended encryption algorithm for Japan's e-government.
*The official names are "HULFT8 encryption option (AES)" or "HULFT 10 encryption option".

HULFT will continue to evolve to meet PQC requirements.

In the next upgrade of HULFT, we will also strengthen the data integrity verification aspect of file transfer, thereby complying with PQC in terms of both data confidentiality and integrity.