![]() The provide a very efficient solution that will avoid the problems that Caballo is having, and also elminate the performance overhead that software encryption runs into. This is why I think in the future you are going to see SEDs (spinning media or solid state) being so important. It is evident that the case-in-point from Caballo is a software implementation. The host-side computer has to do the decryption AFTER the read operation.įor the most recent versions of Windows (server and desktop), BitLocker can do either one (hardware or software). If you are doing software encryption, when you are reading from the disk, the data is encrypted when read. ![]() For hardware-encrypted SEDs, on the other hand, all of the encryption happens in the drive, so CPU impact is pretty much zero. Not very fun! If you are doing software encryption, by definition, the encryption is happening on the host side. For example, in a notebook or desktop system, software encryption will rob you of roughly 15% to 20% of your IO bandwidth. Well, "vary greatly" could include systems where the encryption process can be handled with little impact to IOs, all the way to systems where the impact is quite measurable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |