Skip to content

Commit c329d0d

Browse files
committed
Fix #1211, Add Testing Tools to the Security Policy
1 parent 63b4347 commit c329d0d

File tree

1 file changed

+28
-3
lines changed

1 file changed

+28
-3
lines changed

SECURITY.md

Lines changed: 28 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,38 @@
44

55
To report a vulnerability for the cFE subsystem please [submit an issue](https://github.com/nasa/cFE/issues/new/choose).
66

7-
For general cFS vulnerabilities please [open a cFS framework issue](https://github.com/nasa/cfs/issues/new/choose) and see our [top-level security policy](https://github.com/nasa/cFS/security/policy).
7+
For general cFS vulnerabilities please [open a cFS framework issue](https://github.com/nasa/cfs/issues/new/choose) and see our [top-level security policy](https://github.com/nasa/cFS/security/policy) for additional information.
88

99
In either case please use the "Bug Report" template and provide as much information as possible. Apply appropraite labels for each report. For security related reports, tag the issue with the "security" label.
1010

11+
## Testing
12+
13+
**Disclaimer: nasa/cFE is not responsible for any liability incurred under the [Apache License 2.0](https://github.com/nasa/cFE/blob/main/LICENSE).**
14+
15+
Testing is an important aspect our team values to improve cFE.
16+
17+
To view tools used for the cFS bundle, see our [top-level security policy](https://github.com/nasa/cFS/security/policy).
18+
19+
### CodeQL
20+
21+
The [cFE CodeQL GitHub Actions workflow](https://github.com/nasa/cFE/actions/workflows/codeql-build.yml) is available to the public. To review the results, fork the cFE repository and run the CodeQL workflow.
22+
23+
CodeQL is ran for every push and pull-request on all branches of cFE in GitHub Actions.
24+
25+
For the CodeQL GitHub Actions setup, visit https://github.com/github/codeql-action.
26+
27+
### Cppcheck
28+
29+
The [cFE Cppcheck GitHub Actions workflow and results](https://github.com/nasa/cFE/actions/workflows/static-analysis.yml) are available to the public. To view the results, select a workflow and download the artifacts.
30+
31+
Cppcheck is ran for every push on the main branch and every pull request on all branches of cFE in Github Actions.
32+
33+
For more information about Cppcheck, visit http://cppcheck.sourceforge.net/.
34+
1135
## Additional Support
1236

13-
For additional support, email us at cfs-program@lists.nasa.gov. For help using OSAL and cFS, [subscribe to our mailing list](https://lists.nasa.gov/mailman/listinfo/cfs-community) that includes all the community members/users of the NASA core Flight Software (cFS) product line. The mailing list is used to communicate any information related to the cFS product such as current releases, bug findings and fixes, enhancement requests, community meeting notifications, sending out meeting minutes, etc.
37+
For additional support, submit a GitHub issue. You can also email the cfs community at cfs-community@lists.nasa.gov.
1438

15-
If you wish to report a cybersecurity incident or concern please contact the NASA Security Operations Center either by phone at 1-877-627-2732 or via email address soc@nasa.gov.
39+
You can subscribe to the mailing list [here](https://lists.nasa.gov/mailman/listinfo/cfs-community) that includes all the community members/users of the NASA core Flight Software (cFS) product line. The mailing list is used to communicate any information related to the cFS product such as current releases, bug findings and fixes, enhancement requests, community meeting notifications, sending out meeting minutes, etc.
1640

41+
If you wish to report a cybersecurity incident or concern, please contact the NASA Security Operations Center either by phone at 1-877-627-2732 or via email address soc@nasa.gov.

0 commit comments

Comments
 (0)