Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

implementors should employ response sanitization #28

Open
BenGardiner opened this issue Feb 28, 2019 · 0 comments
Open

implementors should employ response sanitization #28

BenGardiner opened this issue Feb 28, 2019 · 0 comments
Milestone

Comments

@BenGardiner
Copy link
Member

implementors should have response sanitization to ensure that responses from the the open api instance do not contain any secrets. at least:

  • passwords
  • tokens or keys used for upstream (if this is a bridge instance) or other TSP internal services (if this is an integrated instance)

if returning secrets is required for a particular endpoint, then an exception should be made

This is related to #22 -- which could be resolved by sanitizing responses for stacktraces also

Also, the separation of PII designed by account role segmentation could also be shored-up with response sanitization.

@BenGardiner BenGardiner added this to the Later milestone Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant