PATROL Agent ACLs

You can use PATROL Agent Access Control Lists (ACLs) to restrict user access to specific PATROL Agents. Each ACL contains one or more conditions that identify specific PATROL Agents. If you specify an ACL in the authorization profile of a user, the user can access the Agents that are a part of that ACL.

Example

A PATROL Agent ACL that specifies "Host name matches .*.labs.acme.com" restricts the user to those PATROL Agents on systems that have host names ending with .labs.acme.com. Users associated with this authorization profile cannot access any PATROL Agents on other systems. 

PATROL Agent ACLs are not designed to segregate devices. You can set up monitoring policies to automatically segregate PATROL agents based on various criteria. For example, you can create a monitoring policy to monitor all PATROL Agents that run on Windows. For information about creating monitoring policies, see Specifying-server-configuration.

From the PATROL Agent ACLs page, you can perform the actions identified in the following image: 

A different type of object

When you specify other types of objects in an authorization profile, you enable access. PATROL Agent ACLs are different in that they restrict access to PATROL Agents not specified in the ACL. 

patrolAclMain.png

1

2

List of your PATROL Agent ACLs

3

Action menu to edit, view, or delete your PATROL Agent ACLs

Related topics

Role-based-access

Managing-roles

Managing-authorization-profiles

Specifying-objects

Configuring-a-BMC-PATROL-Agent

Executing-tasks-on-BMC-PATROL-Agents-from-Infrastructure-Management

Specifying-server-configuration

 

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