In the latest version of Nessus (6.9.1), the equivilant policy appears to be 'Internal PCI Network Scan' - however the compliance options and plugins are not visible. Any ideas how are you supposed to determine exactly what the scan is going to do before running it?
I haven't used Nessus for a few years. It used to be the case that the built-in PCI policy which at that time was called 'Prepare for PCI-DSS Audits' (mention on this InformationExchange forum post: http://security.stackexchange.com/questions/35922/nessus-html5-version-5-0-3-pci-scan) you could view the compliance options and plugins (all plugins were enabled by default).
@bob thanks Bob. That's steered me in the right direction. Without reinventing the wheel, I can just come up with a solution using the common file dialogue.
OK - tested it. Created a directory and gave administrators group permissions only. Using an account that is a member of administrators, launched Windows Explorer normally, tried to open the folder and as expected got the warning that "You don't currently have permission to access this folder".
OK, correction - the option is still present in Windows 7. But apparently after Windows Vista you can no longer run explorer elevated. At least not without some hackery. That's according to this post: social.technet.microsoft.com/Forums/windows/en-US/… "...explorer has a component which blocks every request to elevate the Explorer."
Basically any third party file explorer would do the trick. The only reason Windows Explorer is useless is because it's related to the explorer.exe shell.
@Bob As it's not possible to run an elevated instance of Windows Explorer, I was hoping that I could run IE elevated and use to navigate directories. Not being able to run Windows Explorer elevated is problematic on a system with UAC enabled.
I'm sure it used to be possible to browse directories using Internet Explorer. It behaved just like Windows Explorer. When I attempt to navigate to C:\ or C:/ it just launches a Windows Explorer window. Anyone know if this is still possible?
I don't like code that relies on the error handler to get you out of trouble. You should think about all possible scenarios and cater for them. When something calls the error handler - see if you can use pre-emptive checking to avoid that ever happening again.
I always write code that avoids jumping to the error handler when a condition isn't satisifed. EG, need to write a file to C:\blah - then check that the path jolly well exists first. Don't just jump to the error handler.
@RubberDuck Did you find a legitimate case for fixed length strings? Something I'm often asked is why VBA has subs and functions, why not always use functions and simply don't set a return value if you don't need one. Yet I continue to use both...