04-13-2023 09:05 AM
Hi everyone,
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.
Thanks in advanced.
04-13-2023 09:42 AM
- Check ISE logs related to the credential scan process (e.g.) ,
M.
04-13-2023 10:48 AM
Why do you wish to do this? ISE is a hardened appliance based on Linux but its shell is not a normal Linux shell.
04-13-2023 11:48 AM
We need it for DoD compliance. Our cyber and validator need to have the nessus scan files for the ISE servers.
04-14-2023 10:56 AM
What are they looking to find?
04-17-2023 04:04 AM - edited 04-17-2023 04:05 AM
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.
04-15-2023 05:00 PM
Likely CSCwd51409, which is resolved in ISE 3.2 Patch 1.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide