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

9/20/2010
11:28 AM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Protegrity Gets Aggressive

Last week Protegrity announced it had filed patent infringement suits against NuBridges and Voltage Security Inc., its main competitors. Patent infringements suits are nothing new with technology companies, but this one was a little odd in that the suits were actually filed in May.

Last week Protegrity announced it had filed patent infringement suits against NuBridges and Voltage Security Inc., its main competitors. Patent infringements suits are nothing new with technology companies, but this one was a little odd in that the suits were actually filed in May.We also learned of a patent infringement suit leveled against Ingrian Networks (now part of Safenet) back in April 2008. It looks like more lawsuits could be coming in the future.

Protegrity is a vendor of encryption products for data security, and many of its products have centered on protecting data that resides in databases. It has always been, in my opinion, technically innovative. And it has authored many patents during the past decade. A couple of the security startups I worked for authored similar patent claims; I was responsible for the technical side of patent development, so I reviewed and contrasted the Protegrity patents at the request of several patent authorities. Though I am not a patent attorney, I do have a basic understanding of the technologies described. There are several patents referenced in the official Protegrity press release, but the "Multi-encryption levels on a data element" is the key claim, with the others building off this central invention.

How I interpret Protegrity's multilevel patent is as follows: It describes a solution for row- or cell-level encryption of data stored in a database. What's of interest is the encryption -- or any other security measures that may be employed -- is described in another database. For the sake of simplicity, this is about the relationship between encrypted data storage and external key management. The second database describes what protections are in place, such as which encryption algorithm was used, the key, the mode of operation, or perhaps describe some masking function. By having a second database that acts as a lookup table for security means, I can implement different encryption schemes and do key rotation on a row-by-row, even element-by-element basis -- very adaptable, and a very easy way to manage complex key/encryption substitutions.

I have asked a couple of people at Protegrity to explain what this really means, specifically the use of "multilevel database encryption," but they are unable to comment at this time over and above what's in the press release. I wanted to know if they felt my interpretation was faulty, but they cannot provide any input at this time.

So there are three lingering questions:

1) What does this mean for the competition? I am not aware that the competitors use such a scheme. Or if they do, there are subtle changes to their deployment that would place them outside of the Protegrity claim.

2) Why didn't it file suit against all of the database and key management vendors? Most databases provide an API for row- and cell-level encryption, and an external key management server is, in fact, a database -- a specialized database, but a database nonetheless.

3) Why announce now? Does this mean it feels it is going to win the suit with Ingrian, or does it mean it just discovered evidence of infringement. Or is there some other motivation?

If you narrowly interpret the claims, then odds are Protegrity does not win this suit. If you broadly apply the principle that Protegrity has described in the patents, then it looks like it owns row- and cell- level database encryption when used with external key management. That would make this battle bigger than a couple of squabbling midtier security providers.

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
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-14318
PUBLISHED: 2020-12-03
A flaw was found in the way samba handled file and directory permissions. An authenticated user could use this flaw to gain access to certain file and directory information which otherwise would be unavailable to the attacker.
CVE-2020-2320
PUBLISHED: 2020-12-03
Jenkins Plugin Installation Manager Tool 2.1.3 and earlier does not verify plugin downloads.
CVE-2020-2321
PUBLISHED: 2020-12-03
A cross-site request forgery (CSRF) vulnerability in Jenkins Shelve Project Plugin 3.0 and earlier allows attackers to shelve, unshelve, or delete a project.
CVE-2020-2322
PUBLISHED: 2020-12-03
Jenkins Chaos Monkey Plugin 0.3 and earlier does not perform permission checks in several HTTP endpoints, allowing attackers with Overall/Read permission to generate load and to generate memory leaks.
CVE-2020-2323
PUBLISHED: 2020-12-03
Jenkins Chaos Monkey Plugin 0.4 and earlier does not perform permission checks in an HTTP endpoint, allowing attackers with Overall/Read permission to access the Chaos Monkey page and to see the history of actions.