Skip to content

Conversation

@benlk
Copy link
Collaborator

@benlk benlk commented Jun 6, 2019

This starts the work of adding a security policy for the INN organization on GitHub, which will provide answers to people who want to report security vulnerabilities in INN's products. Resolves #6

Research

Questions

  • What email address should we send people to? Should we tell people how that email is routed if they are concerned about the chain of custody of such emails?
  • What physical address should people send mail to in event they do not want to, or are unable to, send an email? (Probably the INN main office, to a specific name care of INN)
  • What procedures do we need to implement on our end for the handling of security vulnerability reports? Where should we store those procedures? (INN/docs, likely)
  • Should we talk about email encryption, and if so, whose keys should we tell people to use, or where can we point people to find the keys used by INN's humans?
  • How should we thank people for reporting responsibly?
  • Do we want to set up something like HackerOne?

@benlk benlk requested a review from a team June 6, 2019 11:04
@benlk benlk requested review from joshdarby and kaylima September 20, 2019 22:31
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

Successfully merging this pull request may close these issues.

Create SECURITY

2 participants