Applications used to run in tightly controlled on-premises environments, but in recent years that has extended across hybrid and multi-cloud landscapes. Moving to the cloud has brought flexibility and scalability to countless organizations, but it has also multiplied the ways data can be exposed.
Traditional encryption remains one of the backbones of data protection, but it’s also capable of creating new problems. By definition, it changes the format of the data, which in turn breaks application compatibility or requires significant reengineering.
This is where format-preserving encryption (FPE) enters the frame. Unlike traditional encryption methods, FPE protects sensitive data while keeping it in its same format—think credit card numbers, Social Security numbers or birthdates. For organizations that use this data across complex cloud systems, it makes encryption both effective and practical.
In this article, we’ll look at:
- What is FPE, and why does it matter to modern data protection?
- Cloud FPE best practices.
- Balancing performance, compliance, and scalability with FPE.
- The importance of key management, hardware security modules (HSMs), and crypto-agility in preparing for post-quantum cryptography (PQC).
Let’s start with the basics.
What is FPE and Why Does it Matter?
Format-preserving encryption (FPE) is a way to encrypt sensitive data where the output maintains the same format as the input. So, if the input is a 16-digit credit card number, the encrypted result will also be 16 digits. Or if it’s a U.S. Social Security number with the familiar nine-digit structure, the encrypted result will still look like a Social Security number.
This subtle difference here is important. Many legacy systems and cloud applications are designed around rigid data formats. But traditional encryption turns data into binary strings or long alphanumeric sequences, causing errors or leading to costly and time-consuming code changes. FPE solves that by letting encrypted data flow through existing systems without breaking functionality.
Industries like finance, healthcare and retail rely on FPE because of the enormous volumes of structured data they handle. It’s great for situations where you need to encrypt sensitive information but still fit it into existing data fields. In this sense, it’s a natural fit for cloud environments, where interoperability and speed are critical.
FPE also has an advantage over tokenization in certain cases. While tokenization can be effective, it often requires a central token vault, which introduces another layer of complexity. Using FPE is a way for organizations to reverse the process cryptographically, making it easier to use across distributed cloud systems where teams need real-time access to data.
*Learn more: A guide to Data Tokenization
Let’s take a closer look at four specific best practices for implementing FPE across the cloud:
No. 1: Discover and Classify Sensitive Data
You can’t protect what you don’t know you have. Before rolling out FPE, organizations need a clear picture of the sensitive data they have across all of their systems. This means running automated discovery tools that scan databases, object storage, file systems, and SaaS applications to locate personal information, payment card data, intellectual property, and any other data that should be kept private.
You’ve likely encountered situations where teams store redundant or shadow copies of sensitive data across multiple cloud environments without notifying security teams. If FPE is used only in primary systems but not in these overlooked repositories, there’s still a significant risk. It has become common knowledge in the industry that misidentified or misclassified data is a common root cause of non-compliance.
No. 2: Strengthen Key Management with HSMs
The real strength of format-preserving encryption lies in how your encryption keys are managed. The keys are the crown jewels, and they must be protected at all costs. If they’re mishandled, attackers can unlock everything.
In the cloud, keys might be used across multiple platforms and regions, making centralized enterprise key management essential. Specific best practices here include:
Centralization: Use a unified key management service rather than managing keys separately in each cloud.
Rotation: Rotate keys regularly to minimize the impact of a potential breach.
Segregation of duties: Ensure that no single administrator has full control over both encrypted data and the keys.
HSM integration: If you’re dealing with regulatory or high-assurance requirements, hardware security modules (HSMs) should be used to protect key material in a tamper-resistant environment.
Key management is one of the most overlooked yet critical elements of securing cloud data. FPE without strong key lifecycle practices is like locking your doors but leaving the key under the doormat.
No. 3: Balance Performance with Compliance
FPE sounds great, so why not use it to encrypt everything? The answer is performance. FPE is more computationally intensive than traditional ciphers, so applying it to every dataset leads to higher latency or increased costs when dealing with high volumes of data.
This is why discovery and classification are so important; you want to apply FPE where it matters most. For example, encrypting sensitive customer data in a financial application makes sense, but encrypting every log file may not.
Compliance frameworks also inform how you should adopt FPE. PCI DSS, for example, explicitly allows format-preserving encryption for credit card numbers, provided the implementation follows NIST-approved methods. For healthcare data under HIPAA or personal data under GDPR, the same principle applies: organizations must prove they are protecting sensitive information in a way that balances usability with security.
No. 4: Plan for Crypto-Agility and Post-Quantum Security
The final best practice is something that’s often overlooked across business: proactively planning for tomorrow. Quantum computing poses a serious risk to today’s cryptographic algorithms, including those used in FPE. While symmetric algorithms like AES (a common choice for FPE) are more resistant than public-key algorithms, they will eventually require larger key sizes and ongoing evaluation.
This is why organizations must embrace the concept of crypto-agility, or the ability to switch algorithms or key sizes quickly as standards evolve. The bottom line is, organizations deploying FPE today should ensure their architecture is flexible enough to integrate new PQC algorithms tomorrow.
This is where tools like Fortanix Key Insight and Fortanix Data Security Manager (DSM) can play a role:
- Key Insight helps organizations discover which cryptographic algorithms are in use and which might be vulnerable [source].
- DSM provides crypto-agility by making it easier to swap out algorithms, manage the transition to PQC, and ensure key material remains secure across all environments [source].
There’s no denying it: thinking about PQC now rather than waiting until the risk becomes urgent will save organizations significant cost and disruption later.
FPE Makes Secure Cloud Adoption Possible
The cloud has opened new opportunities for innovation, but it has changed the game for data protection. Format-preserving encryption (FPE) gives any organization with a presence in the cloud a practical, powerful way to protect sensitive information without breaking the systems that rely on it.
The best practices for implementing FPE are clear:
- Start with data discovery and classification.
- Integrate encryption with strong key management and HSMs.
- Balance security with performance and compliance requirements.
- Build crypto-agility into your architecture to prepare for the post-quantum era.
When approached strategically, FPE can become a cornerstone of a broader cloud security program that keeps sensitive data safe while enabling teams to take advantage of seamless application performance.
If you’re ready to strengthen your encryption strategy, explore how Fortanix can help. Request a demo to see how Fortanix can protect your most valuable data assets.


