Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Displaying the Security Audit Log

Updated on July 1, 2021

Display the audit log to view login attempts and other security events.

Before you begin: To display the security audit log, you must have the pzViewAuthPoliciesLP privilege, which is included in the PegaRULES:SecurityAdministrator role.

The Security Audit Log report includes a default filter to display all audit events, which is set to pxCreateDateTime is Less or Equal to Current Month. To adjust the date range, click the link next to Filters in the report header.

To select security events to monitor, use the Security Event Configuration landing page.

To select whether to report successful or unsuccessful login attempts, set the Audit log level setting on the Security Policies landing page.

To display the Security Audit Log, complete the following steps.

  1. In the header of Dev Studio, click ConfigureSystemSettingsSecurity Policies.
  2. Click Display Audit Log.
    Result: The security audit log is displayed. For each logged event, the log captures:
    • Create Date/Time – The time of the attempt
    • Remote IP Address – The IP address of the system from which the attempt was made
    • Remote Host – The name of the computer involved
    • User Name – The operator ID used in the login attempt
    • Message – The status message returned during authentication of the login
    • Browser (User-Agent) – HTTP Request Header "User-Agent"
    • Referrer – HTTP Request Header "User-Agent"
    • Via – Records proxies through which the request was sent

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us