MaxPatrol 360
Company: Positive TechnologiesBug bounty program for MaxPatrol 360
Rewards are paid to individual entrepreneurs and self-employed persons
Program description
Bug bounty program for MaxPatrol 360
MaxPatrol 360 is a modern incident management and cybersecurity operations platform for organizations of any size, from enterprise SOCs to MSSPs.
It supports the complete incident response lifecycle, from organizing data collection and processing to investigation, response, and analytics, helping ensure strong cyber resilience and clear, transparent processes.
It supports the complete incident response lifecycle, from organizing data collection and processing to investigation, response, and analytics, helping ensure strong cyber resilience and clear, transparent processes.
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. Centralized management console & API
- Authentication bypass or authorization bypass in the centralized management console that leads to gaining platform administrator privileges or access to another tenant's data.
- Cross-site scripting (XSS) in any UI input field that could be used to hijack a system administrator's session.
- Insecure deserialization in an API used for data exchange between platform components, enabling remote code execution (RCE).
2. Inter-module communication and data
- Issues that impact the integrity or confidentiality of data exchanged between platform modules (for example, transmission over unencrypted channels, lack of signature verification, or message tampering/forgery).
3. Automated response
- Unauthorized execution of response playbooks that may disrupt business processes (for example, disabling network nodes, blocking users, or modifying security policies without authorization).
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.