1. Scope

This policy covers:

  • the riSim Studio software: the extension for Visual Studio Code, the command-line tools, and the simulator toolchains;
  • the installers and the downloads at dl.risim-studio.com;
  • this website, risim-studio.com, and our license service at license.risim-studio.com and bridge.risim-studio.com.

Some of these run on services of third parties, such as Amazon Web Services for the downloads and Hetzner for this website and the license service: our configuration and our software on them are in scope, the providers' own systems aren't (section 5).

We provide security updates free of charge for all plans, including the free plan, until the end of December 2031, in the latest release (clause 7.1 of our license terms). A release that only fixes a vulnerability doesn't change the free plan's limits or features; where technically feasible, we release security updates separately from other changes. Earlier releases stay available for download, so that projects can pin them in risim-config.toml, but they don't get security fixes: to get a fix, update to the latest release, and update the version that your projects pin.

Vulnerabilities in third-party components that riSim Studio ships, or that our services use, are in scope where they affect riSim Studio; we may pass the technical details on to the component's maintainers.

Simulating a design runs it: through VHDL's file access (TEXTIO), a design can read and write any file that you can, so simulate a design you don't trust only as you would run a program you don't trust, for example under a separate user account (see files and security). What a design can do by those means isn't a vulnerability, and reports of it are out of scope; a way for a design or a project file to do more than that, for example to run other programs or to get around the license checks, is. Crashes and hangs on invalid or endlessly running designs are bugs, which you can report in the issue tracker.

Not in scope are tests by denial of service, load, or brute force, social engineering, physical attacks, and reports from automated scanners without a demonstrated impact.

2. How to report

Send your report by email to security@risim-studio.com, in English or German. Please don't report vulnerabilities through the contact form, which isn't meant for confidential information, or in public, such as in issues, forums, or social media, and don't disclose a vulnerability before the time in section 4.

3. What to include

  • the affected component and its version (risim --version, or the version of the extension);
  • the operating system and its version;
  • a description of the vulnerability and of its impact;
  • the steps to reproduce it, ideally with a minimal example or a proof of concept;
  • whether, and when, you plan to disclose it;
  • how you would like to be credited, if at all.

Please don't send us your designs or other confidential data; if a reproduction needs them, we agree on a way first.

4. What happens next

  • We confirm the receipt of your report within 3 working days (Monday to Friday, except public holidays in Rhineland-Palatinate).
  • We aim to tell you our assessment, and what we plan to do, within 30 working days.
  • We keep you informed of our progress, and aim to fix a vulnerability within 90 days of the report; severe and actively exploited vulnerabilities come first.
  • Once a fix is released, we publish an advisory with the affected versions, the impact, the severity, and how to remedy it, on this page, under Advisories, and in the release notes of the extension, and credit you if you wish; if publishing it right away would put users at risk, we may wait until they've had the chance to update.
  • Please disclose a vulnerability only after we've published our advisory, or 90 days after your report if we haven't by then, unless we agree with you on another date; a way around the license checks or the limits of simulation threads isn't disclosed at all (section 5).
  • If a vulnerability is actively exploited, we report it to the authorities as the Cyber Resilience Act requires and, where needed, inform the affected users.

Apart from the safe harbour in section 5, which binds us, this policy describes how we handle reports and isn't a contract; it gives no rights beyond those of our license terms. We don't pay for reports.

5. Safe harbour

We, xq-Tec GmbH, authorize security research on the software and services in scope (section 1) that follows this policy. For such research, you may analyze the Software on machines of your own, also by decompiling or disassembling it, and run it in virtual machines and containers, despite clauses 3.2 and 4.3 of our license terms. You may also try to get around its license checks (clause 4.1), but only to show that it's possible. This doesn't extend your plan: you may not use the Software, or what you find, for anything else. We won't bring civil claims against you for such research, and we won't file a criminal complaint or an application for prosecution against you.

Research follows this policy if you:

  • test only what section 1 covers, and only with machines, accounts, license keys, trials, and email addresses of your own;
  • don't access, copy, change, or delete data of others; if you come across such data, you stop, tell us right away, don't keep or pass it on, and delete it;
  • don't disrupt or degrade our services or those of others, for example by load tests, flooding, or brute force;
  • report a way around the license checks or the limits of simulation threads only to us, and don't publish or pass it on;
  • report the vulnerability to us first, and disclose it only as section 4 says;
  • don't ask for payment or anything else in return for your report or for not disclosing it.

If you're unsure whether a test is allowed, ask us first. We can't bind prosecutors, courts or other authorities, or third parties such as our customers and providers. We still meet our duties to report to authorities, for example of a personal data breach or of an actively exploited vulnerability, and we may block traffic and suspend accounts and license keys to protect our services. If someone else takes action against you for research under this policy, we'll confirm to them, at your request, that you acted under it. This policy can't authorize tests of the systems of third parties, such as those of Amazon Web Services, Hetzner, Scaleway, mailbox.org or the Visual Studio Marketplace; their own rules apply to them. German law applies to this section.

6. Your data

We use your report and your contact details to handle the report and fix the vulnerability (Art. 6(1)(f) GDPR), and name you in an advisory only if you ask us to (Art. 6(1)(a) GDPR). We may pass the technical details on to the maintainers of an affected third-party component and, for an actively exploited vulnerability, to the authorities under the Cyber Resilience Act; we pass on your name only if you agree. We delete your contact details 3 years after we've closed the report, and keep its technical content without them. More, including who hosts our email, is in our privacy policy.

7. Advisories

None so far.