Your SlideShare is downloading. ×
Security & Scaling at Microsoft
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Security & Scaling at Microsoft

251

Published on

Eric Mittelette and Stanisloas Quastano share stories of Microsoft Security and Scalability lessons learned at FailCon France 2012.

Eric Mittelette and Stanisloas Quastano share stories of Microsoft Security and Scalability lessons learned at FailCon France 2012.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
251
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Security & Software Disasters & changing perceptionEric Mittelette & Stanislas Quastana | Microsoft
  • 2. Do you remember those dark days ? May 4th 2000 July 13th 2001 September 28th 2001 January 25th 2003 August 13th 2003
  • 3. As Microsoft employees we do
  • 4. 15 minutes before SQL Slammer infection
  • 5. SQL Slammer (aka Sapphire) infection
  • 6. Blaster(aka LOVE YOU SAN)
  • 7. Why we fail ?
  • 8. Reason 1 : features,features, features….
  • 9. Reason 2 : Security wasnot in Developer’s DNA
  • 10. Reason 3 : Everything was installed and started by default Ex: IIS Web Server
  • 11. Which response ?
  • 12. “Computing is already an importantpart of many people’s lives. Withinten years, it will be an integral andindispensable part of almosteverything we do. Microsoft and thecomputer industry will only succeedin that world if CIOs, consumers andeveryone else sees that Microsofthas created a platform forTrustworthy Computing”
  • 13. “We have done a great job ofhaving teams work around theclock to deliver security fixes forany problems that arise.Our responsiveness has beenunmatched – but as an industryleader we can and must dobetter”
  • 14. “Flaws in a single Microsoftproduct, service or policy notonly affect the quality of ourplatform and services overall,but also our customers’ view ofus as a company”
  • 15. “So now, when we face a choicebetween adding features andresolving security issues, weneed to choose security”
  • 16. So what we did ?
  • 17. Stop all developmentThe 1st time in our history
  • 18. Every Microsoft developer : back to school !!!Mandatory annual security training
  • 19. « One book toprotect them all »
  • 20. Dear developersFew security bugsin your code= more money inyour pocket
  • 21. SDLC is theMicrosoftsecurity audit& expertisesubstancepublished as amethodology
  • 22. Security Team created
  • 23. Final Security Review mandatory
  • 24. Did it work ?First results
  • 25. Helping IT customers in their job
  • 26. As you see, we did a lot of things But…
  • 27. “Security is a journey,not a destination”
  • 28. 10 years laterIs it better ?
  • 29. “Security is a journey,not a destination”
  • 30. Sometimes it’s better to be the first…
  • 31. Security is an industry problem not a single company issue
  • 32. Really ?
  • 33. same feature but 10 years later
  • 34. “Security is a journey,not a destination”
  • 35. “Security is a journey,not a destination”
  • 36. Thanks you @EricMitt & @SQuastana

×