Repository: Information Exchange Standard (IES)
Description: Details the responsible disclosure process for security vulnerabilities.
The Information Exchange Standard (IES) initiative follows a Coordinated Vulnerability Disclosure (CVD) process to ensure security risks are addressed responsibly.
By reporting security vulnerabilities through the responsible channels, you agree to:
- Not disclose details of the vulnerability publicly until IES maintainers have had a reasonable opportunity to fix it.
- Provide IES maintainers with adequate time to assess and mitigate the risk.
- Act in good faith and follow ethical security research principles.
The IES initiative reserves the right to take necessary action against unauthorised or harmful security testing activities.
IES takes security seriously and encourages responsible reporting of vulnerabilities.
If you believe you have found a security vulnerability in this repository, please do not report it publicly. Instead, follow the steps below to disclose the issue responsibly.
- Do not open a public issue on GitHub. Instead, report security concerns via email to [[email protected]].
- Provide detailed information about the vulnerability, including:
- A clear description of the issue.
- Steps to reproduce the vulnerability.
- Potential impact or risk level.
- Any suggested mitigation strategies.
- Allow time for assessment and response. IES maintainers will review the report and respond within 10 working days to acknowledge receipt.
- Cooperate with IES maintainers to validate and address the issue.
Once a resolution has been identified, IES may choose to:
- Release a patch as part of the next scheduled update.
- Issue a security advisory if the issue is critical.
- Provide acknowledgments where appropriate (subject to IES disclosure policy).
This security policy applies to:
- All IES repositories released as open source
- Code, configuration files, and documentation maintained by IES
- Third-party dependencies included within IES repositories
If you identify a vulnerability in a third-party component that IES relies on (e.g., outdated libraries or known security flaws in dependencies), we encourage you to report it.
Out of scope:
- Issues related to third-party services or software not used within IES repositories
- Vulnerabilities in user environments unrelated to this repository
- Unsolicited security testing or penetration testing without explicit permission
To help maintain security across IES repositories, the following practices are observed:
- Dependencies are scanned and updated regularly (e.g., using automated tools like Dependabot)
- Sensitive credentials must not be included in public repositories
- Security patches are applied in a timely manner, with priority given to critical vulnerabilities
For more details, refer to our internal Secure Development Guidelines (where available).
© Crown Copyright 2025
Maintained as part of the Information Exchange Standard initiative.
This repository is under the custodianship of the Department for Business and Trade (UK), acting on behalf of a cross-government group of stakeholders.
Licensed under the Open Government Licence v3.0.
For full licensing terms, see OGL_LICENSE.md.