Re: a good start to do hardening

From: svek (svek@gmx.net)
Date: 12/30/01 

From: "svek" <svek@gmx.net>
Date: Sun, 30 Dec 2001 13:10:50 +0100

It all depends on what you are going to use it as, as a workstation I can
see why you could want to have a bit more liberty to do things, but as a
server then you should try to lock it down as hard as possible since it
should only do the things you've set it to do so all other serverices and
things to do on it should be disabled.
And it's quite hard to keep up in the investigate when something weird
occurs since the attack usually comes within 24 hours of the first scan
sometimes even an hour which gives you not to much time to find out what
they are up to.

And security is a lot about balancing risk with benefit, if you are a home
user you could have a less secure computer than if yo were in a large
company for abvious reasons.

/svek

"Bill Unruh" wrote:
> Or perhaps just place a shotgun against the case and fire it. Your
> suggestions will make the computer inoperable and useless.
>
> Security is not some little formula, it is trying to see what you can do
> that you want to do in a safe way.
>
> a) Keep up with your distribution's safety patches. This is probably the
> most important thing, beside which all other's are of secondary
importance.
> b) Do not run any services you do not need, whether in /etc/inetd.conf
> or /etc/xinetd.d or in the startup scripts.
> c) Keep your eyes open for any strange behavour and ivestigate why.
>

Relevant Pages

  • Re: Paradigms II
    ... > are not about trying to circumvent security. ... > (server or workstation); however, they can be easily adapted to any other ... > to have at least a vague idea what security, and a secure environment, ...
    (comp.security.misc)
  • Re: Event ID 5719: No Windows NT or Windows 2000 Domain Controller is available for domain .
    ... In my experience what you have done with security policy should ... The workstation gets its networking information from DHCP that, ... updates DNS. ... I don't believe the problem to be at the server end though. ...
    (microsoft.public.win2000.security)
  • Re: "Classic logon" screen in XP does not remeber the user name
    ... I went to the workstation. ... does not show up on the server when I log onto the ... When you are done configuring Local Security Policy run the ... "Local security policy does not allow interactive login on this ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Local Security Policy Locked (or something?)
    ... at one time I may have been booting the server ending up ... for the local workstation. ... Failed to open IPsec policy storage Access is ... or not a given security setting is defined in group policy. ...
    (microsoft.public.windowsxp.security_admin)
  • RE: Cant see other computers/nodes on network!
    ... so when you are on a workstation and you go to \\knight-tech\ you don't ... on the difference between some of the products (Server, XP Pro, XP Home, ... Print, Streaming Media and SECURITY). ... the first thing I see is that the server isn't using the same DNS server ...
    (microsoft.public.windows.server.networking)