Product cybersecurity

Safety integrated into the machine’s life cycle

Vulnerability management is part of our process for designing, developing, maintaining and updating products that incorporate digital elements.

  • CRA

    A process in line with Regulation (EU) 2024/2847.

  • PSIRT

    Coordination team for reception, analysis and remediation.

  • CVD

    Coordinated disclosure to protect the client prior to publication.

Our commitment

A responsible relationship with those who help us improve safety

We want any researcher, client or partner to be able to report a finding clearly, securely and with a predictable response process.

  • Integrity and respect

    Integrity and respect

    We treat your work with seriousness and respect. Every report receives the attention it deserves, with no automated replies or unjustified rejections.

  • Ethics and safety

    Ethics and safety

    We believe in responsible research. Our policy safeguards good faith and precludes legal action against researchers who act within the authorised scope and comply with this policy.

  • Confidentiality assured

    Confidentiality assured

    Every report is treated with the utmost confidentiality. The investigator’s details and technical information are kept secure throughout the analysis and coordination process.

  • Open communication

    Open communication

    We value your time and your opinion. We maintain clear communication throughout the validation, remediation and disclosure processes, whilst respecting your preferences regarding public acknowledgement.

How it works

A five-step report

  • Contact

    Please provide your contact details and, where applicable, the organisation you belong to, so that we can coordinate the analysis and response.

  • Component

    Please identify the machine, product or system affected, its manufacturer and the specific version of the software or firmware.

  • Vulnerability

    Give the finding a title, select the relevant CWE category and provide any CVE/CWE references if they already exist.

  • Details and evidence

    Describe the vulnerability, the steps required to reproduce it, its impact, and provide a proof-of-concept (PoC), commands, code, logs or supporting files.

  • Review and confirmation

    Check all the information, accept the Vulnerability Disclosure Policy and confirm secure submission to the PSIRT.

Responsible disclosure

Before submitting the report

Avoid tests that could compromise people, production, third-party data or the availability of a machine.

Basic rules for research

  • Do not carry out denial-of-service attacks or destructive testing.
  • Do not modify or extract any data beyond what is strictly necessary to demonstrate the finding.
  • Do not attempt to pivot to other systems or networks.
  • If the test could affect axis movement, safety PLCs, emergency stops or other critical functions, stop it immediately.
  • Do not publish technical details until you have coordinated the disclosure with the PSIRT.

For particularly sensitive information, encrypted transmission using a public PGP key can be enabled.

Report a vulnerability

PSIRT Channel

Please complete each step. Required fields are checked before you can proceed.

  • Contact
  • Component
  • Vulnerability
  • Details and evidence
  • Confirmation

1 Contact

2 Component

3 Vulnerability

4 Details and evidence

5 Confirmation

Краткое описание отчета

Контактная информация A
фамилия B
электронная почта C
телефонный -
страна
Удостоверение личности / Паспорт
Организация
Номер связанного оборудования
Продукт или система
Марка компонента
Версия
Название
Категория
Ссылка CVE/CWE
Описание
Шаги для воспроизведения
Воздействие
PoC

Monitoring

What happens next?

  • Submission received

    Secure recording of the case and confirmation to the investigator.

  • Validation

    Reproduction, technical classification and impact assessment.

  • Remediation

    Correction, mitigation, testing and preparation for the update.

  • Disclosure

    Co-ordinated communication with clients and the investigator where appropriate.

FAQs

About CRA and vulnerabilities

CNC, Panel PCs, IPCs, software or digital services, cameras and other digital components supplied or integrated into Nicolás Correa machines.

The channel can be adapted to accept reports containing minimal data. For this proposal, a contact email address is required to facilitate the validation and coordination of the finding.

The obligations to report actively exploited vulnerabilities and serious incidents come into force on 11 September 2026.

No. This channel is exclusively for cybersecurity vulnerabilities in digital products and services.