Skip to Content.
Sympa Menu

ad-assurance - RE: [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

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


Chronological Thread 
  • From: "Capehart,Jeffrey D" <>
  • To: "" <>
  • Subject: RE: [AD-Assurance] Alternative Means for Satisfying Requirements 4.2.5.1 4.2.5.2, and 4.2.8.2.1
  • Date: Fri, 12 Apr 2013 00:02:16 +0000
  • Accept-language: en-US
  • Authentication-results: sfpop-ironport01.merit.edu; dkim=neutral (message not signed) header.i=none

Nicely written up, David!

 

You may want to do a quick review of the IAP criteria section numbers to make sure they are represented consistently and accurately throughout the page.

Jeff

 

From: [mailto:] On Behalf Of David Walker
Sent: Thursday, April 11, 2013 5:15 PM
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

 

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


Archive powered by MHonArc 2.6.16.

Top of Page