QUOTE (pinklloyd @ Nov 1 2008, 06:02 AM)

APK,
Thank you so much for your response.
You're welcome, & I hope this helps you out... it's WHY I put this guide out for "normal folks" (& with the guidance of the CIS Tool, because it makes securing a system (not JUST Windows NT-based ones mind you either, but, also *NIX variants as well) as simple/easy as it gets, w/ out having to know a lot of the "internals" of Windows etc. et al) - it was part of my 2008 "New Year's Resolution", to "Do a good deed"...
QUOTE (pinklloyd @ Nov 1 2008, 06:02 AM)

I'm looking into it right now, let you know my outcome(score)

Well, you may not LIKE your score too much, & honestly? It's NOT that important...
Were I you??
I'd be more concerned with following the advisement of CIS Tool, & shoring up what it shows you.
The rest of the guide MOSTLY applies to end users & how to keep safeŽ online, by far, using some (well, I feel they are) common-sense measures, but, I also largely TRIED to explain WHY those suggestions work, with examples of attacks that used that which I warn folks about + how to stop it etc..
QUOTE (pinklloyd @ Nov 1 2008, 06:02 AM)

You're right about the internet going nuts. You know what i've also noticed is it's gotten worse with the economy.
Probably - people imo @ least? Well, MOST aren't "inherently evil" (for whatever that means) - I think they get caught in things they cannot keep up with or afford & turn to crime to survive them... but, what do I know?
I do agree with you here though, it has gotten much worse than it was circa 1994-2002 or thereabouts. From 2003 onwards, imo, it started up with all these hijacks thru webbrowsers, email, even other apps, & tons of "spam" mails etc. et al... @ least, WORSE THAN EVER BEFORE!
QUOTE (pinklloyd @ Nov 1 2008, 06:02 AM)

Do you use any type of communication/monitoring tools for windows?
TcpView is nice, it'll do PART of the job, but you have to be there to monitor it... so, you're probably looking for more, like something that works remotely & can signal you etc. et al remotely.
Anyhow - You can make the Windows firewall (& others) maintain a log you know, but, it is sort of a hassle to keep up on it, but, worth the doing nevertheless - especially on a server. This leads to another idea, not TOO hard to make either, that I lead into IF YOU WRITE CODE... later on though in this reply.
QUOTE (pinklloyd @ Nov 1 2008, 06:02 AM)

I'd truly like to stop some of these port scanners in their tracks but I can't seem to find anything that will recognize an ip scanning different ports and then block it.
Have you looked into "IDS" (intrusion detection systems)? They're more of that nature...
Myself?
I use a (on my home workstation @ least) combination of a hardware NAT true "stateful packet inspecting" linksys unit, with software firewall (Windows), packet filtering (easy to implement, it's in that guide), & IP Security Policies... if anyone can "blow thru that"? My hat's off to them... honestly.
QUOTE (pinklloyd @ Nov 1 2008, 06:02 AM)

That would be truly nice. I realize that most "TRUE" hackers use a compromised machine so finding the exact ip is almost impossible, stopping the scan in it's tracks shouldn't be that hard.
Closing available ports is what I'd recommend... & stopping ANY services you do NOT need to be running - especially those that maintain "LISTENING" status (a tool like TcpView can show you this much)...
QUOTE (pinklloyd @ Nov 1 2008, 06:02 AM)

Ok so we'd have to recycle through all the ip's every now and then but at least we can stop any immediate danger. I know their are "VERY EXPENSIVE" IDS or intrusion detection systems out their but who has a budget for that, not I.
I'm going to look into CIS Tools.
Heh, as I quoted you earlier? I mentioned/noted IDS's & you've already apparently looked into them (I don't read someone's FULL reply, I quote & reply as I go, not to miss any points they make as I go)
QUOTE (pinklloyd @ Nov 1 2008, 06:02 AM)

Thanks again! Seriously.
No problem - Good luck, & what I gave you is a start... but, that IDS stuff, though expensive, might tend to 'automate' much of what you're looking to do... but, IF you keep logs from say, your Windows Firewall, or a hardware based unit, AND you can code (or, someone you know can)?
Well, writing a program to parse a log file is NOT a big huge trick & then sending emails via say, SMTP is not another huge trick either... you can "rig up/home brew" a solution for that which can 'warn you remotely', pretty fairly easily...
APK