Arkitekt

Coordinated vulnerability disclosure policy

The CVD policy of Arkitekt.

Last modified: . We review this policy at least once a year.

1. Scope

This policy covers vulnerabilities in:

We consider a report a valid vulnerability if it

Output of automated tools or scanners without supporting explanation may not be treated as a valid report. We still read reports about issues that are already fixed, even when they don't start a new CVD process.

2. How to report

Use one of these contact options. Email addresses and telephone numbers are both accepted as ways for us to reach you; leave one with your report.

Product security (PSIRT)

For vulnerabilities in software Arkitekt ships.

Email: psirt@arkitekt.live
OpenPGP key: https://go.arkitekt.live/.well-known/pgp/psirt.asc
Fingerprint: D7B9 A162 DA4B C871 1C3C 9D46 EAF6 8605 EF40 FEA6

Infrastructure security (CSIRT)

For vulnerabilities in services and systems Arkitekt operates.

Email: csirt@arkitekt.live
OpenPGP key: https://go.arkitekt.live/.well-known/pgp/csirt.asc
Fingerprint: E904 021F 2EF9 5EC7 1A32 9A18 91EB 2A60 9F05 5969

Please encrypt and sign email to these addresses with OpenPGP. These contact options are valid until and are reviewed at least quarterly. Our security.txt is clearsigned with the key https://go.arkitekt.live/.well-known/pgp/security-txt.asc, fingerprint BA78 6FE4 2081 B350 7CAC F30B 363E B7A0 FBDE 0CCD.

You can also use the web form, with or without contact details. For confidential information we recommend encrypted and digitally signed email (OpenPGP).

A good report names the affected product or service and its version, describes the vulnerability and its impact, and includes steps to reproduce it. Complex issues may need further explanation or documentation from you. Good communication matters: if you don't answer technical or content questions, we may only be able to process your report in part, or not at all. Questions from you about the status of your report are always welcome.

We accept reports in: en, de.

Anonymous reports

You can report without giving any contact details through the web form. The form stores only what you type in, not your IP address. Because we can't ask you anything, an anonymous report can only be processed to a limited extent, or possibly not at all.

3. What we promise you

4. Response times

Unless a report was submitted anonymously:

No report is closed by a single analyst: closing or rejecting a report always needs a second person to agree.

5. Disclosure

Validated and verified vulnerabilities are publicly disclosed within 90 days. If there is a valid reason for delaying a fix, this period can be extended once by another 90 days, in close consultation with the national CSIRT. Only the national CSIRT can grant further extensions. Disclosure takes place at least in the European Vulnerability Database (EUVD) maintained by ENISA, and we agree the timing and content with you.

We notify our national CSIRT, CERT-Bund at the BSI, without undue delay about actively exploited vulnerabilities in our products or infrastructure. We keep it informed of new information, mitigations and their schedules, and coordinate with it.

6. When the process ends

We consider the CVD process for a report complete when:

Unless you reported anonymously, we tell you without undue delay when the process for your report has ended.

7. Code of conduct

We ask you:

If these rules are not followed, we will not list you on the acknowledgements page. We will still handle your report as well as we can.