To view the latest 11.3.x version, see PATROL Agent 11.3.02.

Security guidelines for the PATROL Agent


This topic lists the security guidelines for the PATROL Agent and related components.

Securing files with sensitive information

  • Restrict access to files containing sensitive information such as certificates, or user credentials must be secured by restricting the access to all types of users except the owner.
  • Lock down the access to files that provide the capability to encrypt or decrypt the data containing sensitive or confidential information, such as sec_encrypt_p3x.exe or mcxpagent.exe.
  • Do not store the files containing sensitive data on the network shares with an open access.

Note

The above security guidelines are applicable for all the PATROL components.

Securing access to the PATROL Agent

  • Use the Agent Access Control List (ACL) to restrict the access to the PATROL Agent. For more information, see Controlling-access-to-the-agent.

    Notes

    • The above security guideline is applicable only to PATROL Agent-side ACL.
    • Applicable only to PATROL 3.x and PATROL 7.x architecture environments, except the client connection for configurations.
  • Use the PATROL Agent selection criteria in the Infrastructure Monitoring Administration authorization profile for policy management. For more information, see the following topics:

Note

  • The PATROL Agent ACL defined in Infrastructure Monitoring Administration doesn't overlap with the Agent ACLs defined within the PATROL Agent

Securing the communication

Securing the system running PATROL Agent

  • Disable the system output window (SOW) in PATROL consoles. For more information, see Controlling-the-system-output-window-display.
  • Set the following permissions for authenticating users to run the agent query tool from Infrastructure Monitoring Administration to the PATROL Agent:
    • Allow execution of Agent Actions
    • Allow trusted connections to PATROL Agents

           For more information, see the following:

Securing monitored resources

Provide read-only access to the user accounts used for monitoring the resources such as Oracle, WebSphere, vCenter, and so on. Refer to the individual documentation spaces of the various knowledge modules for the similar set of security recommendations.

 

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