Engagement audit trail in PX

We are an ISO27001 certified organization where security is a top priority. Preferably every change that affects what our end users see should have who/what/when/why, why being our internal ticket number (a free text comment field could be used for that) and the data should be available through an API so that it could be fetched and fed into our SIEM.

To build on Benny’s request, we have products that must conform to SOC2 audit requirements.  We also have corporate requirements to follow acceptable software development lifecycle procedures (SDLC?).

When we publish any code to our Production environment (this includes engagements and the KC Bot), we must have a code review by engineering and restrict the publication process to a small OPS team.  Because Gainsight PX does not have an internal audit trail for publication, we have to use a complicated workflow in Jira to build an acceptable audit trail.  This can add days to the publication of an engagement.

Please add a review/approval process for publication to the production environment.  It needs to include date/time stamps with person taking action, and have the approvers controlled by role.  A good model to follow is Split (who is a Gainsight customer) for feature flag control.

We are currently working on providing a basic Audit Log - which would provide a timeline from when engagement was Created, Launched, Paused, Re-published - and details of who did it.
It would not have the details of what was actually edited, like Audience rules or Content.

This capability has been partially delivered and allows users to view Engagement Logs.

The logs provide a timeline view of key engagement activities, including who created, edited, launched, or published an engagement.

At present, the logs do not provide detailed information about what specific changes were made during edits. However, they do capture who last updated the engagement.

For more information, refer to the documentation:
https://support.gainsight.com/PX/Engagements/02_Test_Engagement_Configuration/Track_Engagement_Changes