<?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: Baselining or Soaking a Sensor in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/baselining-or-soaking-a-sensor/m-p/958085#M79435</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have a modified policy we use to start with but typically two weeks seems to be sufficient.  That depends upon the sort of traffic you see, the placement of the sensor, and how busy it is.  I could easily see spending an hour a day for several weeks tuning/profiling if this sensor was generating 50k events / day.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Jul 2008 14:07:12 GMT</pubDate>
    <dc:creator>attmidsteam</dc:creator>
    <dc:date>2008-07-14T14:07:12Z</dc:date>
    <item>
      <title>Baselining or Soaking a Sensor</title>
      <link>https://community.cisco.com/t5/network-security/baselining-or-soaking-a-sensor/m-p/958084#M79431</link>
      <description>&lt;P&gt;When a bringing up a new sensor in a network typically how long should the sensor be allowed to baseline or soak for before tunning begins? Does cisco recommend a specific time period?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:11:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/baselining-or-soaking-a-sensor/m-p/958084#M79431</guid>
      <dc:creator>niall-wilkins</dc:creator>
      <dc:date>2019-03-10T11:11:47Z</dc:date>
    </item>
    <item>
      <title>Re: Baselining or Soaking a Sensor</title>
      <link>https://community.cisco.com/t5/network-security/baselining-or-soaking-a-sensor/m-p/958085#M79435</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have a modified policy we use to start with but typically two weeks seems to be sufficient.  That depends upon the sort of traffic you see, the placement of the sensor, and how busy it is.  I could easily see spending an hour a day for several weeks tuning/profiling if this sensor was generating 50k events / day.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2008 14:07:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/baselining-or-soaking-a-sensor/m-p/958085#M79435</guid>
      <dc:creator>attmidsteam</dc:creator>
      <dc:date>2008-07-14T14:07:12Z</dc:date>
    </item>
    <item>
      <title>Re: Baselining or Soaking a Sensor</title>
      <link>https://community.cisco.com/t5/network-security/baselining-or-soaking-a-sensor/m-p/958086#M79436</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can begin performing event analysis as soon as you plug your sensor into the network. This will allow you eliminate false positives and create filters for events you don't want to see again from a particular host/network. The more you tune your signatures, the higher the quality of events you will get from them.&lt;/P&gt;&lt;P&gt;The only aspect that might need any â&amp;#128;&amp;#156;soakâ&amp;#128;&amp;#157; time is the dozen or so â&amp;#128;&amp;#156;anomaly engine signaturesâ&amp;#128;&amp;#157; The anomaly engine needs a day to a week to â&amp;#128;&amp;#156;learnâ&amp;#128;&amp;#157; what is normal traffic on your network, but that isn't any reason to wait to begin signature tuning.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2008 18:36:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/baselining-or-soaking-a-sensor/m-p/958086#M79436</guid>
      <dc:creator>rhermes</dc:creator>
      <dc:date>2008-07-14T18:36:06Z</dc:date>
    </item>
  </channel>
</rss>

