At Clocktimizer, we the security of our systems is our number one priority. However, regardless of the time and effort we put into securing our systems, we acknowledge that there can be vulnerabilities present. The responsible disclosure of security vulnerabilities helps us ensure the security and privacy of our customers and our systems. This policy is designed to create a clear communication path around exploitable vulnerabilities.
We kindly request that all researchers:
- Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing;
- Perform research only within the scope set out below;
- Use the identified communication channels to report vulnerability information to us;
- Do not take in any way advantage of the vulnerability or problem you have discovered;
- Do not download, copy, transfer or publish any data and/or information that is exposed or accessible;
- Do not use the vulnerability or the security problem to gain access to the systems and services of Clocktimizer;
- Keep information about any vulnerabilities you have discovered confidential between yourself and Clocktimizer until (i) we have had 90 days to resolve the issue, or until (ii) we have notified you we have resolved the issue, whichever comes first.
If you follow these guidelines when reporting an issue to us, we commit to:
- Not pursue or support any legal action related to your research;
- Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 5 business days of submission), if the issue poses an actually exploitable vulnerability;
- Recognize, with your consent, your contribution on our Security Researcher List, if you are the first to report the issue and we make a code or configuration change based on the issue.
- Services under (a subdomain of) the domain .clocktimizer.com
Out of scope
Any services hosted by 3rd party providers and services are excluded from scope. These services include:
- Azure (to the extent the issue is not at a Clocktimizer application level)
- Google for Work / G-Suite
- Chargebee / Stripe
In the interest of the safety of our customers, staff, the Internet at large and you as a security researcher, the following test types are excluded from scope:
- Findings from physical testing such as office access (e.g. open doors, tailgating)
- Findings derived primarily from social engineering (e.g. phishing, vishing)
- Findings from applications or systems not listed in the ‘Scope’ section
- UI and UX bugs and spelling mistakes
- Network level Denial of Service (DoS/DDoS) vulnerabilities
Things we do not want to receive:
- Personally identifiable information (PII);
- Credit card holder data; and/or
- Our customer’s privileged and/or client confidential information.
How to report a security vulnerability?
If you believe you’ve found a security vulnerability in one of our products or platforms please send it to us by emailing firstname.lastname@example.org. Please include the following details with your report:
- Description of the location and potential impact of the vulnerability;
- A detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed screen captures are all helpful to us); and
- Your name/handle and a link for recognition in our recognized Security Researchers List or inform us that you do not want to be mentioned.
This Responsible Disclosure Policy is for a large part based on the Open Source Responsible Disclosure Policy, the original version of which is licensed under a Creative Commons Attribution 4.0 International License and can be read in its original form here.