<?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: what does every virtual sensors do when the signature is upd in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/what-does-every-virtual-sensors-do-when-the-signature-is-updated/m-p/2355120#M53298</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Mr.karsten&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you so much for your answer.I got it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We will make some policies on MPF to solve it.the one is fail-open,another is fail-close.we have a/s architecture,but It's hard to use secondary when every time signature is updating on primary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think this spec is serious for customer.&lt;/P&gt;&lt;P&gt;because there are time without inspection.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 29 Oct 2013 09:23:37 GMT</pubDate>
    <dc:creator>fukuta_rep1</dc:creator>
    <dc:date>2013-10-29T09:23:37Z</dc:date>
    <item>
      <title>what does every virtual sensors do when the signature is updated ?</title>
      <link>https://community.cisco.com/t5/network-security/what-does-every-virtual-sensors-do-when-the-signature-is-updated/m-p/2355118#M53294</link>
      <description>&lt;P&gt;Hi,We'd like to implement ASA5585 with SSP-60.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I knew that the inspection will stop while the signature is updating.&lt;/P&gt;&lt;P&gt;because sensor app will be stopped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess there are only one signature database on IPS which is managed by IPS device.&lt;/P&gt;&lt;P&gt;It means every virtual sensor's inspection depends on same signature database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so,&lt;/P&gt;&lt;P&gt;I think all virtual sensor will stop inspecting if some virtual sensor worked on IPS when the signatures is updated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But I can't find evidence what is above.&lt;/P&gt;&lt;P&gt;if you knows it,please tell me about it.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 13:04:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/what-does-every-virtual-sensors-do-when-the-signature-is-updated/m-p/2355118#M53294</guid>
      <dc:creator>fukuta_rep1</dc:creator>
      <dc:date>2019-03-10T13:04:44Z</dc:date>
    </item>
    <item>
      <title>Re: what does every virtual sensors do when the signature is upd</title>
      <link>https://community.cisco.com/t5/network-security/what-does-every-virtual-sensors-do-when-the-signature-is-updated/m-p/2355119#M53295</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are right. Just think about what is virtualized with virtual sensors and what not. Only the processing of the sensor policy is part of the virtualization. All the rest is based on the same shared system for all virtual sensors. Of course you can influence the behavior of your system with inline/promiscous-settings in MPF and also with specifying if you want to use fail-open/fail-close or even using failover to your secondary ASA while the first ASA-module does maintainance.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Oct 2013 08:55:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/what-does-every-virtual-sensors-do-when-the-signature-is-updated/m-p/2355119#M53295</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2013-10-29T08:55:16Z</dc:date>
    </item>
    <item>
      <title>Re: what does every virtual sensors do when the signature is upd</title>
      <link>https://community.cisco.com/t5/network-security/what-does-every-virtual-sensors-do-when-the-signature-is-updated/m-p/2355120#M53298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Mr.karsten&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you so much for your answer.I got it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We will make some policies on MPF to solve it.the one is fail-open,another is fail-close.we have a/s architecture,but It's hard to use secondary when every time signature is updating on primary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think this spec is serious for customer.&lt;/P&gt;&lt;P&gt;because there are time without inspection.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Oct 2013 09:23:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/what-does-every-virtual-sensors-do-when-the-signature-is-updated/m-p/2355120#M53298</guid>
      <dc:creator>fukuta_rep1</dc:creator>
      <dc:date>2013-10-29T09:23:37Z</dc:date>
    </item>
  </channel>
</rss>

