Within the dedicated portal, you can fill out the form, specifying the type of request and its description. More information being entered will contribute to a better efficiency of the service team.

To successfully submit a ticket, you must first
log in or register for the service.

Your report should contain the following information about the vulnerability:
 

• Asset where the vulnerability can be observed (name, code, model, software version, URL, etc.) [mandatory]
• Title of vulnerability [mandatory]
• Description of vulnerability (this should include a summary, supporting files and possible mitigations or recommendations) [mandatory]
• Impact (what could an attacker do?) [mandatory]
• Steps to reproduce [mandatory]

Whenever feasible, reports should provide a benign, non-destructive proof of concept. Doing so enables faster and more accurate triage, helps prevent duplicate reports, and minimizes the potential for malicious exploitation of specific vulnerability classes, including subdomain takeovers.