Vulnerability Disclosure Policy
WICHTIG: Die Vulnerability Disclosure Policy ist derzeit nur in englisch verfügbar.
At TRONITY, we take our commitment to security seriously. We understand that in today's digital age, security is paramount to the success and longevity of any organization. As such, we are dedicated to maintaining the highest levels of security in all areas of our business.
We understand that security threats are constantly evolving, and we are committed to remaining vigilant and proactive in our approach to security. We regularly review our security practices and procedures, and we work closely with experts in the field to identify potential vulnerabilities and mitigate any risks.
As part of our commitment to security, we have developed a Vulnerability Disclosure Policy (VDP) that outlines our procedures for handling security vulnerabilities that are discovered in our systems or products. This policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.
We believe that by maintaining an open and transparent approach to security, we can work together with the security research community to identify and address potential security issues, ultimately making our systems and products more secure for our customers.
If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized. We will work with you to understand and resolve the issue quickly, and TRONITY will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.
Under this policy, "research" means activities in which you:
- Do not break the law.
- Notify us as soon as possible after you discover a real or potential security issue.
- Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
- Only use exploits to the extent necessary to confirm a vulnerability's presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
- Provide us 90 days after you have received our acknowledgement of receipt of your report to resolve the issue before you disclose it publicly.
- Do not submit a high volume of low-quality reports.
Once you've established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.
The following test methods are not authorized:
- Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data.
- Physical testing (e.g., office access, open doors, tailgating), social engineering (e.g., phishing, vishing), or any other non-technical vulnerability testing
We are especially interested in the following test methods that identify the following:
- Cross Cross-Site-Request-Forgery-Attack (CSRF / XSRF)
- Persistent Cross-Site-Scripting (XSS)
- XML External Entity Injections (XXE)
- Bypass Authentification
- Encryption vulnerabilites
- Privilege escalation
This policy applies to the following systems and services:
Source code at https://github.com/tronity
Mobile apps provided for Android and iOS
Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in systems from our vendors fall outside of this policy's scope and should be reported directly to the vendor according to their disclosure policy (if any). If you aren't sure whether a system is in scope or not, contact us at email@example.com before starting your research.
Though we develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We will increase the scope of this policy over time.
Reporting a Vulnerability
We accept vulnerability reports at this form or via firstname.lastname@example.org. Reports may be submitted anonymously. We will never share your personal information with anyone unless we are required by law to do so, for instance with law enforcement agencies. If you share contact information, we will acknowledge receipt of your report within 3 business days.
We encourage you to encrypt the information, you can use our PGP pulbic key:
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQINBGRttxIBEADCUDYLf VPbUxlLflgGITvNGIITmH5L7kusBY7N1r 7XsVZe5z
KETJp ZiDIIH6 RL95jFhMcP8y2Lfufrz0 HtH59tU5 9zw6tX2co7fx2DX9Huu0
j 0LLc6lt5YvjWpZMid2Z1TofZk2QgRCnjfrdfQcnUOkOUVVNDc93bXovxY X4K2
AD4WIQTP8jPSeiZjEZBqn HxETU9 SIRYgUCZG23EgIbAwUJB4YeyAULCQgHAgYV
vCAw 7fsgDb9XAIzXLDyqAergIUOcqxGyT9j7 zOXtlS9up6l6ZO 0BfkQ8U8YdT
NGIPndD2nzJb1rtgdyzUhUa8G ejafHYdLnwV9yIEb5j3j5teAIvYtC/Lma A1nw
sQcz BRLL45/iSoWuie67N2IgYtxMAaqCG9c6u vcRI1lRhlwG4lRJfpX9b6P/fX
gj 3kNh2MsuHtIli tN7mlh/B/Kz/r38TeiMep jmtAlSHZFOLpvtHNDQlv63XQz
o4 AGXwuZ USEWpTVqYS8DMocmZrzEHFWlLQe172L9QvBjyfFthxbtFEhr9KuTDY
-----END PGP PUBLIC KEY BLOCK-----
By submitting a vulnerability, you acknowledge that you have no expectation of payment and that you expressly waive any future pay claims against TRONITY related to your submission.
TRONITY is committed to timely correction of vulnerabilities. However, we recognize that public disclosure of a vulnerability in absence of a readily available corrective action likely increases versus decreases risk. Accordingly, we require that you refrain from sharing information about discovered vulnerabilities until you have received our acknowledgment that we provided a fix. If you believe others should be informed of the vulnerability prior to our implementation of corrective actions, we require that you coordinate in advance with us.
What we would like to see from you
In order to help us triage and prioritize submissions, we recommend that your reports:
- Describe the location the vulnerability was discovered and the potential impact of exploitation.
- Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
- Be in English, if possible.
What you can expect from us
When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.
- Within 3 business days, we will acknowledge that your report has been received.
- To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
- We will maintain an open dialogue to discuss issues.
- Although we do not provide monetary compensation for submissions, we do acknowledge and appreciate the contributions of those who assist us in securing our systems and data. We will not name you without your consent. If appropriate, we will discuss the particulars of a public endorsement with the individual beforehand. Additionally, we offer a reward of up to 1000 Euros for critical findings based on the CVSS v3.0 rating (Critical 9.0-10.0).
Questions regarding this policy may be sent to email@example.com. We also invite you to contact us with suggestions for improving this policy.