Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 May 2005 10:01:33 -0700
From:      David Bear <David.Bear@asu.edu>
To:        freebsd-questions@freebsd.org
Subject:   best practices for administration
Message-ID:  <20050511170133.GD10213@asu.edu>

next in thread | raw e-mail | index | archive | help
Since the BSD community seems to be more security conscious than other
(read windows system administrators) groups, I wanted to see if anyone
here would have any pointers to best practices documents when 
administering ANY operating system, not just FreeBSD. I am assuming
that many of you must manage other operating systems as well.

The nexus of my query lies in my attempt to have our central IT folks
issue additional identities for users to have when administering the
systems versus doing productivity work on them. I'd like to understand
what is done generally when granting users permissions to do things on
the operating system that imply 'administration', ie installing
software, adding printers, modifying system scripts, etc. There are
some here who think that putting standard user ID's into
administrative 'groups' is sufficient for granting such priveledges.

hopefully, I'm not being too obscure.
-- 
David Bear
phone: 	480-965-8257
fax: 	480-965-9189
College of Public Programs/ASU
Wilson Hall 232
Tempe, AZ 85287-0803
 "Beware the IP portfolio, everyone will be suspect of trespassing"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050511170133.GD10213>