command logging for quality control

From: Vijay Bandi <vijay_at_MR.Net>
Date: Wed, 28 Jul 1999 20:52:16 -0500 (CDT)

Dear alpha managers,

        We have a digital box that serves as (among other things)
web, mail, radius, ftp, shell server. It has several hundred websites
on it and provides shell access to almost a thousand people.
It is also administered by an army of sysadmins and webmasters.

        We have well defined procedures and guidelines and most
of the time they are adhered to. But sometimes things break (mangled
configuration files, messed up virtual interfaces and so on) without
anyone owning up to it.

        We have decent backups so the situation isnt catastrophic.
To cope with it better, I'm thinking of -

1. version control for all important files (for text config files).
2. baseline signature for the whole system (perhaps tripwire?)
3. logging and other audit measures for commands typed at shell
        prompt, and others invoked via other means (cgi-bin
        or cronjobs).
4. anything that I am missing.

I can use all the help I get :). I'm trying to contain damage
done by ignorance as opposed to malice.

        Now I need to find out what tools, resources are available
out there and how to deploy them. I'm sure a significant portion of
the readers have "been there, done that", and I'd appreciate your
comments, recomendations, your own home-grown solutions etc etc.

        If there are other resources (urls, books etc), please send
them in. I'll summarize the responses. Thank you!

-vijay
Received on Thu Jul 29 1999 - 01:54:52 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:39 NZDT