You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the ability to have a masked fields property. The desired behavior would be to still include the field in the audit (unless it was in the exclude list) but to mask it. Additionally it may be good to have a configuration for "MaskAllButLastXChars" which would take the number of characters to leave exposed.
For example, with something like a social security or credit card number, supposing MaskAlLButLastXChars = 4, replace the new/old values with ***1234. It would still be clear that the value was in the change set but information security wouldn't be violated.
The text was updated successfully, but these errors were encountered:
No worries, thanks for getting back when you did. I'm glad you think that idea is useful. Great job on the project. Easy to implement and easy to customize data that's saved if necessary.
Actual Behaviour
No field masking allowed
Desired Behaviour
Add the ability to have a masked fields property. The desired behavior would be to still include the field in the audit (unless it was in the exclude list) but to mask it. Additionally it may be good to have a configuration for "MaskAllButLastXChars" which would take the number of characters to leave exposed.
For example, with something like a social security or credit card number, supposing MaskAlLButLastXChars = 4, replace the new/old values with ***1234. It would still be clear that the value was in the change set but information security wouldn't be violated.
The text was updated successfully, but these errors were encountered: