-
Notifications
You must be signed in to change notification settings - Fork 223
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
Fix #173, Create Security Policy MarkDown #163
Fix #173, Create Security Policy MarkDown #163
Conversation
CCB 2021-01-06 APPROVED
|
I called the hotline (877-627-2732) and was told that it is a publicly available service and there are no requirements regarding emailing or calling the service. I was told that there would be no concerns or issues placing the information in a security policy on a public GitHub Repository. Additional References: https://www.nasa.gov/content/cybersecurity-policies
https://www.nasa.gov/offices/ocio/ittalk/07-2010_soc.html
https://hackerone.com/nasa?type=team
I updated the three security policies to include instructions on tagging reports with the security label. I added the security label to cFE, so now all repos have that label available. |
8f82396
to
d859dde
Compare
Fix nasa#63, remove macros within C code
Describe the contribution
Fix #173
Created a draft of a security policy markdown file. The purpose of a security policy is to inform users on how to submit bugs or vulnerabilities. It is ideal to include a section for supported versions.
Additional context
Optional sections that may be included:
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
Contributor Info - All information REQUIRED for consideration of pull request
Ariel Adams, ASRC Federal