Table of Content

1. Objective, Scope and Responsibilities

1.1. Objective

The purpose of this document is to outline the processes and rules guiding the communication and reward process related to vulnerability reports which external security researchers provide.

1.2. Scope

The bug bounty program is limited to vulnerabilities affecting the ZEBEDEE products, APIs/SDKs, platform, or general infrastructure. The vulnerabilities affecting third-party hosted platforms, applications, and games, are not included in the scope of this program.

1.3. Responsibilities

The CTO is responsible for the reward mechanism, with the support of the ZEBEDEE operations and engineering teams that will evaluate the vulnerability and will pay the reward.

2. Process

2.1. Collection

Security researchers must fill out the following form with as much detail as possible https://zeb.gg/vulnerability-report

2.2. Review

2.2.1. Format

A specific format of the vulnerability report is expected to enable the right processing. The language correctness and the clarity of associated evidences must be respected.

The format expects description, reproduction steps and evidences to be clearly separated to ease the processing step. Standard UTF-8 characters are expected to ease the transfer from the communication channel to the internal channels.

2.2.2. Criteria

Multiple criteria must be fullfilled for a vulnerability to be rewarded: