OK, for those of you that have "moved on" to VISTA (or Windows Server 2008 & Windows 7),
as I have recently, in my now using Windows 7 64-bit here? (For around 2++ weeks now or so, in using Windows 7 here, & doing well thusfar, @ least)
WELL - here is what I have done so far to help secure Windows 7 more:BACKGROUND: Since this guide was originally intended for folks with a SINGLE SYSTEM online (or many via a router, but NOT "networked together" via Active Directory (or, otherwise) for File/Folder & Print Sharing for example/for instance),
this too is intended for that SAME kind of "audience", albeit, in regards to Windows 7 (again - I use the 64-bit model of Windows 7 here, but this ought to be fine for 32-bit users as well)
====
Start up SERVICES.MSC (You will need this for turning on/off various services is why)
1.) Turn off the SERVER service (this also aids in making you less vulnerable to the CONFICKER bug out there too, because this service "publishes" shares on your system) - in turn in making you more secure, this also lessens another service that you DO NOT NEED TO BE RUNNING, period, when you are a "standalone single machine @ home connected to the Internet" - do NOT do this if you are part of a LAN/WAN though, you need it in those environs typically
... I also run this .cmd "batch file" on Windows 7 @ my startup (via a shortcut that loads it & runs it minimized):
echo off
NET SHARE C$ /DELETE
NET SHARE B$ /DELETE
NET SHARE D$ /DELETE
NET SHARE E$ /DELETE
NET SHARE F$ /DELETE
NET SHARE G$ /DELETE
C:
NET SHARE ADMIN$ /DELETE
NET SHARE IPC$ /DELETE
NET SHARE DFS$ /DELETE
NET SHARE COMCFG$ /DELETE
NET USE * /DELETE :REM last line is to force complete read of HOSTS file into RAM, that domainname/hostname is the last line in it... apk
ping zzzz.hostindianet.com
That removes shares (just in case, overkill yes, but still, just being safe) & FORCES my system to load my HOSTS file in its entirety too (into my local diskcache kernel mode subsystem's arrays/buffers/structures, because that is the last entry in it & pinging it SHOULD force my system to look into that HOSTS file of mine (more on THAT below, lots more) & since it is the LAST ENTRY, it will read the entire file into RAM @ that point, to do so, effectively caching my HOSTS file, right then & there) - do NOT do this if you are part of a LAN/WAN though, you need it in those environs typically
----
2.) Turn off the TCP/IP over NetBIOS service (this is not needed by a person who does not have a home LAN either, or needs to share his files/folders/disks out to others remote to the system in question also, much like SERVER service above) - do NOT do this if you are part of a LAN/WAN though, you need it in those environs typically
----
3.) I have also been able to turn off the WORKSTATION service as well on Windows 7, albeit, ONLY AFTER I BOOTUP & LOGON in test so far, not sure if you can DISABLE it & still logon, so... keep that in mind!
(This service deals in SMB (server message block iirc) networking)
Turning it off, like any service you don't really need, results in YOUR saving more CPU cycles, RAM, & other forms of I/O also, + even electric power really... as you're not running a program & using power, just like ANY of the above or below recommendations for turning off programs of most anykind really do (albeit, this isn't as much of a "security gain" as the top 2 above are imo) - do NOT do this if you are part of a LAN/WAN though, you need it in those environs typically.
----
4.) I have also turned off (set disabled)
the SSDP Discovery Service (don't need it here is why)
----
5.) I have also turned off (set disabled)
the Function Discovery Provider Host Service (don't need it here is why) - do NOT do this if you are part of a LAN/WAN though, you need it in those environs typically (well, in this case, POSSIBLY only).
----
6.) I have also turned off (set disabled)
the Net.Tcp Port Sharing Service (don't need it here is why & this MIGHT be somewhat of a 'security risk' too, imo @ least, in leaving it "on" & running 24x7) - do NOT do this if you are part of a LAN/WAN though, you need it in those environs typically (well, in this case, POSSIBLY only).
----
7.) I have also turned off (set disabled)
the SSDP Service (don't need it here is why & it "ties in" with UPnP below (read that one))
----
8.) I have also turned off (set disabled)
the UPnP Service (don't need it here is why & UPnP has been KNOWN to have vulnerabilities over time, in OS & in routers even, which IS noted in this guide as to how/when/where/why/what can be 'dangerous' about it...)
----
9.) I have also turned off (set disabled)
the WinHTTP Web Proxy Auto-Discovery Service (don't need it here is why) - do NOT do this if you are part of a LAN/WAN though, you need it in those environs typically (well, in this case, POSSIBLY only).
----
* THAT'S THE END OF SERVICES TRIMMINGS (more on that & a GOOD SOLID CURRENT GUIDE FOR THAT? It's in my "P.S." below... for even more speed & possible security gains you get by turning off services you do NOT need possibly, running in the background when you really do NOT need them to be, soaking up CPU cycles, memory, & other types of I/O your programs you actually USE, could use, instead! Just common-sense, imo...)
ANYHOW -
onto the LOCAL AREA NETWORK CONNECTION"10.) Turn off Client for Microsoft Networking, QoS, + File & Print Sharing in your LOCAL NETWORK CONNECTION (avoiding the potential for shared disk/file/folder access even more, & do this ONLY IF YOU DO NOT HAVE TO CONNECT TO A LAN/WAN (local or remote) for disk/folder/file sharing only, or if you are NOT part of a HOME or WORK LAN/WAN)... & really, any others, other than TCP/IP (this you need for online access).
While you are there, in your LOCAL AREA CONNECTION?
Well - Additionally, You can DISABLE TCP over NETBIOS as well in the LOCAL AREA CONNECTIONS' properties for Tcp/IP, & the ADVANCED button, then click on the WINS tab & check "DISABLE NetBIOS over TCP/IP"... &, there are a few more too, read on:
Extra protocols &/or services that Windows 7 has, such as "Link Layer Topology Discovery Mapper I/O Driver" &/or "Link Layer Discovery Responder" can also be "cranked off" & apparently to NO DETRIMENT EITHER (I have been running for weeks now without it & I am here posting, aren't I? If that doesn't say or prove it for me, not much will I guess... lol!)
I also add in OpenDNS' servers there in the DNS tab (advanced Tcp/IP properties)
& their IP addresses are:208.67.220.220
208.67.200.200
(They are a FASTER DNS system, & respond to fixes + patching faster than any other did when Mr. Dan Kaminsky found the holes & security vulnerabilities he did last yr. in the Domain Name System (DNS)).
LASTLY (though this is more of a "speedup" than a securing tip)
? Try this:Create/paste this into notepad.exe & save it with a .cmd extension (32/64-bit batchfile really, just ends in .cmd rather than .bat, as 16-bit command.com driven ones did in DOS & Windows too)
@echo off
echo Setting TCP/IP flags...
echo -----------------------
echo This only succeeds when run as an administrator,
echo when run as a user it only shows the current settings.
echo.
pause
echo.
netsh int tcp set global rss=enabled
netsh int tcp set global chimney=automatic
netsh int tcp set global netdma=enabled
netsh int tcp set global dca=enabled
netsh int tcp set global autotuninglevel=normal
netsh int tcp set global congestionprovider=ctcp
netsh int tcp set global ecncapability=enabled
netsh int tcp set global timestamps=disabled
pause
cls
echo Current settings:
echo -----------------
netsh int tcp show global
pause
Then, lastly, run it... (create a shortcut to it, & use the ADVANCED button in the shortcut to "RUN AS ADMINISTRATOR"). This is supposed to speed up & help your IPStack perform better/faster, in Windows 7. I just tried it today, seems to work ok (no detrimental effects so far @ least that is).
Anyhow: "Onwards & Upwards!"
----
11.) IF you use a "largish" custom HOSTS file? TURN OFF THE DNS CLIENT SERVICE (which is just like the ones in Windows 2000/XP/Server 2003, which this guide covered MOSTLY as to how to secure those)... - do NOT do this if you are part of a LAN/WAN though, you need it in those environs typically, especially on an "AD Network" on a LAN/WAN (Active Directory is HEAVILY dependent on DNS is why).
* NOW, if you do not do this (turn off the DNS cache local client service), & you use a larger HOSTS file? You will LAG, & badly... amazingly badly in fact!
(I have written MS on this, only to have it "fall on deaf ears" really, so this IS the 'workaround' for that, rather unfortunately, because I believe it can be fixed for larger HOSTS files too, by altering how much can go into the C/C++ structure for records that DNS uses, based on reference BSD designs @ least (I don't have MS' sourcecode so... well, I can only guess on their designs, though they, like most others, tended to use the BSD model to start from @ least for TCP/IP)).
----
12.) USE A CUSTOM HOSTS FILE (for BOTH added SPEED, but more importantly FOR BETTER SECURITY ONLINE):
Custom HOSTS files can literally double your speed online via blocking adbanners (good & bad ones) + having the option to "hardcode in" your favorite websites IP Addresses into a HOSTS file next to its HOSTNAME/DOMAINNAME, avoiding having to call out to remote DNS servers (many of which have been found exploitable, even the allegedly "invulnerable djbdns system", by Mr. Dan Kaminsky & others in case you are interested in specifics here on this note), saving a GOOD 30-N ms roundtrip traveltime per call to remote DNS server to resolve a URL to an IP address...
BUT, their best benefit? Even better than "double your normal internet surfing speed online" (it will get faster, read here in fact):
----
RESURRECTING THE KILLFILE:(by Mr. Oliver Day)
http://www.securityfocus.com/columnists/491PERTINENT EXCERPTS/QUOTES:"The host file on my day-to-day laptop is now over 16,000 lines long. Accessing the Internet particularly browsing the Web is actually faster now."
"From what I have seen in my research, major efforts to share lists of unwanted hosts began gaining serious momentum earlier this decade. The most popular appear to have started as a means to block advertising and as a way to avoid being tracked by sites that use cookies to gather data on the user across Web properties. More recently, projects like Spybot Search and Destroy offer lists of known malicious servers to add a layer of defense against trojans and other forms of malware."
----
So reiterating this: Even BETTER THAN THE SPEED GAINS HOSTS FILES PROVIDE, ARE the SECURITY GAINS!
I.E./E.G.-> I have a pal named Jack, a PI by trade & license/degree, who used to get (no joke) 200++ viruses a week... NOT ANYMORE! He is CONVINCED, as am I, that a good current HOSTS file that blocks out known BAD SERVERS is the key here... as well as his saying literally "my intenet goes TWICE AS FAST with a HOSTS file"...
(FOR GOOD RELIABLE/REPUTABLE HOSTS FILES? There are many good ones!)
Try here -> http://en.wikipedia.org/wiki/Hosts_file & you can use sites like Mr. Dancho Danchev's security blog to update them even more for securiity (i.e. - for the latest in listings of botnet "Command & Control Servers" or bad sites with malware on them in general, here ->
http://ddanchev.blogspot.com/ )
OR
Just use "Spybot 'Search & Destroy'" instead, as it updates your HOSTS vs. known bad websites (& your webbrowser of choice's private block lists, such as IE "Restricted Zones" here -> HKCU,"Software\ Microsoft\Windows\CurrentVersion\Internet Settings\Zones\4 or via Internet Options in CONTROL PANEL, & others like Opera maintain private .ini files (URLFILTER.INI &/or FILTER.INI) for the same general purpose))
E.G.-> Over the past 10 yrs. or so now, those sites have helped me build upt a custom HOSTS file version that has over 660,000++ entries in it, of KNOWN BAD SERVERS OF ALL KINDS...
Mine COMBINES mvps.org's & the one I built up myself since 1997, alongside all those @ the wikipedia site for HOSTS files above, that is completely free of duplicate entries (via a program I wrote & posted of here, "APK Hosts File Grinder 4.0++") & uses the SMALLEST + FASTEST POSSIBLE INTERNAL FORMAT for them on Windows 2000/XP/Server 2003 (0 blocking "ip address", e.g.-> 0
www.knownbadmalwaresite.com ) OR for Windows VISTA/Server 2008/Windows 7 (using 0.0.0.0 which though larger than 0, is the only thing that still works on those most modern versions of Windows)
(ODD THAT, that diff. in blocking IP address used, but the dual layer IPv4/IPv6 tcpip driver in VISTA onwards must have facilitated this, but it too, up until 12/09/2008 could ALSO USE THE SMALLER & FASTER 0 BLOCKING "IP ADDRESS", but after that "Patch Tuesday", even VISTA no longer could... so, I am not sure of WHY MS has pulled this though I have confronted them numerous times on it, repeatedly, & I noted it above also).
I mean, hey - Windows VISTA/Server 2008/& Windows 7?? They're ALL/EACHl based off Windows Server 2003 code, which still can use 0 though oddly, making for smaller & faster HOSTS files - so why doesn't MS allow this now?? Boggles my mind, but worse, is the fact they have evaded answering me on it several times (on their own forums, & on ones like SLASHDOT too + more).
----
PRACTICAL e.g. in the case of mine?a.) Using 0 gets me a
14mb sized HOSTS file, same line entries as the ones below, just using 0 as "blocking IP address" (vs. 0.0.0.0 or 127.0.0.1 which ARE larger & thus, slower to read)...
Whereas, by way of comparison:
b.) Using 0.0.0.0 on Windows 7 is up to
18++mb in size...
c.) However, & WORST OF ALL for both speed & efficiency? 127.0.0.1, the default blocking address used, ends you up with a
22++mb sized HOSTS file!So, as you can see?
I save 30% or so using 0 vs. 0.0.0.0 (have to use THIS latter one though, on VISTA/WinSrv2k8/Windows 7 though, what a shame) in filesize & thus loadspeed of my HOSTS file,
AND approximately ALMOST 50% in size vs. using 127.0.0.1 - to any "naysayers" on this account, I can only say:
"Argue with the numbers", & GOOD LUCK (you'll need it, more like a miracle really).
----
(This turning away of being able to use 0 in a HOSTS in VISTA onwards (again, wasn't always this way in VISTA mind you) is "bloated", because 0 &/or 0.0.0.0 do the same valuable blocking, & are smaller + faster to load because of the size diff.... so, "do the math" yourself, & realize also that smaller files load & parse faster (line by line, in a WHILE loop, with each line terminating in a CR+LF (carriage return + linefeed/enter keypress), & eventually when the "EOF" (end-of-file trailer record-marker) is hit signalling the end of the file & thus the read loop in the File Open/Read-Write/Flush-Close I-O cycle)...
Funniest part of all, is this: Windows 2000 didn't have 0 as a legit blocking IP address in its ORIGINAL DISTRO on CD from MS: They added it LATER... & kept it all the way into VISTA, until 12/09/2008 MS "patch tuesday"... why change it now, especially when it does a GOOD THING for a great thing (hosts files)? And, ping'ing a 0 blocked site from your HOSTS file, on Windows 2000/XP/Server 2003 gets back a 0.0.0.0, a legit IP address (proving this is indeed, LEGIT TO USE, period... so, why did MS remove it, if it makes a HOSTS file smaller & faster?)
----
13.) Look @ your TCP/IP rules "INBOUND" tables in the "ADVANCED FIREWALL CONNECTIONS" section of your Windows Firewall (Run this command for a quick link to it -> %windir%\system32\WF.msc )
There?
Well, I have personally successfully turned off /BLOCKED an ENTIRE ARRAY OF DEFAULT ALLOWABLE PROTOCOLS I JUST PERSONALLY DO NOT NEED & I am again, here posting, just fine (after reboots & all mind you).
(ALSO - this section here? WELL - This may vary by what you yourself need to do though, so bear that in mind)...
PERSONALLY -
I only left the "Core Networking" sections/lines as ALLOWED IN (& I am certain I can block out a couple of those too, but this is all what I have done "so far", successfully, only... more will come in the future I am sure on this one from myself, or others too).
----
14.) A good run of secpol.msc (using its Account Policies &/or Local Policies Left-Hand Side tree items/folders).
(& on secpol.msc,
I applied "AnalogX's IP Security Policy", in the IP Security Policies section also (which I mention in this guide here earlier, & in AnalogX, & WHERE TO GET IT, with directions to install it (cake-easy) & it works great still, too!)
PLUS I added myself as an ADMINISTRATOR user to nearly EVERY category in "User Rights Assignment"! I removed AND DENIED out the following users/groups in my DENY sections (the toughest ones really) in the secpol SECURITY OPTIONS section:
DIALUP
TERMINAL SERVER USER/GROUP (I don't use OR allow this here, you may)
GUEST
ANONYMOUS LOGON (especially this one)
Remote Desktop Users (I don't use OR allow that here either)
REMOTE INTERACTIVE LOGON
IIS Users (I don't host a website here is why on this note)
(STEER CLEAR OF THE DCOM RELATED SETTINGS GUYS - I DID THAT & CAUSED MYSELF A LOT OF "PAIN" (not really - Windows7 recovery bootup from install DVD or System Repair CD let me restore from a Restore Point perfectly once, & a System Image once, & those are the only other times I redid or had to redo this system on Windows 7, which happened the first day, while I was learning more (during tuning tests like these, or checking which boards/cards still worked for me here on Windows 7)... I'd try to help YOU avoid that, though it was not bad!
I do this, this way, here... simply because I have run for the past 15++ yrs. now that way (beyond "STD. ADMINISTRATOR" or "SYSTEM" level rights even)... I do so, successfully!
& despite the 'common belief' it's 'dangerous to do'? Well... I do that, & have not gotten infested/infected since, oh, around 1996-1997 that I know of @ least, but then I know to avoid using the "main malware delivery tools" in IFRAMES + JAVASCRIPT mostly, online, & also what sites I use that have proven reputable too (which some of you may or MAY NOT wish to elect to do on the elevated ADMIN/SYSTEM-LIKE rights assigned to yourself... &, epsecially if you believe in & espouse the UAC "least privelege principal", because its theory is SOUND, but it's not always that way in practice (per folks still getting infested in VISTA, & of course, the antivirus-antispyware test I note here in THIS POST, too))
E.G.-> There, in the I gave myself every right possible under the sun almost (those who believe in the principal of "least privelege is safer" disregard this, & it's so UAC keeps "protecting you" (though it's not that great vs today's threats, it did stop 3/10 of the ones thrown @ it here ->
http://tech.slashdot.org/article.pl?sid=09/11/08/0233248 , it's still NO "Cure" for a user that does not give a hoot & just downloads + opens/runs any email attachment or binary executable from online that he finds, either)
----
15.) GET MICROSOFT SECURITY ESSENTIALS (especially if you do not have a Windows 7 compliant/compatible antispyware + antivirus program)... it has been rated + reviewed VERY WELL online in antivirus/antispyware competitions-contests/ratings, & I have been using it and it is fair FAST @ scanning files/folders plus, it is VERY LIGHT & operates QUITE "transparently" too... not much lag, IF any, is perceptiable from it & it updates, daily too AND IS 100% FREE and WORKS!
----
16.) Do the "FileSystem" & "Registry Hives" ACL security tip I noted here, adding yourself + SYSTEM (& any user groups YOU are part of, & removing other users that do NOT need to be there right out)... it works for security too.
----
17.) Doing the above, on Windows? Between ALL THAT ABOVE should "do the job" & between that +
running a tool like Microsoft Baseline Security Analyzer 2.1.1 (there are 32 &/or 64 bit models out there now mind you too + I posted the download links to them above here earlier a couple posts up from this one)!
====
Doing ALL that to a Windows 7 System that is a "stand-alone" single system hooked to the internet only (not a LAN/WAN or home network)? You SHOULD be "OK"/Fine, for now @ least, on a secured Windows 7 setup...(NICE PART IS, imo thusfar @ least? Well, that is that it really SEEMS you do not have to do NEARLY ANYWHERE AS MUCH as what you had to do for Windows 2000/XP/Server 2003 though really, for security)
... Especially since MS has really, REALLY done a GOOD JOB of securing services for instance, so you don't really have to do that step anymore as I outlined in this guide early on, for securing services & for Windows 2000/XP/Server 2003 for the "utmost in security" even @ the services level, like MacOS X has for example... especially since MS has even helped THOSE older models of Windows do better there, via service packs + hotfixes for them altering the "logon SID entity indentifier" services use (LOCAL SYSTEM, vs. LOCAL SERVICE or the least priveleged in NETWORK SERVICE).
ANYHOW/ANYWAYS: Well - That's my "Top 17", so far @ least, for Windows 7, for now... IF I find more? I'll put them up for your reference (and do pay attention to points in this guide too, as more than a few STILL APPLY to Windows VISTA, Windows Server 2008, & yes, Windows 7 still too)...
APK
P.S.=> NOW - For even MORE "speed-enhancing" services tunings (the above are for SECURITY mostly, but also help you gain speed by plain jane just not running them (pretty common-sense nowadays, & generally accepted as OK, even since the days when I authored what is probably the FIRST publicly noted guide for "Speedup & Securing Windows NT-based OS'" over @ NTCompatible.com as their "Article #1", which Neowin noted back in 2001 when they finally "got wind of it", here ->
http://www.neowin.net/news/main/01/11/29/a...--security-text & they rated it very well also))?
Well, you may wish to check out "BLACK VIPER'S GUIDE", here:http://www.blackviper.com/Windows_7/servicecfg.htmIt's GOOD, & VERY CURRENT + ACCURATE (& flexible)!
Amazes me, that ENTIRE SITES 'sprang up' out of the guide I did ages ago & based on the SAME PREMISE as my original guide was @ NTCompatible.com (circa 1997-2002) for NTCompatible.com as their "Article #1"....
... & I am glad because spreading good information around that makes the world a better place it is just fine by me @ least... (& Black Viper's is particularly OUTSTANDING in this regards, & he "kept up on it", keeping his website running & chock full of CURRENT INFORMATION on this topic, on more current OS (I stopped doing those around the time Windows VISTA came out is why, because it has a LARGELY "self-tuning IP stack" (when I did tunings for TCP/IP networking) & by that point, I had moved onto other areas (programming MOSTLY, vs. networking/tech stuff))... apk