Protect business data: at rest & in transit.
Grant privileges according to job function.
Develop & monitor security policy compliance.
Simplify & enhance Safeguard environments.
Manage and optimize NonStop databases
The NonStop server has an interface to a user-supplied Command Monitoring Process named $CMON. While the $CMON program is not HPE-supplied, it’s recommended that every NonStop system use a $CMON either written by the customer or supplied by a third-party (such as the XYGATE supported $CMON module). When a $CMON is present, messages are sent to the $CMON to verify logon requests and process start requests. The $CMON process can provide many functions for both security and performance reasons:
Note that not having a $CMON presents a serious risk because, if a $CMON is not present, an unauthorized $CMON could be added to the system. The unauthorized $CMON might be used simply to monitor the system or it could be designed with malicious intent (such as stopping, denying or slowing services).