**Title:** fix: redact PII in structured logs#829
Open
SHEROSE0 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#closes #420
Description:
This PR introduces a secure redaction layer for request body logging to ensure compliance with sensitive data handling (specifically Stellar memo PII).
Changes Implemented:
app/lib/privacy.ts: Created a centralized utility module containing regex-based masking for emails, phone numbers, and base32 strings.app/lib/logger.ts: Integrated theredactPIIutility into the serialization pipeline, ensuring request payloads are sanitized before logging.Acceptance Criteria Checklist:
Testing Notes:
#closes