<?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>Intel vPro® PlatformのトピックRe: tampering</title>
    <link>https://community.intel.com/t5/Intel-vPro-Platform/tampering/m-p/222802#M706</link>
    <description>&lt;P&gt;any Intel vPro experts in this group? &lt;/P&gt;</description>
    <pubDate>Mon, 11 May 2009 13:20:32 GMT</pubDate>
    <dc:creator>idata</dc:creator>
    <dc:date>2009-05-11T13:20:32Z</dc:date>
    <item>
      <title>tampering</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/tampering/m-p/222801#M705</link>
      <description>&lt;P&gt;In all the documentation online regarding security of vPro, it does not clarify in detail whether the PC's can be tampered with in anyway that would deactivate the vPro setup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to know, for example, if it's possible to disable vPro by removing the motherboard eprom battery.&lt;/P&gt;</description>
      <pubDate>Fri, 08 May 2009 13:31:51 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/tampering/m-p/222801#M705</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2009-05-08T13:31:51Z</dc:date>
    </item>
    <item>
      <title>Re: tampering</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/tampering/m-p/222802#M706</link>
      <description>&lt;P&gt;any Intel vPro experts in this group? &lt;/P&gt;</description>
      <pubDate>Mon, 11 May 2009 13:20:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/tampering/m-p/222802#M706</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2009-05-11T13:20:32Z</dc:date>
    </item>
    <item>
      <title>Re: tampering</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/tampering/m-p/222803#M707</link>
      <description>&lt;P&gt;What system models do you have?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are different components of vPro&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For the Active Management Technology.  Yes - if the BIOS battery is removed and reinserted, the Intel AMT settings will be reset to factory default.  In addition, some OEMs provide a setting in BIOS to reset Intel AMT upon the next reboot.  The suggest here is lock you BIOS settings and case if that is a concern&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For the Anti-Theft Technology (AT-p) - a BIOS  battery reset will not affect.  Therefore, if someone were to steal a system that is configured with Absolute, Computrace, or other support AT-p security vendor... if the AT-p policy activates and disables the system, only a re-activation key\sequence as defined by the security policy will reactivate the system.  A BIOS battery reset will not&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does that help?&lt;/P&gt;</description>
      <pubDate>Mon, 11 May 2009 15:33:12 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/tampering/m-p/222803#M707</guid>
      <dc:creator>Terry_C_Intel</dc:creator>
      <dc:date>2009-05-11T15:33:12Z</dc:date>
    </item>
    <item>
      <title>Re: tampering</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/tampering/m-p/222804#M708</link>
      <description>&lt;P&gt;Thanks Terry for the info.   I will be setting up vPro with Altiris Out of Band component.    The PC's that I use are HP.    Is the (AT-p) Anti-Theft Technology available for HP computers?   From what I've read, it's only on Lenovo brand.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically, I need to know if there is any other way around disabling AMT vPro other than removing the BIOS battery, however I dont' see anywhere in the Intel vPro documentation regarding the security details.&lt;/P&gt;</description>
      <pubDate>Tue, 12 May 2009 13:23:24 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/tampering/m-p/222804#M708</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2009-05-12T13:23:24Z</dc:date>
    </item>
    <item>
      <title>Re: tampering</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/tampering/m-p/222805#M709</link>
      <description>&lt;P&gt;Correct on AT-p being available for only Lenovo platforms... other's may add the functionality, yet only Lenovo supports at this time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding the disabling or unconfiguring of AMT - Take a look at &lt;A href="http://www.symantec.com/connect/articles/provisioning-intel-vpro-technology-part-4-remotely-resetting-provisioning-state"&gt;http://www.symantec.com/connect/articles/provisioning-intel-vpro-technology-part-4-remotely-resetting-provisioning-state&lt;/A&gt; &lt;A href="http://www.symantec.com/connect/articles/provisioning-intel-vpro-technology-part-4-remotely-resetting-provisioning-state"&gt;http://www.symantec.com/connect/articles/provisioning-intel-vpro-technology-part-4-remotely-resetting-provisioning-state&lt;/A&gt;  On the HP laptops (i.e. 2510p, 6910p, 8510p, 2530p, 6930p, 8530p), there is an option in the BIOS to unconfigure AMT on next boot.  This option requires a confirmation at the next boot.  Thus - it is possible - but can  be controlled by BIOS security.  Similarly - as mentioned in the article - if an Altiris user has sufficient rights\access, they can unconfigure systems remotely.  In both cases - it's a matter of Access Control, rights\permissions, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just curious - how soon will you  be activating vPro\AMT?  How many client systems?  Key usage model?   (if you'd prefer to not answer on blog - send me a private message via vPro Expert center account)&lt;/P&gt;</description>
      <pubDate>Tue, 12 May 2009 14:00:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/tampering/m-p/222805#M709</guid>
      <dc:creator>Terry_C_Intel</dc:creator>
      <dc:date>2009-05-12T14:00:18Z</dc:date>
    </item>
  </channel>
</rss>

