Text LogoText Logo

Responsible Disclosure Policy

Version 1.0 | Last updated January, 2025

 

CD Security Technologies GmbH (hereafter “CyberDanube”) is an Austrian company that uses self-developed technologies for services in the industrial sector. Starting from the core activity of developing and implementing solutions for information security, CyberDanube offers customers complementary services and expertise in defined areas. CyberDanube’s research division, CyberDanube Security Research, conducts in-depth security research mainly focused on networked industrial equipment. Identified vulnerabilities in such devices are handled carefully and aimed to be disclosed responsibly to the public.
Since the privacy, security and safety of our customers as well as users of any examined product is our highest good, CyberDanube Security Research is not disclosing any vulnerabilities that have been found during an engagement, research project or by one of our software products, as long as such a disclosure would result in any kind of risks for organizations or individuals. However, in certain cases it is also important, to ensure that critical security issues become transparent for potential users, to allow them to take proper action for protecting sensitive data or systems. As a result, CyberDanube commits to a responsible disclosure process, which ensures, that we value the privacy and confidentiality with our customers and partners, while at the same time provide critical security information to the community and public as soon as it becomes safe to do so.

Responsible Disclosure Process

CyberDanube is following best practices of the security industry. Therefore, our responsible disclosure process is based on Google’s vulnerability disclosure policy (https://about.google/appsecurity/).

We believe that vulnerability disclosure is a two-way street. Vendors, as well as researchers, must act responsibly. Therefore, CyberDanube adheres to a 90-day disclosure deadline by default, after which security vulnerabilities might be published. This 90-day deadline for disclosing begins after we notify the respective vendor(s) of the products/systems about the respective vulnerabilities – such a notification happens immediately after a new vulnerability is identified. Once the 90-day deadline expires – or sooner if the vendor releases a fix – further details will be shared in public with the defensive community . However, that deadline can vary in the following ways:

    • If a deadline is due to expire on a weekend or Austrian/US public holiday, the deadline will be moved to the next normal work day.
    • Before the 90-day deadline has expired, if a vendor lets us know that a patch is scheduled for release on a specific day that will fall within 14 days following the deadline, we will delay the public disclosure until the availability of the patch.
    • When we observe a previously unknown and unpatched vulnerability in software under active exploitation (a “0day”), we believe that more urgent action—within 7 days—is appropriate. The reason for this special designation is that each day an actively exploited vulnerability remains undisclosed to the public and unpatched, more devices or accounts will be compromised. Seven days is an aggressive timeline and may be too short for some vendors to update their products, but it should be enough time to publish advice about possible mitigations, such as temporarily disabling a service, restricting access, or contacting the vendor for more information. As a result, after 7 days have elapsed without a patch or advisory, we will support researchers making details available so that users can take steps to protect themselves.
  • We reserve the right to extend or cut deadlines in reasonable cases. Shifted deadlines are communicated to the vendor, with no exceptions.

 

Overall, it is important for us to clarify that the timeline of every disclosure of vulnerabilities will be aligned with vendors and/or customers in advance. In case there are reasonable justifications; to delay or advance disclosing certain details, we will always try our best to do so in alignment with the respective vendors and/or customers. The above-mentioned deadlines and default criteria for publishing security vulnerabilities aim to ensure, that we are able to provide security critical information in a timely manner even in situations, where affected vendors/partners/customers are not responsive and/or supportive in resolving the issue; through this we ensure that users and other affected individuals can take proper precautions for securing their data and infrastructure.

Please note, that while the timeline for disclosure of identified vulnerabilities might be subject to change and can be aligned in accordance with relevant circumstances, the decision about disclosure itself is solely up to CyberDanube.

CyberDanube does not take any liability for claims or damages which result from any disclosure done in accordance with this responsible disclosure policy. Furthermore, CyberDanube does not take responsibility for providing a full solution for any disclosed vulnerability; in case recommendations are provided alongside the disclosure of a new vulnerability, such recommendations are seen just as supplementary information which does not replace any kind of official recommendations or guidance provided directly by a vendor or supplier for the affected products.

HOW CAN YOU CONTACT US ?

If you have questions or comments about this notice, you may email us at office [at] cyberdanube.com or by mail to:

CD Security Technologies GmbH
Hohenauergasse 21A/1
Vienna, 1190
Austria