<?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: ISE API - Endpoint Attributes in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-api-endpoint-attributes/m-p/5358984#M599453</link>
    <description>&lt;P&gt;To get the Inactivity Days attribute for your endpoints, you cannot rely on the standard Context Visibility CSV export or the basic Identity APIs, as that specific field is often calculated on the fly rather than stored as a static attribute in the standard endpoint object. Instead, you should use the External RESTful Services (ERS) API to query the endpoints and look for the InactiveDays or LastReceptionTime values.&lt;/P&gt;&lt;P&gt;Since your goal is to identify retired devices without risking an accidental purge, your best bet is to use a script (like Python) to call the GET /ers/config/endpoint API. You can then calculate the inactivity yourself by comparing the lastUpdate or StaticGroupAssignment timestamps against the current date. Alternatively, if you have Cisco ISE 3.x, you can leverage the Data Connect feature (using an SQL query via a reporting tool) to pull the last_activity_at column directly from the database, which is much more efficient for large datasets.&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jan 2026 05:16:16 GMT</pubDate>
    <dc:creator>willisthiel074en</dc:creator>
    <dc:date>2026-01-05T05:16:16Z</dc:date>
    <item>
      <title>ISE API - Endpoint Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-api-endpoint-attributes/m-p/5357474#M599371</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I've been poking around at the various ISE APIs including exporting endpoints via context visibility (CSV file exports) and not finding a way to export the endpoint WITH the inactivity days attribute.&amp;nbsp; We have devices that the users may not tell us when they are retired and we can't purge them automatically.&amp;nbsp; The not purging isn't a technical limitation but rather its if we purge them we may break something as these devices aren't used all that often.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone know how i can get this data?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Dec 2025 13:10:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-api-endpoint-attributes/m-p/5357474#M599371</guid>
      <dc:creator>ryanmbess</dc:creator>
      <dc:date>2025-12-24T13:10:16Z</dc:date>
    </item>
    <item>
      <title>Re: ISE API - Endpoint Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-api-endpoint-attributes/m-p/5357628#M599385</link>
      <description>&lt;P class="lia-align-justify"&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1243902"&gt;@ryanmbess&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;you can use the &lt;STRONG&gt;CLI&lt;/STRONG&gt; command:&lt;/P&gt;
&lt;PRE&gt;ise/admin# &lt;FONT color="#3366FF"&gt;application configure ise&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;Selection configuration option&lt;BR /&gt; ...&lt;BR /&gt; [16]&lt;FONT color="#3366FF"&gt;Get all Endpoints&lt;/FONT&gt;&lt;BR /&gt; ...&lt;BR /&gt; [0]Exit&lt;/PRE&gt;
&lt;P class="lia-align-justify"&gt;and check the &lt;STRONG&gt;Inactivity Days&lt;/STRONG&gt; attribute.&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;Note: &lt;STRONG&gt;Inactivity Days&lt;/STRONG&gt; has a lot of weird bugs, please take a look at&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwr43745" target="_blank" rel="noopener"&gt;CSCwr43745 Inactive Endpoint dashlet in Context Visibility is not matching with the inactive days information present in redis cache or DB&lt;/A&gt;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;Hope this helps !&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Dec 2025 19:32:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-api-endpoint-attributes/m-p/5357628#M599385</guid>
      <dc:creator>Marcelo Morais</dc:creator>
      <dc:date>2025-12-25T19:32:08Z</dc:date>
    </item>
    <item>
      <title>Re: ISE API - Endpoint Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-api-endpoint-attributes/m-p/5357702#M599388</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; From Context Visibility choose the Export menu option, there is a column for "Update Time" which tells you the last time ISE saw anything for that endpoint. You can afterward configure "Endpoints Purge Settings":&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/3-2/admin_guide/b_ise_admin_3_2/b_ISE_admin_33_maintain_monitor.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/3-2/admin_guide/b_ise_admin_3_2/b_ISE_admin_33_maintain_monitor.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Cristian.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Dec 2025 13:57:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-api-endpoint-attributes/m-p/5357702#M599388</guid>
      <dc:creator>Cristian Matei</dc:creator>
      <dc:date>2025-12-26T13:57:07Z</dc:date>
    </item>
    <item>
      <title>Re: ISE API - Endpoint Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-api-endpoint-attributes/m-p/5358984#M599453</link>
      <description>&lt;P&gt;To get the Inactivity Days attribute for your endpoints, you cannot rely on the standard Context Visibility CSV export or the basic Identity APIs, as that specific field is often calculated on the fly rather than stored as a static attribute in the standard endpoint object. Instead, you should use the External RESTful Services (ERS) API to query the endpoints and look for the InactiveDays or LastReceptionTime values.&lt;/P&gt;&lt;P&gt;Since your goal is to identify retired devices without risking an accidental purge, your best bet is to use a script (like Python) to call the GET /ers/config/endpoint API. You can then calculate the inactivity yourself by comparing the lastUpdate or StaticGroupAssignment timestamps against the current date. Alternatively, if you have Cisco ISE 3.x, you can leverage the Data Connect feature (using an SQL query via a reporting tool) to pull the last_activity_at column directly from the database, which is much more efficient for large datasets.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jan 2026 05:16:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-api-endpoint-attributes/m-p/5358984#M599453</guid>
      <dc:creator>willisthiel074en</dc:creator>
      <dc:date>2026-01-05T05:16:16Z</dc:date>
    </item>
    <item>
      <title>Re: ISE API - Endpoint Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-api-endpoint-attributes/m-p/5362281#M599568</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1243902"&gt;@ryanmbess&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;I highly recommend the use of ISE &lt;A href="https://cs.co/ise-dataconnect" target="_self"&gt;DataConnect&lt;/A&gt; for this.&lt;BR /&gt;It is an extremely fast SQL query &lt;EM&gt;directly&lt;/EM&gt; against the ISE database's &lt;EM&gt;endpoints&lt;/EM&gt; table to find this info.&lt;BR /&gt;I've even written the query for you:&amp;nbsp;&lt;BR /&gt;&lt;A href="https://github.com/1homas/ISE_Python_Scripts/blob/main/data/SQL/endpoints_last_auth.sql" target="_blank"&gt;https://github.com/1homas/ISE_Python_Scripts/blob/main/data/SQL/endpoints_last_auth.sql&lt;/A&gt;&lt;/P&gt;
&lt;PRE&gt;iseql.py --insecure data/SQL/endpoints_last_auth.sql --format table&lt;BR /&gt;&lt;BR /&gt;mac                random    timestamp            location                            username                                       endpoint_profile           sgt          device_name              ipv4        passed
-----------------  --------  -------------------  ----------------------------------  ---------------------------------------------  -------------------------  -----------  -----------------------  ----------  --------
F8:4D:89:67:FD:03            2024-09-06 16:50:55  All Locations                       thomas                                                                    Employees    thomas-mr46                          Pass
58:EF:68:E6:46:F0            2024-09-11 16:24:42  All Locations                       thomas                                         Belkin-Device              Employees    thomas-mx68                          Pass
2C:7B:A0:00:00:00            2024-09-17 12:59:01  All Locations                       2C:7B:A0:00:00:00                                                         Blocked      thomas                               Pass
E8:C8:29:00:00:00            2024-09-23 07:57:03  All Locations                       E8:C8:29:00:00:00                              Intel-Device               Blocked      thomas-mbp                           Pass
36:0E:9E:4E:17:F4  ✔         2024-09-23 07:57:21  All Locations                       36:0E:9E:4E:17:F4                                                         Blocked      thomas-mbp                           Pass
9C:8E:CD:2D:2C:17            2024-09-25 17:04:53  All Locations                       9C:8E:CD:2D:2C:17                              Unknown                    Blocked      thomas                               Pass  &lt;/PRE&gt;
&lt;P&gt;Watch the webinar&amp;nbsp;▷&amp;nbsp;&lt;A title="https://youtu.be/_yI7hnhz4s8" href="https://youtu.be/_yI7hnhz4s8" data-from-md="" target="_blank"&gt;ISE Data Connect Deep Dive&lt;/A&gt;&amp;nbsp;2025-04-22 where I talk about using my &lt;A href="https://github.com/1homas/ISE_Python_Scripts%20https://github.com/1homas/ISE_Python_Scripts#iseqlpy" target="_self"&gt;iseql.py&lt;/A&gt;&amp;nbsp;script for these kinds of queries.&lt;/P&gt;
&lt;P&gt;Resources:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://cs.co/ise-api#!data-connect-openapi" target="_blank"&gt;https://cs.co/ise-api#!data-connect-openapi&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://cs.co/ise-dataconnect" target="_blank"&gt;https://cs.co/ise-dataconnect&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://github.com/1homas/ISE_Python_Scripts" target="_blank"&gt;https://github.com/1homas/ISE_Python_Scripts&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://github.com/1homas/ISE_Python_Scripts/blob/main/iseql.py" target="_blank"&gt;https://github.com/1homas/ISE_Python_Scripts/blob/main/iseql.py&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jan 2026 22:13:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-api-endpoint-attributes/m-p/5362281#M599568</guid>
      <dc:creator>thomas</dc:creator>
      <dc:date>2026-01-16T22:13:39Z</dc:date>
    </item>
    <item>
      <title>Re: ISE API - Endpoint Attributes</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-api-endpoint-attributes/m-p/5363263#M599593</link>
      <description>&lt;P&gt;Thomas. Thanks for the links..will give them a read.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2026 12:49:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-api-endpoint-attributes/m-p/5363263#M599593</guid>
      <dc:creator>ryanmbess</dc:creator>
      <dc:date>2026-01-20T12:49:05Z</dc:date>
    </item>
  </channel>
</rss>

