Please do not perform any testing for:

• ethics.epam.com

• profile.epam.com

• carbon.epam.com

• infongen.com

• ebn.epam.com

• solutionshub.epam.com

• telescopeai.com

• wearecommunity.io

==Please note: testing on out-of-scope assets will result in mediation action or immediate ban==

==There are more targets that are out of scope. Please read the program scope carefully before starting any testing!==

==Please avoid testing contact forms at epam.com and at 3rd-level subdomains==

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 has 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. We’re remotely supporting operations for hundreds of clients worldwide in today's market conditions.

EPAM Bounty looks forward to working with the security community to find vulnerabilities to protect our businesses and customers.

Response Targets

EPAM Bounty will make its 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 Bounty | 14 days |

| Time to Resolution | depends on severity and complexity |

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

Disclosure Policy

• Please do not discuss any vulnerabilities (even resolved ones) outside the program without the organization's express consent.

• We do not consider disclosure of any report, regardless of the criticality of the issue.

Instructions for *.lab.epam.com:

Everything under lab.epam.com is a development staging environment, and please consider that fake PII data can be used there.

We will accept the following vulnerabilities as valid submissions for *.lab.epam.com:

• SQL/NoSQL injection

• RCE

• SSRF

• XXE Injections

• Path traversal

• Stored-cross site scripting (not self-XSS)

• PII leakage issues

• Security misconfigurations with demonstrated security impact

• Any other vulnerabilities that will give the possibility threat actor to read files from the server/execute commands/retrieve sensitive information

Program Rules

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

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

• Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.

• All researchers on HackerOne have an email alias in the format username@wearehackerone.com, which automatically forwards to your real email address.

If you would like to create additional test accounts, add a plus (“+”) sign and any combination of words or numbers after your username. For example, username+epam@wearehackerone.com. This enables you to test different attack vectors/account levels without targeting other users or creating multiple HackerOne profiles.

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

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

• Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.

• 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:

• ethics.epam.com

• profile.epam.com

• carbon.epam.com

• infongen.com

• ebn.epam.com

• solutionshub.epam.com

• telescopeai.com

• wearecommunity.io

There are more targets that are out of scope. Please read the program scope carefully before starting any testing!

Please do not report information disclosure at https://investors.epam.com/. EPAM is a public company, and financial information is publicly available to our customers and investors.

Rewards

Our rewards are based on severity per CVSS (the Common Vulnerability Scoring Standard). Please note these are general guidelines, and reward decisions are up to the discretion of EPAM Bounty.

| Tier 0 targets |

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

| access.epam.com |

| cloud.epam.com |

| anywhere.epam.com |

| EPAM Connect (iOS & Android) |

Please pay attention to that bounty for EPAM Connect, and access.epam.com is bigger than for other targets from Tier 0.

| Tier 1 targets |

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

| *.epam.com |

| Tier 2 targets |

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

| *.projects.epam.com |

| *.lab.epam.com |

Please pay attention that *.lab.epam.com is out of scope and not eligible for bounty.

Reward for access.epam.com:

| Critical (9.0 - 10.0) | High (7.0 - 8.9) | Medium (4.0 - 6.9) | Low (0.1 - 3.9) |

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

| $10,000 | $5,000 | $500 | $250 |

Reward for EPAM Connect (iOS & Android):

| Critical (9.0 - 10.0) | High (7.0 - 8.9) | Medium (4.0 - 6.9) | Low (0.1 - 3.9) |

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

| $10,000 | $5,000 | $500 | $250 |

Reward for Tier 0 targets:

| Critical (9.0 - 10.0) | High (7.0 - 8.9) | Medium (4.0 - 6.9) | Low (0.1 - 3.9) |

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

| $5,000 | $2,000 | $500 | $250 |

Reward for Tier 1 targets:

| Critical (9.0 - 10.0) | High (7.0 - 8.9) | Medium (4.0 - 6.9) | Low (0.1 - 3.9) |

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

| $600 | $300 | $150 | $50 |

Reward for Tier 2 targets:

| Critical (9.0 - 10.0) | High (7.0 - 8.9) | Medium (4.0 - 6.9) | Low (0.1 - 3.9) |

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

| $600 | $300 | $0 | $0 |

Subdomain takeover will be awarded a 150$ bounty.

Out-of-scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) the security impact of the bug. Reports with only theoretical assumptions won't be rewarded.

The following issues are considered out of scope:

• Clickjacking

• Host header injection

• Broken link hijacking

• Firebase API key leakage without demonstrated impact

• Session expiration after logout

• Session timeout lengths or account lockout policies

• Usage of components with known vulnerabilities without demonstrated security impact

• Bussiness logic issues without demonstrated security impact

• Unrestricted file upload without demonstrated security impact

• Leakage/disclosure of Google Maps API keys

• External service interaction without demonstrated security impact

• Password complexity and password length issues

• Post-based XSS without demonstrated security impact

• Blind SSRF without demonstrated security impact.

• Self-XSS without demonstrated security 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

• 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 security impact

• CRLF Injection without demonstrated security impact

• Reports from automated scanners

• DDoS

• Cache poisoning

• Cloudfront bypass, which leads to the origin IP disclosure

• SharePoint exposed web services without demonstrated security impact

• Robots.txt or Sitemap.xml without demonstrated security impact

• Information Disclosure FrontPage Configuration Information without demonstrated security impact

• User/email enumeration

List of Mobile bugs we don’t accept:

• Leakage/disclosure of Google Maps API keys

• Broken link hijacking

• Firebase API key leakage without demonstrated impact

• 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.

Test plan for access.epam.com

EPAM Systems is interested in the vulnerabilities in access.epam.com itself. You don't need to jump to the applications mentioned at access.epam.com.

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 Bounty and our users safe!