Key Management Interoperability Protocol Specification Version 1.1

More documents

Recommendations

Info

800801802803804805806807808809810811812813814815Usage for processing cryptographically-protected data (e.g., decryption, verification, etc.) is not limited.The Usage Limits attribute has the three following fields: Usage Limits Total – the total number of Usage Limits Units allowed to be protected. This is thetotal value for the entire life of the object and SHALL NOT be changed once the object begins tobe used for applying cryptographic protection. Usage Limits Count – the currently remaining number of Usage Limits Units allowed to beprotected by the object. Usage Limits Unit – The type of quantity for which this structure specifies a usage limit (e.g., byte,object).When the attribute is initially set (usually during object creation or registration), the Usage Limits Count isset to the Usage Limits Total value allowed for the useful life of the object, and are decremented when theobject is used. The server SHALL ignore the Usage Limits Count value if the attribute is specified in anoperation that creates a new object. Changes made via the Modify Attribute operation reflect correctionsto the Usage Limits Total value, but they SHALL NOT be changed once the Usage Limits Count valuehas changed by a Get Usage Allocation operation. The Usage Limits Count value SHALL NOT be set ormodified by the client via the Add Attribute or Modify Attribute operations.Usage LimitsObject Encoding REQUIREDStructureUsage Limits Total Long Integer YesUsage Limits Count Long Integer YesUsage Limits UnitEnumeration, see9.1.3.2.31Yes816Table 83: Usage Limits Attribute StructureSHALL always have avalueInitially set byModifiable by serverModifiable by clientDeletable by clientMultiple instancespermittedWhen implicitly setApplies to Object TypesNoServer (Total, Count, andUnit) or Client (Total and/orUnit only)YesYes (Total and/or Unit only,as long as Get UsageAllocation has not beenperformed)Yes, as long as Get UsageAllocation has not beenperformedNoCreate, Create Key Pair,Register, Derive Key, Rekey,Re-key Key Pair, GetUsage AllocationKeys, Templates817Table 84: Usage Limits Attribute Ruleskmip-spec-v1.1-cos01 21 September 2012Standards Track Work Product Copyright © OASIS Open 2012. All Rights Reserved. Page 50 of 164
8188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648653.22 StateThis attribute is an indication of the State of an object as known to the key management server. The StateSHALL NOT be changed by using the Modify Attribute operation on this attribute. The state SHALL onlybe changed by the server as a part of other operations or other server processes. An object SHALL be inone of the following states at any given time. (Note: These states correspond to those described in[SP800-57-1]).Figure 1: Cryptographic Object States and TransitionsPre-Active: The object exists but is not yet usable forany cryptographic purpose.Active: The object MAY be used for all cryptographicpurposes that are allowed by its Cryptographic UsageMask attribute and, if applicable, by its Process StartDate (see 3.25) and Protect Stop Date (see 3.26)attributes.Deactivated: The object SHALL NOT be used forapplying cryptographic protection (e.g., encryption orsigning), but, if permitted by the Cryptographic UsageMask attribute, then the object MAY be used toprocess cryptographically-protected information (e.g.,decryption or verification), but only underextraordinary circumstances and when specialpermission is granted.Compromised: It is possible that the object has beencompromised, and SHOULD only be used to processcryptographically-protected information in a client thatis trusted to use managed objects that have beencompromised.Destroyed: The object is no longer usable for anypurpose.Destroyed Compromised: The object is no longer usable for any purpose; however itscompromised status MAY be retained for audit or security purposes.State transitions occur as follows:1. The transition from a non-existent key to the Pre-Active state is caused by the creation of theobject. When an object is created or registered, it automatically goes from non-existent to Pre-Active. If, however, the operation that creates or registers the object contains an Activation Datethat has already occurred, then the state immediately transitions from Pre-Active to Active. In thiscase, the server SHALL set the Activation Date attribute to the value specified in the request, orfail the request attempting to create or register the object, depending on server policy. If theoperation contains an Activation Date attribute that is in the future, or contains no Activation Date,then the Cryptographic Object is initialized in the key management system in the Pre-Active state.2. The transition from Pre-Active to Destroyed is caused by a client issuing a Destroy operation. Theserver destroys the object when (and if) server policy dictates.3. The transition from Pre-Active to Compromised is caused by a client issuing a Revoke operationwith a Revocation Reason of Compromised.4. The transition from Pre-Active to Active SHALL occur in one of three ways:The Activation Date is reached.Pre-Active2 3Active7 8DeactivatedDestroyedCompromisedDestroyedCompromisedA client successfully issues a Modify Attribute operation, modifying the Activation Date to adate in the past, or the current date.1461059kmip-spec-v1.1-cos01 21 September 2012Standards Track Work Product Copyright © OASIS Open 2012. All Rights Reserved. Page 51 of 164
Page 1 and 2: Key Management InteroperabilityProt
Page 3 and 4: NoticesCopyright © OASIS Open 2012
Page 5 and 6: 3.18.1 Operations outside of operat
Page 7 and 8: 11.8 Certify ......................
Page 9: sanction to perform a security func
Page 13 and 14: 11411511611711811912012112212312412
Page 15 and 16: 18818919019119219319419519619719819
Page 17 and 18: 23723823924024124224324424524624724
Page 19 and 20: 28628728828929029129229329429529629
Page 21 and 22: Value SHALL be TTLVencoded.32632732
Page 23 and 24: Object Encoding REQUIREDKey Materia
Page 25 and 26: 3763773782.1.7.11 Transparent ECDH
Page 27 and 28: Object Encoding REQUIREDSymmetric K
Page 29 and 30: 47447547647747847948048148248348448
Page 31 and 32: 50150250350450550650750850951051151
Page 33 and 34: SHALL always have a valueInitially
Page 35 and 36: 558559key contained within the Cert
Page 37 and 38: 577578579580581582583584585586X9, I
Page 39 and 40: 609Table 56: X.509 Certificate Iden
Page 45 and 46: 71571671771871972072172272372472572
Page 47 and 48: Default Operation Policy for Privat
Page 49: SHALL always have a valueInitially
Page 53 and 54: 892893object is destroyed. This att
Page 57 and 58: 944945946indicates when the key man
Page 59 and 60: 9709719729733.34 FreshThe Fresh att
Page 61 and 62: Application SpecificInformationObje
Page 65 and 66: Request PayloadObject REQUIRED Desc
Page 67 and 68: Attribute REQUIRED SHALL contain th
Page 69 and 70: 1152115311541155115611571158As a re
Page 71 and 72: AttributePrivate Key UniqueIdentifi
Page 73 and 74: management server.11941195119611971
Page 75 and 76: 12361237123812391240124112421243124
Page 77 and 78: 12881289129012911292129312941295129
Page 79 and 80: 13241325132613271328132913301331133
Page 83 and 84: Response PayloadObject REQUIRED Des
Page 87 and 88: Response PayloadObject REQUIRED Des
Page 89 and 90: 15371538153915401541154215431544154
Page 91 and 92: 1588158915901591159215931594a list
Page 93 and 94: 16231624162516261627162816291630163
Page 95 and 96: 16651666166716681669167016711672167
Page 97 and 98: 17211722172317241725172617271728172
Page 99 and 100: Option17911792179317941795Table 201
Page 101 and 102:
Request Batch ItemObject REQUIRED i
Page 103 and 104:
18311832183318341835183618371838183
Page 105 and 106:
18811882188318841885188618871888188
Page 107 and 108:
ObjectTagTag ValueCertificate Subje
Page 109 and 110:
ObjectPadding Methodkmip-spec-v1.1-
Page 111 and 112:
TagObjectTag ValueExtension Type420
Page 113 and 114:
19379.1.3.2.4 Wrapping Method Enume
Page 115 and 116:
19469.1.3.2.8 Split Key Method Enum
Page 117 and 118:
RC4 00000016RC5 00000017SKIPJACK 00
Page 119 and 120:
19649.1.3.2.17 Key Role Type Enumer
Page 121 and 122:
19759.1.3.2.21 Derivation Method En
Page 123 and 124:
19879.1.3.2.27 Operation Enumeratio
Page 125 and 126:
19939.1.3.2.30 Batch Error Continua
Page 127 and 128:
200820092010201110 TransportKMIP Se
Page 129 and 130:
Operation Failed20172018Table 249:
Page 131 and 132:
202411.5 Re-keyError Definition Res
Page 133 and 134:
203011.8 CertifyError Definition Re
Page 135 and 136:
Key Wrapping Specification contains
Page 137 and 138:
205011.18 Obtain LeaseError Definit
Page 139 and 140:
a certificate listOne or more of th
Page 141 and 142:
20952096209720982099210021012102210
Page 143 and 144:
CertificateSymmetric KeyPublic KeyP
Page 145 and 146:
22092210Appendix C. Tag Cross-Refer
Page 147 and 148:
Object Defined Type NotesInitializa
Page 149 and 150:
Object Defined Type NotesResult Mes
Page 151 and 152:
221322142215Appendix D. Operations
Page 153 and 154:
22192220222122222223222422252226222
Page 155 and 156:
22932294229522962297229822992300230
Page 157 and 158:
23482349235023512352235323542355235
Page 159 and 160:
24322433243424352436243724382439244
Page 161 and 162:
25162517251825192520252125222523252
Page 163 and 164:
2591Appendix G. Revision HistoryRev
show all

Key Management Interoperability Protocol Specification Version 1.1

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?