Slashdot Mirror
Security Probes for New Clients?
archaic0 asks: "I've recently acquired a new client (I do on call tech work for several companies where I live) who have requested a security audit. In the past I've hired several friends (self-proclaimed security consultants) in the industry to run various exploits and tests for me, but due to the time involved and the cost, I'd like to find a short introductory type option to start a new client off with. I recently ran across a program called Retina, by eEye, and I'm quite impressed however it comes with a $1400 price tag per use (or $14,000 a year for a bulk license). Can anyone point me to tools they've used to do a pretty well-rounded security scan that can produce detailed reports? I know there is no substitute for a real security professional spending time confirming your network security, but I'd like to have at least one good tool to start a new client off with before throwing a huge security team at them."
My company recently purchased an SSL cert from verisign and recently received an email from http://www.qualys.com (in conj. with our purchase) to perform a web based security scan of internet facing machines, such as web servers. The results and demo reports appeared a bit better than our usual Nesus vulneravility scan, however, Qualsys is not free. Try these tools out, for web servers, they have done quite well for my end.
Good free ones: nessus, nmap, nikto. Besides Retina, look at Foundstone. There is also Qualsys, nCircle and several others (search for vulnerability assessment tools). Make sure that you understand the network topology, especially if firewalls & routers are involved. There are also host-based scanning tools designed to be run on individual systems, primarily to harden them.
Not "Nuff said." Any security person who uses only one tool is a damned fool!
He who laughs last is stuck in a time dilation bubble.
[links not provided: it is assumed you can google]
First you'll want "nessus" -- this scans and attempts to exploit vulnerabilities. Comes complete with up-to-date 'signatures' for attacks to ensure that systems are patched or that firewalls are blocking access.
Second you'll want "GFI Languard" and run that to scan the internal Windows PCs -- it will give a nice report of each machine and patches needed (assuming you've got approval and admin access on the domain). This costs like $1k, but has a 30 day free trial to get the client started. Can also be used to deploy patches.
If you don't want to use Languard, which is really quite a bit better, you should at least use Microsofts "Baseline Security" tool. Again, requires admin access, but gives a nice report for each machine you scan.
nmap is nice to document open ports on machines, particularly so-called DMZ or other firewalled internet-accessible hosts.
dsniff is a good tool to watch for insecure protocols. Always fun to report that everyones pop3 password seems to be the same as their domain login password.
lopht crack is good to give a baseline indication of how secure user passwords are. Run it for a set amount of time -- 1 hour say -- using all of the passwords found by dsniff over a day or two as part of it's dictionary.
There's a lot more to do -- check routers etc. for default passwords, war-dial all phone numbers of the company looking for rogue modems and more default passwords, etc. But the tools above should give a pretty good start.
All of these tools produce reports in some flavor, which you can then combine manually. I assume the client is paying you for the report, so some manual effort is OK.
Make sure to push for a 'follow-up' audit after the client has remediated the problems.
"But actually trying to use m4 as a general-purpose langage would be deeply perverse" --ESR
war-dial all phone numbers of the company looking for rogue modems
Combine this with talking each answering person into giving their authentication information. I understand the easiest way to achieve that is by telling them you are hired by their company to make a security audit and said authentication information is necessary to point out flaws in their IT security. Not like I were experienced in the field but that's what they keep telling 'round the 'net, Mr. Mitnick for instance.
Have fun!
I think, therefore thoughts exist. Ego is just an impression.
A proper security audit shoud include a vuln assessment from the internet, but how about
1. Dial in lines..
2. social engineering - ring someone and say "Hi I'm the new guy in IT and I've been asked to check everyones password, can I have yours". Ring the IT dept, "Hi I''m fred from xyz sales inc. we sell firewalls (or whatever) can I spend a few minutes talking about your network security" amd so on.
3. Do they have a security Policy. How to they enforce the policy.
4. What about disaster recovery?
5. What happens when the senior IT security is on holiday/off sick and you get a reported breach?
6.
Security is a process, not a product (no, I didn't make that up - check Bruce Schneier's company).
Security is a fairly wideranging topic, and involves at least half a dozen different, highly specialized disciplines. You may not need to be particularly thorough in all of them, but if you follow the great advice to use Nessus for network scanning, you may not realize that your client has left a gaping big hole in their ASP code which will allow arbitrary database requests to be executed against your client's database.
Or, you could have tightened down your network and website, but have no protection against viruses or worms on the desktop. Or there may be a wifi point allowing access to all and sundry. Or the server room may be accessible from the kitchen where many casual staff work. Or your client's CEO's daughter's boyfriend might have access to his PC with a VPN connection that automatically starts without prompting for a password....
So, yes, it's a good idea to use automated tools to do a basic audit. Nessus is good. You could do worse than read "Hacking Exposed" - it mentions a lot of good tools, both free and commercial, as well as the basic process for conducting a security audit.
However, make sure your client realizes that a clean bill of health (or fixing the issues your tools reported) does not mean they are "safe", (nor that they can sue you for any breaches that might occur), but rather that their organisation is not vulnerable to the attacks you tested for. If you didn't "test" hiring practices, they have no idea whether they are protected against employee fraud (which is still by far the most common form of computer crime). If you didn't "test" their virus protection policy, they have no idea of how exposed they are to the next email worm.
And of course, you are never "safe" - new threats emerge every day, and a server that was as safe as Fort Knox yesterday might be more like a crackhouse when the latest spl0it is released. So it's an ongoing process - assess, evaluate, repair, repeat & rinse.
Now, if your client is a small local firm with family members as employees, who use computers only for non-critical tasks, the "we'll run Nessus once a month" approach might be okay. If they are - oh, say, Microsoft...- that approach is clearly not sufficient.
Think about the interests of your client - not just in terms of saving them money, but protecting them from risk.
It's all very well in practice, but it will never work in theory.
Frankly, if you have to ask these questions, you should shy away from offering security consulting. Pay someone that lives, eats, sleeps and breathes IT security and you'll serve your customer better. I do IT security work (and only IT security work) for a living. I don't know how many times we've gone into a company that paid someone to do a security assessment, asked to see the previous report and been handed the stock report that NessusWX generates. Invariably when we do our work and write our report detailing the risks the customer feels their previous 'security consultants' cheated them. Often we find massive security issues that for one reason or another the automated scanners don't pick up. It won't do your reputation any good to do a poor job. The ability to do proper analysis is not a black art, but it becomes easier with experience and study.