PT Container Security
Company: Positive TechnologiesBug bounty program for PT Container Security
Rewards are paid to individual entrepreneurs and self-employed persons
Program description
Bug bounty program for PT Container Security
The PT Container Security bug bounty program focuses on identifying and validating vulnerabilities that may compromise container and orchestrator environments, allow security control bypass across build/deploy/runtime stages, disrupt DevSecOps workflows, or enable unauthorized control of clusters and underlying hosts.
PT Container Security is an end-to-end security platform for hybrid cloud environments, designed to support secure development and operation of software systems that use container-based virtualization. It protects containers, images, registries, Kubernetes/Docker clusters, and orchestration components across the full lifecycle: from CI/CD pipelines through runtime enforcement. Security flaws in the platform can directly impact critical services and the overall stability of the cloud environment.
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 and API
- Authentication/authorization bypass in the central multi-cluster management console, enabling unauthorized control over clusters and security policies.
- Cross-site scripting (XSS) or cross-site request forgery (CSRF) in the admin UI for managing policies, users, and configuration, potentially enabling actions as a privileged account.
2. Image and registry scanning
- Evasion/bypass of CVE scanning for container images (including those based on Astra Linux or RedOS), potentially allowing vulnerable components to reach production deployments.
- SSRF in registry integration features (Artifactory, Nexus, GitLab Registry, Yandex Container Registry) via registry APIs, which could be used to reach internal services or infrastructure components.
3. Admission controller
- Bypassing deny rules enforced at the admission controller level to execute commands (exec) in a container.
- Cluster takeover scenarios, including escalation to cluster-admin, caused by vulnerabilities in admission webhooks, service account handling, or token validation (TokenReview API).
- Circumventing admission policies to deploy unsafe workloads (for example, privileged containers or containers with sensitive host volume mounts).
4. Runtime security
- Evasion of eBPF-based runtime monitoring used to detect suspicious behavior in containers.
- Tampering with or taking over management of the node-level protection agent (DaemonSet).
- Container escape to the host OS even with syscall monitoring and runtime policies enabled.
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.