33
1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next www.oasis-open.org

1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Embed Size (px)

Citation preview

Page 1: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

1

Addressing the New Complexities in Key

Management Interoperability

KMIP V.Next

www.oasis-open.org

Page 2: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Presenters John Leiseboer

CTO, Quintessence Labs

Nathan TurajskiSenior Product Manager, Thales e-Security

Robert GriffinChief Security Architect, RSA/EMC

Saikat Saha Senior Product Manager, Data Encryption & Control, SafeNet

Tony Cox Technical Director, Cryptsoft

2

Page 3: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Agenda

What KMIP has accomplished New challenges in key management Addressing the challenges

3

Page 4: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

4

KMIP V1.0 / V1.1

Page 5: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Prior to KMIP each application had to support each vendor protocol

5

Page 6: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

With KMIP each application only requires support for one protocol

6

Page 7: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Prior to KMIP each application had to integrate each vendor SDK

7

Page 8: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

With KMIP each application only requires one vendor SDK integration

8

Page 9: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

9

Encrypting Storage

Host

Enterprise Key Manager

@!$%!%!%!%%^&*&^%$#&%$#$%*!^@*%$*^^^^%$@*)%#*@(*$%%%%#@

Request Header

Get Unique Identifier

Symmetric Key

Response Header

Unique Identifier

Key Value

KMIP Request / Response Model

Unencrypted data Encrypted data

Name: XYZSSN: 1234567890Acct No: 45YT-658Status: Gold

Page 10: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

10

KMIP defines a set of Operations that apply to Managed Objects that consist of Attributes and possibly cryptographic material

CreateCreate Key PairRegisterRe-keyRe-key Key PairDerive KeyCertifyRe-certifyLocateCheckGetGet AttributesGet Attribute ListAdd AttributeModify AttributeDelete AttributeObtain LeaseGet Usage AllocationActivateRevokeDestroyArchiveRecoverValidateQueryDiscover VersionCancelPollNotifyPut

Certificate

Symmetric Key

Public Key

Private Key

Split Key

Template

Policy Template

Secret Data

Opaque Object

Managed ObjectsProtocol Operations

Key Block (for keys)

or

Value (for certificates)

Unique IdentifierNameObject TypeCryptographic AlgorithmCryptographic LengthCryptographic ParametersCryptographic Domain ParametersCertificate TypeCertificate LengthX.509 Certificate IdentifierX.509 Certificate SubjectX.509 Certificate IssuerCertificate IdentifierCertificate SubjectCertificate IssuerDigital Signature AlgorithmDigestOperation Policy NameCryptographic Usage MaskLease TimeUsage LimitsStateInitial DateActivation DateProcess Start DateProtect Stop DateDeactivation DateDestroy DateCompromise Occurrence DateCompromise DateRevocation ReasonArchive DateObject GroupFreshLinkApplication Specific InformationContact InformationLast Change DateCustom Attribute

Object Attributes

Page 11: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

11

Transport-Level EncodingKey Client Key Server

API

Internal representation

Transport

Internal representation

Transport

KMIP Encode

KMIP Encode

KMIP Decode

KMIP Decode

API

KMIP TTLV encoding

…Tag Len Val

ueTag Len Val

ue

…TagLenVal

ueTagLenVal

ue

Type

Type

Type

Type

Page 12: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

12

Message Encoding In a TTLV-encoded message, Attributes are

identified either by tag value or by their name, depending on the context:

When the operation lists the attribute name among the objects part of the request/response (such as Unique Identifier), its tag is used in the encoded message

When the operation does not list the attribute name explicitly, but instead includes Template-Attribute (such as in the Create operation) or Attribute (such as in Add Attribute) objects as part of the request/response, its name is used in the encoded message

tag

type length value

operation 04 4 0000000A

tag type length value

Unique Identifier

06 24 1f165d65-cbbd-4bd6-9867-80e0b390acf9

Get Unique identifier

Page 13: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

13

Authentication Authentication is external to the protocol All servers should support at least

TLS V1.0 Authentication message field contains the

Credential Base Object Client or server certificate in the case of TLS

Host

@!$%!%!%!%%^&*&^%$#&%$#$%*!^@*%$*^^^^%$@*)%#*@(*$%%%%#@

@!$%!%!%!%%^&*&^%$#&%$#$%*!^@*%$*^^^^%$@*)%#*@(*$%%%%#@

Enterprise Key Manager

Identity certificate

Identity certificate

SSL/TLS

Page 14: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

KMIP Interop at RSAC 2012

Interop Network

Server Server2 x Server

2 x Server

3 x Client

Server

ClientClient Client3 x Client

Client

14

Page 15: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

15

KMIP Test Cases

Provide examples of message exchanges for common key management requirements

basic functionality (create, get, register, delete of sym. keys and templates)

life-cycle support (key states) auditing and reporting key exchange asymmetric keys key roll-over archival vendor-specific message extensions

Details of the message composition and TTLV encoding

Page 16: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

16

KMIP Profiles Define what any implementation of the specification must

adhere to in order to claim conformance to the specification

1. Define the use of KMIP objects, attributes, operations, message elements and authentication methods within specific contexts of KMIP server and client interaction.

2. Define a set of normative constraints for employing KMIP within a particular environment or context of use.

3. Optionally, require the use of specific KMIP functionality or in other respects define the processing rules to be followed by profile actors.

Examples of KMIP profiles Secret data Symmetric key store Symmetric key foundry

Profiles are further qualified by authentication suite TLS V1.0 / V1.1 TLS V1.2

Page 17: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

17

KMIP Usage Guide

Provides detailed guidance on how to implement KMIP functionality, including such topics as:

Key states and times Using KMIP templates Using vendor-specific extensions Using batch for multiple operations Canceling asynchronous operations

Page 18: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

18

New Challenges in Key Management

Page 19: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Business & IT are evolving rapidly…

19

Page 20: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Cloud Service Provider

App Data

Enterprise IT

Key Server

HSM

Cloud Key ManagementApplication

Users CSPAdministrators

EnterpriseAdministrators

Enterprise App

Key DB

vSphere

20

Page 21: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Backup HSM and Key Archive

HSM With Multiple Partitions

Audit Log

Key Secure

Application + HSM with EKM Client Database + HSM with EKM Client

InitializationActivation

EKM Web Browser

Complex Enterprise Security Requirements

EKM• Centrally see all keys created and used

by HSM

• Stores and manages key attributes

• Centralized audit for compliance

21

Page 22: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

22

PGP Key Management

22

Page 23: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Quantum Key Distribution

23Raw key: True randomFinal key: Secure, secret, replicated, synchronised true random

QKD

Page 24: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Changes in the Threat Landscape

24

Nation state actors

PII, government, defense industrial base, IP rich organizations

Criminals

Petty criminals

Organized crime

Organized, sophisticated supply chains (PII, financial services, retail)

Unsophisticated

Non-state actors

TerroristsAnti-establishment

vigilantes“Hacktivists”Targets of opportunity

PII, Government, critical infrastructure

Page 25: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

25

Addressing the New Challenges in Key Management

Page 26: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Use Cases• Define user stories and sequence for both existing and

new areas of functionalityEnhanced Protocol

• Provided objects, attributes and/or operations as needed for in-scope use cases

Testing Program• Establish formal and on-going program for KMIP

interoperability testingTest Cases

• Enhanced suite of test cases to support interoperability testing as well as protocol validation

Profiles• Establish simpler model for conformance, supported by

profile-specific test cases

KMIP V.Next

26

Page 27: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Cloud Service Provider

App Data

Enterprise IT

Key Server

HSM

Use Cases for Hybrid CloudApplication

Users CSPAdministrators

EnterpriseAdministrators

Enterprise App

Key DBvSphere

Use Cases

• Tenant administration

• Key migration

• Policy distribution

Implications

• Tenant granularity

• Key export/import

• Policy distribution

• Client registration

27

Page 28: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Divisional ApplicationsEnterprise IT

HSM

Use Cases for Hardware Security ModulesApplication

Users ApplicationAdministrators

HSMAdministrators

App Data

Divisional App

vSphere

Key Server

Key DB

Use Case

• Trust establishment

• Protection of keys in transit

Implications

• Devices types

• Vendor extensions28

Key Server

Key DB

Page 29: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Use Cases for PGP Keys

29

Use Cases

• User registration

• Key lookup

• Key signing

• Trust validation

Implications

• Key structures

• User identifiers

• Signature sets

29

Page 30: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

Use Cases for Quantum Key Distribution

30Server: Replicated, synchronised keys across domain boundariesClient: KMIP operations with key server in same domain

Use Case

• QKD trust establishment

Implications

• Stream objects, operations and attributes

Page 31: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

KMIP Interoperability Program KMIP conformance testing program

Design, implementation, management, measurement, and reporting

Test Specification Mentoring and Review Revision tracking Test environment architecture Test case specifics

Test Harness Development Mentoring and Review Revision tracking Delivery mechanisms Peer review and sign-off Website for access (per OASIS requirements) of test results

31

Page 32: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

New members welcome

32

interoperability DRIVE KMIP adoption

Be heard a) business reqs b) use cases

Grow global markets: bigger pie = BIGGER SLICE

Tap into the KMIP

brain trust

You belong here

Contribute to KMIP test cases and profiles

[email protected]

Page 33: 1 Addressing the New Complexities in Key Management Interoperability KMIP V.Next

33

Thank You!

https://[email protected]