BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] NAS: encryption
- Subject: [Discuss] NAS: encryption
- From: warlord at MIT.EDU (Derek Atkins)
- Date: Thu, 09 Jul 2015 09:55:13 -0400
- In-reply-to: <559D3884.7010505@gmail.com> (Richard Pieri's message of "Wed, 8 Jul 2015 10:49:40 -0400")
- References: <5596D8DA.2000201@gmail.com> <55980A9F.4020007@gmail.com> <BY1PR0401MB1641117906253C39D8075681DC940@BY1PR0401MB1641.namprd04.prod.outlook.com> <sjmd203evpz.fsf@securerf.ihtfp.org> <CAFv2jcba50_Kw9V-p7brmeJ5Fk=9rzeQRLRzBUVRK8uZ71wZNA@mail.gmail.com> <BY1PR0401MB164127DEA53006B9692DC60CDC920@BY1PR0401MB1641.namprd04.prod.outlook.com> <3d14590da6e6f0bd76b8e75496117136.squirrel@mail.mohawksoft.com> <559D3884.7010505@gmail.com>
Richard Pieri <richard.pieri at gmail.com> writes: > On 7/8/2015 10:23 AM, markw at mohawksoft.com wrote: >> The problem with internal drive encryption is getting any level of >> disclosure and accountability. > > This is simply not true. > > FIPS security profiles are public record. Here's the security profile > for the cryptographic module used in several of Seagate's enterprise > SEDs: The problem with FIPS certification (and I know this first hand, having been involved in multiple FIPS certifications over the past year) is that all the cert tells you is "yes, the AES algorithm is implemented correctly" and "yes, the FIPS core performs correctly". However..... (and this is the big gotcha)... the certification does not talk about HOW the crypto is used! For example, if you're running disk encryption the *crypto* can be fully FIPS compliant, but it could still do something stupid with the FIPS-certified crypto. For example, it could be using ECB mode instead of some chaining mode. Or it could somehow store the keys in an unprotected mode. Basically, FIPS only talks about what's inside the FIPS boundary, but the system as a whole is always much larger than just the FIPS boundary. As I said before, when using the disk's onboard encryption it is unlikely that you could externally verify that the disk is actually encrypting the data properly, unless the disk actually gives you the encrypted content when the crypto is not initialized. I have no idea if this is how it works; my understanding was that if the disk is encrypted then it wont give you any data without keys. I.e., you cannot verify the encryption is correct. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord at MIT.EDU PGP key available
- Follow-Ups:
- [Discuss] NAS: encryption
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] NAS: encryption
- References:
- [Discuss] NAS: buy vs. build
- From: tmetro+blu at gmail.com (Tom Metro)
- [Discuss] NAS: encryption
- From: tmetro+blu at gmail.com (Tom Metro)
- [Discuss] NAS: encryption
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] NAS: encryption
- From: warlord at MIT.EDU (Derek Atkins)
- [Discuss] NAS: encryption
- From: abreauj at gmail.com (John Abreau)
- [Discuss] NAS: encryption
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] NAS: encryption
- From: markw at mohawksoft.com (markw at mohawksoft.com)
- [Discuss] NAS: encryption
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] NAS: buy vs. build
- Prev by Date: [Discuss] NAS: encryption
- Next by Date: [Discuss] NAS: encryption
- Previous by thread: [Discuss] NAS: encryption
- Next by thread: [Discuss] NAS: encryption
- Index(es):