1. Digital Signatures to support Trust Ronny Bjones Security Architect Microsoft Corporate www.oasis-open.org

2. Digital Signatures Scenarios n Code Signing n Integrity/Trust on a protocol level – many time invisible n Document signing (qualified or not) n Form signing n Claim-based Applications

3. Support Trust in Code n Code Signing l ActiveX l Kernel l Drivers l.Net Apps n Apps have an identity n Software Restriction Policies

4. Support Trust in Protocols n SSL/TLS Client authentication n s/mime signing n IPSec (IKE) n Kerberos PKINIT n …

5. Support Trust in Documents n Signing contract l Office Signature l XPS (XML Paper Specification) - WSIWYS n Patent requests

6. Support Trust in Workflows n XML Signatures (Embedded Signatures) n Document types don’t change in the workflow after signature n XAdES n Server side

7. Support Trust in Authentication & Authorization n Claim-based Applications n Identity Metasystem n Authentication/Authorization become policy-decisions

8. QuEST n Qualified Electronic Signatures Tutorial n Demystify Qualified Electronic signatures n Best practice/guidance for designing a Qualified Electronic signature solution http://tinyurl.com/8428q

9. © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.