blamethenetwork:
Thanks for the insight. Any other ideas on anything other than the first paragraph? AV is a major concern, but I am also hoping to find methods to detect any holes in my client's boat.
Main Topics
Browse All TopicsWhere to begin; I am going to be running a security audit on a client's network. The client has yet to decide on any antivirus solution due to cost constraints. Being their project is nearly finished, a cost effective solution for AV would be useful. They are actually considering to rely on the Firewall's built-in AV and the end-user's AV installed locally. Their thoughts are to save money and keep a reduced load on a bloated server.
I am looking for those "expert" tips that may come in handy. Useful tools for security auditing would also be appreciated. This being my first audit, I am slightly intimidated by putting my seal of approval on the final product. With that said, I'd greatly appreciate any help, but I do ask that if you do provide a suggested solution, please explain and be as descriptive and detailed as possible.
Network Details:
Server 2003 Std.
Exchange Server 2003
Hosting Exchange Server with Webmail (No SSL)
WiFi available on wireless-g signal WPA-2
Print Server (20 Printers)
DHCP Server
Terminal Services enabled and broadcasted to WAN (No VPN)
20-30 connected workstations internally
3-5 users connected remotely (5, being maximum and highly unlikely)
Sonicwall Firewall TZ 170 (Ehanced Firmware)
DMZ available but not in use
Using all content-type filters for web and email
Using wide variety of NAT and Routing policies (Suggestions on frequent holes would be appreciated)
VPN is available and configured, but not used due to several technical issues (Client is considering new end point)
5 inbound global IP addresses being monitored
Logs filed and cataloged very intensively
DHCP server on firewall is disabled and pointing to DHCP server listed above
Desire for site-to-site VPN may be a possibility
Backtrack 4 Live CD is of interest, but I have very limited knowledge of it's functionailty and capabilities. Is this a good tool to audit a Windows environment with?
I am more than willing to consider purchasing any software or hardware that may be of great use.
I will provide more details as they are requested. Thanks for taking the time to look at this, and I am eager to hear suggested.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
blame-
Me:
"Backtrack 4 Live CD is of interest, but I have very limited knowledge of it's functionailty and capabilities."
You:
"If you know linux there are some very powerful network tools, and intrusion detection available. What exactly are you looking to try on this network?"
I'm not sure if my question is not specific in point, or if you did not read it entirely. Please do not take offense, as I do respect anyone who takes the time to view my questions, but I am not sure of how to word my question anymore specific. Perhaps, I should have asked, "Will my client's network be hacked from the outside world?" I am simply wanting to quite literally attack my client's network in an attempt to either crash it or simulate an attack and monitor the firewall logs to ensure that their network is protected. If the firewall fails, I would also want to then attempt any tactics used to get into the server itself. LOL. Perhaps I should have asked, "How do I hack my own client's network before someone else does."
LOL I like that response. So you are looking for a penetration test. If you want a very general firewall test shields up ( https://www.grc.com/x/ne.d
This is a good utility, but I want to hit my server externally from a comptuer that I am controlling. This website requires firewall being scanned to request the scan. I want to scan the firewall from my own computer, plus I want my computer to be outside of the firewall and ISP completely. I want to test this from a cell card.
NMap.
http://nmap.org/
Is my tool of choice.
stlbridge,
For a good continues security scan Nessus comes to my mind. It actively scans the network for unpatched machines and other security holes. You might want to check it out, it's not very cheap though for a small company.
Regards,
LucF
Wyliecoyoteuk, I have used nmap. It's pretty handy, but very cryptic. Any other thoughts?
Thanks for your input.
LucF,
I want to scan externally just as someone who was actually attempting to hit my server would. The tool does seem to be very useful, but I want to use the same tools that most others would use from the outside world.
stlbridge,
Simply said, you don't know what other people from the outside world would use.
Maybe they setup a website which exploids a certain security hole in the browser used and one of the users accidently opens that site.
The idea of "people trying to access your network specifically" should go, for example botnet owners don't care where the computer is located, as long as they can use it. Most likely they don't even care about the data on the systems themselves but you surely don't want to have them in control of your computer.
You need to make sure the systems are patched for all known vulnerabilities.
LucF
Why worry about a DoS? It's not like you can stop it at your end if it's a decent one. A bandwidth consuming DoS will have to be taken care of at your providers routers, as soon as it reaches your WAN connection you're off the net anyways.
If a simple WAN request would trigger a DoS without consuming your bandwidth, it means a security issue on which a patch is most likely already available. Therefor, again the need to check for patches on the systems.
LucF
stlbridge,
I'm guessing you might want to read all my comments again, in no way I'm suggesting that patching is the solution to everything. What I'm trying to explain is that your way of thinking about security is far from reality.
Just for the fun of it, as I see several port scanners mentioned. Would you feel more secure with your Windows XP SP2 computer with enabled firewall connected directly to your modem (which will give you "full stealth" on most tests) or behind a $5000 IDS/IPS which is correctly configured (which might have some open ports as they're needed to serve services)
LucF
Are you suggesting that a hardware firewall is inferior to Windows Firewall? I realize that I am the one asking the question, and I don't mean to seem confrontational, but I do not see your logic. If you could explain further? I feel like I'm asking a question that is almost impossible to answer, but then again, it seems so simple of a question- How would a hacker attempt to destroy my server? What methods would he use? This seems black and white, yet it isn't?
stlbridge,
This will be my last attempt at trying to make you take another look at security as you obviously don't like my replies, it's not just what you can spot from the internet side. In none of my comments I've ever doubted your idea of doing the best you can, however you've been showing that you do the best you know.
1) Why would a "hacker" want to destroy your server?
- You make backups don't you? So they can't.
- If a hacker manages to take ownership of your server with a decent bandwidth, don't you think they have better uses for it?
2) If a "hacker" would even want to destroy your server, why take the difficult route?
- Users accessing that server are very likely to make mistakes (visiting the wrong website, giving their passwords to others etc.)
3) This isn't black & white at all.
- You can make your system seemingly from the internet as secure as you want. Just pull the ethernet plug from your Modem.
- Users will still be able to accidentally leak information even though they don't know it.
Please let me know your thoughts.
Regards,
LucF
stlbridge,
You need to absolutely understand that 'patches' are a critical part of any security audit.
I have done more security audits than I have hair on my head (inside joke) and had available every tool in the IT world.
The first - the very first - test in every audit I have ever done is to verify that the OS patches are ALL in place - on every box on the network - and that every box is current with whatever AV solution is being run.
Also, please back down off your high horse and read Luc's last comment again. He knows more about hardware security than about 99.9% of the people on the planet - and has proven that he is will to help you - so you might demonstrate that you're actually willing to listen (read).
stlbridge,
Most tests can be done easely.
For example patches can be checked on the WSUS console (in case WSUS is used) or as an alternative, you can check some systems for automatic updates and if they've been configured correctly. Or if an alternative logon script (KIX for example) is used, proof that it's being pushed to every workstation.
The same counts for antivirus solutions, if a company grade solution is used there will be a central console which can be checked for all updates.
In the end, of course a portscanner will be able to sort out if servers aren't listening on unusual ports (which might actually indicate an intrusion which has already taken place)
Sadly, the easy portscans will only show what is listening and maybe what's behind them. Not the security issues which might be on the applications operating on those ports.
LucF
Younghv
Thanks for the input. I suppose I am slightly irritated due to the lack of responses that actually answer my question. I do not mean to come across as an angry kid. I am simply curious as to how I can establish my client's current status in relation to WAN security. I clearly spell out what is going on with their network, but for whatever reason, I'm not geting an answer to what I had thought was mapped out rather nicely. I want to learn more, but I'm obviosly not seeing this from the right angle, and I think that the mindset of security precaution needs to be viewed not only from we-the admin side, but also the "hacker's" perspective. That's what I'm trying to get in tune with. From what I understand, many of IT Security's greatest minds were at one time some of the greatest and most dangerous "hackers".
WIth that little rant said, where could an educated mind point me? And when I ask that, I also mean, where can I be directed that will not only answer my questions, but also provide information that I haven't even asked for yet (that way I can quit bothering the experts here).
Now, I realize that I have a problem with coming across as a complete pr*ck, but I assure you that I mean no kind of sarcasim nor rudeness in this comment. LOL, that should be my new signature.
It seems that I appear to be asking, "What's the trade secret to network security?" I am very eager to learn and do appreciate the help I am getting, but at the same time, I do not care
Here's an easier question, that I think I should have asked. If my client's server is backed against the internet with RDP enabled without any other security than windows logon, how long will it take? Furthermore, how can I see the failed BF attempts that are made? This would have been a better way for me to put this. So it goes:
Remote Computer -> Connect to TS (also mail server) via Global IP -> Hits Firewall -> NAT Pushes 3389 to TS/Mail Server. Windows Logon is displayed with the Administrator as the username predefined.
Password is very strong, but how strong is "strong"? It's the last line of defense, as far as I am concerned. So, how can we keep this more secure without VPN due to VPN not being an option at all (don't ask).
I will see you nerdy guys tomorrow. Thanks for being paitent with a security novice!
stlbridge,
>> It seems that I appear to be asking, "What's the trade secret to network security?"
I'm sorry to say this, but it's not something I can teach you. It's a thing you learn by doing it and making mistakes. If an auditor tells you things about which might cause an issue (now or in the future) listen to it and act on it.
Making mistakes is an option.
This might sound weird, but it really isn't. Every administrator, and probably you're not an exception on that, will learn to set up multiple layers of security (authentication, authorization, encryption, etc.) so if one appears to have a problem, no harm is done yet. The problem is fixed and the security was up-and-running even though an issue was found.
LucF
>> Remote Computer -> Connect to TS (also mail server) via Global IP -> Hits Firewall -> NAT Pushes 3389 to TS/Mail Server. Windows Logon is displayed with the Administrator as the username predefined.
There's a mistake, not a real security issue yet. You should setup the terminal server not to show any username on the login screen and change the administrator account to a different name so you don't give away 50% of the authentication which would lead to authorization.
An option on this one will also be to disallow the access for a couple of minutes after every failed logon attempt. (Tools are available to do this) which will highly limit the amount of passwords which can be tried in a certain timespan. A brute-force attack will have less to zero chance on getting the password before being spotted. Bad logon attempts can easely be checked through the event viewer.
However, keep in mind that what you mentioned an example, other issues may appear with other servers which may or may not be connected to the internet.
LucF
In my experience, one of the greatest sources (huge reading requirement) starts with Carnegie-Mellon CERT (http://www.cert.org/cert/
Another is from SANS (http://www.sans.org/)
Both have large reading rooms and a lot of pre-built systems/process checklists that have been used by many thousands of SysAdmins trying to do just what you are.
During all of the years that I did Network Security, I would always spend 8-10 weeks (every year) in formal training sessions learning the latest tricks of the trade and learning how to use the new tools that were available.
/Opinion
The success of any Security Audit will depend more on the evaluation of people/procedures, than on the physical side of things.
Almost everything you need to know about the devices can be done for you with the tools available (Google network security tools), but the success of your endeavor will be focusing on what the people are actually DOING.
/end Opinion
You're in great hands with Luc, so I'm going to find something easy to work on.
Good luck with you audit - a job that never ends.
The best I've ever used was iPrism from StBernard software for web monitoring.
http://www.stbernard.com/
Email monitoring can get pretty complicated with the laws of various countries/states and we never used any in the U.S. Military.
Since I got an EE warning on this: my 5 cents.
First of all, since you get the inside information of your client you should start by reviewing the security architecture.
The way I read the information provided, this is already seriously flawed. If one of the publically available servers gets compromised, the attacker is immediatly inside the private network. There is no seperation, a situation where you do not want to be in. I understand budget constraints, but this most certainly must be made clear to your customer.
Secondly, again since you have internal access: review the security configuration against the different security guides and best practices (to be found at Technet, since this seems to be a MS environment). Correct hardening is the second most important defense (disable unneeded services, least privilege principle for accounts used (including user accounts), disable or lower privileges ...). These are easy to review using the guides.
I said that hardening is the second most important, because - and this has already been mentioned - patching is primordial. And WSUS is free.
So next to an external scan both above recommendations are very important to be able to explain the scan findings. This will provide the "What is wrong" and "how can it be improved". And it will provide insights which an external scan can never show.
On terminal server directly on the internet: Currently there are only 2 vulnerabilities known for TS 2003: a man in the middle attack - even implemented in a well known white hat testing tool - but extremely hard to execute over the public internet, and a DDOS.
If this is not a high secure environment and no legal or industry requirements are prohibitting this then your client may accept the risk. Otherwise, access it through VPN to mitigate the MITM attack.
kr, J.
Stlbridge, yes it is against the policy of EE. In the past if have been slapped for this. I do not agree with security through obscurity, as the bad guys do have this knowledge. Sadly enough EE does not agree with me, we had our discussion in the past and I have up on that part rather then stopping to share information. Since I can not provide it here, this is one exception where you can mail me on my private email for the information. See my profile for my address.
Younghv, thanks for the kind words. But English is only my third language. You should hear me in Dutch or French :-p
Well, my French speaking colleagues would not agree but I find English a very 'expressive' language and it is my preferred one. Even above my mother tongue Dutch, although they are very close.
kr, J.
stlbridge,
I'll post this in English - since we all appear to be conversant.
Your method of closing this question is flat wrong.
You have been around EE long enough to understand the protocol for what to do when multiple Experts contribute to a conversation.
I don't have any expectations that you will now do the right thing, but that is your loss.
Business Accounts
Answer for Membership
by: blamethenetworkPosted on 2009-03-24 at 08:46:14ID: 23969574
I would recommend avast, www.avast.com as an inexpensive AV solution. It has some great features and catches more potential threats then McAfee, and is more reliable then AVG.