ad-assurance - Re: [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call
Subject: Meeting the InCommon Assurance profile criteria using Active Directory
List archive
- From: David Walker <>
- To:
- Subject: Re: [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call
- Date: Fri, 04 Oct 2013 15:02:01 -0700
On Fri, 2013-10-04 at 21:19 +0000, Capehart,Jeffrey D wrote:
It seems many of us originally thought the encryption was supposed to protect the password store in case the server got hacked. Do we need to explicitly state that is not the intent of this requirement? Yes, I think so. I would put it in our interpretation. The physical security and other controls (patching, limiting access, etc.), are already required as good practice. And yes, while it would be ideal that a hacker can’t steal your password database because it is encrypted, the system has to be able to read it somehow. And if the system can read it, then a hacker who can compromise the system can probably figure out how to do that too. So, from a technology standpoint, it is probably impossible to encrypt the data so that a compromised machine won’t expose the passwords. Having terrific physical security would tend to make an IT person think that Bitlocker is unnecessary and thus hard to convince to add it “just in case the server is lost/stolen”. Exactly. I suppose, in theory, that good enough physical security would be a compensation for weak storage encryption, but I'd need to see that argument put into practice before I'd agree to it. It would be necessary, for example, for that physical security to follow the disk clear to its destruction, not just while it was in use. That said, it does still seem like we are only requiring Bitlocker to meet the “Approved Algorithm” portion. In essence, encrypting the whole disk just to make sure the passwords are encrypted with an approved algorithm. If Microsoft thinks syskey provides the same level of protection (or better) than Bitlocker, maybe they could write up the alternative means statement. Somehow, though, I don’t think we will be reassured just because the algorithm is not published and therefore is “secure”. Yeah, I don't think they could make that case successfully. If they offer, we can let them propose something, but I wouldn't solicit it from them. -Jeff C. From: [mailto:] On Behalf Of David Walker
|
- [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call, David Walker, 10/04/2013
- RE: [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call, Michael W. Brogan, 10/04/2013
- Re: [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call, David Walker, 10/04/2013
- RE: [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call, Capehart,Jeffrey D, 10/04/2013
- RE: [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call, Michael W. Brogan, 10/04/2013
- Re: [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call, David Walker, 10/04/2013
- RE: [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call, Ron Thielen, 10/04/2013
- RE: [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call, Capehart,Jeffrey D, 10/04/2013
- Re: [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call, David Walker, 10/04/2013
- RE: [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call, Eric Goodman, 10/04/2013
- Re: [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call, David Walker, 10/04/2013
- RE: [AD-Assurance] Quick notes from the 10/4/2013 AD Assurance call, Michael W. Brogan, 10/04/2013
Archive powered by MHonArc 2.6.16.