diff --git a/README.md b/README.md index 9df2cd5..21755ca 100644 --- a/README.md +++ b/README.md @@ -4,3 +4,4 @@ This repository contains files related to many or all repositories withing the ` - the [Siemens Contributor License Agreement](cla/) and related automation - the [Siemens organization profile](profile/) +- a [default security policy](SECURITY.md) for repositories that don't have their own diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..4e82fb2 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,24 @@ +# Security Policy + +Siemens takes the security of its code seriously. If you think you have found a security vulnerability, +please read the next sections and follow the instructions to report your finding. + +## Scope of this policy + +This is the default security policy for all repositories within the `siemens` organization on GitHub.com. + +It does not apply for reposities that have their own security policy. +It also does not apply for forks where you should follow the upstream policy instead. + +If you are unsure whether the policy applies feel free to reach out via the channels mentioned below and we'll be happy to help. + +## Reporting a Vulnerability + +Please DO NOT report any potential security vulnerability via a public channel (mailing list, GitHub issue, etc.). +Instead, [report the vulnerability privately via GitHub](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability) +(if enabled for the repository) or [contact us via email](mailto:opensource@siemens.com). + +Please provide a detailed description of the issue, the steps to reproduce it, the affected version(s) and, if already available, +a proposal for a fix. You should receive a response within 5 working days. If for some reason you do not, please follow up via email to ensure we received your original message. + +If we confirm the issue as a vulnerability, we will publish an advisory (e.g. on GitHub) and give credits for your report if desired. We follow the [coordinated vulnerability disclosure](https://vuls.cert.org/confluence/display/CVD) model and will define an appropriate disclosure timeline together with you.