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

Implement a Security Policy #1068

Closed
ArielSAdamsNASA opened this issue Jan 6, 2021 · 0 comments · Fixed by #1048 or #1109
Closed

Implement a Security Policy #1068

ArielSAdamsNASA opened this issue Jan 6, 2021 · 0 comments · Fixed by #1048 or #1109
Assignees
Labels
docs This change only affects documentation. security
Milestone

Comments

@ArielSAdamsNASA
Copy link

Describe the bug
Create a security policy for users on how to report security vulnerabilities.

Expected behavior
The security policy should instruct users on how to report security vulnerabilities and provide them additional contact information for questions and concerns.

Additional context
Additional sections that may be included:

  • What to expect security-wise such as what type of testing is done
  • Address privacy concerns
  • Supported versions
  • License
  • Known vulnerabilities

References to Public Security Policies:
https://github.com/thanos-io/thanos/security/policy
https://github.com/minhealthnz/nzcovidtracer-app/security/policy
https://github.com/odoo/odoo/security/policy

Reporter Info
Ariel Adams, ASRC Federal

@ArielSAdamsNASA ArielSAdamsNASA self-assigned this Jan 6, 2021
@ArielSAdamsNASA ArielSAdamsNASA added security docs This change only affects documentation. labels Jan 6, 2021
astrogeco added a commit that referenced this issue Jan 21, 2021
Fix #1068, Create cFE Security Policy Markdown
@astrogeco astrogeco added this to the 7.0.0 milestone Jan 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs This change only affects documentation. security
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants