This reminds me of these enterprise solutions to prevent data leakage, Data Loss Prevention tools (Safetica, Forcepoint, etc.).
Could this be adapted to inherit DLP policies? I have a sample use case, for example:
- Some DLP customers don't need full name protection but might need to prevent credit card PAN numbers from being leaked, per a PCI DSS compliance standard. Expiration dates don't need protection, and only the first 6 and last 4 numbers of a credit card can be shown; CVV2 is off the table, of course.
By checking out the repo, I know this can be configured manually, but can you make it so that it inherits DLP configuration instead of manual configuration? This could considerably boost enterprise adoption.
Big companies don't want to keep manual maintenance of a separate tool, whereas if they adopt it and "just works" with their existing ecosystem, that's an easy win.
This is easily, easily something you could sell as a business exit to a DLP company, because it's one of the "limbs" of protection they offer.
Could this be adapted to inherit DLP policies? I have a sample use case, for example:
- Some DLP customers don't need full name protection but might need to prevent credit card PAN numbers from being leaked, per a PCI DSS compliance standard. Expiration dates don't need protection, and only the first 6 and last 4 numbers of a credit card can be shown; CVV2 is off the table, of course.
By checking out the repo, I know this can be configured manually, but can you make it so that it inherits DLP configuration instead of manual configuration? This could considerably boost enterprise adoption.
Big companies don't want to keep manual maintenance of a separate tool, whereas if they adopt it and "just works" with their existing ecosystem, that's an easy win.
This is easily, easily something you could sell as a business exit to a DLP company, because it's one of the "limbs" of protection they offer.