ING Responsible Disclosure
By ING Vulnerability disclosure program on Intigriti
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report on Intigriti
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
Rewards
What Intigriti lists as the payout for each severity.
This program does not pay cash rewards.
- Pays cash
-
Yes
A financial reward is also possible after the invitation.
- Safe harbor
-
Partial
Nevertheless, if you act in good faith and according to ING’s rules, we will not report your actions to the authorities, unless required to do so by law.
Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test.
Products and areas 1
- Any ING (sub)domain
Rules
What the policy asks of you, and the bug types it won't reward, quoted from ING Responsible Disclosure (via Intigriti)'s policy. "We" in these lines means the program, not this site.
While testing
-
Reports are required to be written in English.
-
Make sure that during your investigation you do not cause any damage or disruptions to our systems so do not alter, change or delete data from our systems.
-
Do not put a backdoor in the system, not even for the purpose of showing the vulnerability
-
do not penetrate the system any further than required for the purpose of your investigation.
-
Make sure that during your research you do not inadvertently cause a data breach (i.e. sharing screenshots or recordings on 3rd party cloud solution).
-
Do not utilise social engineering in order to gain access to our systems.
Not accepted
-
API key disclosure without proven business impact
-
Pre-Auth Account takeover/OAuth squatting
-
Self-XSS that can't be used to exploit other users
-
Verbose messages/files/directory listings without disclosing any sensitive information
-
CORS misconfiguration on non-sensitive endpoints
-
Missing cookie flags
-
Missing security headers
-
Cross-site Request Forgery with no or low impact
-
Presence of autocomplete attribute on web forms
-
Reverse tabnabbing
-
Bypassing rate-limits or the non-existence of rate-limits.
-
Best practices violations (password complexity, expiration, re-use, etc.)
-
Clickjacking on pages with no sensitive actions
-
CSV Injection
-
Sessions not being invalidated (logout, enabling 2FA, etc.)
-
Mixed content type issues
-
Cross-domain referrer leakage
-
Anything related to email spoofing, SPF, DMARC or DKIM
-
Content injection on error pages
-
Username/email enumeration
-
Email bombing
-
HTTP Request smuggling without any proven impact
-
Homography/typosquatting
-
XMLRPC enabled
-
Banner grabbing/Version disclosure
Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 17 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope removed
Any ING (sub)domain
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from www.intigriti.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Description
Responsible Disclosure indicates ING’s continued commitment to improve its security posture. As part of this process, we work closely with security researchers to identify and report vulnerabilities they find within our systems.
ING appreciates security researchers efforts in reporting vulnerabilities on its systems as long as the discovered vulnerability is in scope, detected without the use of intrusive testing techniques, and follows the disclosure guidelines below:
Rules of engagement
Reports are required to be written in English. Please include a clear attack scenario outlining detailed reproduction steps. Make sure that during your investigation you do not cause any damage or disruptions to our systems so do not alter, change or delete data from our systems. Do not put a backdoor in the system, not even for the purpose of showing the vulnerability as inserting a backdoor will cause even more damage to the safety of our systems and do not penetrate the system any further than required for the purpose of your investigation. Make sure that during your research you do not inadvertently cause a data breach (i.e. sharing screenshots or recordings on 3rd party cloud solution).
Law regulations for Responsible Disclosure may differ by country. We strongly advise you to take these regulations into account. Your investigation on our systems could be regarded as a criminal act under local or international law and you may then risk criminal prosecution. If you have detected vulnerabilities in one of ING’s systems, please be aware that local law takes precedence over ING rules. Nevertheless, if you act in good faith and according to ING’s rules, we will not report your actions to the authorities, unless required to do so by law.
In scope
Introduction
At ING, the safety of internet banking and the continuity of our online services are our top priorities. Our specialists work continuously to optimise our systems and processes. Despite the effort we put into the security of our systems, vulnerabilities can still be present.
Do you have the skills and have you discovered any vulnerabilities in our systems? Please help by reporting them to us, so that we can improve the safety and reliability of our systems together.
To encourage reporting vulnerabilities to ING, we would urge you to send any vulnerability you detect to us. Any researcher who provides a high quality report which will be important for the continuity and reliability of the bank will be invited to the private ING program in Intigriti. A financial reward is also possible after the invitation.
We are happy to announce our program! We've done our best to clean up our known issues and now would like to request your help to spot the ones we missed!
Feedback Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:
Program feedback link Please note this form will be checked periodically and must not be used for submission or support queries.
Out of scope
Domains
- Domains not owned by ING
Application
- API key disclosure without proven business impact
- Pre-Auth Account takeover/OAuth squatting
- Self-XSS that can't be used to exploit other users
- Verbose messages/files/directory listings without disclosing any sensitive information
- CORS misconfiguration on non-sensitive endpoints
- Missing cookie flags
- Missing security headers
- Cross-site Request Forgery with no or low impact
- Presence of autocomplete attribute on web forms
- Reverse tabnabbing
- Bypassing rate-limits or the non-existence of rate-limits.
- Best practices violations (password complexity, expiration, re-use, etc.)
- Clickjacking on pages with no sensitive actions
- CSV Injection
- Sessions not being invalidated (logout, enabling 2FA, etc.)
- Mixed content type issues
- Cross-domain referrer leakage
- Anything related to email spoofing, SPF, DMARC or DKIM
- Content injection on error pages
- Username/email enumeration
- Email bombing
- HTTP Request smuggling without any proven impact
- Homography/typosquatting
- XMLRPC enabled
- Banner grabbing/Version disclosure
- Open ports without an accompanying proof-of-concept demonstrating vulnerability
- Weak SSL configurations and SSL/TLS scan reports
- Not stripping metadata of images
- Disclosing API keys without proven impact
- Same-site scripting
- Blind SSRF without proven impact (DNS pingback only is not sufficient)
- Disclosed and/or misconfigured Google API key (including maps)
- Host header injection without proven impact
- Spam, social engineering and physical attacks
- DoS/DDoS attacks or brute force attacks
- Reports that state that software is out of date/vulnerable without a proof-of-concept
- Attacks requiring physical access to a victim’s computer/device, man in the middle or compromised user accounts
General
- In case that a reported vulnerability was already known to the company from their own tests or other reporting, it will be flagged as a duplicate
- Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited, may be excluded or be lowered in severity
- Vulnerabilities that are limited to non-current browsers (older than 3 versions) will not be accepted
- Do not utilise social engineering in order to gain access to our systems.
- Vulnerabilities detected by ING employees or former employees of ING are welcomed but excluded from any rewards.
Furthermore, this program is not intended for:
- Reporting complaints about ING’s services or products
- Questions and complaints about the availability of ING websites, mobile banking or internet banking
- Reporting monetary issues (e.g. ATM’s and PIN devices)
- Reporting Fraud or the presumption of fraud
- Reporting fake SMS messages, e-mails or phishing/SMSishing (report these to [email protected])
- Reporting malware
- Reporting incompliance regarding International law and regulations
Severity
This program follows Intigriti's triage standards
FAQ
Where can we get credentials for the app?
We currently don’t offer any credentials to test user roles.