HP OpenView Operations Administrator's Reference - filibeto.org

Who Needs to Protect Remote Actions
About OVO Security
About Security in OVO Operations
OVO offers a variety of security mechanisms that prevent the misuse of
remote actions. These security measures are especially important for
companies that manage systems from more than one customer with one
OVO management server. Remote actions designed for the managed
nodes of one customer may not be executed on the managed nodes of
another. Some of these security mechanisms are active by default. Others
must be enabled manually.
Types of Security Mechanisms for Remote Actions
To prevent the misuse of remote actions, OVO offers the following
security mechanisms:
❏ Assigning Trusted User to Configuration Files
All OVO configuration files on the managed nodes must belong to a
trusted user. By default, this trusted user is the super user. You can
change the trusted user (that is, the account under which the OVO
agents run) to another user. For details, see the man page
opcswitchuser(1M).
❏ Encrypting Message Source Templates
By default, OVO message source templates that are assigned and
installed on a managed node are encrypted. Encryption protects
message source templates from unwanted modifications and misuse.
❏ Disabling Remote Actions
If necessary, you can entirely disable remote actions for all managed
nodes.
A remote action is defined as an automatic action or
operator-initiated action which is defined within an OVO message
sent by Managed Node A and configured to run on Managed Node B.
The execution of such actions can be controlled with the file
/etc/opt/OV/share/conf/OpC/mgmt_sv/remactconf.xml
Chapter 12 511