ad-assurance - [AD-Assurance] Alternative Means for Satisfying Requirements 4.2.5.1 4.2.5.2, and 4.2.8.2.1

Subject: Meeting the InCommon Assurance profile criteria using Active Directory

List archive

[AD-Assurance] Alternative Means for Satisfying Requirements 4.2.5.1 4.2.5.2, and 4.2.8.2.1

From: David Walker <>
To:
Cc: DHW <>
Subject: [AD-Assurance] Alternative Means for Satisfying Requirements 4.2.5.1 4.2.5.2, and 4.2.8.2.1
Date: Thu, 11 Apr 2013 14:15:09 -0700
Authentication-results: sfpop-ironport05.merit.edu; dkim=pass (signature verified)

Everyone,

As mentioned in last week's call, I've modify Ron's alternative means statement for sections 4.2.5.1, 4.2.5.2, and 4.2.8.2.1 to include the more general reasoning I had drafted earlier about using monitoring to comply with technical requirements that have an implicit assumption of "correct" end-user behavior. The result is in a wiki page at:

https://spaces.internet2.edu/x/FoFHAg

This is a subpage of our "Restricted Working Group Documents" page; I've also moved my more general statement there so that people looking over our shoulders don't think it's a direction we're taking.

David

[AD-Assurance] Alternative Means for Satisfying Requirements 4.2.5.1 4.2.5.2, and 4.2.8.2.1, David Walker, 04/11/2013
- RE: [AD-Assurance] Alternative Means for Satisfying Requirements 4.2.5.1 4.2.5.2, and 4.2.8.2.1, Capehart,Jeffrey D, 04/11/2013
  - Re: [AD-Assurance] Alternative Means for Satisfying Requirements 4.2.5.1 4.2.5.2, and 4.2.8.2.1, David Walker, 04/12/2013

List archive

[AD-Assurance] Alternative Means for Satisfying Requirements 4.2.5.1 4.2.5.2, and 4.2.8.2.1