OWASP AppSec DC 2012/SharePoint Security 101 - Revision history

Mark.bristow at 18:33, 25 March 2012

2012-03-25T18:33:36Z

Mark.bristow at 01:01, 12 March 2012

2012-03-12T01:01:03Z

Mark.bristow: Created page with "{{:OWASP AppSec DC 2012 Header}} NOTOC == The Presentation == rightSharePoint is big, very big. In fact, it is one..."

2012-03-02T20:55:04Z

Created page with "<noinclude>{{:OWASP AppSec DC 2012 Header}}</noinclude> __NOTOC__ == The Presentation == rightSharePoint is big, very big. In fact, it is one..."

New page

<noinclude>{{:OWASP AppSec DC 2012 Header}}</noinclude>
__NOTOC__
== The Presentation ==
[[Image:Owasp_logo_normal.jpg|right]]SharePoint is big, very big. In fact, it is one of the fastest growing products in Microsofts history, achieving more than a billion in revenue in 2009. This represents a 30% year-over-year growth. As one analyst ominously described, ÐSharePoint is like a virus growing inside the organization.Ó But the real question is this: How did Microsoft take into account security when building SharePoint? Given Microsofts spotty record in security, when it comes to SharePoint, Britney may have summarized it best: ÐOoops, I did it again.Ó This talk will: - Highlight common SharePoint use cases and their key security issues. - Prescribe the mitigation steps every enterprise should take minimize the odds of a breach.
== The Speakers ==
Rob Rachwald, Amichai Shulman and Noa Bar-Yosef
<noinclude>{{:OWASP AppSec DC 2012 Footer}}</noinclude>

@@ Line 2: / Line 2: @@
 __NOTOC__
 == The Presentation  ==
-SharePoint is big, very big.  In fact, it is one of the fastest growing products in Microsofts history, achieving more than a billion in revenue in 2009.  This represents a 30% year-over-year growth.  As one analyst ominously described, _SharePoint is like a virus growing inside the organization.Ó  But the real question is this:  How did Microsoft take into account security when building SharePoint?  Given Microsofts spotty record in security, when it comes to SharePoint, Britney may have summarized it best: _Ooops, I did it again.Ó This talk will: - Highlight common SharePoint use cases and their key security issues. - Prescribe the mitigation steps every enterprise should take minimize the odds of a breach.
+SharePoint is big, very big.  In fact, it is one of the fastest growing products in Microsoft's history, achieving more than a billion in revenue in 2009.  This represents a 30% year-over-year growth.  As one analyst ominously described, _SharePoint is like a virus growing inside the organization.'  But the real question is this:  How did Microsoft take into account security when building SharePoint?  Given Microsoft's spotty record in security, when it comes to SharePoint, Britney may have summarized it best: _Ooops, I did it again.' This talk will: - Highlight common SharePoint use cases and their key security issues. - Prescribe the mitigation steps every enterprise should take minimize the odds of a breach.
 == The Speakers  ==
 <table>
 <tr>
 <td>
 ===Rob Rachwald===
 [[Image:AppSecDC12-Rob_Rachwald.jpg|left]]Bio TBA
 </td>
 </tr>
 </table>
 <noinclude>{{:OWASP AppSec DC 2012 Footer}}</noinclude>

OWASP AppSec DC 2012/SharePoint Security 101 - Revision history

Mark.bristow at 18:33, 25 March 2012

Mark.bristow at 01:01, 12 March 2012

Mark.bristow: Created page with "{{:OWASP AppSec DC 2012 Header}} __NOTOC__ == The Presentation == rightSharePoint is big, very big. In fact, it is one..."

Mark.bristow: Created page with "{{:OWASP AppSec DC 2012 Header}} NOTOC == The Presentation == rightSharePoint is big, very big. In fact, it is one..."