Keyfactor Crypto Agile PKI EB 1118 PDF
Keyfactor Crypto Agile PKI EB 1118 PDF
Table of Contents
THE NEED FOR CRYPTO-AGILITY: How to Know When Your Cyber Security Is Past
Its Expiration Date .............................................................................................................................. 3
For nearly all hardware and software used in traditional IT predictable evolution of computing power will ultimately
environments and burgeoning Internet of Things ecosys- erode the defenses of cryptography.
tems, the scale of potential threat is immense. It’s very like-
ly that many IoT devices’ lifespans will extend well beyond To be even more proactive, organizations must become
the effectiveness of their cryptographic keys. agile in their readiness to respond to high-level crypto risk.
The ability to act before threats become serious becomes
One strategy to counter these threats is to make it difficult an innate part of the lifecycle, resulting in a condition
for cyber criminals to crack cryptography through what- where crypto-agility is fundamental.
ever computing resources are accessible. However, the
When a Root of Trust (RoT) is breached, all trust is lost. In Similar to a compromised RoT, a complete replacement
the case of a certificate authority issuing certificates, a is required. Any keys using the affected algorithm are
breach renders the chain of trust and all public and private insecure. Rogue actors can break their encryption easily,
keypairs moot, or even dangerous, as they can be issued rendering communication insecure while making data
and used maliciously. The immediate replacement of that readily accessible.
RoT is required, along with the updating of all certificates
and keys used by devices.
Discovery of a bug in crypto libraries may result in the need According to Gartner analysts Mark Horvath and David
to generate new keys and reissue certificates according to Anthony Mahdi, most public-key algorithms in use today will
the technology used in patching or replacing it. be susceptible to attack by quantum computing processors
within the next five to eight years.
CERTIFICATE EXPIRATION
When certificates are used past their shelf life, they can fail years to avoid any chance of it expiring while in service and
at authentication or establishing secure communication tun- requiring replacement. Certificate expiration is an important
nels. Certificate expiry on its own is not necessarily a secu- mechanism to ensure certificates are regularly re-issued. It
rity response incident like the scenarios mentioned above. offers a check and balance system, in the form of workflow
However, the method used to avoid such interruption of and approvals, to verify current legitimacy and authorization.
service is such a case. It is common to see organizations ex- Experts recommend applying validity periods of two to three
tend the validity period of a certificate to 25, 50, or even 99 years for this reason.
Devices that you own today may be In addition to transferring a device’s Any change in business ownership
sold or transferred to another party in ownership, there are cases when a or structure may result in the need to
the future. This is especially common new entity is introduced to support modify access policies within the IoT
with devices that have long lifespans a fleet of devices and handle their ecosystem. Such scenarios require
and high price tags in industrial envi- maintenance or servicing. There are modifying device identities, similar to
ronments. Sending such devices back also situations where a new business the cases mentioned above, as well as
to the manufacturer for reprogram- partner requires interaction with the modifying crypto keys and certificates
ming is not an option, nor is expand- device alongside its existing process- located on servers and appliances
ing the private chain of trust to include es and communication. It’s not advis- within on-premise or cloud-hosted
new owners. Regardless, for devices able to share a private RoT, extending infrastructures.
to communicate with the proper sys- its chain from one organization to an-
tems, there is a need to reconfigure. other as relationships are formed as
the device’s identity. This is achieved it presents a future threat if/when re-
by generating new keys and issuing lationships disband. A better practice
new certificates, along with updating is to adjoin additional identities to the
the trust stores that define who the device issued from a different RoT, al-
device trusts and who trusts it. lowing all parties to trust and commu-
nicate with it independently.
Frequently in enterprise IT environments, responding to changes in business structure can take months
if not years to complete. The same principle applies to IoT, where the quantity, diversity, and geogra-
phic distribution of connected devices poses additional potential hurdles. In both cases, it is vital that
crypto-agility be a priority, even when business changes occur at a slow pace.
01 02 03
01 05
How many digital certificates do you have? When will they expire?
02 06
03 07
What are they used for? How are you protecting valuable
code-signing certificates?
04 08
What hash algorithm are they using and Do you have a centralized method
what is their overall health? to securely update each one?
What you can see doesn’t always amount to what you have.
Network discovery is a basic means to assemble a collection
of certificates after they’ve been issued and deployed - but
is often too little and too late. With the ability for individual
application and networking teams to issue, purchase, and
KEYFACTOR COMMAND CA
deploy their own certificates, control over certificate policies
is easily lost. The result is certificates deployed on the in- Gateways allow for direct integration with your certifi-
ternal network — and often on the public Internet — that do cate authority, or multiple CAs in parallel. This capabili-
not conform to security policy, and whose configuration and ty enables you to ascertain every issued certificate, and
expiration can lead to costly downtime or security breaches. coordinate every lifecycle management action taken.
Certificates issued by these CAs are automatically syn-
Additionally, without any centralized database of these chronized, allowing you to inventory, renew, reissue, and
troublesome certificates, tracking them down, replacing re-enroll with one-step automation from within your single
them, and mitigating the risk they pose becomes a signifi- Keyfactor Command console.
cant time-consuming challenge. Only direct synchronization
with your Certificate Authorities (CAs) results in a complete
view of your certificate inventory, comprehensive certificate
lifecycle management capabilities, and infrastructure-wide KEYFACTOR COMMAND ANY AGENT
enforcement of security policy. When you are in control of Built to satisfy wider spread adoption of public key infra-
certificate issuance processes, and are aware of all new cer- structure (PKI), Any Agent allows for customized connec-
tificates as they are issued and deployed, you can success- tions into any agent to serve as the centralized manager
fully build a digital identity foundation that is manageable, for certificates located in disparate keystores.
scalable, and secure.
Secure Certificate
Management at Scale
Removing the manual and error-prone elements of com-
mon certificate management actions such as enroll-
KEYFACTOR COMMAND ONE-STEP AUTOMATION
ment, re-issuance, renewal, renovation and inventory,
Keyfactor Command provides a central console responsi- Alleviates the costs and burdens of manual, partial, and
ble for all certificate management tasks. Manual processes, decentralized certificate tracking, elevating security to re-
spreadsheets and advanced monitoring tools may work well quired levels. Leveraging agents for device, server and
for small certificate counts and environments with limited is- network appliance endpoints and CA gateways for direct
suance capabilities, but most large organizations have come synchronization with a range of certificate authorities,
to recognize that there are more certificates deployed than one-step automation provides a platform for comprehen-
they can track or even know about. The result is an increase sive monitoring and full lifecycle management of all enter-
in efforts and costs to stay on top of them, with the risk of prise certificates.
security degradation from error and omission.
Many experts believe that quantum computing will pose ISARA is preparing for a “post-quantum” world by creating
a legitimate threat somewhere between 2025 and 2035. crypto algorithms designed to withstand the coming on-
When it does, today’s cryptographic algorithms such as RSA slaught of quantum computers. ISARA has been refining
and ECC will become easily breakable. While 2025 may these quantum-resistant algorithms and working with stan-
seem like a long way off, many systems being designed dards bodies such as the International Telecommunication
and deployed today will still be around then — especially Union and Cisco to ensure that tomorrow’s protocols and
“long-life” cryptographic systems such as industrial-focused data formats can accommodate the new algorithms.
IoT devices, cryptocurrencies, and PKIs. Savvy product engi-
neers have already begun to plan for this event by design-
ing crypto-agility directly into their products, with the help of
the Keyfactor platform.
PARTNERSHIP
Keyfactor and ISARA have joined forces to make this tech- Sun Tzu wrote in Art of War that “To … not prepare is the
nology usable today. By combining the power and flexibility greatest of crimes; to be prepared beforehand for any con-
of our Keyfactor platform with ISARA’s cryptographic know- tingency is the greatest of virtues.” In our quickly changing
how, we’ve created an easy way to generate and man- computing environment, the risk of not being ready for this
age certificates at massive scale, which are dual-signed — post-quantum era is potentially calamitous.
once with a conventional signature, and once with a quan-
tum-resistant algorithm.
ABOUT