Vulnerability Disclosure
Security is what we do. If you believe you have found a vulnerability in a OneFirewall product, service or website, we want to hear from you and will work with you to resolve it responsibly.
Submit a security report
support@onefirewall.com
Prefer email? Send your report, proof of concept and any attachments directly to our security team.
- Acknowledge your report within 3 business days
- Keep you informed while we triage and fix the issue
- Credit you publicly once resolved, if you wish
- Take no legal action against good-faith research
Machine-readable contact details are published at /.well-known/security.txt (RFC 9116).
Vulnerability Disclosure Policy
1. Purpose
This policy describes how OneFirewall Alliance LTD (“OneFirewall”) receives, handles and discloses reports of potential security vulnerabilities in its products and services. It sets out what reporters can expect from us and what we ask of them, following the principles of ISO/IEC 29147 and the internal handling process of ISO/IEC 30111.
2. Scope
In scope: onefirewall.com and its subdomains; the OneFirewall platform, portals and APIs; OneFirewall agents (including F3D); the OneFirewall MCP server; and mobile applications published by OneFirewall Alliance LTD.
Out of scope: denial-of-service or volumetric testing; social engineering, phishing or physical attacks against staff, offices or partners; spam; third-party products and services we do not operate (please report those to the relevant vendor); and automated scanner output without a demonstrated security impact.
3. How to report
Report vulnerabilities using the form on this page or by email to support@onefirewall.com. Our contact details are also published in machine-readable form at /.well-known/security.txt (RFC 9116). We accept reports in English, Italian and Spanish.
To help us verify the issue quickly, please include: the affected product, URL or component and version; a description of the vulnerability; step-by-step instructions to reproduce it; a proof of concept where possible; the potential impact; and how we can contact you. Reports may be submitted anonymously, although we may then be unable to keep you updated.
4. Our handling process
Every report follows the same five phases:
- Receipt – we acknowledge your report within 3 business days and give you a tracking reference.
- Verification – we reproduce and triage the issue, assess its severity (using CVSS) and confirm whether it is in scope. We aim to share our initial assessment within 10 business days.
- Remediation development – we develop, test and prioritise a fix or mitigation according to severity and risk to customers.
- Release – we deploy the fix and, where appropriate, publish a security advisory and notify affected customers.
- Post-release – we monitor the effectiveness of the fix, respond to follow-up questions and feed lessons learned into our secure development lifecycle.
We will keep you informed of progress throughout and let you know when the issue is resolved.
5. Coordinated disclosure and timelines
We follow coordinated vulnerability disclosure. We ask that you do not disclose the vulnerability publicly or to third parties until a fix is available or we have agreed a disclosure date with you. Our default target is to remediate and disclose within 90 days of the report; we may agree a shorter period for actively exploited issues, or ask for an extension where a fix is complex, explaining the reason.
Where a vulnerability affects other vendors, open-source components or multiple parties, we will coordinate with them and, where appropriate, with national CSIRTs and CVE Numbering Authorities.
6. Security advisories
When we publish a security advisory it will, where applicable, include: a unique identifier and CVE ID; the affected products and versions; a description of the vulnerability; its severity and CVSS score; the impact; remediation or mitigation steps; the disclosure timeline; and credit to the reporter (with their consent).
7. Guidelines for reporters
- Only test against accounts and data you own or have explicit permission to use.
- Do not access, modify, exfiltrate or delete data belonging to others; if you encounter personal or customer data, stop and report it immediately.
- Do not degrade or disrupt our services or those of our customers.
- Use the minimum testing necessary to demonstrate the vulnerability.
- Do not demand payment or make threats in exchange for information about a vulnerability.
- Comply with all applicable laws.
8. Safe harbour
Research carried out in good faith and in accordance with this policy is considered authorised. OneFirewall will not initiate or support legal action against you for such research, and if a third party brings a claim against you in connection with activity covered by this policy, we will make it known that your actions were authorised.
9. Recognition
OneFirewall does not currently operate a paid bug bounty programme. With your permission, we will publicly credit you in the relevant security advisory once the issue is resolved.
10. Confidentiality and data protection
Vulnerability reports are treated as confidential and shared internally only with those who need them to resolve the issue. Personal data you provide is processed solely to handle your report, in accordance with UK GDPR and our privacy notice. We will not share your identity with third parties without your consent.
11. Policy review
This policy is reviewed at least annually and whenever our products or processes change materially. Questions about this policy can be sent to support@onefirewall.com.
