|
Nedenfor er resultatet af din e-mail formular. Indsendt af hkrebs@hkrebs.dk message: Some ideas: 1. There should only be one 'real' secofr on the system (including trusted backup persons end a sealed envelope). 2. Clarify the rules: This is allowed, this is not. 3. Force a log of all secofr's activities (including forcing the secofr at signon + signoff to write a note of what he is dooing) 4. Put an journal on sensitive files - at least logging OPN/CLO 5. Get rid of those untrustworthy IT people 6. Get more openess on sallary 7. Encrypt Personally I prefer solution 2. When I was an IT-manager I had a call from one of my users: "My collegue is ill today. Would you please call him at home and authorize him to phone me with his password. There is a function that we MUST have done now." Nobody really want to behave badly. > I'd like to set up someone as a security officer, but exclcude them from > certain libraries. What is the best way to go about doing this? realname: Henrik Krebs email: hkrebs@hkrebs.dk REMOTE_HOST: 134.146.4.10 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.