<?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: Uncredential scan on Cisco ISE - Nessus Scanner in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4813980#M581143</link>
    <description>&lt;P&gt;Why do you wish to do this?&amp;nbsp; ISE is a hardened appliance based on Linux but its shell is not a normal Linux shell.&lt;/P&gt;</description>
    <pubDate>Thu, 13 Apr 2023 17:48:36 GMT</pubDate>
    <dc:creator>ahollifield</dc:creator>
    <dc:date>2023-04-13T17:48:36Z</dc:date>
    <item>
      <title>Uncredential scan on Cisco ISE - Nessus Scanner</title>
      <link>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4813906#M581136</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I just upgraded our ISE from 3.1 to 3.2. Before the upgrade, I'm able to scan get a credential scan using a domain user account on ISE with ACAS. However, after the upgrade, I'm no longer able to get a credential scan using the same domain user account. I already have a ticket open with TAC, but I'm just checking if anyone here have had the same issue and was able to resolve it.&lt;/P&gt;&lt;P&gt;Thanks in advanced.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Apr 2023 16:05:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4813906#M581136</guid>
      <dc:creator>Lyn17</dc:creator>
      <dc:date>2023-04-13T16:05:53Z</dc:date>
    </item>
    <item>
      <title>Re: Uncredential scan on Cisco ISE - Nessus Scanner</title>
      <link>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4813926#M581139</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;- Check ISE &lt;STRONG&gt;logs&lt;/STRONG&gt; related to the credential scan process &lt;STRONG&gt;&lt;U&gt;(e.g.&lt;/U&gt;) ,&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Apr 2023 16:42:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4813926#M581139</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2023-04-13T16:42:30Z</dc:date>
    </item>
    <item>
      <title>Re: Uncredential scan on Cisco ISE - Nessus Scanner</title>
      <link>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4813980#M581143</link>
      <description>&lt;P&gt;Why do you wish to do this?&amp;nbsp; ISE is a hardened appliance based on Linux but its shell is not a normal Linux shell.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Apr 2023 17:48:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4813980#M581143</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-04-13T17:48:36Z</dc:date>
    </item>
    <item>
      <title>Re: Uncredential scan on Cisco ISE - Nessus Scanner</title>
      <link>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4814007#M581146</link>
      <description>&lt;P&gt;We need it for DoD compliance. Our cyber and validator need to have the nessus scan files for the ISE servers.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Apr 2023 18:48:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4814007#M581146</guid>
      <dc:creator>Lyn17</dc:creator>
      <dc:date>2023-04-13T18:48:48Z</dc:date>
    </item>
    <item>
      <title>Re: Uncredential scan on Cisco ISE - Nessus Scanner</title>
      <link>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4814658#M581165</link>
      <description>&lt;P&gt;What are they looking to find?&lt;/P&gt;</description>
      <pubDate>Fri, 14 Apr 2023 17:56:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4814658#M581165</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-04-14T17:56:55Z</dc:date>
    </item>
    <item>
      <title>Re: Uncredential scan on Cisco ISE - Nessus Scanner</title>
      <link>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4814987#M581174</link>
      <description>&lt;P&gt;Likely&amp;nbsp;CSCwd51409, which is resolved in ISE 3.2 Patch 1.&lt;/P&gt;</description>
      <pubDate>Sun, 16 Apr 2023 00:00:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4814987#M581174</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2023-04-16T00:00:13Z</dc:date>
    </item>
    <item>
      <title>Re: Uncredential scan on Cisco ISE - Nessus Scanner</title>
      <link>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4815902#M581187</link>
      <description>&lt;P&gt;Vulnerabilities and/or bug such as CSCwd51409. There was a vulnerability (medium) on ISE that's the reason why I upgrade to 3.2 Patch 1 to resolve it. Unfortunately, after the upgrade, the CLI join domain was broken and I can no longer do a credential scan our 2 ISE nodes.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Apr 2023 11:05:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/uncredential-scan-on-cisco-ise-nessus-scanner/m-p/4815902#M581187</guid>
      <dc:creator>Lyn17</dc:creator>
      <dc:date>2023-04-17T11:05:15Z</dc:date>
    </item>
  </channel>
</rss>

