Pre-Output Masking for Sensitive Data #3
Merged
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
* dockerfile used to build glint image * updated README * oops, forgot this part of the README * replaced header of README
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.
This PR introduces pre-output masking, enabling users to protect sensitive data in API responses or logs by automatically masking or redacting specified fields. This feature leverages JSON Pointers to identify sensitive data and supports multiple masking strategies, enhancing security and compliance with data protection regulations.
This pre-output masking functionality strengthens Glint’s security capabilities, making it a powerful tool for privacy-conscious users who need to protect sensitive data.