Determine if there are alternative ways to deploy AD to ensure compliance with InCommon Bronze and Silver. If there are, develop an Alternate Means Proposal for the set of practices identified (which may be some form of the Cookbook) and submit to InCommon for review. If the risks addressed by the profiles cannot be mitigated adequately using AD, develop community and specification recommendations for next steps.
There are two primary dimensions to selecting a scope for this effort:
Active Directory Products
The most pressing use cases for many campuses are related to their dependence on Active Directory - Domain Services (AD-DS) in various ways within their IdMS. Based on this, the following use cases have been prioritized:
- Windows 2008R2 AD-DS used as the verifier for the IdP
- Windows 2008R2 AD-DS storing a provisioned copy of the credentials but not acting as the IdP's verifier
For each of these cases, AD-DS may be an on-premise deployment or be hosted by a service provider.
A review of IAP v1.2 indicated the following requirements should be in scope because they apply to the use cases listed above and AD-DS may have special challenges meeting the requirements:
- 22.214.171.124 - Stored authentication secrets (S). Challenges related to use of Approved Algorithms.
- 126.96.36.199 - Basic protection of authentication secrets (B).
- 188.8.131.52 - Strong protection of authentications secrets (S). Challenges related to use of Protected Channel.
- 184.108.40.206 - Resist replay attack (B, S).
- 220.127.116.11 - Resist eavesdropper attack (B, S).
- 18.104.22.168.1 - Network Security (S). Challenges related to use of Protected Channel.