<?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 &amp;quot;Unhackable&amp;quot; CPU? in Industry News</title>
    <link>https://community.isc2.org/t5/Industry-News/quot-Unhackable-quot-CPU/m-p/22059#M2725</link>
    <description>&lt;P&gt;Researchers at the University of Michigan claim they have a &lt;A href="https://securityboulevard.com/2019/05/scientists-claim-to-have-invented-the-unhackable-processor/" target="_blank" rel="noopener"&gt;processor that can't be hacked&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The description is a bit thin, but it seems a variation on memory shuffling to avoid direct attacks on specific locations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I very much doubt that it is hack proof.&amp;nbsp; (I'd go for "denial of service" first off ...)&lt;/P&gt;</description>
    <pubDate>Tue, 07 May 2019 16:43:11 GMT</pubDate>
    <dc:creator>rslade</dc:creator>
    <dc:date>2019-05-07T16:43:11Z</dc:date>
    <item>
      <title>"Unhackable" CPU?</title>
      <link>https://community.isc2.org/t5/Industry-News/quot-Unhackable-quot-CPU/m-p/22059#M2725</link>
      <description>&lt;P&gt;Researchers at the University of Michigan claim they have a &lt;A href="https://securityboulevard.com/2019/05/scientists-claim-to-have-invented-the-unhackable-processor/" target="_blank" rel="noopener"&gt;processor that can't be hacked&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The description is a bit thin, but it seems a variation on memory shuffling to avoid direct attacks on specific locations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I very much doubt that it is hack proof.&amp;nbsp; (I'd go for "denial of service" first off ...)&lt;/P&gt;</description>
      <pubDate>Tue, 07 May 2019 16:43:11 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/quot-Unhackable-quot-CPU/m-p/22059#M2725</guid>
      <dc:creator>rslade</dc:creator>
      <dc:date>2019-05-07T16:43:11Z</dc:date>
    </item>
    <item>
      <title>Re: "Unhackable" CPU?</title>
      <link>https://community.isc2.org/t5/Industry-News/quot-Unhackable-quot-CPU/m-p/22079#M2728</link>
      <description>&lt;P&gt;Unhackable? Not a chance.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If it's unplugged and never used, then I will concede it's unhackable.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The term "unhackable" is two frequently banded around by those looking to further sales or uptake of services they offer. Yet-to-be-hacked, now that's a term I'm happy with.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unhackable technology is up there with the discovery and keeping of unicorns or, simply put, non-existent.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2019 09:51:21 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/quot-Unhackable-quot-CPU/m-p/22079#M2728</guid>
      <dc:creator>HTCPCP-TEA</dc:creator>
      <dc:date>2019-05-08T09:51:21Z</dc:date>
    </item>
    <item>
      <title>Re: "Unhackable" CPU?</title>
      <link>https://community.isc2.org/t5/Industry-News/quot-Unhackable-quot-CPU/m-p/22102#M2731</link>
      <description>&amp;gt; HTCPCP-TEA (Contributor I) posted a new reply in Industry News on 05-08-2019&lt;BR /&gt;&lt;BR /&gt;&amp;gt; Yet-to-be-hacked, now that's a term I'm happy with.&lt;BR /&gt;&lt;BR /&gt;How about "yet-to-be-hacked--that-you-know-of"?&lt;BR /&gt;&lt;BR /&gt;====================== (quote inserted randomly by Pegasus Mailer)&lt;BR /&gt;rslade@vcn.bc.ca slade@victoria.tc.ca rslade@computercrime.org&lt;BR /&gt;If you can't say anything good about someone, sit right here by&lt;BR /&gt;me. - Alice Roosevelt Longworth&lt;BR /&gt;victoria.tc.ca/techrev/rms.htm &lt;A href="http://twitter.com/rslade" target="_blank"&gt;http://twitter.com/rslade&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://blogs.securiteam.com/index.php/archives/author/p1/" target="_blank"&gt;http://blogs.securiteam.com/index.php/archives/author/p1/&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://is.gd/RotlWB" target="_blank"&gt;https://is.gd/RotlWB&lt;/A&gt;</description>
      <pubDate>Wed, 08 May 2019 17:40:04 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/quot-Unhackable-quot-CPU/m-p/22102#M2731</guid>
      <dc:creator>rslade</dc:creator>
      <dc:date>2019-05-08T17:40:04Z</dc:date>
    </item>
    <item>
      <title>Re: "Unhackable" CPU?</title>
      <link>https://community.isc2.org/t5/Industry-News/quot-Unhackable-quot-CPU/m-p/22190#M2752</link>
      <description>&lt;P&gt;Well, yes. I'd accept any variation on the phrase provided it doesn't state complete fabrications.&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2019 21:17:45 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/quot-Unhackable-quot-CPU/m-p/22190#M2752</guid>
      <dc:creator>HTCPCP-TEA</dc:creator>
      <dc:date>2019-05-10T21:17:45Z</dc:date>
    </item>
  </channel>
</rss>

