EPAM’s global teams serve customers in more than 35 countries across North America, Europe, Asia, and Australia. As a recognized market leader in multiple categories among top global independent research agencies, EPAM was one of only four technology companies to appear on the Forbes 25 Fastest Growing Public Tech Companies list every year of publication since 2013 and ranked as the top IT services company on Fortune’s 100 Fastest-Growing Companies list in 2019 and 2020. We value collaboration, work in partnership with our customers, and strive for the highest standards of excellence. In today’s market conditions, we’re supporting operations for hundreds of clients around the world remotely.

EPAM looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.

Response Targets

EPAM will make a best effort to meet the following SLAs for hackers participating in our program:

| Type of Response | SLA in business days |

| ------------- | ------------- |

| First Response | 2 days |

| Time to Resolution | depends on severity and complexity |

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

• As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.

• Follow HackerOne's disclosure guidelines.

Program Rules

• Please include a header X-Hackerone: <h1_username> when you test so we can identify your requests.

• Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.

• Submit one vulnerability per the report, unless you need to chain vulnerabilities to provide impact.

• When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).

• Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.

• Social engineering (e.g., phishing, vishing, smishing) is prohibited.

• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.

Please do not perform any testing for https://ethics.epam.com/

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario/exploitability and (2) the security impact of the bug. The following issues are considered out of scope:

• Clickjacking

• Post-based XSS without demonstrated impact

• Self-XSS without demonstrated impact

• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions

• Attacks requiring MITM or physical access to a user's device.

• Previously known vulnerable libraries without a working Proof of Concept.

• Comma Separated Values (CSV) injection without demonstrating a vulnerability.

• Missing best practices in SSL/TLS configuration.

• Any activity that could lead to the disruption of our service (DoS).

• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS

• Rate limiting or brute force issues on non-authentication endpoints

• Missing best practices in Content Security Policy.

• Missing HttpOnly or Secure flags on cookies

• Missing email best practices (Invalid, incomplete, or missing SPF/DKIM/DMARC records, etc.)

• Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]

• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g., stack traces, application or server errors).

• Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case-by-case basis.

• Tabnabbing

• Open redirect - unless an additional security impact can be demonstrated

• Issues that require unlikely user interaction

• HTML Injection without demonstrated impact

• CRLF Injection without demonstrated impact

List of Mobile bugs we don’t accept:

• Decompile/reverse engineer an app

• SQL injection in content providers with no privilege boundary

• Root detection (application does not detect if it is on a rooted device)

• Issues that only occur on rooted/jailbroken devices or the emulator

• Phishing and social engineering attacks

• App requesting excessive permissions

• Hardware attacks

• Developer mode bugs

• Reports on non-eligible device versions

• Tapjacking

• Screenshot of the application contains sensitive data

• Certificate pinning

• Lack of binary protection, such as the absence of Stack Canary

• Vulnerabilities requiring extensive user interaction

• Exposure of non-sensitive data on the device

• Vulnerabilities on third-party libraries without showing the specific impact on the target application

• Use of deprecated/banned API

• Sensitive info in logs in staging/test builds

• It is not a vulnerability if an app exports an activity, receiver, content provider, or service unless it can be used to gain unauthorized access to application data or functionality.

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct, and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep EPAM and our users safe!