1 NIST Key State Models SP Part 1SP (Draft)
2 KMIP Key Role Types Key Role Type 1.1 Key Role Type KMIP NameDescriptionValue BDKBase Derivation Key CVKCard Verification Key DEKData Encryption Key MKACApplication Cryptograms MKSMCSecure Messaging for Confidentiality MKSMISecure Messaging for Integrity MKDACData Authentication Code MKDNDynamic Numbers MKCPCard Personalization MKOTHOther A KEKKey Encryption or Wrapping Key B 16609ISO MAC Algorithm C 97971ISO MAC Algorithm D 97972ISO MAC Algorithm E 97973ISO MAC Algorithm F 97974ISO MAC Algorithm ISO MAC Algorithm ZPKPIN Block Encryption Key PVKIBMPIN Verification Key, IBM PVKPVVPIN Verification Key, Visa PVV PVKOTHPIN Verification Key, Other ExtensionsFuture or Vendor Specific Use8XXXXXXX Proposal for 1.2 Key Role Type KMIP NameDescriptionValue BDKBase Derivation Key CVKCard Verification Key DEKData Encryption MKACApplication cryptograms MKSMCSecure Messaging for Confidentiality MKSMISecure Messaging for Integrity MKDACData Authentication Code MKDNDynamic Numbers MKCPCard Personalization MKOTHOther A KEKKey Encryption or wrapping B 16609ISO MAC algorithm C 97971ISO MAC Algorithm D 97972ISO MAC Algorithm E 97973ISO MAC Algorithm F 97974ISO MAC Algorithm ISO MAC Algorithm ZPKPIN Encryption PVKIBMPIN verification, IBM PVKPVVPIN Verification, VISA PVV PVKOTHPIN verification, KPV, other algorithm DUKPTDUKPT Initial Key (also known as IPEK) IVInitialization Vector (IV) KBPKTR-31 Key Block Protection Key ExtensionsFuture or Vendor Specific Use8XXXXXXX
3 KMIP Profiles Purpose is to define what any implementation of the specification must adhere to in order to claim conformance Define the use of KMIP objects, attributes, operations, message elements and authentication methods within specific contexts of KMIP server and client interaction Define a set of normative constraints for employing KMIP within a particular environment or context of use Optionally, require the use of specific KMIP functionality or in other respects define the processing rules to be followed by profile actors (e.g. Server & Client) Defined OASIS Profiles Profiles are further qualified by authentication suite TLS V1.0 / V1.1 / V1.2 or similar External Profile in development – (Not OASIS developed) INCITS T10 profile – Fibre Channel Security Protocol v2.0 (FCSP2)
4 Defining Profiles Server requirements (required) Includes all objects, operations and attributes that a client can access Defined down to all required components of those objects, operations and attributes Even if optional in KMIP specification, it can be required in a profile Definition of any extensions and how they are to be used Client requirements (optional) What are the bare minimum requirements for a Client to claim conformance e.g. Must support get of a symmetric key using unique identifier Can be a single statement Basically states that support of any operation, object and attributes that are supported by the server and you can be conformant Protocol requirements (recommended) Wire protocol KMIP messaging uses (e.g. SSL 3.0, TLS v1.2, FCSP, etc…) Authentication requirements (recommended) Certificates, user ID/password, mutual authentication, DH-CHAP, etc… Interoperability Requirements (recommended) How to prove conformance either as part of the profile or as a separate Test Case guide Use Cases (recommended) How objects, operations and attributes are to be used with message examples