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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
US Formally Attributes SolarWinds Attack to Russian Intelligence Agency
Jai Vijayan, Contributing Writer,  4/15/2021
News
Dependency Problems Increase for Open Source Components
Robert Lemos, Contributing Writer,  4/14/2021
News
FBI Operation Remotely Removes Web Shells From Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-35979
PUBLISHED: 2021-04-21
An issue was discovered in GPAC version 0.8.0 and 1.0.1. There is heap-based buffer overflow in the function gp_rtp_builder_do_avc() in ietf/rtp_pck_mpeg4.c.
CVE-2020-35980
PUBLISHED: 2021-04-21
An issue was discovered in GPAC version 0.8.0 and 1.0.1. There is a use-after-free in the function gf_isom_box_del() in isomedia/box_funcs.c.
CVE-2020-35981
PUBLISHED: 2021-04-21
An issue was discovered in GPAC version 0.8.0 and 1.0.1. There is an invalid pointer dereference in the function SetupWriters() in isomedia/isom_store.c.
CVE-2020-35982
PUBLISHED: 2021-04-21
An issue was discovered in GPAC version 0.8.0 and 1.0.1. There is an invalid pointer dereference in the function gf_hinter_track_finalize() in media_tools/isom_hinter.c.
CVE-2021-30031
PUBLISHED: 2021-04-21
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.