
2026-04-07
Modern organizations rely heavily on cryptography to secure applications, networks, and data. Yet many companies still lack a clear inventory of the cryptographic assets running across their infrastructure.
In this #KEYMASTER session, Sven Rajala interviews Dr. Vladimir Soukharev, VP of Cryptography at InfoSec Global (part of Keyfactor), about how organizations can discover, analyze, and manage their cryptographic footprint more effectively.
The conversation highlights a major reality: most companies do not fully understand where or how cryptography is being used within their systems. Without proper visibility, organizations risk vulnerabilities, outages, and compliance issues.
Below is a summary of the key insights from the discussion.
Historically, organizations attempted to catalogue cryptographic assets manually. This approach is highly inefficient and almost guaranteed to miss large portions of the cryptographic footprint.
Manual processes can take months or even years and still result in an incomplete inventory. Instead, a combination of automated discovery methods is necessary. Effective strategies include:
Binary analysis is particularly important because organizations often run software from third-party vendors or legacy systems where the source code is unavailable. Hidden cryptographic implementations frequently reside in these binaries.
One of the biggest risks in enterprise environments is shadow cryptography—cryptographic implementations that teams are unaware of or have not documented.
This often appears in:
Binary scanning can reveal unexpected algorithms or cryptographic standards that organizations did not knowingly deploy. In some cases, companies even discover foreign cryptographic algorithms embedded in software components from external vendors.
These discoveries raise important questions about software supply chains, security policies, and compliance requirements.
Once cryptographic assets are discovered, the next challenge is understanding which issues matter most.
Security teams typically analyze multiple dimensions when evaluating risk:
Correlation between assets is also critical. For example:
These problems are not always cryptographic weaknesses themselves, but are often implementation and operational risks.
Several issues commonly appear during cryptographic scans:
Private keys stored outside secure keystores represent a serious security flaw—like writing a password on a sticky note.
Weak or deprecated algorithms may still exist in legacy systems.
Expired certificates can cause widespread service outages if organizations cannot quickly locate all instances of the certificate in their environment.
These operational issues can disrupt services even when no security breach has occurred.
Interestingly, cryptographic inventory can also support malware threat detection.
Sophisticated attackers often plant malicious code gradually across systems, and these payloads frequently include cryptographic artifacts. By regularly scanning environments and monitoring changes, security teams can detect new cryptographic components appearing unexpectedly.
Sudden cryptographic changes may indicate the early stages of a malware deployment.
Managing cryptography manually is not scalable. Automation and integrations are essential.
Organizations can improve operations by:
The goal is to embed cryptography management directly into existing operational workflows.
A major theme in the discussion is crypto agility—the ability to quickly change cryptographic algorithms, keys, or libraries across systems.
Many organizations currently rely on multiple cryptographic libraries due to:
Rather than forcing a single library everywhere, the more practical goal is to build infrastructure that enables rapid cryptographic updates.
Crypto agility allows organizations to:
Tools alone cannot solve cryptographic challenges. Organizations also need internal expertise.
Developers often implement cryptography without deep knowledge of cryptographic security principles. While an algorithm may technically encrypt data, it may still be broken or implemented incorrectly or insecurely.
Having at least a small number of skilled cryptography experts inside an organization helps ensure:

