Introduction
At Cortech, our ambition is to be a best-in-class provider of high-quality software solutions, delivering excellence across the customer experience while continuously improving our people and processes. Ensuring the security and integrity of our products and customer information is central to achieving this ambition.
This Vulnerability Disclosure Policy outlines our approach to addressing security vulnerabilities. We recommend you read this policy in full before reporting a vulnerability and ensure you act in compliance with it. We value those who take the time and effort to report security vulnerabilities responsibly. Please note, however, that we do not offer monetary rewards for vulnerability disclosures.
Reporting Vulnerabilities
If you believe you have identified a security vulnerability, you may report it through one of the following channels:
Security email: security@cortech.co.uk
Support email: support@cortech.co.uk
Support desk phone: +44 (0)1925 750 607
Vulnerability Disclosure Policy Web Page: https://cortech.co.uk/vulnerability-disclosure-policy/
Additionally, Cortech actively monitors the National Vulnerability Database (NVD) to identify and address potential flaws. https://nvd.nist.gov/
Please include the following information in your report:
* A brief description of the type of vulnerability (e.g. “XSS vulnerability”).
* The Site, Application, IP address, or Web Page where the vulnerability can be observed (ideally with the version number if available).
* Steps to reproduce. These should be a benign, non-destructive, proof of concept. This helps to ensure that the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers.
Severity Classifications
We use the Common Vulnerability Scoring System (CVSS v4.0 https://www.first.org/cvss/ ) to classify vulnerabilities based on their severity.
Acknowledgement and Communication
Initial Acknowledgement.
* All reported vulnerabilities will be logged into our case module, automatically generating a unique reference number.
* An acknowledgement receipt will be sent in accordance with the CVSS classification table below:
| CVSS Classification | CVSS Score | Acknowledgement |
| Low | 0.1 to 3.9 | 3 Working Days |
| Medium | 4.0 to 6.9 | 1 Working Day |
| High | 7.0 to 8.9 | 1 Working Day |
| Critical | 9.0 to 10 | 1 Working Day |
Remediation and Updates
Triage and Resolution
We aim to triage your report within 10 working days and prioritise remediation based on impact, severity, and exploit complexity.
Vulnerability resolution timelines may vary depending on the nature and severity of the issue.
Communication During Remediation
Regular Updates
Affected users and partners will receive regular progress updates detailing the development and implementation of solutions.
The security vulnerability page on our website will be updated consistently with the latest information, including estimated timelines for resolutions.
End User Notification
All affected end users and relevant technical partners will be informed within 7 days of a vulnerability being reported.
Post-Resolution Disclosure:
Once your vulnerability has been resolved, we welcome requests to disclose your report. We’d like to unify guidance to affected users, so please do continue to coordinate public release with us.
Guidance for Responsible Reporting
You Must NOT:
* Break any applicable law or regulations.
* Access unnecessary, excessive or significant amounts of data.
* Modify data in the Organisation’s systems or services.
* Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
* Attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests.
* Disrupt the Organisation’s services or systems.
* Submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with “best practice”, for example missing security headers.
* Submit reports detailing TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS1.0 support.
* Communicate any vulnerabilities or associated details other than by means described in the published security.txt.
* Social engineer, ‘phish’ or physically attack the Organisation’s staff or infrastructure.
* Demand financial compensation in order to disclose any vulnerabilities.
You Must:
* Always comply with data protection rules and must not violate the privacy of the Organisation’s users, staff, contractors, services or systems. You must not, for example, share, redistribute or fail to properly secure data retrieved from the systems or services.
* Securely delete all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law).
Legalities
This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with the law, or which might cause the Organisation or partner organisations to be in breach of any legal obligations.
