Cybersecurity Measures for TEAC IoT Products

We, TEAC group companies, consider cybersecurity to be an essential element of the quality of our IoT products and will implement cybersecurity measures for our products based on the following guidelines:

1. We will verify the security of the product software during development and strive to sell products with minimal vulnerability impact.
2. We will establish a reception desk for reports of vulnerability information from users and respond promptly.
3. We will disclose information regarding corrected vulnerabilities.
4. We will provide new security update information free of charge.
5. We will provide security update support for two years from the end of the sale of the products.

The statements of conformity, vulnerability disclosures, vulnerability disclosure policy and others regarding vulnerabilities related to our IoT products are as follows:

Statement of Compliance

Under Development.

Vulnerability Disclosures

No security advisories are currently issued.

How to Report Vulnerability Incidents

Please provide the information below in reporting the vulnerability in English:

1. Your name
2. Your contact email address
3. Model name of the product to be reported
4. Vulnerability details
5. Your preference to share your name and contact data with TEAC affiliated companies overseas: Yes/No
6. Your preference to publish your name on Security Advisory: Yes/No

Please be advised that we may not be able to respond to your report properly if the required information above is insufficient.

Process after your report

After receiving the vulnerability information via the report form, we will reply basically within five business days for the first response. Our reply may be a little late during public or our own holidays.

Your report will be thoroughly examined by our team for product security incident response for our products. If you agree to share your whole report including your name and contact with our parent or affiliated companies overseas or you allow us to contact directly from one of those companies, please notify us of your preference on that.

With regards to products other than those manufactured by TEAC, please contact the manufacturer of the respective product.

After the reporter contacts us, we will communicate with the reporter by e-mail. If the e-mail and/or attachments contain sensitive information about undisclosed vulnerabilities, please first report to us without sending the information. We will further notify the reporter in response how we will receive the information, including how to encryption the e-mail and/or attachments to prevent unintentional disclosure.

Investigation and Countermeasures

The relevant product design and development department will investigate the vulnerability information the reporter provided, and if the following three conditions are met, it will be determined as a new vulnerability and we will immediately notify the result of the investigation to the reporter. We may request additional information as necessary.

Vulnerability criteria:

• Identifies a true product security issue.
• The vulnerability is possible to be reproduced.
• The vulnerability is undisclosed.

If a vulnerability is found, we will implement countermeasures and prepare to disclose a new vulnerability. If it is not a new vulnerability, we will close the investigation and notify the reporter of our conclusion.

Publication of Security Advisory

In order to enable our customers to take appropriate measures against new vulnerabilities in our products, we will prepare a security advisory to publish the vulnerability. We will coordinate the date of publication of the advisory with the reporter and other stakeholders as soon as the advisory is ready for publication and publish it on our website below.

Vulnerability Information

We may report the vulnerability to certain governmental offices, coordinating body or other agent such as CSIRT and ENISA as necessary, however, basically we will not disclose the details regarding the vulnerability to third parties other than the reporter, coordinating body and/or product developer.

Acknowledgements to the people who have contributed to the discovery or resolution of the vulnerability in our products will be posted in the security advisory after agreement with those contributors. If multiple individuals or organizations report the same vulnerability, acknowledgments to the first reporter will be posted in the security advisory.

Vulnerability Disclosure Policy

Introduction

This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to us (the "Organisation"). We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always acting in compliance with it.

We value those who take the time and effort to report security vulnerabilities according to this policy. However, we do not offer monetary rewards for vulnerability disclosures.

Reporting

If you believe you have found a security vulnerability, please submit your report to us using the following link/email:

[Report email]

In your report, please include the following information below:

1. Your name designation
2. Your email address
3. Model name of the product to be reported
4. Vulnerability details
5. Your preference to share your contact data with TEAC affiliated companies overseas: Yes/No

Regarding 4), vulnerability details, it would be much helpful if you could provide information such as:

• The website, IP or page where the vulnerability can be observed.
• A brief description of the type of vulnerability, for example; “XSS vulnerability”.
• Steps to reproduce. These should be a benign, non-destructive, proof of concept.

This helps to ensure that the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers.

Guidance

You must NOT:

• Break any applicable law or regulations.
• Access unnecessary, excessive or significant amounts of data.
• Modify data in the Organisation's systems or services.
• Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
• Attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests.
• Disrupt the Organisation's services or systems.
• Submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with “best practice”, for example missing security headers.
• Submit reports detailing TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS1.0 support.
• Communicate any vulnerabilities or associated details other than by means described in the published security.txt.
• Social engineer, ‘phish’ or physically attack the Organisation's staff or infrastructure.
• Demand financial compensation in order to disclose any vulnerabilities.

You must:

• Always comply with data protection rules and must not violate the privacy of the Organisation’s users, staff, contractors, services or systems. You must not, for example, share, redistribute or fail to properly secure data retrieved from the systems or services.
• Securely delete all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law).

Process after you report

After you have submitted your report, we will respond to your report within 5 working days and aim to triage your report within 10 working days. We’ll also aim to keep you informed of our progress.

Priority for remediation is assessed by looking at the impact, severity and exploit complexity. Vulnerability reports might take some time to triage or address. You are welcome to enquire on the status but should avoid doing so more than once every 14 days. This allows our teams to focus on the remediation.

We will notify you when the reported vulnerability is remediated, and you may be invited to confirm that the solution covers the vulnerability adequately.

Once your vulnerability has been resolved, we welcome requests to disclose your report. We’d like to unify guidance to affected users, so please do continue to coordinate public release with us.

Legalities

This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with the law, or which might cause the Organisation or partner organisations to be in breach of any legal obligations.