ad-assurance - RE: [AD-Assurance] Microsoft Strategy / FICAM / Kantara
Subject: Meeting the InCommon Assurance profile criteria using Active Directory
List archive
- From: "Capehart,Jeffrey D" <>
- To: "" <>
- Subject: RE: [AD-Assurance] Microsoft Strategy / FICAM / Kantara
- Date: Tue, 7 May 2013 03:18:02 +0000
- Accept-language: en-US
- Authentication-results: sfpop-ironport02.merit.edu; dkim=neutral (message not signed) header.i=none
David, From Kantara, see
http://kantarainitiative.org/programs/iop-saml/ where the product or service for ADFS 2.0 is listed as “IDP Light”. There is also a note showing other protocols for ADFS are “WS-Federation”. Yes, I agree on SAML 2.0, but Kantara Initiative is supposed to meet similar SP800-63 requirements for LOA-2 just as InCommon Silver. If ADFS is being offered
as a SAML 2.0 interoperability product under IdP Lite, (similar to Shibboleth for SAML 2.0 under InCommon?) then would not the IdP be responsible as well to meet the requirements of protecting stored secrets, protected channels, and approved algorithms, regardless
of choice of interoperability (SAML 2.0)? Therefore shouldn’t Microsoft explain how to configure both ADFS and ADDS to meet the requirements? The table linked above has an entry for
ADFS that links to a Microsoft page with many further links. I’ve summarized a handful of links that I traversed through. AD FS 2.0 Content Map http://social.technet.microsoft.com/wiki/contents/articles/2735.ad-fs-2-0-content-map.aspx Interesting Q&A on ADFS.
http://blogs.technet.com/b/askds/ Question
In Windows 7 and Server 2008 Kerberos DES encryption is disabled by default. At what point will support for DES Kerberos encryption be removed? Does this happen in Windows 8 or Windows Server 2012, or will it happen
in a future version of Windows? Answer
DES is still available as an option on Windows 8 and Windows Server 2012, though it is disabled by default. It is too early to discuss the
availability of DES in future versions of Windows right now. There was an
Advisory Memorandum published in 2005 by the Committee on National Security Systems (CNSS) where DES and all DES-based systems (3DES, DES-X) would be retired for all US Government uses by 2015.
That memorandum, however, is not necessarily a binding document. It is expected that 3DES/DES-X will continue to be used in the private sector for the foreseeable future. I'm afraid that we can't completely eliminate DES right now. All we can do is push it to the back burner in favor of newer and better algorithms
like AES. Even more good stuff… Microsoft Security Intelligence Report (SIR) on Managing Risk and “Defending Against Pass the Hash”
also has some information that may be helpful for Alternative Means. http://www.microsoft.com/security/sir/strategy/default.aspx#!password_hashes For example:
“Microsoft has never provided an intentional way for any user to access stored credentials,
although several tools have been discovered that are designed to give attackers access to stored hashes, often using Local Security Authority (LSA) process injection. Even then, the tools require Local System, local Administrator, or domain Administrator account
level access to be successful—in other words, the attacker needs to have already compromised the computer or network before these tools can be used to harvest and use hashes.” And finally, from Microsoft Technet Ask Premier Field Engineering (PFE) Platforms:
“What can be used to keep Active Directory data secure?” With the increase in concern over data privacy and security, one of my customers recently asked about securing Active Directory data while stored
on disk and what could be done in relation to network traffic. My first thoughts were BitLocker and IPSEC. However, there are a number of different considerations that factor in. […] Jeff From: [mailto:]
On Behalf Of David Walker Jeff, On the question “Does Microsoft have a strategy for supporting compliance with the Federal Identity, Credential, and Access Management (FICAM) requirements at LoA-2? If so, what is the time frame?” |
- [AD-Assurance] Microsoft Strategy / FICAM / Kantara, Capehart,Jeffrey D, 05/06/2013
- Re: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, David Walker, 05/06/2013
- RE: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, Capehart,Jeffrey D, 05/06/2013
- Re: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, David Walker, 05/07/2013
- Re: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, Ann West, 05/07/2013
- RE: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, Capehart,Jeffrey D, 05/07/2013
- Re: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, David Walker, 05/07/2013
- RE: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, Capehart,Jeffrey D, 05/08/2013
- Re: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, Ann West, 05/08/2013
- Re: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, David Walker, 05/08/2013
- RE: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, Capehart,Jeffrey D, 05/08/2013
- Re: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, David Walker, 05/07/2013
- Re: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, David Walker, 05/07/2013
- RE: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, Capehart,Jeffrey D, 05/06/2013
- Re: [AD-Assurance] Microsoft Strategy / FICAM / Kantara, David Walker, 05/06/2013
Archive powered by MHonArc 2.6.16.