NCS

NCS Group is a multinational information technology company headquartered in Singapore.
Security is very important to us and this Bug Bounty program shall help us meet highest industry standards to offer the most secure service and experience to all parties.

Program Rules

Testing Policy and Responsible Disclosure

Please adhere to the following rules while performing research on this program:

• Denial of service (DoS) attacks on NCS applications, servers, networks or infrastructure are strictly forbidden.
• Avoid tests that could cause degradation or interruption of our services.
• Do not use automated scanners or tools that generate large amount of network traffic.
• Do not leak, manipulate, or destroy any user data or files in any of our applications/servers.
• Do not copy any files from our applications/servers and disclose them.
• No vulnerability disclosure, full, partial or otherwise, is allowed.

Reward Eligibility

We are happy to thank everyone who submits valid reports which help us improve the security of NCS, however only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability (see below).
• The report must contain the following elements:
  • Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and NCS, and remediation advice on fixing the vulnerability
  • Proof of exploitation: screenshots demonstrating the exploit was performed, and showing the final impact
  • Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc
• You must not break any of the testing policy rules listed above
• You must not be a former or current employee of NCS or one of its contractors.

Reward amounts are based on:

• Reward grid of the report's scope
• CVSS scoring and actual business impact of the vulnerability upon performing risk analysis

PII Bonus

Only vulnerabilities that lead to direct PII exposure without the need for user interaction will be eligible for bounty. A PII bonus will be given in addition to the BBP award.

We are running a special project where we are only looking specifically for vulnerabilities (without the need for user interaction) that lead to direct PII exposure.

Bounty Rewards

You do not have to validate how many PII records were exposed beyond the need to prove that the vulnerability exists and PII is impacted. E.g. If you found an IDOR vulnerability, you can report it to us, our team will investigate internally and let you know what is the estimated amount of PII affected if the IDOR was to be exploited at scale.

FYI, as we are based in Singapore, PII are defined as per PDPA:

• https://www.pdpc.gov.sg/
• https://sso.agc.gov.sg/Act/PDPA2012

Ineligible vulnerability reports

Vulnerabilities that require user interaction (e.g. CSRF, XSS or CORS) will not be eligible for this bonus. Below are some examples of ineligible vulnerability reports for PII bounty tier:

• Reflected or Stored XSS that leads to hackers being able to retrieve PII. Ineligible for PII bonus as it requires user interaction (clicking on malicious link or browsing to malicious page). Exceptions can be considered for Blind XSS on administrative users that have access to vast PII data.
• CSRF/CORS misconfiguration that leads to hackers being able to retrieve PII or perform account takeover. Ineligible for PII bonus as it requires user interaction (clicking on malicious link).
• Subdomain takeover that leads to hackers being able to retrieve cross-domain cookies, and thereby perform account takeover and PII. Ineligible for PII bonus as it requires user interaction (browsing to the malicious subdomain).

Geoip restriction

https://support.dialog.com.au/ is only accessible from Australia.
Please use a VPN to test this asset if you are not located in Australia.