Forum Discussion
Anonymous
5 years agoActive Directory Starter Scan Background As part of our...
Active Directory Starter Scan Background As part of our endeavor to help reduce our customers’ cyber exposure, we are releasing a Starter Scan template along with plugins that will peel the onion ...
scott_hislop
5 years agoConnect Rookie
It's frustrating that you have to search the community discussions forum to find out how to use new features like these :-(
Here's how I got it working in Tenable.sc:
- Create a new policy using the Active Directory Starter Scan template (eg. called ADSCAN).
- Accept all the defaults for Port scanning, Assessment and Results tabs.
- On the Authentication tab, click Add Authentication Settings and choose type=Miscellaneous then ADSI, then click Select.
- For Domain Controller, I enter the FQDN of a DC near one of my managed Nessus scanners.
- For Domain, I entered the NETBIOS domain name.
- For Domain Admin, I entered the samaccountname of a domain administrator account, and then obviously the password in the Domain Password field.
- Click Submit to save the policy.
- Then create a new Active Scan.
- Give it a name and for the Policy, select the policy created above (ie. ADSCAN)
- On Settings tab, I just import into my normal repository for vulnerabilities.
- On Targets tab, I specified the same FQDN of the DC used in step 4 above.
- On Credentials tab, I chose the credential that I know has Domain Admin rights (same one I used in step 6 above).
- Click Submit to save the scan.
- Run the scan and then view the results.
It seems to only fire one of the new plugins when something bad is found, so for me, I didn't get results for all 10 new AD plugins - only a few.
Hope this helps someone else.