top of page
iMQ logo-new.jpg
藍色抽象背景

Product Security Support

Software and Hardware Security Incident Response Procedure

This portal is dedicated to promptly addressing security vulnerabilities in iMQ products. iMQ responds to reported issues, documents findings, and provides customers with clear, actionable guidance regarding the impact, severity, and appropriate mitigation measures.
 

​

Scope of Security Issues

iMQ is responsible for investigating and managing a range of security-related issues. The following cases fall within its scope:

  • Product Security Vulnerabilities: Security flaws affecting iMQ hardware or software components.

  • Documentation Deficiencies: Flaws, ambiguities, or inaccuracies in security-related iMQ documentation (e.g.,datasheets, application notes).

  • Information Exposure: Unauthorized access to, or unintended public exposure of, sensitive iMQ technical documents and security information.

 

​

Vulnerability Management Process

Security vulnerabilities are addressed through a structured, multi-stage process designed to ensure timely and effective resolution. Timelines may vary depending on issue complexity and severity:

  1. Acknowledgment & Intake:  Upon receiving a report, iMQ acknowledges receipt and keeps the reporter updated throughout the investigation.

  2. Evaluation & Verification:  iMQ verifies the vulnerability, assesses associated risks, determines potential impact, and assigns handling priority.

  3. Remediation:  Where applicable, iMQ develops mitigation strategies, firmware updates, or hardware workarounds to resolve confirmed vulnerabilities.

  4. Communication:  iMQ coordinates directly with affected customers, providing relevant details about the issue and verified mitigation steps.


Reporting a Potential Security Vulnerability
If you believe you have identified a potential security vulnerability in an iMQ product, please contact Technical Support at supports@imqtech.com directly. 

 

iMQ strives to acknowledge all reported vulnerabilities within 24 hours of receipt. Please note that response times may extend to 72 hours during weekends or holidays, depending on the urgency of the issue. If you do not receive a response within this timeframe, we recommend resending your message.
 

To help us assess and respond to your report effectively, please provide the following information (in English):

 

  • Affected product model(s) and hardware/firmware version(s)

  • A comprehensive description of the suspected vulnerability

  • Proof-of-concept (PoC), exploit details, or step-by-step reproduction instructions

 

Security Notice: Due to the sensitive nature of vulnerability reports, iMQ strongly recommends encrypting all submissions using our official PGP key >> Download iMQ PGP Key

Responsible & Coordinated Disclosure
iMQ collaborates with security researchers and reporters to practice coordinated disclosure—protecting customer security while upholding transparency.

​

Because iMQ products are embedded chips often deployed in resource-constrained environments where in-field updates are difficult or impossible, public disclosure terms may require:

​

  • Extended coordination timelines to allow customers sufficient time to implement hardware or system-level mitigations

  • Redacted or limited technical details in initial disclosures to prevent exploitation

  • Partial or anonymized notices to avoid premature exposure of vulnerable end devices

​

​

​

​

Last Updated: November 2026

bottom of page