|
Posted by Roger Abell [MVP] on November 22, 2005, 12:17 am
If you were Registered and logged in, you could reply and use other advanced thread options
and allowed accessors/ips, is likely the one approachable thing
you can do to reduce the risks. Karl also makes a good point
about IPS instead of simple firewall. About the only other thing
you could do is to look for application replacements so you can
get out of the situation.
Most other things you could try would be in my opinion a waste
of time. I mean, so you could spend much time trying to configure
the systems better, etc. but if the bullet that gets them is going to
be a remotely accessible vulnerability in the unpatched OS code
then that extra effort is not going to make much of a difference.
> Any recommendations for securing NT going forward? My shop has a
> couple hundred Windows servers, but a handful cannot be upgraded from
> NT 4.0 due to legacy applications. These are internal-use servers
> only. Has anyone attempted to create a quasi-safe environment for such
> a situation? One approach might be to isolate them behind an
> additional internal firewall and allow only the very few
> ports/protocols in use by those servers. Any thoughts? Seen any
> articles? I've searched but haven't turned up anything.
>
> Thanks.
>
| 
XML site map