SCROLL DOWN In compliance with Regulation (EU) 2024/2847 (Cyber Resilience Act), ZANASI S.r.l. is committed to ensuring high standards of cybersecurity across its products with digital elements throughout their entire lifecycle.
To manage potential cybersecurity vulnerability reports in a structured and timely manner, we have established a dedicated PSIRT (Product Security Incident Response Team).
- How to Report a Vulnerability
If you have identified a potential vulnerability or security issue in one of our products, please contact us at: psirt@zanasicoding.com
What happens next? Upon receiving your email, our team will send you an initial acknowledgement along with instructions (and our official reporting form) to gather the technical details needed for our analysis.
- Coordinated Vulnerability Disclosure (CVD) Policy
ZANASI adheres to a Coordinated Vulnerability Disclosure (CVD) Policy to ensure that reported vulnerabilities are properly investigated and remediated before detailed technical information is publicly disclosed.During this regulatory transition phase, our PSIRT team is committed to:
● Report Acknowledgement: Confirming receipt of the report submitted via our official form and initiating the internal logging process.
● Technical Analysis and Triage: Verifying the reproducibility of the reported vulnerability and assessing the potential risk level for our products and customers.
● Management and Remediation: Developing, evaluating, and implementing appropriate countermeasures (such as software updates, firmware patches, or temporary mitigation guidance) consistent with the time required for technical analysis and development.
● Coordinated Disclosure: Maintaining a communication channel with the reporter and coordinating any public security advisory only after a fix has been implemented, in order to protect our end users.
- Minimum Required Information
To help us analyze the issue effectively, you will be asked to provide:
● Affected Product: Product model, serial number, and active firmware/software version.
● Issue Description: Detailed explanation of the observed behavior or Proof of Concept (PoC).
● Technical Evidence: System logs, configuration files, or screenshots documenting the behavior.
● Contact Information: Details to allow our technical team to reach out for further clarification.