Repository navigation
2784 document backend log redaction - #2828
Merged
RUKAYAT-CODER merged 2 commits intoOct 17, 2026
Merged
RUKAYAT-CODER merged 2 commits into
RUKAYAT-CODER merged 2 commits into
Conversation
Add LOG_RETENTION.md to define backend logging standards including log levels, retention windows, and data protection rules. Closes EarnQuestOne#2734.
Closes EarnQuestOne#2784. Governance change limited to Governance/ folder. - Created Governance/backend/LOG_REDACTION.md documenting backend log-redaction requirements and sensitive-field policy - Listed all fields that must be redacted before logging (auth tokens, PII, financial data, cryptographic secrets) - Defined redaction methods (full redaction, partial masking, hash-based truncation, length-based truncation) - Specified implementation requirements for middleware, manual log statements, configuration, and testing - Documented exceptions for debug mode, audit logging, and security incident response - Set ownership to backend maintainers with 6-month review cadence - Linked from Governance/README.md
|
@boalambo Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
Thank you for contributing to the project |
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
2 participants
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.
Summary
This PR adds
Governance/backend/LOG_REDACTION.mdto document the backend log-redaction and sensitive-field policy, closing a governance gap. The document defines how backend services must redact sensitive fields before logging to protect user privacy and security while maintaining useful logs for debugging.Changes
Created
Governance/backend/LOG_REDACTION.mdwith:Updated
Governance/README.mdto link to the new documentAcceptance Criteria
Testing
This is a governance documentation change. No code changes or tests are required. The document itself includes testing requirements for future code implementations that must follow this policy.
Governance
This change is limited to the
Governance/folder and follows the governance amendment process defined inGovernance/AMENDMENTS.md.Closes #2784