Security & vulnerability reporting
If you find a security vulnerability in any of our products, we want to know — ideally before it becomes an incident. Here's how to report it, what to expect from us, and what we ask of you.
Report a vulnerability
Email security@esharp.se. The address goes straight to E-Sharp's management. Do not use public channels — GitHub issues, support tickets, social media or the ordinary contact form — for security reports.
If you need an encrypted channel, email us first and we'll arrange one. Please include:
- the affected product and version,
- impact and severity,
- steps to reproduce,
- relevant environment details,
- how you'd like to be credited.
What to expect from us
- We acknowledge your report within 24 hours, and that a human is reading it.
- An initial assessment within 5 working days.
- Updates at least every 14 days.
- Notice when a fix is released.
- If we decide not to fix something, we explain why.
We don't run a paid bug-bounty programme, but we're glad to offer public credit.
Safe harbour
We consider good-faith research that follows this policy to be authorised, and we won't take or support legal action against it. If you're unsure whether something is within the policy, email security@esharp.se and ask first.
What we ask of you
- Don't access, change or delete data that isn't yours — stop at the minimum needed to demonstrate a finding.
- Don't degrade services through overload, load testing or heavy automated scanning.
- Don't use social engineering, phishing or physical intrusion.
- If you come across personal data, credentials or customer information, report it immediately and keep no copy.
Coordinated disclosure
We ask for 90 days from your first report before a vulnerability is made public. We can agree longer timelines when a fix needs to reach hardware in the field. We're happy to join coordinated security advisories and same-day disclosure.
Scope
In scope: Probe, Assert, Trace, E-Sharp's MCP servers, Accordion instruments and modules, E-Sharp's USB PD power supplies, and the websites esharp.se and demo.esharp.se.
Out of scope: third-party services we use but don't operate, customer deployments where the issue lies in the customer's own configuration, and customers' own systems.
Low priority (unless real impact can be shown): missing security headers or TLS findings on the marketing site, self-XSS, missing rate limiting, unvalidated scanner output, and outdated versions with no exploitable vulnerability.
Regulatory compliance
E-Sharp is a manufacturer under the EU Cyber Resilience Act (Regulation (EU) 2024/2847). For actively exploited vulnerabilities or serious incidents, we report to CERT-SE and ENISA and inform affected users directly.
Contact
For vulnerability reports and security questions: security@esharp.se. For anything else, see esharp.se.