Fix #743, Create OSAL Security Policy Markdown#696
Fix #743, Create OSAL Security Policy Markdown#696astrogeco merged 1 commit intonasa:integration-candidatefrom ArielSAdamsNASA:SecurityPolicy
Conversation
ArielSAdamsNASA
added
the
CCB:Ready
ArielSAdamsNASA
changed the title
ArielSAdamsNASA
changed the title
astrogeco
added
CCB-20210106
and removed
CCB:Ready
astrogeco
left a comment
astrogeco
left a comment
There was a problem hiding this comment.
Follow similar format for cFS and other submodules
SECURITY.md
Outdated
|
|
||
| ## Reporting a Vulnerability | ||
|
|
||
| To report a vulnerability, submit the issue via Github in the subsystem it applies to. |
There was a problem hiding this comment.
Swap the first two lines and combine them as so
To report a vulnerability for the Operating System Abstraction Layer (OSAL) please [submit an issue](URL to issue)
For general cFS vulnerabilities please [open a cFS framework issue](URL to open an issue at the bundle level) and see our [top-level security policy](URL to cFS-bundle security.md)
I think we can leave the "other subsystem" part out since they'll see that if they navigate to the bundle repo.
SECURITY.md
Outdated
|
|
||
| ## Additional Support | ||
|
|
||
| For additional support, reach out to [email protected]. This mailing list includes all community members/users of the NASA core Flight Software (cFS) product line. |
There was a problem hiding this comment.
Replace "reach out" with "email us at"
Swap [email protected] with [email protected] since the community list will bounce messages from non-members.
Keep the community mailing list sentence and add the clause "For help using OSAL and cFS"
There was a problem hiding this comment.
@astrogeco Please let me know if the changes meets your requests. I will then apply the same format to cFS and other submodules.
ArielSAdamsNASA
changed the title
4 participants
Describe the contribution
Fixes #743
Created a draft of a security policy markdown file for OSAL. 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