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

Add Testing Tools to the Security Policy #1211

Closed
ArielSAdamsNASA opened this issue Mar 5, 2021 · 0 comments · Fixed by #1212
Closed

Add Testing Tools to the Security Policy #1211

ArielSAdamsNASA opened this issue Mar 5, 2021 · 0 comments · Fixed by #1212
Assignees
Labels
docs This change only affects documentation.
Milestone

Comments

@ArielSAdamsNASA
Copy link

Is your feature request related to a problem? Please describe.
Users are unaware of how cFS/cFE is tested. By providing this information, transparency is provided to the community which promotes trust.

Describe the solution you'd like
The security policy should inform users what tools are being used to test cFS/cFE while being cautious of liability issues. To do so, we can state explicitly that our software does not provide liability under the Apache license. The security policy should inform users that they may view the LGTM results. The policy would state that the alerts from LGTM may not be accurate, since they cannot be dismissed.

Add that security report should be emailed.

Additional context
References: https://github.com/thanos-io/thanos/security/policy

Requester Info
Ariel Adams, ASRC Federal

@ArielSAdamsNASA ArielSAdamsNASA added the docs This change only affects documentation. label Mar 5, 2021
@ArielSAdamsNASA ArielSAdamsNASA self-assigned this Mar 5, 2021
@skliper skliper added this to the 7.0.0 milestone Sep 24, 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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants