No, but . . .
Rather than think of excluding a user from every object on the system, think of excluding a user (or their group) from applications. If you think about how applications are implemented, they are typically a set of libraries and/or directories. If you exclude a user (or their group) from the library or directory, they cannot access anything in the library or directory. For the libraries the user does need access to, you're going to have to determine whether you need to exclude the user from other objects in that library. But rather than thinking of excluding someone from every object on the system, try stepping back and taking a slightly broader approach. Hopefully the task won't seem so daunting that way. ==================================
MORE INFORMATION ON THIS TOPIC
==================================
The Best Web Links: tips, tutorials and more.
Search400's targeted search engine: Get relevant information on security.
Ask your systems management questions--or help out your peers by answering them--in our live discussion forums.
Check out this Search400.com Featured Topic: Top ten security tips
|
