TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------
You have to run the console as the user that installed it. This is part of
the authentication mechanism to prevent unauthorized users from connecting
to an engine.
You do have two choices. You can give a separate NT Workstation to your
NetOps group and place a console on it. Since the main console would have
what is called Master Status the 2nd console given to NetOps could watch
what an engine is doing, but not administer it. This is the best option.
The other option is to log into the same machine with a new account, install
RealSecure, and export the authentication keys for this user to the engine.
This is a rather inelegant way of doing things. It is also a security risk
since you will have several people sharing the same machine. All it takes
is for one rogue employee to compromise the machine and they could modify or
delete any logs you have gathered. You also run into the issue of
installing several copies of the software from different users over the top
of each other. This may not be a big issue, but on a multi-boot Win 98/NT
machine it can create some "interesting" situations.
How you proceed is up to you, your budget, and how much effort you wish to
expend. Security is not only looking for intruders, but it is also policy
and risk management. With reduced risk comes inconvenience. You have to
ask yourself (and maybe your management) is the reduced risk worth the
inconvenience. On the other hand you may not want to ask your management.
:)
John Foster
MIS Director - Pandora's Box
http://www.gothicknights.org
PGP Public Key: http://www.gothicknights.org/pubkey-dh.asc
