Try it yourself
How format-preserving encryption works.
A fictitious customer record, protected with OpenText SecureData in Prewen's demo environment. You can see how format and structure are preserved and what a view by role can look like.
Illustration of the principle · not a measurement
Under your control · Switzerland
Provider · SaaS · Cloud · foreign law
Application
your systems
Protection layer
Web Service · SecureData Simple API
Sentry
Proxy (ICAP) · API Protection Gateway
Provider
SaaS · Cloud
Key Server
derives keys
Disclosure request
to the provider
Recordplaintext
SurnameMuster
Credit card4111 1111 1111 1111
IBANCH93 0076 2011 6238 5295 7
Step 1 of 5
Without protection
The record leaves the application in plaintext and is held by the provider in that form. Providers with a US connection can be required under US law (e.g. the CLOUD Act) to disclose it, even if the data is stored in Switzerland or the EU.
Values from Prewen's OpenText SecureData demo instance; the flow is animated, and Sentry does not run there.
Customer record · fictitious sample values
Offline preview · recorded values
What you see
Three properties that count in everyday use.
Format is preserved
Digits remain digits, dots and @ stay in place. Database fields, interfaces and validations keep running without modification.
View by role
Customer service sees the last four digits, accounting the bank details, Analytics only protected values.
Linkable and separate
Identical values produce identical ciphertexts – links between systems work. Different tenants receive different ciphertexts.
With your applications
How would this look in your environment?
We will gladly show you the demo live and discuss which data and applications are your focus.