<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Self Encrypting SAS HDD with Smart Array P411 in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/self-encrypting-sas-hdd-with-smart-array-p411/m-p/6242317#M46809</link>
    <description>&lt;P&gt;Hi Dennis,&lt;/P&gt;&lt;P&gt;&amp;nbsp; Thanks for the response.&amp;nbsp; I know SED's encrypt/decrypt all the time.&amp;nbsp; The point of SED's is for them to be encrypted and data is unatainable - or at least much harder to obtain - should the drives be stolen or an incorrect key is entered at system boot time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; SED's seem like a great idea by removing the encryption load from the CPU to the HDD but it seems like the technology is too new to be able to get infromation from vendors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; I'd still appreciate it anyone can tell me if my proposed set up will work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;RobC&lt;/P&gt;</description>
    <pubDate>Mon, 21 Oct 2013 08:32:37 GMT</pubDate>
    <dc:creator>robertcompton</dc:creator>
    <dc:date>2013-10-21T08:32:37Z</dc:date>
    <item>
      <title>Self Encrypting SAS HDD with Smart Array P411</title>
      <link>https://community.hpe.com/t5/disk-enclosures/self-encrypting-sas-hdd-with-smart-array-p411/m-p/6239791#M46803</link>
      <description>&lt;P&gt;Good morning,&lt;/P&gt;&lt;P&gt;&amp;nbsp; I'm trying to find out if it is possible to use self encrypting SAS HDD's housed in a StorageWorks D2600 and connected to my DL380 G7 via a Smart Array P411 controller.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; I cannot see any mention of self encryption being supported by the P411 in any of the literature I've seen.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; My aim is to swap out the current SAS HDD's and replace them all with self encrypting ones instead.&amp;nbsp; The main reason is that I want to remove the encryption load from the servers CPU and hand it over to the hardware on the HDD instead.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Does anyone know if this scenario is at all possible?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;RobC&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2013 10:12:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/self-encrypting-sas-hdd-with-smart-array-p411/m-p/6239791#M46803</guid>
      <dc:creator>robertcompton</dc:creator>
      <dc:date>2013-10-18T10:12:27Z</dc:date>
    </item>
    <item>
      <title>Re: Self Encrypting SAS HDD with Smart Array P411</title>
      <link>https://community.hpe.com/t5/disk-enclosures/self-encrypting-sas-hdd-with-smart-array-p411/m-p/6240501#M46804</link>
      <description>&lt;P&gt;&amp;gt;replace them all with self encrypting ones instead.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unless you have software that "takes ownership" of the SEDs, there is no protection of data.&lt;/P&gt;&lt;P&gt;The SEDs will be quite happy to encrypt on writes and decrypt on reads.&lt;/P&gt;</description>
      <pubDate>Sat, 19 Oct 2013 02:10:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/self-encrypting-sas-hdd-with-smart-array-p411/m-p/6240501#M46804</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2013-10-19T02:10:30Z</dc:date>
    </item>
    <item>
      <title>Re: Self Encrypting SAS HDD with Smart Array P411</title>
      <link>https://community.hpe.com/t5/disk-enclosures/self-encrypting-sas-hdd-with-smart-array-p411/m-p/6242317#M46809</link>
      <description>&lt;P&gt;Hi Dennis,&lt;/P&gt;&lt;P&gt;&amp;nbsp; Thanks for the response.&amp;nbsp; I know SED's encrypt/decrypt all the time.&amp;nbsp; The point of SED's is for them to be encrypted and data is unatainable - or at least much harder to obtain - should the drives be stolen or an incorrect key is entered at system boot time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; SED's seem like a great idea by removing the encryption load from the CPU to the HDD but it seems like the technology is too new to be able to get infromation from vendors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; I'd still appreciate it anyone can tell me if my proposed set up will work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;RobC&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2013 08:32:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/self-encrypting-sas-hdd-with-smart-array-p411/m-p/6242317#M46809</guid>
      <dc:creator>robertcompton</dc:creator>
      <dc:date>2013-10-21T08:32:37Z</dc:date>
    </item>
    <item>
      <title>Re: Self Encrypting SAS HDD with Smart Array P411</title>
      <link>https://community.hpe.com/t5/disk-enclosures/self-encrypting-sas-hdd-with-smart-array-p411/m-p/6242451#M46811</link>
      <description>&lt;P&gt;&amp;gt;The point of SEDs is for them to be encrypted and data is unattainable - should the drives be stolen or an incorrect key is entered at system boot time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes.&amp;nbsp; You must have software to take ownership of the drive.&amp;nbsp; This includes changing the authentication key and to set lock on powerfail.&amp;nbsp; And as you said, software to read the key and unlock the band.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2013 09:51:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/self-encrypting-sas-hdd-with-smart-array-p411/m-p/6242451#M46811</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2013-10-21T09:51:57Z</dc:date>
    </item>
  </channel>
</rss>

