Addition of a security policy SECURITY.md to github.com/peeringdb/peeringdb

[netravnen]

Do we want to enable GitHubs functionality to privately report potential code security issues via GitHub?

When reading the docs I am not able to accurately identify any clear publicly available description for how to report potential code security issues to PeeringDB.

Links:

• https://github.com/peering-manager/peering-manager/security
• https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository
• https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability
• https://github.com/microsoft/.github/blob/main/SECURITY.md

Edit: If we already have a clear channel of communication for the above mentioned suggestion. Please disregard this issue.

[leovegoda]

We have this: https://docs.peeringdb.com/howto/make-a-security-report/

We should create a SECURITY.md and point it there, I suppose.

[netravnen]

Summary suggestion:

1. Create a SECURITY.md file at github.com/peeringdb/.github
2. Create /.well-known/security.txt on www.PeeringDB.com

---

Minimal /.well-known/security.txt

# Our security policy
Policy: https://docs.peeringdb.com/howto/make-a-security-report/

[mcmanuss8]

+1

[grizz]

+1

[jackcarrozzo]

Pc call: we have the policy so we might as well put it there

+1

[jbartig]

+1

[grizz]

This still needs ops work to add the .well-known/security.txt file

[leovegoda]

Completed via #1567