PATROL Agent security methods

The following table lists the methods available for maintaining security for the PATROL Agent and tells you where you can find instructions for changing security.

Methods for maintaining security for the PATROL Agent

Method of maintaining security	How security Is established	Task reference
Security levels	Allows you to install one of five security level policies which secure the dataflow between the PATROL Agent, and PATROL Consoles.	PATROL Security User Guide
User account	The default account for commands run by the agent is specified by the defaultAccount variable in the agent configuration file. The agent cannot run application discovery and parameters properly without a valid user name.	Changing ownership and permissions on UNIX
User and host names	The Access Control List (ACL) is defined by an agent configuration variable. The ACL specifies which user names can be used with which computers when connecting with an agent. The ACL configuration variable is described in Managing console connections.	Controlling access to the Agent
Directory and file ownership and permissions	The PATROL_HOME/log and PATROL_HOME/config directories are created when the PATROL Agent process is run for the first time. At that time, the ownership and permissions of the PATROL Agent log and configuration directories are set. If the $PATROL_ADMIN environment variable is set, it specifies the user that owns all of the newly created log and configuration files. If the $PATROL_ADMIN environment variable is not set, the user PATROL owns all of the files by default.	Changing ownership and permissions on UNIX
PATROL Access Control	Access is controlled by configuration variables in patrol.conf	PATROL Console for Microsoft Windows User Guide — Customizing PATROL, Volume 3

PATROL Agent security methods

Comments