BT Responsible Disclosure Policy
This document contains a set of guidelines regarding the process of responsible disclosure which is defined in the ISO / IEC 29147 as a process through which vendors and vulnerability finders may work cooperatively in finding solutions that reduce the risks associated with a vulnerability. Additionally, this represents the commitment of Banca Transilvania to ensure the continuous improvement of security practices in order to safeguard our clients’ information. This policy is intended to provide security researchers guidelines regarding the assets and types of research that are considered in-scope and the vulnerability reporting process.
Given that the security researcher will comply with the following set of terms, Banca Transilvania will acknowledge that the vulnerability identification has been conducted in good faith and will not pursue any legal action.
- Any testing or research must be performed against permitted systems without affecting the functionality of our services.
- In accordance with the principle of responsible disclosure, the security researcher should establish communication with the designated point of contact and report any vulnerability that has been discovered.
- If a vulnerability has been discovered, please refer to the Reporting a vulnerability section in order to find details on how to contact us.
- Please allow our team a reasonable amount of time to respond to your report.
- Once a vulnerability has been identified, the researcher should cease any activity that could lead to a compromise or could affect the integrity of Banca Transilvania’s services and systems.
- After a vulnerability has been confirmed, we make a commitment towards fixing the issue within 60 days.
The following assets are covered by this policy:
- All services within AS34184 and AS34358.
The following vulnerabilities fall under the scope of this policy:
- Server Security Misconfiguration - Using Default Credentials, CAPTCHA Implementation Vulnerability, Unsafe File Upload, No Rate Limiting on Form, Misconfigured DNS that leads to High Impact Subdomain Takeover, etc.
- Broken Authentication and Session Management - Authentication Bypass, Account Takeover, Second Factor Authentication (2FA) Bypass, etc.
- Sensitive Data Exposure - Disclosure of Secrets For Publicly Accessible Assets like hardcoded passwords, sensitive data over unecrypted connection, etc.
- Server-Side Injection - LFI, RFI, RCE, SQLi, XXE, etc.
- Cross-Site Scripting - Stored, Reflected, DOM.
- Denial of Service.
Out-of-Scope Testing Methods and Vulnerabilities
The following testing methods (i.e. types of research) and vulnerabilities do not fall under the scope of this policy:
- Physical testing against Banca Transilvania's Facilities / Property.
- Phishing (either of an employee or a client/user of Banca Transilvania’s services).
- Lack of security headers (Strict-Transport-Security, X-Frame-Options, X-Webkit-CSP etc.).
- Flaws affecting the users of out-of-date browsers and plugins.
- Self XSS.
- Banner grabbing.
- HTTP trace/options methods enabled.
- CSRF with minimal impact (login, logout etc.).
- Open redirects (POST or header based).
- Disposable email addresses allowed during registration.
- Lack of obfuscation.
- Header injection without a demonstrable impact.
- Lack of Secure and HTTPOnly cookie flags (critical systems may still be in scope).
- Static content served over HTTP.
- Weak password policies.
Reporting a Vulnerability
If you have discovered a vulnerability or you have any questions, please contact us at the following email address: firstname.lastname@example.org.
In order to ensure confidentiality and integrity, please use PGP key 0x6F077A29C359A429 for encrypting the communication. You can find our security.txt file at the following address:
Could include but not limited to: customer-related information, financial or personally identifiable information, information related to the vulnerable assets.
The security researcher agrees that they will not disclose any of the above to a third party without Banca Transilvania’s agreement. Therefore, any potential vulnerability reports should be treated as confidential information.