Vulnerabilities
Vulnerability management: how to report a flaw to us
Think you have found a flaw in the platform? Here is how to report it to us, what we ask of you, and how fixes are distributed.
Contents
No software is free of defects. What matters is how a defect is reported, handled and fixed. This page is for our customers’ security teams, integrators and anyone who thinks they have discovered a vulnerability in the platform.
How to report a flaw to us
Reports go through the contact page, choosing the subject “Security / compliance”. Briefly describe the problem in this first message, without attaching exploitation details: we will get back to you to agree on an exchange suited to the level of sensitivity.
What we ask of you
A useful report makes it possible to reproduce the problem and measure its scope. Where possible, indicate:
- the platform version concerned, visible from the interface;
- the component involved: interface, analysis engine, comparison, inventory connector, license;
- the steps to reproduce the problem and the observed result;
- the impact you foresee: unauthorized access, data leak, unavailability;
- your contact details, so we can keep you informed.
Please test only on an installation you are responsible for, do not access other people’s data, and do not make the problem public before a fix is available.
How a report is handled
Receipt
We acknowledge receipt of the report and get back to you for the next steps.
Analysis
We reproduce the problem, assess its severity and identify the affected versions.
Fix
The fix is developed, tested, then published as a new signed release.
Notification
Affected customers are informed, with the fixed version and, if needed, workarounds until it is installed.
We do not publish a guaranteed timeframe: each case depends on the severity and complexity of the fix. We keep you informed of progress throughout.
What is in scope
The scope covers the platform as we deliver it: interface, analysis engine, comparison, inventory connector and license mechanism, in a published version. Out of scope are problems that belong to your infrastructure (operating system, network configuration, your inventory tool itself); if you notice any during your tests, report them anyway: we will tell you whether a setting on our side can reduce the risk. Configuration or usage questions, without a confirmed flaw, go through the same form, with the appropriate subject.
Coordinated disclosure
We practice coordinated disclosure: the vulnerability is made public only once a fix is available and customers have been informed. If you want to publish your finding, we agree together on the timing and content, and we can credit your contribution if you wish.
We do not currently offer a bug bounty program.
How fixes reach you
A fix is always delivered as a new release, compiled and signed, whose signature is checked at installation, then at each start launched by the installation script. There is no hot modification and no automatic update channel: your team decides when to install, in line with your change process. Details are described on the page Signed updates and license.
Installation on your premises has an advantage here: since the platform can only be reached from your network, a flaw’s exposure surface is reduced by your own protections while waiting for the fix.