Hierarchical Key Rotation. Should I rotate the lowest level keys? Ultimately, your DEK is the critical one - if someone has your data and your DEK then it is game over Moreover, if someone has access to your data and the DEK then rotating all the other keys won't matter Still, only you can decide whether or not it is worth the effort to rotate the DEK Hence the question: what is your threat model?
How do SED drives generate the DEK? - Information Security Stack Exchange The DEK is used to encrypt all content on the drive In the case the drive needs to be securely wiped, the DEK can simply be erased, regardless of whether or not the AK is set According to the TCG, the DEK is generated on the drive itself, rather than being generated on the computer and transferred over through some vendor-specific ATA command:
encryption - Why not use the KEK directly to encrypt data . . . The DEK never changes: you don't want to re-encrypt every single file, so you don't change the DEK You may want to change the KEK: if your KEK expires, got compromised, or you transfer ownership of the data to someone, you can re-encrypt the DEK with another key
cryptography - Exchange of DEK and KEK (encryption keys) between app . . . To make the system more secure, instead of storing DEK in plain text in the app server, it is stored in encrypted form (en_dek) in the app server The key to encrypt the DEK is stored in a totally separate server and is called the Key Encryption Key (KEK)
How encryption decryption of RSA private key by passphrase works? What I don't understand is that number string behind the algorithm type info- 225AAFE1E579A5E38EC1C7F479C5F877 The similar one but shorter was present also in DEK-Info header of the key which had DES What are these numbers? Is the passphrase digested to the key in some standard way? Is it different for every algorithm used?
How to process or manage Key-Encryption-Key using HSM? Data Encryption Key will be decrypted using KEK Based on the above concept, my doubts are: Do we need to send the Encrypted DEK to the HSM for decrypting it or Do we need to decrypt the KEK and retrieve it from HSM ? I just want to know the key encryption and decryption process flow, while using HSM Also provide any helpful links
Is it Secure to Use a Single AES-GCM Encryption Key for an Entire . . . A better option is to have two keys: A data encryption key (DEK) which encrypts the data and a key encryption key (KEK) which encrypts the DEK When you rotate the KEK, you only have to re-encrypt the DEK, not all data For rotating the DEK, assign a unique ID to each key and store this ID together with the ciphertext
Thales HSM: relationship between the various key types? I am going through the Thales HSM manuals, and frankly the key acronyms are driving me crazy I would like to understand the differences between the following keys, and how they relate to one anoth
Checking if an RSA private key is passphrase protected The 'legacy' (OpenSSL) unencrypted format does start with MII (which is 30 82, the first two octets of all reasonable-sized ASN 1 DER SEQUENCEs, and encrypted does not, but they are also distinguished by the Proc-type and DEK-info lines which are much more obvious