<?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 Extended Device tracking in SDA in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/extended-device-tracking-in-sda/m-p/4886921#M2475</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Cisco&amp;nbsp;DNA Center&amp;nbsp;Version 2.3.3.7-72328&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;As I understand it standard Assurance Client information only goes back 7 days. I have a requirement from our CSIRT team to be able to tell them what client (MAC address) was using a specific IP address and where the device was seen on the network&amp;nbsp;(for compliance /&amp;nbsp; copyright infringement /&amp;nbsp;security reasons) for the past 100 days.&lt;/P&gt;&lt;P&gt;Can DNAC be used for this or should we investigate a different tool, or develop our own?&lt;/P&gt;&lt;P&gt;thanks in advance - Michael&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 18 Jul 2023 11:41:59 GMT</pubDate>
    <dc:creator>Michael Warren</dc:creator>
    <dc:date>2023-07-18T11:41:59Z</dc:date>
    <item>
      <title>Extended Device tracking in SDA</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/extended-device-tracking-in-sda/m-p/4886921#M2475</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Cisco&amp;nbsp;DNA Center&amp;nbsp;Version 2.3.3.7-72328&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;As I understand it standard Assurance Client information only goes back 7 days. I have a requirement from our CSIRT team to be able to tell them what client (MAC address) was using a specific IP address and where the device was seen on the network&amp;nbsp;(for compliance /&amp;nbsp; copyright infringement /&amp;nbsp;security reasons) for the past 100 days.&lt;/P&gt;&lt;P&gt;Can DNAC be used for this or should we investigate a different tool, or develop our own?&lt;/P&gt;&lt;P&gt;thanks in advance - Michael&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jul 2023 11:41:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/extended-device-tracking-in-sda/m-p/4886921#M2475</guid>
      <dc:creator>Michael Warren</dc:creator>
      <dc:date>2023-07-18T11:41:59Z</dc:date>
    </item>
    <item>
      <title>Re: Extended Device tracking in SDA</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/extended-device-tracking-in-sda/m-p/4892183#M2506</link>
      <description>&lt;P&gt;do u have this requirement only to ports protected by AAA? if u do u can take this info from ISE. assuming your operational DB on ISE has more than 100+ days of purge frequency&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2023 14:19:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/extended-device-tracking-in-sda/m-p/4892183#M2506</guid>
      <dc:creator>Andrii Oliinyk</dc:creator>
      <dc:date>2023-07-25T14:19:04Z</dc:date>
    </item>
    <item>
      <title>Re: Extended Device tracking in SDA</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/extended-device-tracking-in-sda/m-p/4892755#M2511</link>
      <description>&lt;P&gt;Thanks for the reply Andy&lt;/P&gt;&lt;P&gt;Unfortunately we have this requirement for all end user hosts on the network. This is further complicated in that we have our switches set to no authentication atm (we hope to start using ISE in the very near future) and do not use Cisco wireless. The real problem we have is that we little control over much of the desktop clients (UK University with a highly fragmented federated IT environment - no single AD, multiple data sources of users, etc...) which will make&amp;nbsp;things like 802.1X difficult to implement.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I think the answer to all this lies with a tool outside of DNAC - or a custom built system. Although ISE might be central to this once we figure out how to use it!&lt;BR /&gt;&lt;BR /&gt;Mike&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2023 10:25:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/extended-device-tracking-in-sda/m-p/4892755#M2511</guid>
      <dc:creator>Michael Warren</dc:creator>
      <dc:date>2023-07-26T10:25:16Z</dc:date>
    </item>
    <item>
      <title>Re: Extended Device tracking in SDA</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/extended-device-tracking-in-sda/m-p/4892819#M2512</link>
      <description>&lt;P&gt;u need to use external logger then to keep history on-boarding entries along the ISE deployment option.&lt;/P&gt;
&lt;P&gt;with ISE u may live on authentication open mode for infinity &amp;amp; still have endpoint-info at its full extent.&lt;/P&gt;
&lt;P&gt;basically i'd expect a lot of whishes made already for this feature to be back in DNAC...&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2023 11:51:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/extended-device-tracking-in-sda/m-p/4892819#M2512</guid>
      <dc:creator>Andrii Oliinyk</dc:creator>
      <dc:date>2023-07-26T11:51:23Z</dc:date>
    </item>
  </channel>
</rss>

