TheArchive/zitadel
1
0
Fork 0
mirror of https://github.com/zitadel/zitadel.git synced 2024-12-12 11:04:25 +00:00
Code Issues Packages Projects Releases Wiki Activity
f7c4141147
zitadel/SECURITY.md
mffap 4d30d3a7e1
chore: various typos (#3686) 
* fix(cli): typo in clis

* chore: fix typos in guides and readme

* markdown lint

* readme typos

* markdown lint

* typos in security.md

* login de

* login en

* console de

* console en

* Apply suggestions from code review

E-Mail instead of Email

Co-authored-by: Florian Forster <florian@caos.ch>

Co-authored-by: Florian Forster <florian@caos.ch>
2022-05-21 10:44:09 +00:00

1.5 KiB
Raw Blame History

Security Policy

At ZITADEL we are extremely grateful for security aware people who disclose vulnerabilities to us and the open source community. All reports will be investigated by our team.

Supported Versions

Version Supported
2.x.x ✅ as soon as officially released
1.x.x ✅
0.x.x ❌

Reporting a vulnerability

To file an incident, please disclose it by e-mail to security@zitadel.com including the details of the vulnerability.

At the moment GPG encryption is no yet supported, however you may sign your message at will.

When should I report a vulnerability

  • You think you discovered a
    • potential security vulnerability in ZITADEL
    • vulnerability in another project that ZITADEL is based on
  • For projects with their own vulnerability reporting and disclosure process, please report it directly there

When should I NOT report a vulnerability

  • You need help applying security related updates
  • Your issue is not security related

Security Vulnerability Response

TBD

Public Disclosure

All accepted and mitigated vulnerabilities will be published on ZITADEL's GitHub Security Page.

Timing

We think it is crucial to publish advisories ASAP as mitigations are ready. But due to the unknown nature of the disclosures the time frame can range from 7 to 90 days.