# Audit identity attribute change

**URL:** <https://developer.sailpoint.com/discuss/t/audit-identity-attribute-change/62737>\
**Category:** IIQ Discussion and Questions\
**Tags:** identityiq\
**Created:** [June 5, 2024, 9:18am UTC](https://developer.sailpoint.com/discuss/t/audit-identity-attribute-change/62737 "2024-06-05T09:18:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kjakubiak](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/kjakubiak/32/7052_2.png) [@kjakubiak](https://developer.sailpoint.com/discuss/u/kjakubiak)\
**Post date:** [June 5, 2024, 9:21am UTC](https://developer.sailpoint.com/discuss/t/audit-identity-attribute-change/62737/2 "2024-06-05T09:21:46Z")

</div>

For authoritative application changes you can use this

> [@How to log Identity Attribute changes](https://developer.sailpoint.com/discuss/t/how-to-log-identity-attribute-changes/57992):
>
> Hello SailPoint Community, I wanted to share a simple BeanShell rule I’ve created achieve simple but quite important audit event. Usualy when incident happens it’s Identity Management System the one guilty of the problem. Sometimes it’s true but more often it’s just because of wrong data received from source systems. That’s why I believe it is crucial to have an audit trail for changes made to identity attributes due to updates in authoritative source systems. This rule logs all such changes in…

For manual changes you have to configure OoTB auditing for identity updates

 ![image](https://global.discourse-cdn.com/sailpoint/original/2X/f/f471dbd57c8dd6a5e178c0a7175e0377dd170b6e.png)

---

_[View the full topic](https://developer.sailpoint.com/discuss/t/audit-identity-attribute-change/62737)._