PT Dephaze
Company: Positive TechnologiesBug bounty program for PT Dephaze
Rewards are paid to individual entrepreneurs and self-employed persons
Program description
Bug bounty program for PT Dephaze
This bug bounty program focuses on finding and validating vulnerabilities in PT Dephaze, an automated continuous security testing solution.
PT Dephaze is an automated pentesting tool that models attacker progression through an organization's infrastructure.
Regular penetration testing is an objective way to assess an infrastructure's security posture. Because traditional pentests happen periodically, security gaps can build up between engagements. PT Dephaze enables ongoing, controlled security assessment so that weaknesses can be fixed before they're abused by attackers.
Regular penetration testing is an objective way to assess an infrastructure's security posture. Because traditional pentests happen periodically, security gaps can build up between engagements. PT Dephaze enables ongoing, controlled security assessment so that weaknesses can be fixed before they're abused by attackers.
Limitations
When the program launches, access to the product's test environments will be limited.
Broader access will be provided later, once the supporting infrastructure and operational procedures are finalized.
Broader access will be provided later, once the supporting infrastructure and operational procedures are finalized.
General information
Types of vulnerabilities eligible for review. We accept vulnerability reports in the following categories (including, but not limited to):
1. Web interface and management API
- Authentication/authorization bypass affecting the management console for simulations and agents.
- Cross-site scripting (XSS) in sections for creating attack scenarios or viewing reports, allowing an attacker to hijack an administrator's session.
- Insecure deserialization in an API used to schedule tasks or receive results from agents, which may lead to remote code execution (RCE).
- Server-side request forgery (SSRF) in features that check simulation targets, allowing attacks against internal systems.
2. Attack simulation engine
- Bypassing the "safe mode" for scenario execution, which may cause disruption of target systems, such as triggering a denial of service on a critical server.
- Manipulation or corruption of simulation outputs (reports) due to weaknesses in how the system collects and aggregates simulation data.
- Unauthorized execution of arbitrary code or commands on a target system outside the set of scenarios explicitly allowed by the approved scenario library.
3. BAS agents
- Removing, disabling, or bypassing BAS agent self-protection on a target host without having the necessary privileges.
- Compromising the agent in order to gain control over the system the agent is running on.
- Forging or modifying an agent's telemetry data reported to the central server in order to conceal actual activity or disguise an attack.
4. Attack and scenario library
- Updating the attack library from an untrusted external source (for example, by exploiting a vulnerability in the update mechanism).
- Injecting a malicious scenario into the shared library to be later executed by other users of the system.
Note. Findings that do not present a practical security risk (for example, purely theoretical issues or reports without exploit validation) may be rejected or treated as informational and are not eligible for a bounty payout.
Rewards
Payout amounts are listed in the table below:
| Severity | Payout amount |
|---|---|
| Critical | RUB 300,000–500,000 |
| High | RUB 150,000–300,000 |
| Medium | RUB 50,000–150,000 |
| Low | RUB 0–50,000 |
Rewards are paid only for attack scenarios that can be reproduced on an officially supported product version that is fully patched with all available updates. Reports for end-of-support versions are accepted as well, but a payout for such issues is not guaranteed.
Vulnerability severity is assessed during triage and validation based on the issue's impact on the product security.
The product security team makes the final severity determination.
The product security team makes the final severity determination.
Participation requirements
Participants must be at least 18 years old.
Researchers aged 14–18 are allowed to participate only if they can present the written consent of a parent or a legal guardian.
Current Positive Technologies employees, as well as former employees whose employment ended less than three years ago, may take part in the program but are not eligible to receive a bounty payout.
Researchers aged 14–18 are allowed to participate only if they can present the written consent of a parent or a legal guardian.
Current Positive Technologies employees, as well as former employees whose employment ended less than three years ago, may take part in the program but are not eligible to receive a bounty payout.
Participant obligations:
- Follow the vulnerability disclosure rules of the Positive Technologies program and the Standoff 365 Bug Bounty platform.
- Follow the rules related to the handling of sensitive information. Do not gain access to data belonging to another user without the user's permission, change or destroy the data, or disclose any sensitive data obtained inadvertently during the vulnerability testing process or exploit demonstration. Deliberate access to sensitive data is prohibited and can be deemed illegal.
- Maintain communication with the security team, send them reports on discovered vulnerabilities according to the program requirements, and provide feedback if they have questions about the report.
- Do not publicly disclose any details of the vulnerabilities discovered. Positive Technologies retains the right to decide if and when information about the reported vulnerability will be published.
- Public disclosure of a vulnerability is allowed only after a fix is released and a publicly registered CVE/BDU identifier has been assigned.
- If a researcher requests disclosure of the report, Positive Technologies will initiate the coordination process to register a vulnerability identifier.
Rewards for reported vulnerabilities
No reward will be given for:
- Reports generated by security scanners and other automated tools.
- Disclosure of non-sensitive information (such as software name and version or technical characteristics and metrics of the system).
- Information about IP addresses, DNS records, and open ports.
- Reports of issues and vulnerabilities based on the product version without demonstrating exploitation.
- Reports of vulnerabilities whose exploitation is prevented by security tools, if the researcher does not demonstrate how to bypass the security tools.
- Reports of insecure SSL/TLS ciphers without demonstrating exploitation.
- Reports indicating the lack of SSL or other best current practices (BCPs).
- Reports of vulnerabilities already reported by other participants (duplicate reports).
- 0-day or 1-day vulnerabilities identified by our security team based on information from open sources.
- Reports of brute-force vulnerabilities without providing an attack method that is significantly more efficient than a straight-forward brute-force approach.