Active Directory Starter Scan  Background As part of our...

@Jesus Galan​ 

So I am guessing if we wanted to scan multiple AD/DC's when we setup the credentials in the policy under Authentication>Misc>ADSI we would need to have an entry for each server we setup in the active scan under targets?

Also, if we are using port 636 rather than 389 is the policy/scan smart enough to figure that out? All the Tenable.SC documentation I can find only references port 389 when using the ADSI creds. I can't find anything about being able to specify port 636.

Lastly, are there any efforts being worked by tenable to allot the use of "managed" credentials? If we use an integration with an IAM Tool to manage credentials is Tenable working on a solution to allow the use of the managed creds in the policy or via the active scan like all other creds? Do we need to open a feature request for something like this?