Database encryption or application level encryption?

Question

When you need to store sensitive data such as CCs or SSNs, do you:

1) Build your own encryption routine within the application, define a secret key somewhere in a config file, and then manually encrypt/decrypt data going to the database.

2) Push all the problem to the database, using the built in DB capabilities (I think most vendors call it Transparent Database Encryption).

What trade-offs have you find for your solution? Does writing your own routine perform poorly when compared to TDE? Is code maintainability, or conversely DB vendor lock-in an issue?

Nola

Why did you post a link to your company in your question? – Apposition

Sorry, force of habit, cause that's how I sign-off on my blog. Now removed. – Nola

I once posted a good answer here on StackOverflow describing a great way to add application level encryption using the RijndaelManaged Class, and got in some pretty big HELL over it. I'm "ASSuming" you're going to get directed to DB encryption. – Earleenearlene

application level encryption - #3063397 – Earleenearlene

Answer 1

I've used a variety of encryption techniques and I believe it is both easier and more secure to encrypt on the application side using a proven encryption routine (i.e. .NET libraries).

If you encrypt on the database, that means the data is sent to and from the database in unencrypted form. This potentially allows for snooping/tampering between the application and the encryption routines on the database. Even if you store the key on the application side, it is still required on the database side to perform encryption. If the database is compromised, your data is at serious risk (just imagine someone running profiler while your application runs).

If you encrypt/decrypt in the application, sensitive data (including the key) is never revealed outside of the application server. Someone would have to compromise both the Web server and database server to access all of your data.

Also, I would highly recommend you not roll your own encryption routine. Chances are you will make a mistake that will reduce the overall security of your solution.

EDIT:

Also wanted to add another factor that will influence your decision. Do you need to query off of that encrypted data? If you encrypt at the application level, you will need to bring the data to the application, decrypt, and work from there. This becomes prohibitive as the data set grows larger - whereas with database encryption you can filter the data before it is sent back to the application.

Degenerate

You've raise good points. I do agree that Application Encryption, if correctly implemented, is the more secure solution. I've also argued that database encryption never existed as a topic before PCI --- ie. it's PCI that added it as a statement, vendors came in with solutions and now most people think it's the only option that's ideal. – Nola

if communication channel is only big issue then it could be fixed by securing transport layer. All dbs would support secure connections. – Rakia

Are there any libraries available for app encryption? – Kacykaczer

@Mayo: First of all, it is highly unlikely that the communication between the Database and the application server be compromised. This is why encryption for data in transit (TLS, etc) is implemented. Otherwise you could argue that tampering could occur from the app server to the service server, from the service server to the API, and so on. – Baleful

@Mayo: BTW, encryption keys should never be stored in the database, but rather in a HSM. So, you could argue the same way that one would have to compromise both the HSM and the database to access the data. Lastly, I would argue that an HSM is, by definition, much harder to compromise than a web server. – Baleful

@Mayo: lastly, it is much harder to get app-level encryption for data done right. Therefore, I personally think DB encryption is easier to implement, can be more secure, and is offered out of the box by many database vendors. – Baleful

Answer 2

When you encrypt sensitive data, you are essentially restricting access to those who have access to a key. The problem then becomes one of key management: ensuring only authorized people/systems have access to the key needed to decrypt the data.

You should of course use a standard encryption algorithm, easy enough these days, but what you do need to think about is what threats you are protecting against, how you are going to control access to the key(s), and how you control physical access to the servers.

Using TDE ensures that the contents of a database and its backups are encrypted, with minimal impact for authorized users of the database. So anyone who can access the database server with valid credentials will be able to see the unencrypted data. Also any DBA will usually have access to the key and be able to see the unencrypted data. But a third party who, say, gets hold of an offsite backup won't be able to access the data - which can be important for compliance with regulatory requirements.

On the other hand, if you encrypt in the application tier, you can use a key that is only accessible by administrators of the application server. This potentially gives you more security, if, for example, database server and application server administrators are kept apart (e.g. members of different organizations). DBAs who don't have access to the application server key won't be able to see the data.

In your original post, you talk about hiding a secret key in a configuration file on the application server. On the face of this, it sounds like the security equivalent of hiding the front door key under the doormat. If you do this, you need to think about how you will ensure that unauthorized people can't get access to the key.

Zenda

Answer 3

I agree with Mayo, but encryption in the DB could simplify the maintenance of the whole system.

Encryption to the Application level needs you manage the keys, the authentication and authorization phase for the keys and the visualization of the data (according with what Mayo has written).

If you choose Application Encryption you have to worry about the algorithm correctness not only in the developlment phase but in the maintenance phase. You have to implement unit test for no-regression. You have to manage the change of encryption algorithm because maybe you want a different and better algorithm.

And you have to be sure that Encrypted data will be always decrypted. It's not an obvious thing, because software has bugs and so on. Lost data is worse than clear data ;-)

Sure you can use a well known encryption library, but all the remainig things is a huge work to do for you.

Encryption into the DB protects only in the DB but you can consider to use some sort of SSL communication with the DB. I think (but I'm not sure) TDE implements this kind of secure communication.

Application is used from the user, an untrusted entity. You have to consider that the data in the application is lost. Why? If I want to steal data from a system that implements Encryption of the data at Application level or DB level, it could enough to use a photo-camera to get the data! Very simple!

You have to consider the security of the system, but the functionality too. More is the Security, less is the Functionality. I hope my considerations will be useful to you.

Reannareap

Answer 4

Being PCI-DSS Compliant does not remove your legal liability...

Currently there are only two states which provide such an exemption: Washington & Minnesota...

DBA's Promoting TDE as a PCI-DSS solution BEWARE!

TDE only protects data at rest, not data in transit or data in memory... Anybody whom has read access can read the all the data with any tool...

IMHO TDE is good when combined with a robust Application level encryption solution... As a stand-alone solution using TDE alone, it is a ticking time-bomb that the PCI QSA's buying it off as PCI-DSS Compliant have failed miserably to take note of... Wait till the lawyers get a grasp on this fundamental flaw...

Any security guru will tell you layers of security is the best approach....

Kresic