encryption - Need help implementing key management scheme -
scheme has following requirements
- client application should perform encryption/decryption using component 1, component 2 , zpk (zone pin key. client should key host in encrypted form).
- host application should perform encryption/decryption using key mk (master key formed component 1 , component 2) , zpk.
here how i'm generating components
online-auth>gc enter lmk id [0-2]: 0 enter key length [1,2,3]: 2 enter key type: 002 enter key scheme: u clear component: **** **** **** **** **** **** **** **** encrypted component: uxxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx key check value: xxxxxx online-auth>gc enter lmk id [0-2]: 0 enter key length [1,2,3]: 2 enter key type: 002 enter key scheme: u clear component: **** **** **** **** **** **** **** **** encrypted component: uyyyy yyyy yyyy yyyy yyyy yyyy yyyy yyyy key check value: yyyyyy online-auth>fk enter lmk id [0-2]: 0 enter key length [1,2,3]: 2 enter key type: 002 enter key scheme: u enter component type [x,h,t,e,s]: e enter number of components [1-9]: 2 enter component 1: uxxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx component 1 check value: xxxxxx continue? [y/n]: y enter component 2: uyyyy yyyy yyyy yyyy yyyy yyyy yyyy yyyy component 2 check value: yyyyyy continue? [y/n]: y encrypted key: uzzzz zzzz zzzz zzzz zzzz zzzz zzzz zzzz key check value: zzzzzz
what don’t understand is
- what benefits of creating mk using enciphered components how decrypt enciphered zpk component 1 , component 2.
- what relation between component 1, component 2 , output of fk command
- is encrypting pin block under zpk enough/ubiquitous
any appreciated. ps want stick ubiquitous implementations.
you not first :)
i try explain (but english not clear enough :( ).
hsm never works plain keys, keys processing, encrypted under other, called key encryption key (kek), keys. lmk kek securely stored in secure environment, hsm. main idea of hsm is, can not real lmk key value, respectively, can not real working key plain value. keys using hsm cryptograms. lmk personal kek not accessible other parties (what means secure kek). these keys should keep in database use own hsm.
sometimes, need transmit keys other parties, eg, visa or mastercard exchange encrypted data pin-blocks. in case should use kek called zmk. transport key used other key exchange. unable use zmk encrypted keys hsm. first, must import key under lmk make managanbe.
conclusion:
1) should keep in db keys under lmk
2) keys under zmk used transmitted other parties.
if not clear enough pls not hesitate ask, try find explanation.
Comments
Post a Comment