1 / 18

Windows Communication Foundation

Windows Communication Foundation. Security. Security?. Why do we need security? When we do need security? Is there any case when we do not need security?. WCF security features. Source: http://sanjevsharma.blogspot.com/2011/10/basics-of-wcf-security-part-i.html. Security methods.

sandys
Download Presentation

Windows Communication Foundation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Windows Communication Foundation Security

  2. Security? • Why do we need security? • When we do need security? • Is there any case when we do not need security?

  3. WCF security features Source:http://sanjevsharma.blogspot.com/2011/10/basics-of-wcf-security-part-i.html

  4. Security methods • Authentication • Transfer security • Authorization • Security auditing

  5. WCF Authentication • No authentication • Windows authentication • Username & password • X509 Certificate • Custom mechanism • Issued token

  6. No authentication Source: http://cs430.files.wordpress.com/2011/07/please-rob-me.png

  7. Windows authentication • Use windows user credentials for authentication TransportClientCredentialType = Windows

  8. Username & password • Username & password in SQL Database • Credentials managed by IIS

  9. X509 Certificate Security relies on private and public keys provided by certificates. • Certificate Authority (CA) • Certificate signed by CA (for Server and Client)

  10. Custom mechanism Can implement a custom authentication mechanism. i.e: • Custom Username and Password validator • Complex multi-certificate layered authentication

  11. Issued Token • Token - Unique identificator for every user • It's easy to generate tokens. • Token is only for identification.

  12. WCF Authorization • Credentials store • Callers => logical roles • Roles => operations • Callers => operations • Windows groups & accounts • ASP.NET Provider

  13. WCF Transfer security • Transfer Security Modes • None transfer security mode • Transport security • Message security • Mixed transfer security • Both transfer security

  14. Transport security Point-to-point Source: http://i.msdn.microsoft.com/dynimg/IC227287.png

  15. Message security End-to-end Source: http://i.msdn.microsoft.com/dynimg/IC227288.png

  16. Binding security levels

  17. Security auditing The security risks will always remain. • Use event logging • Authentication • Authorization ServiceSecurityAuditBehavior Source: http://www.the-it-department.co.uk/security-audit.html

  18. Tänan kuulamast Küsimusi?

More Related