I “tweaked” my hammy just reading this

Recently, I was reading about the Format Preserving Encryption (FPE)* variation that we implemented in our cloud data privacy/ tokenization gateway solution and realized that they had used a tweak to make it much stronger.

I am proud of our guys who burned some extra midnight oil to get this out on time to save our customer sensitive data moving to the cloud. This allowed us to work with some major cloud providers to help with their data storage in a highly secure manner. Watch out for my next blog on how FPE can help you preserve your data fairly easily. You can also read my blog about protecting sensitive data that is sent to the cloud here.
Essentially a tweak is…………..
a cross between a salt and a nonce (thank god it is not crossed with pepper!). For format preserving encryption (FPE), it can be used to significantly enhance the encryption security.

Here is how:
If you use a deterministic/tweakless scheme, it is possible that an attacker could create by non-cryptographic means a useful dictionary of plaintext/ciphertext pairs. For example, assume that you are encrypting the middle 6-digits of a 16-digit Credit Card Number (CCN or PAN data). Out of a possible 100 million entries, there would be 100 CCNs with the same 6 digits (It is fairly common to keep the first 5 digits preserved for routing purposes and the last 4 digits for validation purposes, thus leaving only the middle 6 digits to be encrypted). Every plaintext/ciphertext pair that an attacker identified would allow the attacker to decrypt every CCN that happens to have those same middle 6 digits. Utilizing a different tweak for these different encryptions would eliminate this information leakage. In this case, the tweak could be:
• The other ten digits of the CCN. (Perfect seed of using what is already there).
• A string that is unique to the specific document in which the encryption is occurring.
• A randomly generate string that is used for a much smaller subset of the encryptions than the specific key is being used for.
As the first two possible sources of tweaks indicated, a tweak value does not need to be secret. It just needs to be large enough to uniquely differentiate related encryptions in the same or different documents.
Summary: a tweak is just a mechanism to add entropy between encryption that could leak information. Using a tweak can significantly enhance security and is therefore strongly recommended.
*Format Preserving Encryption (FPE) is a process that deterministically encrypts plaintext into ciphertext that has the same character set and same number of logical radix characters. This allows the encrypted data to be stored and transmitted by the same programs and databases that handled the plaintext data without modifying the service storing and transmitting the data. For example, a credit card number can be a 16 byte decimal string. If FPE is applied to the number, the ciphertext is also a 16 byte decimal string. Another example is encrypting an alphanumeric address, where the ciphertext must also be an alphanumeric string of same length.

About these ads

About Andy Thurai
This blog is published by Andy Thurai, Chief Architect & Group CTO for the Intel unit that is responsible for Cloud/ Application security, API, Big Data, SOA and Mobile middleware solutions, where he is responsible for architecting API, SOA, Cloud, Governance, Security, and Identity solutions for their major corporate customers. In his role, he is responsible for helping Intel/McAfee field sales, technical teams and customer executives. Prior to this role, he has held technology architecture leadership and executive positions with L-1 Identity Solutions, IBM (Datapower), BMC, CSC, and Nortel. His interests and expertise include Cloud, SOA, identity management, security, governance, and SaaS. He holds a degree in Electrical and Electronics engineering and has over 25+ years of IT experience. He blogs regularly at www.thurai.net/securityblog on API, Security, SOA, Identity, Governance and Cloud topics. You can find him on LinkedIn at http://www.linkedin.com/in/andythurai. or on Twitter at @AndyThurai.

2 Responses to I “tweaked” my hammy just reading this

  1. Pingback: Part 2: Context aware Data Privacy « SOA, Cloud, Identity & Security Blog

  2. Pingback: Context Aware Data Privacy (part II) « Intel XML Gateway – SOA Expressway Blog

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 28 other followers

%d bloggers like this: