How do YOU audit transform changes?

New transforms and changes to existing transforms are not captured in SailPoint audit logs, but transforms are certainly highly relevant to auditors. The transforms we use to determine lifecycle state, at the very least, should be considered in-scope for SOX at any publicly-traded company. There’s unfortunately also no event triggers or workflow triggers focused on transform changes, so we can’t even trigger anything automatically when a change is submitted.

Are your auditors not looking at or asking about this? If they are, what are you doing to show changes to transforms, and how are you doing it? Please share your processes!

And while we’re at it, please vote for this feature request on the Ideas portal asking for transforms changes to be included in audit logs!!

1 Like

You are right there is no audit log for transforms that we can see. For the tranform changes or infact any code changes the check-in history in a git hub tool should suffice here. Also if there is a rule how will you show the change to the auditor. If the code is properly checked it as soon as it is changed in the tenant then the history in the code repo can be shown to auditors as a work around.