Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

11/20/2009
08:00 AM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Two Ways To Encrypt Your Database

File/operating system level-encryption is actually implemented outside the database engine -- but it's still a form of database encryption. And it's referred to as "transparent" encryption because it doesn't require any changes to the database, or calling an application.

File/operating system level-encryption is actually implemented outside the database engine -- but it's still a form of database encryption. And it's referred to as "transparent" encryption because it doesn't require any changes to the database, or calling an application.In my last post, I introduced transparent database encryption perform as part of the native database technology. This is in contrast to file/OS encryption, which performs encryption tasks as part of the underlying operating system, independent of the database platform.

File/OS encryption works by intercepting the database's writes to disk, encrypting data blocks before storing them. Conversely, data is decrypted as the database requests information from disk. It can be used to encrypt an entire disk or just specific folders where the data is stored. This provides a degree of granularity if you only want to encrypt some portion of the database or a single database instance in a larger installation.

If you are confused that two database encryption technologies with radically different implementations both are considered "transparent," you're not alone. So let's compare and contrast transparent database encryption proper and file/OS encryption.

Both methods protect data stored on disk or media from direct inspection. Both can be easily retrofitted into existing database environments. Both operate seamlessly and do not require modifications to the database structure, queries, or calling application platform to use. Both offer industry-standard encryption algorithms and optional external key-management support. And perhaps most importantly, both are acceptable for many compliance mandates, such as PCI.

So when deciding which one to adopt, you should consider:

Ease of deployment: OS or file-level encryption is installed as a component of the operating system, requiring a software installation, configuration, possibly a recompilation of the kernel, and a system reboot. Database transparent encryption gets the edge in simplicity as it usually only involves changing some of the database configuration and, as worst, a database restart. In the big picture, both are simple operations.

Performance: My experience shows both are very close. Informal testing and feedback from several clients indicate database transparent encryption hovers around 6 percent overhead for typical environments. File/OS layer encryption was around 3 percent overhead, giving the external variant a slight edge. This is not a scientific evaluation and can vary a lot given how the database is used, but the distinction is somewhat irrelevant as both offer satisfactory performance.

Vendor Association: Let's face it, trust in the vendor and ability to haggle on price play a part as well. Many firms have a long-standing relationship with their database vendor and trust their products -- not to say file/OS is less reliable, but established trust is a big deal to many firms I speak with. Couple that with customers leveraging pricing and support as a bundle, and discounted pricing wins many customers over.

Versatility. Odds are you have multiple security and compliance issues to address, and being able to leverage a single investment to solve multiple security problems is a big advantage. As file/OS products encrypt general files as well as database contents, you can secure nondatabase content. This single product can be used for multiple purposes with a single, unified interface. And for companies that run more than one type of database, file/OS options give a unified approach to database encryption. The file/OS options provide a breadth of coverage with greater flexibility.

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security consulting practice. Special to Dark Reading. Adrian Lane is a Security Strategist and brings over 25 years of industry experience to the Securosis team, much of it at the executive level. Adrian specializes in database security, data security, and secure software development. With experience at Ingres, Oracle, and ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7029
PUBLISHED: 2020-08-11
A Cross-Site Request Forgery (CSRF) vulnerability was discovered in the System Management Interface Web component of Avaya Aura Communication Manager and Avaya Aura Messaging. This vulnerability could allow an unauthenticated remote attacker to perform Web administration actions with the privileged ...
CVE-2020-17489
PUBLISHED: 2020-08-11
An issue was discovered in certain configurations of GNOME gnome-shell through 3.36.4. When logging out of an account, the password box from the login dialog reappears with the password still visible. If the user had decided to have the password shown in cleartext at login time, it is then visible f...
CVE-2020-17495
PUBLISHED: 2020-08-11
django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database.
CVE-2020-0260
PUBLISHED: 2020-08-11
There is a possible out of bounds read due to an incorrect bounds check.Product: AndroidVersions: Android SoCAndroid ID: A-152225183
CVE-2020-16170
PUBLISHED: 2020-08-11
The Temi application 1.3.3 through 1.3.7931 for Android has hard-coded credentials.