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

Audit service to run over Recipe to highlight risks for EFPIA partners (e.g. sending Inchi key to a remote service) #1

Open
proccaserra opened this issue Nov 20, 2019 · 0 comments
Labels
priorization: long-term goal / not time-critical this issue was given low priorization by one of the admins.

Comments

@proccaserra
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Discussion with @egonw @nsjuty about the need to perform an Audit over any code included in the recipes to ensure the EFPIA partners (and others ?) that no data is leaked publicly or send to public services (e.g. sending a private/proprietary Inchi key to public REST service)

Describe the solution you'd like
A service that would raise warnings over any API call hitting a public service
A declarative document from the developer listing all the potential risks associated with using a service for an EFPIA partners

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priorization: long-term goal / not time-critical this issue was given low priorization by one of the admins.
Projects
None yet
Development

No branches or pull requests

1 participant