Close popover

Table of Contents

Enabling security auditing for a data class or rule type

Version:

You can record changes for single values and aggregate properties when you enable security auditing.

To enable security auditing for a data class or a rule type, complete the following steps.

  1. In Dev Studio, create a data transform named pyTrackSecurityChanges with an applies to class equal to the class you want to audit.

    Examples with this name are provided as standard data transforms for tracking changes to access groups, operator ID instances, Access of Role to Object rules, flows, case type rules, and application rules. You can save copies of these standard data transforms into your ruleset and update the list of properties to be tracked.
  2. On the Definition tab, in the Action field, select Set.

  3. Specify the property in the Target field.

    • For value list or value group properties, enter a numeric index to identify one value.
    • For page mode properties, enter a reference to a single-value property within the page structure.
  4. In the Source field, enter a word or phrase that will be displayed on the History Details section.

  5. Click Save.

  6. Create a Declare Trigger rule named TrackSecurityChanges.

    The Apply to (class) field and Add to ruleset field are filled out automatically, but can be changed if needed.

  7. Optional:

    Leave the Value column blank for a row to apply custom text from a field value rule.

  8. On the Trigger tab, in the Trigger when an instance is field, click Save.

  9. In the Trigger activity section, in the Name field, select TrackSecurityChanges for the activity name.

  10. In the Execute field, click Immediately.

  11. Click Save.

  12. Optional:

    Test the feature by changing a rule or data instance and review the history.

  • Rule and data change auditing

    Pega Platform maintains a history of changes to certain data classes and rule types. You can use this history to diagnose system issues and to demonstrate compliance to internal and external auditors.

  • Customizing the memo text for an audited rule

    You can customize the memo text to provide a more detailed description of the change that was made to a rule or data object. Use field value rules to change the memo text that is displayed on the history details reports for a property.

  • Auditing changes to aggregate properties

    The history detail for aggregate properties does not indicate changed values as it does for single-value (scalar) properties. Instead, the history details shows two entries when a value is changed: one entry about deleting the prior value and another about adding the new value.

  • Security event configuration

    The security event configuration feature is part of security information and event management (SIEM) that combines security information management (SIM) and security event management (SEM). Use the Security Event Configuration landing page to configure the logging of security events so that you can diagnose system issues and demonstrate compliance to auditors.

Suggest Edit

Have a question? Get answers now.

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