MaxPatrol SIEM
Company: Positive TechnologiesBug bounty program for MaxPatrol SIEM
Rewards are paid to individual entrepreneurs and self-employed persons
Program description
Bug bounty program for MaxPatrol SIEM
The MaxPatrol SIEM bug bounty program focuses on identifying and validating vulnerabilities that could impact the collection, storage, or analysis of security event data, or that could allow MaxPatrol SIEM to be abused as an initial access point for attacks against a customer environment.
MaxPatrol SIEM is designed to collect, store, and analyze event data from an organization's IT infrastructure. This supports security monitoring across the whole infrastructure and also at the level of specific departments, hosts, and applications.
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
- Cross-site scripting (XSS) that could be used to hijack an administrator session or execute actions with administrator privileges.
- Cross-site request forgery (CSRF) that could allow unauthorized changes to system configuration.
- Insecure direct object reference (IDOR) that could allow a user to access or delete another tenant's data or assets.
- SQL injection in API parameters or UI inputs used for asset management or data collection task management.
2. Authentication and authorization
- Authentication/authorization bypass at any point in the authentication flow (for example, during password reset) that results in unauthorized access to system features.
- Access control flaws that allow a low-privileged user to escalate privileges to a system administrator.
- Security issues in the single sign-on (SSO) implementation.
3. Data processing and correlation
- Server-side request forgery (SSRF) in event enrichment features (for example, when querying external services to validate IP addresses), which could be used to target internal systems.
- Insecure deserialization in event processing and correlation logic that may result in arbitrary code execution.
- Path traversal issues in the handling of log or configuration files collected from monitored assets.
4. Integrations and third-party services
- Insecure storage of sensitive data, including credentials used to integrate with external systems.
- Remote code execution (RCE) through file parsing/analysis in integrated components (for example, during file inspection in a sandbox).
5. Architecture and deployment
- Docker container weaknesses that allow container escape and host compromise.
- Arbitrary file read on the SIEM system due to vulnerabilities in underlying components (for example, LogSpace or Elasticsearch).
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.