User Management and Backup Policy

[James Beamish-White]

Hi all,

Does anyone out there have a user management or backup policy document they are willing to share? I am implementing a bunch of policies in the organisation I am working for, but I would prefer not to re-invent the wheel if there exists one already.

The basis of the user management policy should include:
*authorisation required to set up user
*what do do with old accounts
*review of system users

The basis of the backup policy should include:
*what to do when a new system is introduced
*what backup cycle is required based on system availability/importance
*restore testing

Any help would be much appreciated, so I don't have to spend the next few days typing documentation ;-)

Cheers!
James

[Andre Da Silva Dias]

I'm sending you a doc regarding security policies.

Hope it helps.

Andre

[Roger Baptiste]

Hi,

I don't have a document as such, but we follow certain guidelines :

<<*authorisation required to set up user>>

User's request needs to be authorised by his manager to be created. Authorisation can
be a document or a email or a webform. Depends on the site and number of users being supported. Also, in very large shops, we have a separate team taking care of user creation requests , sparing the unix admin for more important tasks. Restricted SAM access can be given to a bunch of newbies to creat the user accounts.

<<*what do do with old accounts >>

If a person is quitting, his account is terminated. SOme accounts can remain if they are running jobs which cannot be changed immediately.

<<*review of system users >>

None. Except for password management. Root passsword is changed at a certain frequency.


<*what to do when a new system is introduced >>

Decide on which cell server it has to go.
Set up a system backup policy, where everything
on Vg00 is backed up (except /var/adm/crash or /tmp). Decide on the drives it needs to use. If you have a SAN setup, this needs to be worked with the backup folks on the site. IF it is standalone setup, then you would need to hook DLT to the box.
So, again this is site dependent. But, there should be a backup policy, where you atleast signoff saying this system is being backed up or not being backedup .

<<*what backup cycle is required based on system availability/importance >>

Daily incremental. Weekly full. Monthly and yearly. For database backups, it needs tobe worked out with DBA and users, depending on what sort of backup they need on a periodic basis. Again, this is very site dependent.
Also depends on what sort of backup resources you have. Number of silos, drives, san?, backup support , media , offsite policy ..
Also, include a ignite backup in the policy.

<<*restore testing >>

It can be a part of yearly DRP.


HTh
raj

[John Bolene]

*authorisation required to set up user


Department server = member of department
Corporate server = accounts setup by security


*what do do with old accounts

Old as in left the company? Account normally deleted before telling the user he has been let go, or the same day if it was his choice.


*review of system users

If job title changes, access authority can change.


The basis of the backup policy should include:
*what to do when a new system is introduced


Sysadmin says when system is ready for use, backups begin at that time.


*what backup cycle is required based on system availability/importance


Production systems = full backup on weekends, incremental every night.
Development systems = full backup each weekend.
Test systems = whenever I do it


*restore testing

whenever I do it



Hopefully the HTML will come thru, otherwise, you get the point.