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

Major Vendors Propose Interoperability Standard For Key Management

IBM, HP, RSA head up list of vendors supporting guidelines designed to ease deployment and management of encryption

A group of vendors have proposed a new industry standard designed to simplify the implementation and management of encryption technology across large enterprises.

Brocade, HP, IBM, LSI, RSA, Seagate, and Thales (formerly nCipher) today announced the creation of the Key Management Interoperability Protocol (KMIP), a jointly developed specification for enterprise key management. KMIP is designed to provide a single protocol for communication between enterprise key management services and encryption systems, the companies say.

The seven vendors plan to submit the specification to the Organization for the Advancement of Structured Information Standards (OASIS) as an industry standard.

The problem with encryption, particularly in large enterprises, is that there are so many products and methods of doing it, observers say. Companies often deploy separate encryption systems for different business uses, such as laptops, storage, databases, and applications. And each encryption product typically has a different method of generating, distributing, storing, expiring, and rotating encryption "keys" -- the technologies that code and decode the data.

The concept of "key management" -- the practices associated with generating and storing encryption keys across an enterprise -- has been debated for decades. But vendors and cryptographers have never been able to agree on the best way to do it, leaving enterprise security managers stuck with the largely manual process of managing keys separately for each vendor or product. This administrative issue has made enterprises slow to roll out encryption on a broad scale.

"In general, enterprises have a lack of confidence that, once encrypted, IT managers will be able to actually recover the encrypted data when they'll need to," the standards developers say.

KMIP is designed to help resolve this problem in large enterprises that have multiple encryption tools, the vendors say. "The problem addressed by KMIP is primarily that of standardizing communication between encryption systems that need to consume keys and the key management systems that create and manage those keys," the specification says.

"By defining a low-level protocol that can be used to request and deliver keys between any key manager and any encryption system, KMIP enables the industry to have any encryption system communicate with any key management system," the specification says. "Through this interoperability, enterprises will be able to deploy a single enterprise key management infrastructure to manage keys for all encryption systems in the enterprise."

If it becomes widely adopted, the new standard could make encryption easier to deploy and manage, no matter which products or vendors the organization chooses, observers say. This ease of deployment is becoming increasingly important given that more regulatory and industry compliance guidelines require some form of encryption. Forty-four percent of enterprises plan to encrypt more than 75 percent of their data by 2009, according to IDC Research.

Although many encryption and key management technologies have been held up as potential "industry standards" during the years, KMIP is the "first specification for enterprise key management that is ready for adoption," the vendors say. It is designed to be "complementary" to application-specific standards projects, such as IEEE 1619.3 (for storage) and OASIS EKMI (for XML), the group says.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
How to Better Secure Your Microsoft 365 Environment
Kelly Sheridan, Staff Editor, Dark Reading,  1/25/2021
Attackers Leave Stolen Credentials Searchable on Google
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3142
PUBLISHED: 2021-01-28
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2020-35128. Reason: This candidate is a reservation duplicate of CVE-2020-35128. Notes: All CVE users should reference CVE-2020-35128 instead of this candidate. All references and descriptions in this candidate have been removed to preve...
CVE-2020-35124
PUBLISHED: 2021-01-28
A cross-site scripting (XSS) vulnerability in the assets component of Mautic before 3.2.4 allows remote attackers to inject executable JavaScript through the Referer header of asset downloads.
CVE-2020-25782
PUBLISHED: 2021-01-28
An issue was discovered on Accfly Wireless Security IR Camera 720P System with software versions v3.10.73 through v4.15.77. There is an unauthenticated stack-based buffer overflow in the function CNetClientManage::ServerIP_Proto_Set during incoming message handling.
CVE-2020-25783
PUBLISHED: 2021-01-28
An issue was discovered on Accfly Wireless Security IR Camera System 720P with software versions v3.10.73 through v4.15.77. There is an unauthenticated heap-based buffer overflow in the function CNetClientTalk::OprMsg during incoming message handling.
CVE-2020-25784
PUBLISHED: 2021-01-28
An issue was discovered on Accfly Wireless Security IR Camera System 720P with software versions v3.10.73 through v4.15.77. There is an unauthenticated stack-based buffer overflow in the function CNetClientGuard::SubOprMsg during incoming message handling.