<?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 IME connection requirements for ASA-SSM module in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ime-connection-requirements-for-asa-ssm-module/m-p/1507857#M66314</link>
    <description>&lt;P&gt;I am looking into monitoring an IPS device at a remote site over the internet. I would like to install IME at my main site and have IME connect to the SSM module at the remote site over the internet.&amp;nbsp; Can anyone offer advice on the TCP ports required (is it simply tcp 443) and if this is advisable?&amp;nbsp; Any ideas on how much traffic this would generate over the internet connection?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My thoughts are that I could create a static translation on the ASA for the IP address of the management interface of the SSM module and restrict access through the ASA to my main site public IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any assistance is much appreciated.&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 12:09:42 GMT</pubDate>
    <dc:creator>davidbuit</dc:creator>
    <dc:date>2019-03-10T12:09:42Z</dc:date>
    <item>
      <title>IME connection requirements for ASA-SSM module</title>
      <link>https://community.cisco.com/t5/network-security/ime-connection-requirements-for-asa-ssm-module/m-p/1507857#M66314</link>
      <description>&lt;P&gt;I am looking into monitoring an IPS device at a remote site over the internet. I would like to install IME at my main site and have IME connect to the SSM module at the remote site over the internet.&amp;nbsp; Can anyone offer advice on the TCP ports required (is it simply tcp 443) and if this is advisable?&amp;nbsp; Any ideas on how much traffic this would generate over the internet connection?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My thoughts are that I could create a static translation on the ASA for the IP address of the management interface of the SSM module and restrict access through the ASA to my main site public IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any assistance is much appreciated.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 12:09:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ime-connection-requirements-for-asa-ssm-module/m-p/1507857#M66314</guid>
      <dc:creator>davidbuit</dc:creator>
      <dc:date>2019-03-10T12:09:42Z</dc:date>
    </item>
    <item>
      <title>Re: IME connection requirements for ASA-SSM module</title>
      <link>https://community.cisco.com/t5/network-security/ime-connection-requirements-for-asa-ssm-module/m-p/1507858#M66317</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All you need is to open up TCP/443 for the IME to be able to successfully connect. So, you can have a static for the SSMs management IP address on TCP port 443 and put in an access-list entry to allow that traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not really sure of how much traffic this will take up but it should not be much.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps. let me know how it goes!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Prapanch&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Oct 2010 15:36:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ime-connection-requirements-for-asa-ssm-module/m-p/1507858#M66317</guid>
      <dc:creator>praprama</dc:creator>
      <dc:date>2010-10-26T15:36:52Z</dc:date>
    </item>
  </channel>
</rss>

