<?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: RDEP and SDEE in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/rdep-and-sdee/m-p/373585#M96663</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The sensor can serve out events in both formats simultaneously.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version 4.x sensors stored events in the older RDEPv1 format, and could only server events with the older RDEPv1 format.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version 5.x sensors instead store events in the newer SDEE/CIDEE format, and will natively serve out these events in the SDEE/CIDEE format using the sdee-server web service.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, to ensure compatibility with systems designed for 4.x with the RDEPv1 format, a converter was also included with the 5.x sensor.  When the event-server web service is connected to (instead of the sdee-server web service) the sensor will automatically internally convert the natively stored SDEE/CIDEE formatted alarms into the older RDEPv1 format and serve them out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So yes a RDEPv1 style client can connect and receive events from the sensor at the same time that a new SDEE/CIDEE style client connects and receives events from the sensor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOTE: CIDEE contains the Cisco specific parameters that are added on to the standard SDEE format.  SDEE/CIDEE may also be referred to as RDEPv2 format.  &lt;/P&gt;&lt;P&gt;Specifications are available for download from:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/cgi-bin/dev_support/access_level/product_support?pcgi=1&amp;amp;product=IDS_INT_API" target="_blank"&gt;http://www.cisco.com/cgi-bin/dev_support/access_level/product_support?pcgi=1&amp;amp;product=IDS_INT_API&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 29 Mar 2005 18:59:14 GMT</pubDate>
    <dc:creator>marcabal</dc:creator>
    <dc:date>2005-03-29T18:59:14Z</dc:date>
    <item>
      <title>RDEP and SDEE</title>
      <link>https://community.cisco.com/t5/network-security/rdep-and-sdee/m-p/373584#M96662</link>
      <description>&lt;P&gt;Greetings all. I'm continuing to educate myself about RDEP and SDEE so apologies in advance if my understanding is not the greatest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have custom apps which pull events from a Cisco 4235 appliance (v 5.0) via RDEP. Some members of my group are also interested in using third-party apps to read/view the same events via SDEE. My question to the forum is....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to read/view events from a v5.0 sensor using both technologies/formats simultaneously? or are they mutually exclusive? Thank you.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 09:21:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rdep-and-sdee/m-p/373584#M96662</guid>
      <dc:creator>gdntsoc</dc:creator>
      <dc:date>2019-03-10T09:21:36Z</dc:date>
    </item>
    <item>
      <title>Re: RDEP and SDEE</title>
      <link>https://community.cisco.com/t5/network-security/rdep-and-sdee/m-p/373585#M96663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The sensor can serve out events in both formats simultaneously.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version 4.x sensors stored events in the older RDEPv1 format, and could only server events with the older RDEPv1 format.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version 5.x sensors instead store events in the newer SDEE/CIDEE format, and will natively serve out these events in the SDEE/CIDEE format using the sdee-server web service.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, to ensure compatibility with systems designed for 4.x with the RDEPv1 format, a converter was also included with the 5.x sensor.  When the event-server web service is connected to (instead of the sdee-server web service) the sensor will automatically internally convert the natively stored SDEE/CIDEE formatted alarms into the older RDEPv1 format and serve them out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So yes a RDEPv1 style client can connect and receive events from the sensor at the same time that a new SDEE/CIDEE style client connects and receives events from the sensor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOTE: CIDEE contains the Cisco specific parameters that are added on to the standard SDEE format.  SDEE/CIDEE may also be referred to as RDEPv2 format.  &lt;/P&gt;&lt;P&gt;Specifications are available for download from:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/cgi-bin/dev_support/access_level/product_support?pcgi=1&amp;amp;product=IDS_INT_API" target="_blank"&gt;http://www.cisco.com/cgi-bin/dev_support/access_level/product_support?pcgi=1&amp;amp;product=IDS_INT_API&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Mar 2005 18:59:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/rdep-and-sdee/m-p/373585#M96663</guid>
      <dc:creator>marcabal</dc:creator>
      <dc:date>2005-03-29T18:59:14Z</dc:date>
    </item>
  </channel>
</rss>

