eddwo wrote:
The stuff about having all those services turned off gets ridiculous. Having the firewall on by default means most of the services cannot be reached by incoming connections so there is no need to worry about them.
Well, it is an extra level of defence in case someone decides to run with the firewall off. I've seen a number of people saying they'll turn it off and ignore Security Center, relying on a hardware firewall - I don't recommend this. Hardware firewalls are also
susceptible to bugs. Many of them, like the Linksys WAG54G I connect with, run Linux - our firewall at work, a WatchGuard Firebox X, runs Linux 2.0.35 IIRC. Hope WatchGuard have been keeping up with patches, there's nothing worse than a security appliance
with known vulnerabilities.
If you have a network that's in any way open - allowing users with laptops to move between home networks and the corporate network, or a wireless network that isn't locked down - a user could pick up a virus or worm from another location, then when they return
to the corporate network, the worm could spread to other machines if they're not firewalled. This happened with the Blaster and Slammer worms.
eddwo wrote:
Moving to using restricted user accounts I agree with, but something like that will take a long time while so much software refuses to work with anything but administrator rights.
It'll take a lot longer if we don't start doing it. It's painful to start with - especially apps where the installer doesn't offer an 'Install for all users' option, where you have to run the installer using your own account but as an administrator. See Aaron
Margosis' tool
MakeMeAdmin for the moment. You can selectively weaken security as necessary by changing permissions on files and registry keys.
One caveat to watch out for is that new objects created by an administrator on XP are, by default, owned by that user. On other versions of Windows, including Server 2003, they're owned by the Administrators group. Any software you installed before changing
over to a Limited User account will be owned by you. Windows has a special CREATOR OWNER entry in object permissions, which by default has Full Control, which maps to the object's owner. Unless you change the ownership or the security settings for this software
in some way, you won't get some of the benefits of lowering your privilege level.
Most users on older 32-bit-only x86 machines actually won't notice anything much in SP2 apart from the firewall and the IE6 information bar, and maybe Local Machine Lockdown if they do local web page development. There's a lot more going on, but most of it's
under the covers - DCOM and RPC security, for example, seriously restricts the possible from-remote attack vectors. Few users will ever see that, because few users expose DCOM or RPC services from their computers. The ability for the RPC subsystem to punch
holes in the firewall as required makes it possible to run sensibly with the firewall enabled. Memory protection (DEP, No Execute) is a hardware feature only on the newest x64 and Itanium systems.
Silent changes are absolutely the right way to go. The user doesn't want to be disturbed by functionality that no longer works. It's weird how noisy components like Norton Anti-Virus or Norton Internet Security are considered more highly. Perhaps it's a reassurance
that it's actually doing something, but I found it irritating ("I blocked an attempt to connect to a port that nothing was listening on, aren't I brilliant? [OK]")
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.