HP OpenView Operations Administrator's Reference - filibeto.org

About OVO Security
About Network Security
484
About DCE Security
Network security involves the protection of data that is exchanged
between the management server and the managed node. This security is
intimately related to DCE. OVO addresses the problem of network
security by controlling the authenticity of the parties, in this case the
RPC client and the server, before granting a connection and ensuring the
integrity of data passed over the network during the connection.
OVO carries out its own, basic authorization checks for communication
between the management server and the managed nodes. However, DCE
allows you to implement more stringent security at the process level
between an RPC client and an RPC server, specifically in the areas of
authentication and privacy, or data protection.
The level of data protection is chosen by the RPC client, although the
RPC server has the option of deciding whether a chosen level is
sufficient. OVO authentication is handled by RPC clients and servers.
For example, in the same way that an RPC server needs to determine
whether or not an incoming request is from a genuine OVO client, an
RPC client also needs to be sure that the server it is calling really is an
OVO server.
Configuring DCE
If you want to protect communication between the OVO management
server and managed nodes using DCE security mechanisms, you need to
carry out some extra configuration steps:
❏ DCE Server
Make a DCE server installation available on your local network.
❏ DCE Nodes
Make sure all participating nodes are members of DCE cells that are
configured to trust one another.
OVO does not require a particular DCE configuration.
For more detailed information on DCE, see the product-specific
documentation and “To Configure DCE Nodes to use Authenticated
RPCs” on page 486.
Chapter 12