Responsible disclosure
Report a vulnerability in Vellaci
We welcome reports from security researchers and customers. We acknowledge within 2 business days, keep you informed, and coordinate publication. Please do not access other customers' data, run denial-of-service tests or use social engineering.
Scope
Vellaci web application, public API, CLI, integrations and infrastructure operated by Vellaci. Third-party services are out of scope unless the issue is in how Vellaci uses them.
What to include
- The affected URL, endpoint or component
- Steps to reproduce and a minimal proof of concept
- The impact you demonstrated, not only the theoretical one
- How we can reach you, and whether you want to be credited
What we commit to
- Acknowledge within 2 business days
- Triage and severity assessment within 5 business days
- Fix timelines: critical 7 days, high 30 days, medium 90 days
- Credit in our acknowledgments (opt-in)
- No legal action against good-faith research that follows this policy
Rewards
Vellaci does not currently run a paid bug bounty. We credit reporters who want it and coordinate the publication date with you.
Encrypted contact
E-mail security@vellaci.ch. A PGP key is provided on request until published here. Machine-readable contact: security.txt.
Acknowledgments
No public acknowledgments yet.
Out of scope
Findings we will close without action
These are reported often but carry no demonstrable risk on their own. If you can chain one into real impact, report the chain.
- Reports from automated scanners without a demonstrated, reproducible impact
- Missing or permissive SPF, DKIM or DMARC records, and missing security headers without a working exploit
- Clickjacking on pages without state-changing actions, CSRF on logout, self-XSS
- Software or version disclosure, verbose banners and descriptive error messages without further impact
- Rate limiting on non-authentication endpoints, and denial-of-service or load testing of any kind
- Social engineering, phishing and physical attacks against Vellaci staff, offices or customers
- Vulnerabilities in third-party services, unless the issue is in how Vellaci configures or uses them
Policy updated . Follows the coordinated disclosure principles of ISO/IEC 29147 and ISO/IEC 30111.
For manufacturers
Need a disclosure policy like this for your own products?
The Cyber Resilience Act requires manufacturers to put in place and enforce a coordinated vulnerability disclosure policy and to publish a contact address for vulnerability reports (Annex I Part II(5)–(6)).