← All articles

Bank Grade Security - South African bank edition

After reading an interesting post by Troy Hunt about so called "bank grade" security on Aussie internet banking sites I was curious to see what the results would be for South African banks and more specifically how my bank stacks up against the competition. The results are similar with some very surprising names scoring quite low using Qualys SSL Server Test.

Bank Grade SSL3 SHA1 TLS 1.2 RC4 FS* POODLE
African Bank A- PASS FAIL PASS PASS FAIL PASS
Sasfin A- PASS FAIL PASS PASS FAIL PASS
Bidvest B PASS PASS PASS FAIL FAIL PASS
First National Bank B PASS PASS PASS FAIL FAIL PASS
Nedbank B PASS PASS PASS FAIL FAIL PASS
Investec B FAIL FAIL PASS FAIL FAIL PASS
Grindrod B FAIL PASS FAIL FAIL FAIL PASS
Capitec B PASS FAIL FAIL FAIL PASS- PASS
Standard Bank C FAIL FAIL FAIL FAIL FAIL FAIL
ABSA F FAIL FAIL FAIL FAIL FAIL FAIL
Imperial Bank F FAIL PASS- PASS FAIL PASS- FAIL

* Forward Secrecy

The most surprising to me was Standard Bank and ABSA, the top two largest banks in the country, are failing dismally on their SSL implementation. Imperial Bank is frightening and vulnerable to both POODLE and FREAK attacks. The smallest banks seem to score the highest and a number of South African banks don't even have internet banking such as uBank and Postbank.

Although the grades look decent overall, the amount of red is quite concerning.

The conversation

6 comments
ssl person
Looking at a bank's other domains is often interesting

https://pentest-tools.com/reconnaissance/find-subdomains-of-domain

"access.sasfin.com": "M"
"sip.sasfin.com": "B"
"old.sasfin.com": "M"
"www.sasfin.com": "B"
"www.sasfin.com": "B"
"sasfin.com": "B"
"owa.sasfin.com": "F"
"ibank.sasfin.com": "A-"

events.sasfin.com - not found, no ssl

sasfin.com M - only valid for www.sasfin.com (SSL Labs automatically tests www. if you only put the domain name in)
Werner Author
I did take a look at some alternate domains for those banks and the grades were not great. The URLs tested (the ones in the links on the table) are the domains that host the internet banking portion and not necessarily the bank's main portal/website.

To be fair, only the internet banking domains were tested which are generally more secure or at least supposed to be. I used the URLs of the pages that display the login request form to access internet banking, the same pages users would land on if they went through the bank's main website and the ones where SSL is most important.

For example, Bidvest scores a B on the bank's internet banking domain "secure.bidvestbank.com", but an F of the bank's main website "bidvestbank.co.za".
William
I suspect this has a lot to do with clients using older browsers that don't support the newer protocols. In a perfect world they would immediately discontinue anything that posed a security risk but I imagine they are prioritising customer access. Unfortunately the customers with the older browsers are also the most likely to end up complaining when their internet banking stops working.

The smaller banks have fewer customers so can afford to implement quick security upgrades with less of an impact.
Werner Author
I agree that the banks reduce their security requirements in favour of users with older browsers, but that is no excuse to compromise everybody's security for the sake of making it easier for those users. Banks should be forcing users to be more secure, they would be worse off becoming the victim of an exploit than a few users complaining that they cannot use internet banking because they are using outdated, insecure software. You have no idea how often I see people on their laptops in public places (public WiFi) doing banking, the vast majority of the time the bank can be faulted if those ignorant users are compromised with simple SSL based exploits because those users expect the banking sites to be more secure than they actually are.
Desain
What should users—and banks—make of grades ranging from A⁻ to F issued via the Qualys SSL Server Test?
Werner Author
@Desain: They can make of it whatever they want to. Anyone is welcome to re-run the tests to check for improvement over time. Bad scores simply mean bad security (in terms of SSL usage), how else should you interpret that?