Vulnerability Disclosure Terms

This page is created using templates from disclose.io.

Introduction

Security is core to our values, and we value the input of hackers acting in good-faith to help us maintain a high standard for the security and privacy for our users. This includes encouraging responsible vulnerability research and disclosure. This policy sets out our definition of good-faith in the context of finding and reporting vulnerabilities, as well as what you can expect from us in return.

Expectations

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

Work with you to understand and validate your report, including a timely initial response to the submission;
Work to remediate discovered vulnerabilities in a timely manner; and
Recognize your contribution to improving our security if you are the first to report a unique vulnerability, and your report triggers a code or configuration change.

Scope

All of Volkis’s assets are in scope unless otherwise stated in the Out-of-Scope section below. This includes:

*.volkis.com.au
*.volk.is
Third party applications/services/platforms used by Volkis - Make sure that you get consent from the third party before attempting to hack them!

We will only acknowledge submissions that have real-world impact. To better prove this impact, a working Proof of Concept is highly recommended and may result in a better outcome. We will not accept theoretical vulnerabilities such as TLS vulns and missing security headers, unless you can show impact.

Out-of-Scope

The following lists the scope and attacks that are excluded from this policy, meaning that we do not give consent to test against these assets/methods:

*.volkis.io;
Social engineering of any kind;
Physical attacks against Volkis, its employees, or any property belonging to Volkis or its employees;
(Distributed) Denial of Service of any kind;
Actions that violate Australian law.

Although submissions with no impact will be reviewed, they are unlikely to be accepted as part of this program. Some example of submissions that won’t be accepted are:

Missing HTTP headers;
Out-of-date software/libraries unless you can prove their impact;
Theoretical SSL/TLS findings;
“Best practice” configurations that do not have impact;
“Self” exploits (such as Self-XSS) and exploits that required significant actions from users;

Rewards

We reward based on the impact of the finding, the quality of the report and how much effort went into the PoC. Keep in mind, that we are a small company but we are hoping to increase our rewards as we grow.

Rewards are based on the severity of the vulnerabilities as outlined in Bugcrowd’s Vulnerability Rating Taxonomy:

Severity	Reward
P1	$512 - $1337 (+ Swag + cookies*)
P2	$256 - $512 (+ Swag)
P3	Swag
P4	Contributors mention
P5	No reward

(*: Our Managing Director will bake you real cookies. Your choice of Choc Chip or ANZAC. No, really. This isn’t a joke.)

All accepted submissions of P4 and above will receive a mention in our Contributors list below.

The final decision for the reward amount is at our discretion.

Duplicate Submissions

We’ve participated in bug bounties so we know how frustrating dupes are! Although we can’t reward dupes, we vow to reduce their potential by fixing accepted submissions within 60 days.

Official Communication Channels

All submissions should be send to [email protected].

If you feel you need to encrypt the submission, put the report in a separate file, encrypt that file using the PGP key below and attach it to the email.

PGP Public Key

Fingerprint: B09D A8B3 6BC8 034B

Disclosure Policy

Discretionary Disclosure: The researcher or Volkis can request mutual permission to share details of the vulnerability after approval is explicitly received.

We value the work of researchers and the benefit of public disclosure. To that end, we encourage researchers to request permission from us prior to disclosing their findings. If permissions is granted, the researchers should ensure any sensitive and confidential information is removed or redacted prior to publishing.

Ground Rules

To encourage vulnerability research and to avoid any confusion between legitimate research and malicious attack, we ask that you attempt, in good faith, to:

Play by the rules. This includes following this policy any other relevant agreements;
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;
Handle the confidentiality of details of any discovered vulnerabilities according to our Disclosure Policy;
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.

Safe Harbor

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

Authorized in view of 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 in view of relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
Exempt from restrictions in our Terms and Conditions 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.

Contributors

We’d like to thank the following people for their awesome contribution to Volkis’s security, the security of our customers and the security of the Internet. You all rock!

Hacker	Criticality	Date
Shuai Yu	P4	2025-03-24
Dekow Mohamed Abdisalan	P4	2024-07-01
Prial Islam	P2	2022-10-28
Vibhor Sharma	P4	2022-09-10
Soman Verma	P3	2022-06-14
Ajay Sharma	P4	2021-12-03

Need help with your cyber security?

Get in touch with Volkis