<?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 Fair enough.  in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firesight-sourcefire-ips-licensing/m-p/2677152#M44862</link>
    <description>&lt;P&gt;Fair enough.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 18 Jun 2015 18:45:30 GMT</pubDate>
    <dc:creator>nrunge1</dc:creator>
    <dc:date>2015-06-18T18:45:30Z</dc:date>
    <item>
      <title>FireSight/SourceFire IPS Licensing</title>
      <link>https://community.cisco.com/t5/network-security/firesight-sourcefire-ips-licensing/m-p/2677150#M44856</link>
      <description>&lt;P&gt;With my bundle I received two control+protect licenses.They have no expiration in the licensing portion of the UI and were a $0 SKU on the order. I purchased only the URL filtering subscription, not IPS or Malware. However when I create and apply intrusion policies in FireSight the UI does not complain.&lt;/P&gt;&lt;P&gt;Is the IPS component functional based on the control+protect licenses that I received?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 13:23:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-sourcefire-ips-licensing/m-p/2677150#M44856</guid>
      <dc:creator>nrunge1</dc:creator>
      <dc:date>2019-03-10T13:23:57Z</dc:date>
    </item>
    <item>
      <title>The Control / Protect</title>
      <link>https://community.cisco.com/t5/network-security/firesight-sourcefire-ips-licensing/m-p/2677151#M44861</link>
      <description>&lt;P&gt;The Control / Protect licenses should be applied to the module(s) to ensure full functionality of any of the other feature licenses.&lt;/P&gt;&lt;P&gt;It's true that they won't necessarily error out when you haven't done so; but the features may fail in more subtle ways depending on how your policies are crafted.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jun 2015 14:39:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-sourcefire-ips-licensing/m-p/2677151#M44861</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2015-06-18T14:39:49Z</dc:date>
    </item>
    <item>
      <title>Fair enough. </title>
      <link>https://community.cisco.com/t5/network-security/firesight-sourcefire-ips-licensing/m-p/2677152#M44862</link>
      <description>&lt;P&gt;Fair enough.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jun 2015 18:45:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firesight-sourcefire-ips-licensing/m-p/2677152#M44862</guid>
      <dc:creator>nrunge1</dc:creator>
      <dc:date>2015-06-18T18:45:30Z</dc:date>
    </item>
  </channel>
</rss>

