Potential fix for code scanning alert no. 42: Clear-text logging of sensitive information #37
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.
Potential fix for https://github.com/fabriziosalmi/caddy-waf/security/code-scanning/42
To fix the problem, we need to ensure that sensitive information is redacted or obfuscated before being logged. This can be achieved by implementing a function that checks for sensitive keys and redacts their values in the log fields. We will modify the
prepareLogFields
function to include this redaction process.prepareLogFields
function to call the redaction function before returning the log fields.sensitiveKeys
array and replaces their values with a redacted string.Suggested fixes powered by Copilot Autofix. Review carefully before merging.