2+1 years

1 Introduction

Mirka is committed to ensuring the security of its client and the public by protecting their information. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.

This policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.
We encourage you to contact us to report potential vulnerabilities in our systems.

2 Authorization

If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized. We will work with you to understand and resolve the issue quickly, and Mirka will not recommend or pursue legal action related to your research if it is deemed to be in accordance with this policy. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.

3 Guidelines

Under this policy, “research” means activities in which you:

• Notify us as soon as possible after you discover a real or potential security issue.
• Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
• Only use exploits to the extent necessary to confirm a vulnerability. Do not use an exploit to compromise or exfiltrate data, establish persistent access, or use the exploit to pivot to other systems.
• Conduct testing during normal Finnish office hours only.

Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, or proprietary information or trade secrets), you must stop your test, notify us immediately, and not disclose this data to anyone else.

4 Test Methods

The following test methods are not authorized:

• Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data.
• Physical testing (e.g., office access, open doors, tailgating).
• Social engineering (e.g., phishing, vishing), or any other non-technical vulnerability testing.
• Brute forcing attacks and other attacks against login interfaces.
• Automated vulnerability scans that are likely to overload the Mirka system with a high volume of requests.

5 Scope

This policy applies to the following systems and services: *.mirka.com
Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in systems from our vendors fall outside of this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any).

Don't send reports indicating that our services do not fully align with “best practice” e.g. missing security headers (CSP, x-frame-options, x-prevent-xss etc) or suboptimal email related configuration (SPF, DMARC etc).

6 Reporting a Vulnerability

Reports cannot be submitted anonymously and must include author’s details.

What we would like to see from you in the reports:

• Describe the location the vulnerability was discovered and the potential impact of exploitation.
• Offer a detailed description of the steps needed to reproduce the vulnerability i.e., proof of concept,
  scripts, and screenshots.
• Do not submit a high volume of low-quality reports.
• The language used in the report is to be English. Contact us by email, security@mirka.com with “vulnerability disclosure” as the subject and use our PGP key for encryption.

What you can expect from us:

• Within 3 business days, we will acknowledge that your report has been received.
• In pursuit of good faith, you are to give Mirka a 90-day ultimatum to address the vulnerability before you disclose to any third party.
• In submission of a legitimate vulnerability, Mirka will post the name of the author on Mirka’s Hall of fame for vulnerability disclosure.

Document Change History

Version	Date	Description
1.3	14.8.2023	Updated scope
1.4	18.8.2023	Updated template