Contributing to Cloud Native SecurityHub
- Contributing to SecurityHub
Code of Conduct
Cloud Native Security Hub has has a Code of Conduct to which all contributors must adhere, please read it before interacting with the repository or the community in any way.
How to Contribute a Security Resource
- Fork this repository
- Create a YAML file under
resources/falcodirectory to create a Falco rule
- You can use an existing YAML file as template and fill out the YAML fields with your security resource information
- Ensure your security resource is a valid YAML file:
make checkwill check all rules
- Submit a pull request
NOTE: In oder to make reviewing and merging of PRs faster, please submit changes to multiple security resources in separate PRs.
And thank you very much for taking time to contribute!
Other discussion, and support requests should go through the
#cloud-native-security-hub channel in the Sysdig slack, please join
Developer Certificate Of Origin
The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project.
Contributors to the Falco project sign-off that they adhere to these
requirements by adding a
Signed-off-by line to commit messages.
This is my commit message Signed-off-by: John Poiana <email@example.com>
Git even has a
-s command line option to append this automatically to your commit message:
$ git commit -s -m 'This is my commit message'