<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: SQL 2008 one click database encryption gives a false sense of security</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/sql-server/sql-2008-one-click-database-encryption-gives-a-false-sense-of-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/sql-server/sql-2008-one-click-database-encryption-gives-a-false-sense-of-security/</link>
	<description></description>
	<pubDate>Mon, 23 Nov 2009 18:28:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Mrdenny</title>
		<link>http://itknowledgeexchange.techtarget.com/sql-server/sql-2008-one-click-database-encryption-gives-a-false-sense-of-security/#comment-81</link>
		<dc:creator>Mrdenny</dc:creator>
		<pubDate>Mon, 18 Aug 2008 14:42:08 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/sql-server/sql-2008-one-click-database-encryption-gives-a-false-sense-of-security/#comment-81</guid>
		<description>Brent,
Keeping in mind that I haven't had time to really beat on TDE that much.  But if your SAN admin took a snap of the LUN that the encrypted database was on, they probably also have a snap of the master database, and all the various keys which are stored in the master database, and the folder that the master database is sitting in.  They can probably just attach that database to another machine, fire it up with the old master database and have the system decrypt the database as all the keys are there.

(Again I haven't played with it to try this yet.)

If as a DBA you can't trust your SAN admin, you've got bigger problems than the SAN admin swiping the database.

Denny</description>
		<content:encoded><![CDATA[<p>Brent,<br />
Keeping in mind that I haven&#8217;t had time to really beat on TDE that much.  But if your SAN admin took a snap of the LUN that the encrypted database was on, they probably also have a snap of the master database, and all the various keys which are stored in the master database, and the folder that the master database is sitting in.  They can probably just attach that database to another machine, fire it up with the old master database and have the system decrypt the database as all the keys are there.</p>
<p>(Again I haven&#8217;t played with it to try this yet.)</p>
<p>If as a DBA you can&#8217;t trust your SAN admin, you&#8217;ve got bigger problems than the SAN admin swiping the database.</p>
<p>Denny</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BrentOzar</title>
		<link>http://itknowledgeexchange.techtarget.com/sql-server/sql-2008-one-click-database-encryption-gives-a-false-sense-of-security/#comment-80</link>
		<dc:creator>BrentOzar</dc:creator>
		<pubDate>Mon, 11 Aug 2008 13:42:37 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/sql-server/sql-2008-one-click-database-encryption-gives-a-false-sense-of-security/#comment-80</guid>
		<description>Hi, Denny.  The other reason TDE is useful is in SAN environments.  The SAN administrator can take a snapshot of an array at any time without stopping the application.  Granted, the snapshot will be dirty, but it's usually recoverable, and even if it isn't, they can retake the snapshot until they get a decent copy.  Then, they can mount that snapshot on another server and they've got a working copy of the company's databases, bypassing security.  TDE is great for that.

SAN-to-SAN replication makes this an even bigger issue: if you're doing SAN-based replication to your DR site, and especially if your DR site is a colo, someone else can take the snapshot at your DR site and pull the copied drives.</description>
		<content:encoded><![CDATA[<p>Hi, Denny.  The other reason TDE is useful is in SAN environments.  The SAN administrator can take a snapshot of an array at any time without stopping the application.  Granted, the snapshot will be dirty, but it&#8217;s usually recoverable, and even if it isn&#8217;t, they can retake the snapshot until they get a decent copy.  Then, they can mount that snapshot on another server and they&#8217;ve got a working copy of the company&#8217;s databases, bypassing security.  TDE is great for that.</p>
<p>SAN-to-SAN replication makes this an even bigger issue: if you&#8217;re doing SAN-based replication to your DR site, and especially if your DR site is a colo, someone else can take the snapshot at your DR site and pull the copied drives.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->