<?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: Scanning Cisco ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4828450#M581531</link>
    <description>&lt;P&gt;I'm still working with TAC on the issue. Have you guys figure this out?&lt;/P&gt;</description>
    <pubDate>Thu, 04 May 2023 10:27:26 GMT</pubDate>
    <dc:creator>Lyn17</dc:creator>
    <dc:date>2023-05-04T10:27:26Z</dc:date>
    <item>
      <title>Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4695504#M577450</link>
      <description>&lt;P&gt;Is there a way to scan Cisco ISE?&amp;nbsp; I'm not getting a credentialed scan even with my admin credentials.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Sep 2022 17:26:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4695504#M577450</guid>
      <dc:creator>Lyn17</dc:creator>
      <dc:date>2022-09-28T17:26:34Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4695563#M577451</link>
      <description>&lt;P&gt;Could you explain more about what you're trying to do and what you were hoping would happen?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Sep 2022 19:28:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4695563#M577451</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2022-09-28T19:28:19Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706465#M577838</link>
      <description>&lt;P&gt;Hi Damien,&lt;/P&gt;&lt;P&gt;I'm trying to get a credentialed scan on our ISE server using ACAS. I used my SSH credentialed and saw our ACAS scanner logged in using the credential I provided but when I checked Nessus Scan Information, it wasn't credentialed. Our cyber team and asking for a credentialed scan.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2022 10:52:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706465#M577838</guid>
      <dc:creator>Lyn17</dc:creator>
      <dc:date>2022-10-20T10:52:27Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706516#M577839</link>
      <description>&lt;P&gt;The ISE CLI isn't a normal Linux prompt.&amp;nbsp; The vulnerability scanner probably doesn't know how to parse it.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2022 12:23:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706516#M577839</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2022-10-20T12:23:10Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706550#M577843</link>
      <description>&lt;P&gt;A Nessus/ACAS credentialed scan will make certain assumptions about the target host. For a "Linux" host which ISE (somewhat) is, the assumption would be that your credentials allow you to login with root privileges.&lt;/P&gt;
&lt;P&gt;However, ISE does not allow customers access to the underlying RHEL Linux operating system (either as root or any other user). That is only possible with a time-limited root patch that is used exclusively by Cisco TAC.&lt;/P&gt;
&lt;P&gt;Logging in to ISE as an admin user only give admin (full) access to the ADE-OS (Application Development Environment - Operating System) that is an abstraction layer "above" the Linux OS.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2022 13:18:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706550#M577843</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-10-20T13:18:00Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706570#M577845</link>
      <description>&lt;P&gt;Thanks for the response. Yes, I think that is what's happening. I can see the credential that I provided being used to SSH to ISE but I'm getting a non credentialed scan everytime.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2022 13:44:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706570#M577845</guid>
      <dc:creator>Lyn17</dc:creator>
      <dc:date>2022-10-20T13:44:46Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706607#M577847</link>
      <description>&lt;P&gt;Thanks for the response Marvin.&lt;/P&gt;&lt;P&gt;So, it's not possible to do a credentialed scan on ISE itself without the Cisco TAC involvement?&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2022 14:24:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706607#M577847</guid>
      <dc:creator>Lyn17</dc:creator>
      <dc:date>2022-10-20T14:24:29Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706614#M577848</link>
      <description>&lt;P&gt;No, and I don't think TAC will agree that this a valid use-case for a root patch.&amp;nbsp; Why do you feel the need to scan your ISE nodes?&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2022 14:30:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706614#M577848</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2022-10-20T14:30:48Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706620#M577849</link>
      <description>&lt;P&gt;Like &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199513"&gt;@ahollifield&lt;/a&gt; said - no you&amp;nbsp; CANNOT do a credentialed scan, even if you ask the TAC.&lt;/P&gt;
&lt;P&gt;The root patch is only for TAC troubleshooting and uses an ssh key that they will not share with the customer. That's by design to keep the system more secure and not allow unauthorized changes (including things that a credentialed scan might do!)&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2022 14:41:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706620#M577849</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-10-20T14:41:41Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706630#M577851</link>
      <description>&lt;P&gt;Personally, I don't think it's necessary, but I need to answer to our cyber team why ISE is not getting a credentialed scan.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2022 14:54:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706630#M577851</guid>
      <dc:creator>Lyn17</dc:creator>
      <dc:date>2022-10-20T14:54:27Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706634#M577853</link>
      <description>&lt;P&gt;I would tell them it's a secure appliance and the vendor does not support customer access to the underlying operating system.&lt;/P&gt;
&lt;P&gt;(nice way of saying "go pound sand")&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2022 15:00:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4706634#M577853</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-10-20T15:00:32Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4793985#M580471</link>
      <description>&lt;P&gt;Don't think we are doing anything different but we are able to get credentialed scans, most of the times. Makes sense what it was said before about the Linux OS vs the&amp;nbsp;&lt;SPAN&gt;&lt;SPAN class=""&gt;ISE ADE-OS... When the scanner recognizes the&amp;nbsp;ISE ADE-OS then we get credentialed scans... when it thinks is a linux box then we don't.&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2023 19:05:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4793985#M580471</guid>
      <dc:creator>hector.l.rivera11</dc:creator>
      <dc:date>2023-03-14T19:05:33Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4813911#M581137</link>
      <description>&lt;P&gt;I was able to get a credentialed scan by adding the identity store. Unfortunately, after the upgrade to version 3.2, I'm back to not being able to get a credentialed scan even after double checking that everything on our DC side and domain user account hasn't changed. What version are you using?&lt;/P&gt;</description>
      <pubDate>Thu, 13 Apr 2023 16:11:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4813911#M581137</guid>
      <dc:creator>Lyn17</dc:creator>
      <dc:date>2023-04-13T16:11:01Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4813916#M581138</link>
      <description>Good morning,&lt;BR /&gt;&lt;BR /&gt;We started having issues once we upgrade to 3.2 ourselves. I'm working with&lt;BR /&gt;our ISE SME to see if we can fix it.&lt;BR /&gt;</description>
      <pubDate>Thu, 13 Apr 2023 16:26:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4813916#M581138</guid>
      <dc:creator>hector.l.rivera11</dc:creator>
      <dc:date>2023-04-13T16:26:27Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4813966#M581140</link>
      <description>&lt;P&gt;I opened a ticket with TAC. Can you let me know if you guys fix it and what the solution would be?&lt;/P&gt;</description>
      <pubDate>Thu, 13 Apr 2023 17:29:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4813966#M581140</guid>
      <dc:creator>Lyn17</dc:creator>
      <dc:date>2023-04-13T17:29:37Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4813970#M581141</link>
      <description>Will do&lt;BR /&gt;</description>
      <pubDate>Thu, 13 Apr 2023 17:37:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4813970#M581141</guid>
      <dc:creator>hector.l.rivera11</dc:creator>
      <dc:date>2023-04-13T17:37:27Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4828450#M581531</link>
      <description>&lt;P&gt;I'm still working with TAC on the issue. Have you guys figure this out?&lt;/P&gt;</description>
      <pubDate>Thu, 04 May 2023 10:27:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4828450#M581531</guid>
      <dc:creator>Lyn17</dc:creator>
      <dc:date>2023-05-04T10:27:26Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4828727#M581534</link>
      <description>Not yet, we are still working on the issue. Will let you know if we are able&lt;BR /&gt;to fix the issue.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Hector&lt;BR /&gt;</description>
      <pubDate>Thu, 04 May 2023 14:54:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4828727#M581534</guid>
      <dc:creator>hector.l.rivera11</dc:creator>
      <dc:date>2023-05-04T14:54:39Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4835661#M581751</link>
      <description>&lt;P&gt;I'm still t/s the issue with TAC.&lt;/P&gt;</description>
      <pubDate>Mon, 15 May 2023 15:20:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4835661#M581751</guid>
      <dc:creator>Lyn17</dc:creator>
      <dc:date>2023-05-15T15:20:32Z</dc:date>
    </item>
    <item>
      <title>Re: Scanning Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4855220#M582256</link>
      <description>&lt;P&gt;Hi Hector,&lt;/P&gt;&lt;P&gt;Update: The two plugins that's causing the uncredentialed scan for ISE:&lt;/P&gt;&lt;P&gt;The 2 plugins most relevant in this case are 97993 &amp;amp; 12634.&lt;BR /&gt;&lt;BR /&gt;Output of Plugin &lt;STRONG&gt;97993&lt;/STRONG&gt;:&lt;BR /&gt;&lt;BR /&gt;It was possible to log into the remote host via SSH using 'password' authentication.&lt;BR /&gt;&lt;BR /&gt;The remote host is &lt;STRONG&gt;not currently&lt;/STRONG&gt; supported by this plugin.&lt;BR /&gt;&lt;BR /&gt;Output of Plugin&lt;STRONG&gt; 12634&lt;/STRONG&gt;:&lt;BR /&gt;&lt;BR /&gt;It was possible to log into the remote host using the supplied&lt;BR /&gt;password.&lt;BR /&gt;&lt;BR /&gt;The output of "&lt;STRONG&gt;uname -a&lt;/STRONG&gt;" is :&lt;BR /&gt;Failed to log in 6 time(s)&lt;BR /&gt;Last failed login on Tue Jun 13 08:20:21 2023 from 172.20.33.59&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jun 2023 12:55:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/scanning-cisco-ise/m-p/4855220#M582256</guid>
      <dc:creator>Lyn17</dc:creator>
      <dc:date>2023-06-15T12:55:38Z</dc:date>
    </item>
  </channel>
</rss>

