SSL Evaluation for Oman Banks
We all know that any bank that offers online banking should anticipate its customers’ security concerns. I was disappointed to know that most of Oman local banks are not aware of their grades which could be a real threat to them and their clients. I am going to list some of them with recommendations on how to mitigate the issues, in case you belong to any of the listed entities please make sure you inform the security teams to take action. If they face difficulty please do not hesitate to contact us, this may sound simple to you but I am pretty sure it will lead to security breaches in the near future and its our national duty to enhance security.
Before we start please note that I have previously published a tutorial on how to solve SSL issues and obtain grade A+ you can find it here banking security specialist feel free to make use of it.
Overall rating scheme: (Latest test on 5-11-2016):
- Overall rating scheme:
- A+ (Excellent)
- A (Very good)
- A- (Good)
- B (Acceptable)
- C (Weak)
- T (Very weak)
- F (Fail).
All of the below tests results were obtained PUBLICLY from SSLLAB. The result are published on a well recognized security company Qualys all I did was explaining the problem and providing a solution for the sake of having secure online banking. Additionally I made sure that I have contacted all of the mentioned banks via phone, Twitter, Facebook and Email and informed them that they have a problem that has to be solved immediately.
- Some banks should consider using strong ciphers that supports Forward Secrecy.
- All banks should generate a new certificate with RSA 4096 bits key.
Important Note and DISCLAIMER:
The contents of this blog do not relate in any way to a specific incident. This blog is especially not suggesting or even providing an argument that the recent card skimming going on in Oman is related to one of the aforementioned banks.
The specific tests that were run and discussed on this blog are for only one area of security, which emphasizes the strength of connection security between the end user and the bank via a web browser.
While some banks may not have ranked as strong as I had hoped on this test (a test that any person may perform themselves because it is publicly accessible), banks that rank lower on this test may rank higher on other tests. Banks can be very strong in other aspects of their security and their security as a whole cannot be determined based on a single test. Additionally, to test other aspects of security prior authorization by a specific bank is required, which this blog and the average person do not have.
Eagle Eye Digital Solutions – SSL Status:
As we have seen most of them fail to meet the security standards for SSL which drives the online banking. I believe that banks should always make sure that they maintain grade A+ as explained here.
Latest posts by Warith Al Maawali (see all)
- Migrate Vbulletin to Burning board – Hows and Whys - March 27, 2016
- Getting your mass marketing email to the inbox – Effective Email Techniques - March 6, 2015
- IOS Tips Keyboard Shortcuts on IPHONE & IPAD - February 22, 2015
- Security Assessments - January 1, 2015
- Secure Dedicated Hosting - December 21, 2014
There are many reasons why a certificate may not be trusted. The exact problem is indicated on the report card in bright red. The problems fall into three categories:
Unknown Certificate Authority
1. Invalid certificate
A certificate is invalid if:
It is used before its activation date
It is used after its expiry date
Certificate hostnames don’t match the site hostname
It has been revoked
2. Invalid configuration
In some cases, the certificate chain does not contain all the necessary certificates to connect the web server certificate to one of the root certificates in our trust store. Less commonly, one of the certificates in the chain (other than the web server certificate) will have expired, and that invalidates the entire chain.
3. Unknown Certificate Authority
In order for trust to be established, we must have the root certificate of the signing Certificate Authority in our trust store. SSL Labs does not maintain its own trust store; instead we use the store maintained by Mozilla.
If we mark a web site as not trusted, that means that the average web user’s browser will not trust it either. For certain special groups of users, such web sites can still be secure. For example, if you can securely verify that a self-signed web site is operated by a person you trust, then you can trust that self-signed web site too. Or, if you work for an organisation that manages its own trust, and you have their own root certificate already embedded in your browser. Such special cases do not work for the general public, however, and this is what we indicate on our report card.
4. Interoperability issues
In some rare cases trust cannot be established because of interoperability issues between our code and the code or configuration running on the server. We manually review such cases, but if you encounter such an issue please feel free to contact us. Such problems are very difficult to troubleshoot and you may be able to provide us with information that might help us determine the root cause.