| The answer to your question can be found in the DECmcc Use Guide,
Chapter 2, Maintaining Security. Also, documentation on the manageable
entities will be helpful.
Basically, MCC uses the security features of the operating system and
the network. If you want to restict access to certain Access Modules,
you can protect the executable images so that the average user cannot
activate the image. Then create access control lists of trusted users
and apply the acl to the files.
Then you would have to review all the manageable entities and figure
out how access to the entity is obtained. For Example, DECnet Phase IV
nodes can be secured by protecting the objects used to gain access to the
node, and the account the object uses. Lan Bridge 150 and 200 can have
passwords, the Bridge Access Module requires VMS privileges.
Linda
|
| Well as Linda mentioned, you can control access to the entity. Then
on a class by class basis you can determine what these changes in
access due to the users ability to access directives. I can do a
lot of things, like looking at a phase 4 node through the dna4 am
with a non priveliged account, but to do sets my system is set up
such that I can't set with out privs.
The access control is related to what directives you can operate
but it done on a class by class basis and is class and not typically
directive specific. Currently we don't give out information on
tailoring dictionarys (time consuming) to do what you ask, nor do
we have a built in mechanism to do it -- good item to add to the
wish/work list for the PMs.
|