IMPORTANT

You are allowed to test the authenticated part of the platform but no tests accounts are provided. You are free to create an account or use your existing personal account if you already have one. Note however that no refund will be done through this program. Be extra careful on your actions with your account, as we can’t promise to fix issues you might cause yourself.

For information, we are running in parallel a temporary bug Bounty program on a staging environment with test accounts. If you want to go further with your tests, please send us an email at BforBank_TECH.OPS.SECURITY@bforbank.com and we will invite you when it's open.

About

Welcome to BforBank bug bounty program! This page aims at defining the objectives and the scope of this program.

Thank you for your consideration of our program. If you have any questions contact us at BforBank_TECH.OPS.SECURITY@bforbank.com

BforBank

BforBank is a Crédit Agricole Group company, created in 2009, that provides online banking services to its customers.

BforBank has built online banking services that are currently up and running. Recently, BforBank launched a Move-To-Cloud initiative to have our banking services in the Cloud (GCP). Therefore, we want to ensure that our new banking services running in the Cloud are well secured.
This Bug Bounty Program shall help us meet highest security standards to offer the most secure service and experience to all our customers.

BforBank App

Our new mobile app allows the following operations :

• Customer acquisition (Login, identity verification, screening, etc.)
• Bank account management (view balance, transactions...)
• Credit card management (request, upgrade, replacement, PIN visualization / recovery, etc.)
• Management of IBANs / beneficiaries (add/delete)
• Payments (classic SEPA transfers, instant payment, etc.)
• Direct debit (mandate management, debit execution, etc.)
• Account-to-account transactions
• Live Chat
• Apple Pay payments
• Consumer credit
• Mobile insurance
• Savings

Program Rules

Participants are permitted to perform any tests and investigations on the systems, as long as they act in good faith and respect the scope and rules described below.

Testing Policy and Responsible Disclosure

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

• Denial of service (DoS) attacks on BforBank 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.
• The vulnerability must be reported exclusively through our designated reporting platform, yeswehack.com.
• No phishing on users and employees

Failure to comply with the preceding rules will result in the rejection of your report.

Reward Eligibility

We are happy to thank everyone who submits valid reports which help us improve the security of BforBank, 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 BforBank, 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 BforBank (including internship) 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

Reports of leaks and exposed credentials

In the context of this program, we do not intend to encourage, accept or reward reports of leaks or exposed credentials.
We will only consider vulnerabilities or leaks that are identified directly on the scope of this program.

Also, in order not to encourage dark and grey economies, in particular the purchase, resale and trade of identifiers or stolen information, as well as all types of dangerous behavior (e.g. social engineering, ...), we will not accept or reward any report based on information whose source is not the result of failure on the part of our organization or one of our employees/service providers.

This excludes, but is not limited to:

• Stolen credentials gathered from unidentified sources (e.g. …)
• Exposed credentials on an out-of-scope assets
• Exposed GitHub/GitLab (or similar) instance
• Exposed secrets (e.g. API tokens/keys or other technical credentials)
• Exposed PII on an out-of-scope asset

To summarize our policy, you may refer to this table :