Skip to content
Fast Company Executive Board

The Fast Company Executive Board is a private, fee-based network of influential leaders, experts, executives, and entrepreneurs who share their insights with our audience.

How to build a crypto-agile organization

From IT debt to strategic resilience, here’s a roadmap to treat cryptography as a strategic asset

[Photo: Getty Images]

Profile photo of Elizabeth Green

Advisory Board · QuSecure

For two decades, organizations have unknowingly accumulated a massive, silent liability on their balance sheets: cryptographic technical debt. Unlike infrastructure debt—servers needing upgrades or legacy apps needing refactoring—crypto-debt is far more dangerous because it sits deep inside systems, products, hardware, APIs, supply chains, and vendor stacks. Most executives don’t even know it exists.

The National Institute of Standards and Technology (NIST) does. And its latest guidance is clear: If you don’t build crypto-agility now, your organization will struggle to respond to the next cryptographic shift—whether it’s post-quantum migration or the next algorithmic deprecation.

The message is urgent: Your cryptography cannot remain static. It must become agile.

THE HIDDEN IT DEBT NO ONE TRACKS

Most companies have millions of lines of code, dozens of third-party libraries, embedded hardware, SaaS tools, mobile apps, and API integrations that rely on hard-coded cryptography.

And that’s the problem.

Over the last decade, cryptographic algorithms, protocols, and libraries were often built deeply and rigidly into systems, making them difficult—sometimes nearly impossible—to swap out. Developers made decisions that felt reasonable at the time:

  • Hard-coding RSA or ECC algorithms to meet a deadline
  • Embedding cryptography directly into device firmware
  • Using libraries without upgrade paths
  • Prioritizing compatibility instead of future flexibility
  • Relying on vendor-provided crypto “black boxes”
  • Adopting protocols that were never designed for long-term adaptability

Each decision saved time then. Each decision costs exponential IT debt now.

And the older the system, the more deeply this rigidity is baked in.

This is why NIST’s new emphasis on crypto-agility is not merely a “post-quantum prep project.” It’s a strategic modernization mandate.

WHY NIST IS SOUNDING THE ALARM—AGAIN

In its latest draft guidance on crypto-agility, NIST urges organizations to:

1. Inventory all cryptography—everywhere

Organizations cannot change what they cannot see. NIST stresses that most enterprises have no complete inventory of their cryptographic assets:

  • Which algorithms are used
  • Where they are used
  • How they are implemented
  • Whether they can be upgraded
  • Whether third-party vendors allow changes

Without this, migration is guesswork.

2. Design for algorithm swap, not static encryption

NIST’s message is blunt: Hard-coded cryptography must become modular.

The guidance emphasizes building systems that support:

  • Multiple algorithms
  • Hybrid algorithm suites (classic + PQC)
  • Abstraction layers
  • Configurable, policy-driven cryptography
  • Seamless algorithm replacement

This is the core of crypto-agility.

3. Shift from “one-time upgrades” to a continuous cryptographic lifecycle

NIST is pushing leaders to recognize cryptography as a living control, not a static one. This means:

  • Monitoring algorithm health
  • Tracking vulnerabilities
  • Preparing for transitions
  • Updating governance and contracts
  • Planning for periodic algorithm replacement

The future won’t be “upgrade once to post-quantum and we’re done.” The future will be continuous cryptographic change.

4. Break vendor lock-in

Perhaps the most overlooked part of NIST’s guidance: removing dependencies on vendors that use fixed algorithms or proprietary crypto with no upgrade paths. This includes:

  • Hardware security modules
  • IoT/OT devices
  • Firmware stacks
  • SaaS platforms
  • Network gear

Vendor crypto-rigidity is vendor risk.

THE BUSINESS CONSEQUENCE OF CRYPTO-DEBT

Crypto-debt is no longer just a cybersecurity problem. It’s a business resilience problem.

1. Systems may take years to migrate

Large enterprises discovered during TLS and SHA-1 migration that cryptographic change can take:

  • 18–36 months for inventory
  • 12–24 months for architecture redesign
  • 6–24 months to coordinate vendors
  • 6–12 months to deploy, test, and validate

Quantum-era migrations could be larger and more complex.

2. “Harvest now, decrypt later” raises long-tail liability

Encrypted data stolen today can be decrypted tomorrow when algorithms fail. Crypto-debt turns into:

  • Privacy liabilities
  • IP exposure
  • Insider risk
  • Customer loss
  • Regulatory penalties

It’s deferred risk—paid with future reputational and operational costs.

3. Legacy cryptography slows innovation

Cloud modernization, API-first architectures, distributed work, hybrid environments, and AI systems all rely on secure, manageable crypto foundations. Crypto-debt creates friction that slows transformation.

HOW LEADERS CAN START REDUCING CRYPTO-DEBT TODAY

NIST doesn’t just issue warnings—they are urging concrete steps enterprises can take now:

1. Start a cryptographic inventory and dependency map

This should include:

  • All applications and services
  • APIs and libraries
  • Hardware devices
  • Certificates and keys
  • Firmware and embedded components
  • Vendors and third-party systems

This becomes your baseline.

2. Establish a crypto-agility architecture

Build or evolve to a structure that supports:

  • Modular cryptographic libraries
  • Configuration-driven algorithms
  • Centralized policy enforcement
  • Abstraction layers that decouple apps from algorithms
  • Support for hybrid PQC + classical crypto suites

This is foundational for anything NIST is urging.

3. Develop a cryptographic governance program

Key elements include:

  • Roles and responsibilities
  • Standards and policy updates
  • Vendor requirements
  • Algorithm transition roadmaps
  • Testing, validation, and monitoring
  • KPIs for “crypto-agility maturity”

This elevates crypto from an IT concern to an enterprise governance function.

4. Engage your vendors—now

Ask every vendor:

  • Which algorithms do you use?
  • Are they upgradeable?
  • What is your post-quantum roadmap?
  • Do you support crypto-agility?
  • Is your architecture modular or fixed?
  • What is your timeline for PQC-supported products?

If they cannot provide answers, they are a liability.

CRYPTO-AGILITY IS THE NEW SECURITY RESILIENCE

The organizations that will thrive in the next decade won’t just be the ones that modernize their cryptography.

They will be the ones that build the capability to keep modernizing it.

Crypto-agility transforms cryptography from a rigid technical dependency into an adaptable business capability. It reduces IT debt, enables innovation, reduces long-tail risk, and positions firms to respond to whatever cryptographic challenges emerge next—quantum or otherwise.

NIST’s message is clear: The future belongs to the organizations that treat cryptography as a strategic asset—not a static one.

Elizabeth Green is an advisory board member of QuSecure.