1. Secure Windows App Development

4. Authentication

5. ******** username

7. ******** username

8. Users sign in from any device using their existing username/password. 1 Users must also authenticate using their phone or mobile device before access is granted. 2 User Apps Microsoft Azure Active Directory Multi-Factor Authentication Server https://channel9.msdn.com/Events/ Microsoft-Azure/AzureCon-2015/ACON312

9. Introducing Microsoft Passport and Windows Hello

11. During OOBE setup

12. 1. Validate if the user has set up a PIN, and optionally Windows Hello, on their device KeyCredentialManager.IsSupportedAsync 2. Create CredentialKey and attestation KeyCredentialManager.RequestCreateAsync 3. Register public key, attestation and user information with the server for validation on login

13. 37451

14. Microsoft Passport and Windows Hello

15. Securing data in flight

16. Client/server Web services

19. More control over validation Can validate certificate chain Custom logic for multiple domains/root CAs

21. SSL Pinning

23. API https://channel9.msdn.com/events/ Microsoft-Azure/AzureCon-2015/ACON313

24. Securing data at rest

26. var vault = new Windows.Security.Credentials.PasswordVault(); vault.Add(new Windows.Security.Credentials.PasswordCredential("My App", username, password));

32. © 2015 Microsoft Corporation. All rights reserved. Microsoft, Windows 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.