https://wiki.owasp.org/index.php?action=history&feed=atom&title=SQL_Server_Forensics_2.0SQL Server Forensics 2.0 - Revision history2026-04-10T19:08:56ZRevision history for this page on the wikiMediaWiki 1.27.2https://wiki.owasp.org/index.php?title=SQL_Server_Forensics_2.0&diff=66475&oldid=prevDhruvsoi at 06:53, 24 July 20092009-07-24T06:53:58Z<p></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;' lang='en'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 06:53, 24 July 2009</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1" >Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>Many forensics investigations lead to the discovery that a SQL Server database might have been breached. If investigators cannot assess and qualify the scope of an intrusion, they may be forced to report it publicly – a disclosure that is painful for companies and customers alike. There is only one way to avoid this problem: Learn the skills needed to qualify and investigate SQL Server intrusions.</div></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>Many forensics investigations lead to the discovery that a SQL Server database might have been breached. If investigators cannot assess and qualify the scope of an intrusion, they may be forced to report it publicly – a disclosure that is painful for companies and customers alike. There is only one way to avoid this problem: Learn the skills needed to qualify and investigate SQL Server intrusions.</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del class="diffchange diffchange-inline"> </del></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>This session will provide you an overview of how to collect and preserve artifacts from the published and unpublished repositories of Microsoft SQL Server and how these artifacts can be analyzed to confirm or discount a database intrusion. We’ll also review techniques that can be used to qualify the actions that were performed by an unauthorized database user.</div></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>This session will provide you an overview of how to collect and preserve artifacts from the published and unpublished repositories of Microsoft SQL Server and how these artifacts can be analyzed to confirm or discount a database intrusion. We’ll also review techniques that can be used to qualify the actions that were performed by an unauthorized database user.</div></td></tr>
</table>Dhruvsoihttps://wiki.owasp.org/index.php?title=SQL_Server_Forensics_2.0&diff=66474&oldid=prevDhruvsoi: Created page with 'Many forensics investigations lead to the discovery that a SQL Server database might have been breached. If investigators cannot assess and qualify the scope of an intrusion, the…'2009-07-24T06:53:39Z<p>Created page with 'Many forensics investigations lead to the discovery that a SQL Server database might have been breached. If investigators cannot assess and qualify the scope of an intrusion, the…'</p>
<p><b>New page</b></p><div>Many forensics investigations lead to the discovery that a SQL Server database might have been breached. If investigators cannot assess and qualify the scope of an intrusion, they may be forced to report it publicly – a disclosure that is painful for companies and customers alike. There is only one way to avoid this problem: Learn the skills needed to qualify and investigate SQL Server intrusions.<br />
<br />
This session will provide you an overview of how to collect and preserve artifacts from the published and unpublished repositories of Microsoft SQL Server and how these artifacts can be analyzed to confirm or discount a database intrusion. We’ll also review techniques that can be used to qualify the actions that were performed by an unauthorized database user.</div>Dhruvsoi