Security

Introduction to Bigstack co. ltd Vulnerability Disclosure Policy

Bigstack 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, and what you can expect from us.

Response targets

Bigstack will make the best effort to meet the following response targets:

• Time to first response (from report submissions): 3 business days
• Time to triage (from report submission): 10 business days

We will keep you informed about our progress throughout the process.

Disclosure Policy

Let us know as soon as possible upon discovering a potential security issue, and we'll make every effort to resolve the issue quickly.

Provide us with a reasonable amount of time to resolve the issue before any disclosure to the public or a third party. We may publicly disclose the issue before resolving it, if appropriate.

If you want to encrypt your report, please use the PGP key with long ID 0xD8CE02903ABB3F1460F52CFBDBEEAD63EC389B9 (available in the public keyserver pool).

​​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

In-scope

This program covers vulnerabilities discovered in all currently supported versions (as outlined in our lifecycle policy) of our products, including Cube Cloud Operating System (CubeCOS), Cube Cloud Management Portal (CubeCMP), and the following hostnames:

• s3.bigstack.co
  

Product downloads and source code is available at CubeCOS GitHub repository.

In addition to our products, this program covers vulnerabilities affecting our applications, APIs, and infrastructure hosted on AWS, including the following host names:

• docs.bigstack.co 

Any service not expressly listed above, such as any connected services, is excluded from the scope and is not authorized for testing. Findings related to AWS’s underlying cloud infrastructure (such as hypervisors, network backbone, or AWS-managed services) should be reported directly to AWS.

Out of Scope

Exclusions, ineligible bugs, and out-of-scope:

• Presence/ absence of DKIM/SPF/ DMRAC records
• Missing HTTP headers (such as CSP, Permissions-Policy, etc)
• Clickjacking
• Missing HTTP cookie flags
• Information disclosure of non-sensitive contents (like robots.txt, sitemap.xml, files, directories, etc)
• Absence of best practices
• Self-Attacks
• CSRF with low or no impact
• Open ports
• Attacks requiring pre-conditions that would be security issues per se (e.g. usage of outdated browsers, vulnerable browser plugins, weak user passwords)
• Lookalike domains
• Broken links
• Metadata in assets (like images, PDFs, etc)
• Theoretical attacks with no realistic exploit scenario
• Weak SSL/TLS settings
• Homograph attacks
• Software that is out of date without proven security impact
• Missing multi-factor authentication

Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.

Our Commitments

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 related to this policy. 

Our Expectations

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.  
  

Official Channels 

Please report security issues via security@bigstack.co, providing all relevant information. 

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 Service (TOS) and/or Acceptable Usage Policy (AUP) 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 one of our Official Channels 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. 

Thank You 

Thank you to all who report security vulnerabilities to us.

Back to Trust Center →