Most encryption implementations are protecting against the wrong threat. These methods do nothing to
counter modern day data breach risk and attacks.
Common Misconceptions With Encryption
Across the industry from security professionals to auditors, there are some common misconceptions about encryption methods that a lot people get confused about in terms of the threat model and risks that are actually being mitigated.
Without understanding the methods and what you are protecting against, it’s difficult to ensure the appropriate data protection model. Further, actually implementing encryption can be quite complex with several interdependencies.
Read our article on the threat model and how these gaps do not stop attackers in “Why you can’t stop data breaches – Part I”
Read the article by our CTO, PD Kolte, on “Why data tokenization is insecure”
Download the white paper on “Simplifying Application Level Encryption”
Below is an overview of some of the different methods that are commonly available.
Disk Level Encryption
Transparent Data Encryption (TDE)
Field Level Encryption
Record Level Encryption
Encrypts data at the physical disk layer and protects against physical data theft of a hard drive or laptop. Operating system access provides full access to the data in the clear.
Provides encryption of a database as a container on the file system. This protects against physical data theft and against access from a non-DBA who may have access to a system where the database resides. Access to the database provides full access to the data in the clear.
Encrypts columns or fields of data in a structured data environment. This protects against privileged users and DBAs with access to a database, insider threat, 3rd party developers, and attackers moving laterally (east-west) in an environment from seeing sensitive data in the clear. This method is sometimes referred to as Application Level Encryption (ALE)
Encrypts data on a per row or record basis in a structured data environment using different keys for different rows. This helps prevent oversharing of data in co-mingled data stores or multi-tenant SaaS environments and can also be applied to segment data based on classification. This method is sometimes referred to as Record Level Encryption (RLE)
All of these methods are commonly referred to as Encryption At-Rest. Perhaps part of the issue is with the term “Encryption At-Rest”, because technically, all of these methods are at-rest encryption options. But, clearly the risk mitigation provided is different based on the data protection method.
On the right is an example of Transparent Data Encryption (TDE).
As you can see, anyone with access to the database sees the data in the clear.
- It does nothing to protect against a modern day hack or breach. (most recent breaches had TDE in place and data was still stolen)
- Data in the logs are in the clear, which violates compliance regulations such as PCI
- Data in memory is in the clear
- Attackers moving laterally in the network gain access to data in the clear
To the left is an example of Application Level Encryption or Field Level Encryption.
- Privileged users and insiders with access to the system see the data encrypted
- Attackers accessing the system laterally through the network see encrypted data
- Data in logs are encrypted
- Data in memory are encrypted
Baffle delivers application level encryption on a per field basis via a “no code” model. The technology supports “homomorphic-like” capabilities — the ability to perform mathematical operations on AES encrypted data without ever decrypting the underlying values. Data stays protected in memory, in use and at-rest.
No application code modification
Virtually no performance
Integrates easily into your
AES encryption in memory, in use,
Two years ago, the General Data Protection Regulation (GDPR) was introduced and hailed as the most important change in data privacy regulation in two decades. Originating in the EU, GDPR empowered consumers to not only have a right to know what their data will be used for and giving them the right to be forgotten,…
(Why you can’t stop data breaches – Part II) This blog, the second in a series on “Why you can’t stop data breaches”, details various attack methods used to compromise a set of common tokenization methods. The first entry in the series discussed database level encryption, encryption at-rest and gaps in the threat model and…
On January 1, 2020, the California Consumer Privacy Act (CCPA) became operational, however, enforcement of privacy-related suits cannot be initiated until July 1. The regulation, similar to the EU’s General Data Protection Regulation (GDPR), seeks to offer people greater control over the sharing of their personal information by businesses. For example, consumers can request to…
See How Baffle Can Protect Your Data
Schedule a live demo with one of our solutions experts to get answers to your questions