Slimstock Vulnerability Disclosure Policy

Introduction

Slimstock welcomes feedback from security researchers and the general public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect, what you can expect from us.

This policy applies to any digital assets owned, operated, or maintained by Slimstock, most notably, anything on the slimstock.com or slim4cloud.com domain.

Assets or other equipment not owned by Slimstock are out of scope. Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.

What can you report?

You can report security vulnerabilities in on our services. Examples include:

  • Cross-Site Scripting (XSS) vulnerabilities.
  • SQL injection vulnerabilities.
  • Weakly configured secure connections.
  • Vulnerabilities in (mobile) applications.

What you don’t need to report

If you find any issues with the topics below, you may assume Slimstock is aware and has decided to accept the risk. We ask you not to report vulnerabilities of these types.

  • HTTP 404 codes and other non-HTTP 200 codes
  • Run-on type inserted 404 paged.
  • Version banners on public services
  • Files and folders with non-sensitive information accessible tot he public
  • Clickjacking on pages without login functionality
  • Cross-site request forgery (CSRF) on forms accessible anonymously
  • A lack of ‘secure’ or ‘HTTP Only’ flags on non-sensitive cookies
  • Use of HTTP OPTIONS method.
  • Host header injection
  • Absence of SPF, DKIM and DMARC records
  • Absence of DNSSEC
  • Absence or incorrectly applied HTTP security headers, including but not limited to:
    • Strict-Transport-Security (HSTS)
    • HTTP Public Key Pinning (HPKP)
    • Content-Security-Policy (CSP)
    • X-Content-Type-Options
    • X-Frame-Options
    • X-WebKit-CSP
    • X-XSS-Protection

How to report?

Please report security issues via mailto:[email protected], providing all relevant information. The more details you provide, the easier it will be for us to triage and fix the issue.

What you may expect from us

When working with us, according to this policy, you can expect us to:

  • Respond to your report promptly, and work with you to understand and validate your report;
  • Strive to keep you informed about the progress of a vulnerability as it is processed;
  • Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and
  • Extend Safe Harbor for your vulnerability research that is related to this policy.

What we expect from you

In participating in our vulnerability disclosure program in good faith, we ask that you:

  • Play by the rules, including following this policy and any other relevant agreements. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;
  • Report any vulnerability you’ve discovered promptly;
  • Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
  • Use only the Official Channels to discuss vulnerability information with us;
  • Provide us a reasonable amount of time (at least 90 days from the initial report) to resolve the issue before you disclose it publicly;
  • Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
  • If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information;
  • You should only interact with test accounts you own or with explicit permission from the account holder; and
  • Do not engage in extortion.Do not generate excessive amounts of (scanning) traffic to find and/or demonstrate vulnerabilities

Safe Harbor

When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be:

  • Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
  • Authorized concerning any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
  • Exempt from restrictions in our Terms of Use (TOU) that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
  • Lawful, helpful to the overall security of the Internet, and conducted in good faith.
    You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through mailto:[email protected] before going any further.
Note that the Safe Harbor applies only to legal claims under the control of the organization participating in this policy, and that the policy does not bind independent third parties.

Slimstock