Email redaction administration; improvement suggestion

adamd641
Fri, 16 Aug 2024 09:30:24 +0000
Product Feedback

Context:
Sending email notifications after execution of actions which are un-redacted without switching off redaction for all users in a group or a particular domain.

Suggested improvement is to allow finer grain control over redaction exceptions, for example being able to apply them to a particular action (with authorisation of a info governance admin for example) or particular code repos / pipelines with a similar propose and approve workflow.

Why we cannot do it today:
Email redaction is a good idea and necessary given the risk of data leakage, however there are some use cases where for use experience purposes and where un-redacted email notifications are necessary. Currently this can only be disabled for specific user groups or delivery domain which results in a higher risk of mistakes or breaches.

Workarounds:
The current workaround is to use an external email service such as SES in conjunction with Egress policies, which can be invoked via actions and affords a higher degree of control of what / who can trigger notifications.

Benefits:
This will allow for better, more relevant email notifications from appropriately controlled and governed resources in Foundry while keeping in place the strict and necessary redaction for other areas of the platform where data leakage could be more of an issue

3 posts - 3 participants