Blog

Announcement: Scalable Audit Data in Non-Employee Risk Management

Author

  • jeff_lakey

    SailPoint

SailPoint Non-Employee Risk Management is introducing improvements to the performance of audit event tables in the user interface.

Prior to these updates, the longer that event history is amassed in NE Risk Management, the performance of the UI tables which display this history could be negatively affected. This includes the history of workflows, profiles and API actions, which may be useful for troubleshooting.

With this change, we have significantly improved the performance of these tables by utilizing a service which stores and allows queries of event history within a specific retention period.

When is this change being applied to my tenant?

  • These updates will be applied to all current production tenants beginning the week of August 5, 2024.
  • Tenants that have been created since the beginning of the year may have already received these updates.

What is changing?

  • Improved Performance: Non-Employee Risk Management will be utilizing a service to query event history that will be able to handle much larger data sets than our previous database. This will allow the UI to load event data more quickly. This service will be used to display audit events that are captured when the following are changed:
  • Profile Types
  • Workflows
  • Pages
  • Forms
  • Attributes
  • Roles
  • Value Builders
  • Portals
  • API Error events: Non-Employee Risk Management will now be logging errors relating to the API token. This will allow administrative users to debug errors, such as 400 Errors, using their API token. Routine, successful GET requests will no longer be captured as historical API Events.
  • Profile creation events: Non-Employee Risk Management will now log an audit event when a new Profile is created. Previously, all change history to existing Profiles was captured, but not the initial creation of the profile. This will provide administrators a more complete picture of a Profile's history.

How long will event history be stored?

  • Profile event history - duration of customer relationship
  • Configuration change event history – 1 year
  • Workflow events - 18 months
  • API Error Events - 30 days

What happens to old events?

  • Profile event history (all) will be migrated
  • Workflow event history (90 days) will be migrated.
  • API event history will not be migrated, but the service will run for a few days prior to the UI being enabled, in order to populate the table with recent events.

Are there any changes to the user interface associated with these updates?

  • No, the UI elements for tables displaying Profile History, Workflow History, and API history will remain the same.