=?iso-8859-1?Q?Re:_Guidelines_For_System_Administrators??=

Theres only two main rules;

- Thou Shalt Not Access The Data Of Others Without Permission From
Management.
- Thou Shalt Not Modify A System Withou A Change Control Process Having
Been Completed.

If you make breaking these rules a "gross misconduct" offence (which
usually means instant dismissal) it should ensure that anything SAs can
do is done in a controlled manner.

The other thing is, of course, seperation of duties. Do not have any
single SA with the ability to access all system, but have different SAs
for different areas (i.e. one for production and one for DR where all
the replica data is held), that way if one SA does go bad, the data
held by the other should be OK.

Hope this is useful.

Al.
--
Al Sutton
Argosy TelCrest
www.argosytelcrest.com


Lim Kah Wee <yauii@linuxmail.org> wrote on 21.10.2005, 11:40:21:
> Hi,
>
> Was wondering if there are any guides or codes of ethics which lists the do's 
> and dont's for a system administrator?
>
> A system administrator would be something like a "god" in the organization 
> from a system perspective, with virtually full rights to all the systems. So 
> was wondering if there are any set "guidelines" on what can or cannot be done 
> by the system administrator? Any good links to look at?
>
> Thanks.
> -kw-
>
>
> -- 
> _______________________________________________
> Check out the latest SMS services @ http://www.linuxmail.org
> This allows you to send and receive SMS through your mailbox.
>
> Powered by Outblaze