Add Standard Audit Logging for Data Changes Performed by HelloID in Target Systems
Remco Houthuijzen
In the $outputContext.Data and $outputContext.PreviousData objects, we currently return the new and old data to HelloID. We would like to see a standard audit logging message whenever there are differences between the new and old data. This logging should include the old and new values, along with the corresponding fields.
Currently, we calculate these values in some PowerShell connectors, such as EntraID or TOPdesk.
The benefits of moving this functionality to HelloID include reduced PowerShell code complexity and increased consistency across target systems.
Example:
Old values:
DisplayName: Janine van den Boelen
Surname: van den Boelen
New values:
DisplayName: Janine de Vries
Surname: de Vries
R
Rick van den Dijssel
Hey Remco Houthuijzen, thanks for your feedback! I have a few more questions for you:
- What specific target systems should the audit logging feature support initially?
- How frequently do you anticipate needing to access these audit logs?
- Are there any specific compliance or regulatory requirements that the audit logs need to meet?
Remco Houthuijzen
Hey Rick van den Dijssel, thank you for your fast response.
- What specific target systems should the audit logging feature support initially?
The audit logging feature should ideally be generic, supporting PowerShell V2. It might be useful to include a Boolean setting in the target system configuration to enable or disable this logging as needed. Starting with the built-in Active Directory (AD) system could also be a practical first implementation.
- How frequently do you anticipate needing to access these audit logs?
When a customer is new to HelloID, the audit logs will likely be accessed frequently, especially if certain values change unexpectedly. The logs provide precise details about when changes occurred and what values were updated. Additionally, the audit logs offer customers valuable insights, potentially reducing the need for support and lowering the learning curve for understanding HelloID provisioning.
- Are there any specific compliance or regulatory requirements that the audit logs need to meet?
Not that I’m aware of. However, having these audit logs in Elastic adds significant value. For example, makes it easier to search for specific situations, and it also allows for longer retention times.