When a bank is under DDoS, its customers ask one question within minutes: is my money still there?
The attack cannot touch the money. It can stop people seeing it, stop them freezing a stolen card, and keep the bank's own staff from watching a fraudulent transfer leave while everyone is looking at the flood.
That makes a bank's DDoS test different from a load test on a busy website. The pages are the easy part. The hard parts sit behind them and beside them.
DDoS testing for banks, defined
DDoS testing for banks checks two things at once, with permission and under a flood: that customers can still reach and control their accounts, and that the bank can still see what is happening to them. In practice that means online and mobile banking login, the core banking calls behind every logged-in page, the authentication channel that also confirms payments, the contact centre that takes the overflow, and the fraud operation that keeps working while the incident runs.
The rails themselves, and the clocks that card schemes and payment schemes hold over a bank, have their own post on DDoS testing for financial services. Approvals, ramps and abort criteria are no different for a bank than for anyone else, so use the complete guide to DDoS testing for those. This page stays on the retail side: the customer, the core and the fraud desk.
| Path | What the flood actually threatens | What the test measures |
|---|---|---|
| Logged-in pages | The core banking connection pool | Core call latency and pool occupancy |
| Login and step-up | The one-time-code channel shared with payment approval | Codes delivered per second, end to end |
| Contact centre | The same back end, reached by phone | Queue length, time to block a card |
| Fraud operations | Attention, alert queues and held payments | Alert latency on planted test transactions |
| Hosted online banking | A platform shared with other banks | The provider's evidence, your own fallbacks |
The campaign that taught banks what attackers aim at
From September 2012 into 2013, a campaign that called itself Operation Ababil ran sustained floods against the online banking sites of dozens of US banks. In March 2016 the US Department of Justice charged seven people over attacks on 46 financial institutions across 176 days (reported by Reuters, March 2016).
Three details from that campaign still shape how banks should test.
The targets were the customer-facing sites
The floods went for online banking, not for card switches or payment systems. Customers could not log in or see balances, and that was the outcome the campaign wanted: visible, embarrassing, and repeated.
The botnet ran on servers, not home routers
The traffic came from a botnet of compromised web servers, known as Brobot, sitting in hosting data centres. Each source had far more bandwidth than a home device and could send a heavy stream of HTTP requests on its own.
A per-IP rate limit tuned for millions of small sources behaves very differently against a few thousand large ones. A botnet built on hosting servers is worth modelling separately from an IoT one.
The targets were announced in advance
The group posted the next week's targets publicly. Banks knew roughly when their turn would come.
That turns readiness into something testable on a calendar. Can the bank raise its posture for a named day: pre-provision scrubbing, lower thresholds, staff the right desks, warn the contact centre? A ransom DDoS note with a deadline poses the same question.
Online banking is a thin layer over an old core
The web and app front ends are modern, scaled out and usually behind a CDN. The thing they talk to is often not.
The channel answers, the core decides
Between the front end and the ledger sits channel middleware: an API gateway or integration layer that turns a page view into calls on the core banking system. That layer holds a fixed pool of connections to the core, and the core itself has an online transaction capacity sized for branches plus normal digital traffic.
Scaling the web tier does nothing for either. A flood that gets past the edge with valid-looking requests is a flood on the core, filtered through a pool that was never sized for it.
Every logged-in page is a core call
The landing page after login shows balances and recent transactions. Those cannot be cached for long, because a customer who has just been paid expects to see it.
So an attacker who can get through login, or who floods the endpoints a logged-in session calls, is buying core capacity with every request. The cost per request is not visible at the edge; API floods show the same asymmetry, and in a bank the expensive endpoint is usually the one that reads the ledger.
The batch window shrinks the path
Many core systems still run an end-of-day batch. While it runs, online channels are served from a reduced path: a snapshot balance, memo posting of new transactions, fewer online connections, slower responses.
A flood that lands in that window meets a smaller pipe. If it slows the batch itself, the damage spreads past the online channel into the next morning's postings and into the settlement cut-offs that the financial services post covers.
The arithmetic of a slower core
Connections held open equal calls per second multiplied by seconds per call; that is Little's law. Take an illustrative 250 core calls a second at 20 milliseconds each: 5 connections in use, against a middleware pool of 80.
Now let core latency climb to 800 milliseconds, through batch, through a flood, or both. The same 250 calls a second want 200 connections. The pool pins at 80, new calls queue, and the queue is what customers see as a login that spins and a balance that never loads. No server fell over.
Find the rate at which the pool pins
Measure core call latency and middleware pool occupancy, not page load time at the edge. Run the profile twice: once in daytime conditions and once in the batch-window conditions, the second in a production-like environment if the live core cannot take it.
Record the request rate at which the pool pins. That number, not the CDN's capacity, is the online bank's real ceiling.
The code that logs you in also approves your payments
Login floods at banks rarely stop at the password form, and the reason is specific to banking.
Credential floods walk the whole path
Attackers hold large lists of leaked username and password pairs. Sending those at volume makes the flood indistinguishable from customers who mistyped, and a fraction of the pairs work, so the requests pass the password check and reach step-up authentication.
The account lockout side of this, where your own policy locks real customers out, is covered in the post on VPN gateway DDoS testing. In a bank, a locked-out customer phones, which feeds the next section.
Step-up shares a channel with payment approval
Under PSD2's strong customer authentication rules, a payment code must be dynamically linked to the amount and the payee (Article 5 of Delegated Regulation (EU) 2018/389). Many banks deliver both login codes and payment approval codes through the same channel: an SMS aggregator, a push service, or an authenticator back end.
That channel has a throughput limit. Messages per second per sender, push requests per second per app, signatures per second on the back end.
A login flood that exhausts it does not only stop logins. It stops customers who are already logged in from approving a transfer, because their approval code is queued behind the attacker's login codes.
The channel is also a bill
Every SMS sent is charged, and attackers who trigger codes to premium numbers turn the flood into revenue for themselves. That metering side belongs to EDoS testing; for this test the point is capacity.
Prove whether the channels are shared
Use test accounts with test phone numbers or a provider sandbox, never real customers. Flood the login path with test credentials that pass the password check, and measure two numbers together: login codes delivered per second, and the time for a payment approval code to arrive on a separate test account. If the second rises with the first, the channels are shared, whatever the architecture diagram says.
When the app fails, customers phone
A bank's contact centre is its overflow channel, and it is rarely tested as part of a DDoS exercise.
The phone line reaches the same back end
The IVR's self-service options (balance, recent transactions, card block) call the same middleware the app calls. The agent desktop does too. So a flood that pins the core pool also slows the menu, and slows every agent looking up a caller's account.
Call volume rises at the moment each call takes longer to handle. Queue length grows on both counts.
Freezing a card is a safety control
The in-app card freeze goes down with the app. The lost and stolen card line is then the only way a customer can stop a card, and that is a control the bank should treat like any other security control: it must work during the incident, not after it.
Check where the card block actually executes. If it runs through the same channel middleware, the hotline inherits the flood.
Put the phones in the test window
During a test window, with the contact centre briefed, have a small team place scripted calls on test accounts. Measure time to answer, IVR completion rate, agent lookup time and the time from call start to a confirmed card block. Repeat with the middleware pool pinned. Those figures belong in the report beside the request rates.
A flood can be cover for fraud
The flood is often not the point. It is noise.
Regulators have said so plainly
US banking regulators' joint FFIEC statement on DDoS attacks (April 2014) warned that some attacks had been used to divert attention while fraud was carried out, and asked institutions to keep that possibility inside their incident response. It is the reason a bank's DDoS plan cannot be owned by the network team alone.
What the incident takes away
A large flood draws the most experienced people into a bridge call. It fills the security monitoring pipeline with flood logs, so fraud and account-takeover alerts wait behind them. Payment holds pile up as risk checks slow, and someone senior asks whether the hold limits can be relaxed to clear the backlog.
Every one of those is the window a fraud crew wants. Account takeover attempts and high-value transfers go out while the fraud analysts are short-staffed and their alerts are late.
What the test proves
Make the fraud operation part of the test, not a bystander. While the flood runs, push a small set of planted transactions through test accounts that should trip the fraud rules: a new payee and a large transfer, a login from an unusual device followed by a change of phone number.
Then measure what happens to them. How long until the alert fires, how long until an analyst sees it, and whether the payment is held. Check also that nobody changed a velocity limit or released held payments to clear a queue during the run. A DDoS war game is the place to rehearse that pressure without traffic first.
Keep fraud monitoring off the flood's path
Where the fraud engine shares log ingest, message queues or network paths with the internet edge, give it its own. An engine that answered every request but raised its alert twenty minutes late has failed this test.
Many banks share one online banking platform
Smaller banks and credit unions often do not run their own online banking. A hosted digital banking provider runs it for them, and for many other institutions on the same infrastructure.
Your login page is a tenant
The bank's online banking hostname points at the provider. An attack aimed at any bank on that platform lands on the shared front door, and every bank on it can feel it.
How far that reaches depends on how the provider isolates tenants, and the mechanics (silo or pooled, per-tenant limits, cells) are set out in DDoS testing for SaaS platforms. From the bank's side the question is narrower: what happens to my customers when the target is someone else?
The right to test belongs to the provider
You cannot load a shared platform without the provider's written permission, and even with it you would be loading other banks' customers. So for a hosted bank the test evidence comes partly from the provider.
Ask for it in writing: how a targeted tenant is isolated, whether its hostname can be moved or rate-limited without affecting the rest, the provider's recovery objective for the platform, and when it last tested any of that.
What a hosted bank can still test itself
Plenty. Your own DNS and any edge you put in front of the hostname. Your contact centre, card block line and status page. Your own core, if you run it. And the scenario where the platform is down for everyone: who decides what customers are told, and through which channel. That scenario needs no traffic at all; a tabletop session with the provider's contact in the room covers it.
Telling customers, from somewhere the flood cannot reach
A bank's status message is part of the security response, because silence reads as "something is wrong with my money".
Host the status page on separate infrastructure and a separate provider from online banking. Prepare wording that separates "you cannot log in" from anything about funds, and agree who can publish it in minutes rather than hours. Phishing crews read outages too, and a clear official channel is what customers check before they trust a text claiming to be from the bank.
What supervisors expect
In the US, the 2014 FFIEC statement asked institutions to assess DDoS risk, plan with their internet service and hosting providers, and make sure incident response covers a sustained attack. British supervisors frame the question as impact tolerances for important business services, which the post on UK DDoS testing works through. EU banks fall under DORA (DORA DDoS testing), and threat-led work for UK firms runs through CBEST.
This is orientation, not legal advice. What examiners tend to ask for, under any of these, is evidence per customer path: the planted fraud transfer that was held, the card block that went through, the pool that pinned at a known rate and was resized.
A bank DDoS test plan, path by path
| Path | Before the test | During the test | Pass looks like |
|---|---|---|---|
| Core behind the channels | Find the middleware pool size and the batch window | Measure core latency and pool occupancy, day and batch profiles | Pool does not pin below the agreed attack rate |
| Login and codes | Set up test accounts, test numbers or a provider sandbox | Login codes per second against approval code delivery time | Approval codes arrive inside their timeout |
| Contact centre | Brief the floor, script test calls | Time to answer, IVR completion, time to block a card | Card block confirmed within the target |
| Fraud operations | Write planted transactions on test accounts | Alert latency, analyst pickup, payment held or not | Alerts on time, no limits relaxed |
| Hosted platform | Get the provider's written evidence and permission | Test only what is yours: DNS, edge, phones, status page | Fallbacks work with the platform degraded |
| Communication | Status page off the main stack, wording agreed | Publish a test notice inside the target time | Customers have an official channel |
FAQ
Why do attackers go after online banking rather than payment systems?
Online banking faces the internet by design, and an outage there is public. Payment systems sit on private networks with the schemes. The best-known campaign against US banks, Operation Ababil in 2012 and 2013, went almost entirely for customer-facing sites.
Does a DDoS attack put customers' money at risk?
Not directly. A flood does not move money. The risk is what runs under its cover: account takeover and fraudulent transfers while fraud analysts are short-handed and their alerts are delayed, and customers unable to freeze a stolen card.
Can a credit union test its DDoS resilience if online banking is hosted?
Yes, within limits. The platform belongs to the provider, so loading it needs the provider's written permission and affects other institutions. The credit union can test its own DNS, contact centre, card block line, status page and communications, and should ask the provider for its own isolation and recovery evidence.
Should one-time passcodes be part of a bank DDoS test?
Yes. A login flood with credentials that pass the password check triggers codes, and the same channel often delivers payment approval codes. Measure both together on test accounts, never on real customers.
Does a bank DDoS test need to cover card and payment rails too?
A complete one does, but those paths are tested against scheme simulators and their timeouts, which our financial services post covers. This page adds the customer's side: whether people can get into their accounts and whether the fraud team can see what moves while they cannot.
Two kinds of sight
A bank in a DDoS has two audiences watching the same accounts. Customers want to see their money and stop it moving. The fraud team wants to see it moving when it should not.
A test that only counts requests at the edge measures neither. Can a customer load a balance, approve a payment and freeze a card in the twentieth minute of the flood? Did a planted fraudulent transfer get held while it ran?
Ask both questions in the same window. The attacker already does.
