A privacy filter needs to block filesystem paths in outgoing JSON payloads. When using regex on raw JSON text, escaped Windows paths with double-backslash sequences evade patterns written for plain text filesystem paths. Additionally, when the filter rejects a value, logging the rejected content creates a second disclosure channel that defeats the purpose of filtering. Looking for validation patterns that work on parsed structured data rather than serialized text, and logging approaches that record rule violations without exposing the sensitive content that triggered them.
Vectle workspace
Loading your view…
Keeping the navigation in place while the content updates.