<?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: vPro AMT System Defense in Intel vPro® Platform</title>
    <link>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610351#M6887</link>
    <description>&lt;P&gt;Hello PT,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;I am following up your question and we would like to know if you need further assistance&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;Best regards,&lt;P&gt;&amp;nbsp;&lt;/P&gt;Sergio S.</description>
    <pubDate>Thu, 08 Nov 2018 01:23:29 GMT</pubDate>
    <dc:creator>idata</dc:creator>
    <dc:date>2018-11-08T01:23:29Z</dc:date>
    <item>
      <title>vPro AMT System Defense</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610346#M6882</link>
      <description>&lt;P&gt;Has anyone tried using system defense rules in AMT? I am trying to see if we can use it to restrict AMT connection from a specific management server IP.&lt;/P&gt;&lt;P&gt;I created a Drop all rule and I can still connect to AMT from anywhere the management console is installed (So long as I am using an account that has access, such as user ID and password, or Kerberos via AD groups).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I then thought OK, can I limit connections to a specific port, say SMB (445) - I created a filter and a policy and applied it using Mesh Commander, but I can still connect to the endpoint via SMB. Confusing!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you see anything wrong with my 445 filters?&lt;/P&gt;&lt;P&gt;ProtocolID=6,SrcAddress=xx.xx.xxx.xxx,SrcMask=xxx.xxx.xxx.x,HdrDestPortStart=445,HdrDestPortEnd=445&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Oct 2018 19:12:43 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610346#M6882</guid>
      <dc:creator>PBurn1</dc:creator>
      <dc:date>2018-10-25T19:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: vPro AMT System Defense</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610347#M6883</link>
      <description>&lt;P&gt;Hello PT,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;Please help us providing some additional information:&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;Can you please provide us the AMT version that you are currently running?&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;Also, please provide to the model of your systems.&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;On how many systems you are deploying AMT?&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;Also, we do recommend checking the &lt;A href="https://www.intel.com/content/dam/support/us/en/documents/software/Intel_SCS_User_Guide.pdf"&gt;https://www.intel.com/content/dam/support/us/en/documents/software/Intel_SCS_User_Guide.pdf&lt;/A&gt; user guide.&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;Best regards,&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;Sergio S.</description>
      <pubDate>Sat, 27 Oct 2018 01:50:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610347#M6883</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2018-10-27T01:50:50Z</dc:date>
    </item>
    <item>
      <title>Re: vPro AMT System Defense</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610348#M6884</link>
      <description>&lt;P&gt;Hello PT,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;We are following your question and we would like to know if you need further assistance.&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;Best regards,&lt;P&gt;&amp;nbsp;&lt;/P&gt;Sergio S.</description>
      <pubDate>Tue, 30 Oct 2018 01:57:58 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610348#M6884</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2018-10-30T01:57:58Z</dc:date>
    </item>
    <item>
      <title>Re: vPro AMT System Defense</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610349#M6885</link>
      <description>&lt;P&gt;Hello there - Not sure of the version - This is on a Dell Precision 3520 laptop. Still unsure if the filter is formatted correctly, but it doesn't seem to drop 445 packets. &lt;/P&gt;</description>
      <pubDate>Thu, 01 Nov 2018 17:48:24 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610349#M6885</guid>
      <dc:creator>PBurn1</dc:creator>
      <dc:date>2018-11-01T17:48:24Z</dc:date>
    </item>
    <item>
      <title>Re: vPro AMT System Defense</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610350#M6886</link>
      <description>&lt;P&gt;Hello PT,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;Please provide us with a copy of the RCS log in order to check the version of the AMT that you have.&lt;P&gt;&amp;nbsp;&lt;/P&gt;The log files of the RCS are located in a folder named RCSConfServer in one of these hidden locations: • ProgramData\Intel_Corporation • Documents and Settings\All Users\Application Data\Intel_Corporation&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;The log file is named RCSLog.log and records all operations and actions done by the RCS. Each time the log file becomes too large, or the RCS is restarted, the file content is moved to a new file with this format: RCSLog.logYYYY-MM-DD-HH-MI-SS.log.&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;Best regards,&lt;P&gt;&amp;nbsp;&lt;/P&gt;Sergio S.</description>
      <pubDate>Fri, 02 Nov 2018 01:26:25 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610350#M6886</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2018-11-02T01:26:25Z</dc:date>
    </item>
    <item>
      <title>Re: vPro AMT System Defense</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610351#M6887</link>
      <description>&lt;P&gt;Hello PT,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;I am following up your question and we would like to know if you need further assistance&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;Best regards,&lt;P&gt;&amp;nbsp;&lt;/P&gt;Sergio S.</description>
      <pubDate>Thu, 08 Nov 2018 01:23:29 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610351#M6887</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2018-11-08T01:23:29Z</dc:date>
    </item>
    <item>
      <title>Re: vPro AMT System Defense</title>
      <link>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610352#M6888</link>
      <description>&lt;P&gt;                                                       &lt;/P&gt;&lt;P&gt;Hello PT,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;      &lt;P&gt;&amp;nbsp;&lt;/P&gt;      In case you need further assistance please contact us back&lt;P&gt;&amp;nbsp;&lt;/P&gt;      &lt;P&gt;&amp;nbsp;&lt;/P&gt;      &lt;P&gt;&amp;nbsp;&lt;/P&gt;      Best regards,&lt;P&gt;&amp;nbsp;&lt;/P&gt;      Sergio S.</description>
      <pubDate>Thu, 15 Nov 2018 03:45:44 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-vPro-Platform/vPro-AMT-System-Defense/m-p/610352#M6888</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2018-11-15T03:45:44Z</dc:date>
    </item>
  </channel>
</rss>

