How can the secrets of a credit card be revealed in less than 10 minutes without the plastic being scratched? At the beginning of the 1990s, a young engineer entered a security laboratory with the idea that a PIN could be secured by a smart card design. The card was returned, but in effect violated: the lab engineers had been able to extract the PIN anyway. This is the moment, seeing the so-called secure technology broken, when we should keep in mind that there is no proof of a rule like that in modern engineering: the feeling of confidence is not the feeling of a proof, and the feeling of trust that has never been verified is a well-dressed feeling.
That lesson dwarfed much higher than payment cards. Secure chips quietly slipping under the carpet were the identity layer of devices that people do not strongly relate with cryptography, phones, vehicles, industrial controllers, medical devices, routers, and infrastructure systems. Their task is not as easy as it sounds: they have to keep a secret a cryptographic identity that is used to authenticate a device, to determine actions, and to verify updates. When that is revealed, the other defenses of the system can be compromised. The contradiction lies in the fact that computation is physical, and chips cannot employ secrets without leaving any hints of it. Power current variations; time variations; electromagnetic incidences change. Within a serious attack lab, engineers view that side effects as an indicator, and then push the button further–adding some faults, adding some electromagnetic noise, removing some silicon until the device tells something it was not designed to tell.
This is the reason why security by design must encompass security by destruction. The most effective security teams are not acting like civil auditors, but rather like antagonists with a time limit. The controls of access, the vetting, the documentation, the repeatability of the same, those details are important since the objective is not curiosity. It is to transform all effective breaches into a design input when there is still time to recover. Once secure hardware has become part of the background, organizations can easily forget that it also decays, but attackers do not.
What assailants desire does not alter quantum computing. It alters their speed in accessing it. A lot of the current online trust depends on the use of the public-key cryptography as a way of encryption and verification. An effective quantum computer poses a risk to that background, as it can decrypt data that is intercepted, and it allows the possibility of attacks based on impersonation, including fuzzing signatures posted in software updates or certificates. The next operational issue is already well-known to the security agencies and compliance teams, the so-called Harvest Now, Decrypt Later (HNDL) when today encrypted data is gathered and stored to be decrypted in the future. In the case of long-lived information, such as intellectual property, sensitive personal data, medical records, strategic plans, the exposure starts when the quantum machine is collected and not when the quantum machine is brought online.
Research is being transformed to governance in terms of engineering responses. NIST has finalized its first specifications of the post-quantum cryptography in August 2024 ( FIPS 203, 204, 205 ) as an anchor point in its industry, defining algorithms that are supposed to operate on conventional systems and survive quantum-enabled attacks. Such standardization is important since post-quantum migration is not a single upgrade as much as a dependency puzzle: certificates, code signing, device onboarding, update systems and public key infrastructure all interoperate. The initial action is rather prosaic but inevitable: construct a cryptography inventory system, protocols, certificates, libraries and embedded systems then architect around crypto agility to enable a swap of algorithms without dismantling the production systems.
Hardware is yet another limitation, identities are not created in slide decks, but in factories. The transition between silicon trust and post-quantum policy is made through secure provisioning program keys, device identifiers, and certificates during manufacturing. When the supply chain is incapable of demonstrating what was supplied, where and under what controls, then, quantum readiness becomes paperwork surrounding uncertain devices. That is to say, the migration is not merely concerning improved mathematics; it is operational evidence.
Attack laboratories are there to ensure that such evidence is truthful. The systems that will come through to the eventual arrival of quantum pressure will be the ones that were already used to being shattered intentionally.
