tracking security

jgold

Member
what methods do you use/suggest for tracking security. We are revising all our security settings for groups and users and are finding that the security table grows rather exponentially.
I am afraid that in the future we will have a hard time what/why we did certain things. Any good sugestions on how to manage this?
 
1. Deny All to Public
2. Grant back prvileges to Groups/Roles on as needed basis
3. Document
 
1. Deny All to Public
2. Grant back prvileges to Groups/Roles on as needed basis
3. Document

thats exactly what were doing...it's #3 in your list that im havign trouble with.. any good methods for documenting?
 
I don't know it our method is particularly good or not - but it works for us. We record in a Lotus Notes database the following for each access/security permissions change to an object:

Date
Group(s) Affected
Access Granted/Removed details
Requested By
Approved By
Reason for Security change
Processed By

You could do the same in a excel spreadsheet, and access DB, etc. I think the main thing is to document what was changed, for who, why, and when.

Regards,
 
Back
Top