Report a vulnerability

If you have found a security problem in an MTechnology product, write to us. A person reads it, you get an answer, and we tell you what we intend to do about it.

This page tells you who to write to, what we need to know, how quickly we reply and which products we cover. These are commitments we put in writing, not courtesies.

security@mtechnology.it

This is the point of contact for the security of MTechnology products. If you prefer another channel, you can call +39 02 9815404 or write to the postal address at the bottom of this page: either is fine.

What we need to know

The more precise the report, the faster we can tell whether the problem is real and how many products it affects. If you do not have some of this information, write to us anyway: we will ask for the rest.

For first contact a description is enough, with no credentials, personal data or exploitation details. If you need to send us confidential material, tell us in a couple of lines and we will agree a suitable channel first: please do not email it unprompted.
Please do not send us data we do not need: working credentials, video recordings, addresses of third-party sites or personal data. To understand the problem we only need the model, the steps and the faulty behaviour.

What happens next, and when

These times run from the moment your message arrives. We have deliberately set them wide: we would rather state a deadline we can keep than a tight one and miss it.

WhenWhat you receive
Immediately For reports sent by email, an automatic acknowledgement of receipt. The case reference comes with the hand-over to a person.
Within 5 working
days
A person takes the case on, with the case reference. From then on you are talking to someone, not to a mailbox.
Within 30 calendar
days
The outcome of our assessment: whether the problem concerns us, how serious we consider it and what we intend to do. If the checks are not finished we tell you where we stand, what is missing and when we will write again.
Every 30 calendar
days
A status update, for as long as the case stays open.
On the fix The public security advisory, with the affected products and the instructions to update.

Working days means Monday to Friday, excluding Italian public holidays.

If a vulnerability turns out to be already exploited, we do not wait for the fix to speak up. In that case we immediately warn the customers who have the affected products, telling them what they can do straight away to reduce the risk, and the update follows.

Coordinated disclosure

We ask you not to disclose the vulnerability publicly for 90 calendar days from the moment your report reaches us, so that installers have time to act on systems already in service. We count from receipt rather than from when we take the case on, because that second date is one we control. The deadline is open to agreement: if you believe less time is needed, or more, we set it together.

Coordination is not a gagging order. If users are at immediate risk, warning them comes first, and no agreement with us prevents you from approaching the competent authorities.

When we publish the advisory we credit you as the reporter, but only once you have confirmed that you want to be named: without your confirmation the report stays anonymous. If a CVE identifier has already been assigned to the vulnerability, we include it.

Our commitment to authorised researchers

For research and reporting activities carried out within the conditions set out below, and only those, Gamma Commerciale undertakes not to bring civil proceedings or file a criminal complaint against you, without prejudice to obligations imposed by law. The conditions are: that your research concerns your own products, or systems you have the owner's authorisation to test, and stays within those limits; that you do not degrade anyone's service; and that you agree the disclosure timing with us.

This commitment binds us. It does not authorise access to third-party systems and it does not bind the authorities or any other rights holder: it is not, and could not be, a free pass.

If you accidentally access third-party data during your research, stop the activity that caused it, do not acquire any more, and tell us without sending the data to us: we will agree together how to handle any copies. An accidental access that you disclose does not cost you this commitment.

Which products this channel covers

In scope

  • All products branded MTechnology and EASY MT Series: IP cameras, recorders, network accessories.
  • With no age limit: including discontinued models and systems installed years ago. Those are often the ones that matter most.
  • Even if you cannot say for certain which model or firmware version is affected: tell us anyway and we will help you identify them, starting from what you do know.

Out of scope

  • The other brands we distribute: the manufacturer is a different legal entity and has its own channel. Write to us anyway and we will point you to the right one.
  • Websites and online services independent of the products: we are glad to hear about them, but outside this procedure and these timescales. A remote service without which a product loses a function does fall in.

Accepting a report and fixing a product are two different things

We will assess and answer you on any product carrying our brand, however old. Whether an update is available, however, depends on the support period of the individual model, which is no shorter than five years from its placing on the market. If an update is no longer planned for a product, we will say so plainly rather than leave you waiting, and we will tell you about any mitigations we have identified, along with their limits. The end of the support period does not mean withdrawing updates already published.

What we do with your report

We open a case and log it. We try to reproduce the problem on our own equipment. We assess its severity against the way the products are actually installed. If the vulnerability lies in a component we do not make ourselves, we report it to whoever does and coordinate the fix, remaining your point of contact throughout. When we release a security update we publish the instructions to tell whether it applies to you and how to install it. Publication of the technical details of the vulnerability may be deferred where that protects people whose systems are still exposed — but we do not conceal the existence of the risk.

Behind this channel there is a written procedure: it assigns responsibility to named people, keeps a register of cases, and is based on ISO/IEC 29147 and ISO/IEC 30111. It provides for an annual test of the channel.

Vulnerabilities already being exploited take a shorter route

If a vulnerability in one of our products turns out to be already exploited, or a severe incident occurs, as the manufacturer we are required to notify ENISA and the Italian CSIRT within a matter of hours, under Article 14 of Regulation (EU) 2024/2847. That is why we ask you to tell us immediately if you have any indication of this, even before you have the full picture.