Take the 2-minute tour ×
Information Security Stack Exchange is a question and answer site for Information security professionals. It's 100% free, no registration required.

I'm configuring my relying party (a website) to use either ADFS or Azure ACS 2.0.

ADFS 2.0 has some interesting features such as Token Replay prevention (in the SQL version) and may have other SAML security features as well (which I may not understand)

Can someone distill the differences between ADFS and ACS security risks?

For example:

  • Is token replay handled differently in each?
  • Does the difference in protocol support increase or decrease security?
  • What is more secure OpenID, OAuth, SAML1 or SAML2, etc...
  • Is encryption and hashing done similarly?
  • How are key renewals done? (e.g. ADFS will refresh on an interval)
  • Can the home realm discovery page be disabled, customized as to not leak IDP's?
  • ...?
share|improve this question

2 Answers 2

up vote 5 down vote accepted

This is a great question. However, there are quite a few differences between ACS v2 and ADFS v2 from a risk perspective.

  1. ACS does not have an IdP, therefore it does not do any authentication, whereas ADFS does.
  2. As far as I understand it, ACS does not attempt to prevent token replays. It leaves that up to the IdP providing the original token, and the RP. I cannot definitevely say this is 100% true though as I can't find any documentation on it, but I'm working on a project to test this... will update with results.
  3. ACS supports 3 token types and protocols (WS-Fed, SAML 1.1/2.0, and SWT), whereas ADFS supports only 2 types (WS-Fed. SAML 1.1/2.0).
  4. ADFS supports custom attribute stores. ACS will only use claims within received tokens.

With all of that being said, I would argue that ACS and ADFS are more complimentary than anything. ACS works nicely as an endpoint for Azure/Cloud hosted applications, as it can be modified relatively easily to accept other IdP's. ADFS works well internally, but its a bit of a pain to add IdP trusts. This gives a security boundary between the application, the environment(cloud et al), and the organization internally.

EDIT: Follow up questions:

share|improve this answer
    
What would you compare ACS's "service identities" to? They permit a client to authenticate to ACS with a certificate, password, or PSK. Funny you mention token replays... it is this is what prompted me to ask this question. –  makerofthings7 Apr 11 '11 at 17:28
    
@makerofthings I should have been more specific... Service identities do allow for authn to ACS, but they are not designed for user authentication. –  Steve Apr 11 '11 at 17:45
    
ADFSv2 doesn't support the Service Identity feature of redirection for OAuth which is included in ACS more information... –  makerofthings7 May 11 '11 at 15:47
    
ACS supports OpenID whereas ADFS doesn't more information... –  makerofthings7 May 11 '11 at 15:49

By default, tokens can be replayed in the ACS unless the developer takes steps to protect against it.

See this Microsoft published list of security issues what a secure deployment should keep in mind when using ACS

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.