Important This documentation space contains information about PATROL Agents when deployed in a BMC Helix Operations Management environment. If you are a TrueSight Operations Management user, see PATROL Agent 24.3.01

Account and access security

The PATROL Agent strengthens security by managing application-specific and user accounts, making sure all actions are carried out under the correct credentials. The PATROL Agent also prevents unauthorized connections by using access control settings, including the patrol.conf file and the Access Control List (ACL). These measures help you control who can connect to the PATROL Agent and under what conditions, and ensure secure and authorized access.


Application account security

The PATROL Agent uses separate accounts for each application and instance, securely managing permissions and access. This isolation of credentials reduces security risks. See Establishing accounts and ports.


User account security

To ensure proper user authentication for application discovery and parameter operations, use a valid user account specified by the defaultAccount variable in the agent configuration file.


PATROL Agent access control

The PATROL Agent uses robust access control mechanisms to make sure that only authorized users and hosts can connect, including connections from pconfig clients. These controls can be managed through the patrol.conf file and the Access Control List (ACL). 


Access Control List (ACL)

The Access Control List (ACL) specifies which users can connect to the PATROL Agent, the modes of connection allowed, and the permitted hosts. This is configured by using the /AgentSetup/accessControlList variable. 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*