But again I’m going to repeat what I posted earlier, the purpose of running security software is to provide users with malware-free environment. This is done through a variety of layers and modules targetting:
- Distribution: web filtering, CDR, IPS
- Pre-execution: static analysis, dynamic analysis, sandboxing, CDR, reputation, standard antivirus
- Post-execution: anti-bot, behavioural monitoring.
These should be enough to tackle banking trojans in due time. If not tackled, the malware has already probably exfiltrated passwords, payment details and worst of all, session cookies. The process takes 2-3 seconds and can’t be interrupted by banking protection.
Banking protection hence is an unnecessary
gimmick screaming “look how much we are doing for you”, when in reality nothing is being done. It is
extremely sad that some vendors are heavily-focused on such gimmicks and not enough focused on core security modules.
As per the F-Secure documentation for example, available here:
What is Banking Protection and how does it work? Banking Protection adds another layer of security when banking online or when entering other types of sites that contain sensitive information. When Banking Protection is turned on in the product, every website that you enter is checked by...
community.f-secure.com
F-Secure banking protection merely disconnects processes with no “safe” reputation from the internet — something that should be happening without banking protection and round the clock too — not just when user are banking. Had F-Secure developed a firewall that is, but firewall doesn't sound as fancy as "Banking Protection".
F-Secure DeepGuard is highly aggressive towards unknown and suspicious processes anyway so such processes will most likely end up terminated, no banking protection required.
F-Secure Banking Protection will provide ~0 security in the following cases:
- Users open malicious website, for example website infected with Magecart malware
- Users open brand new phishing site that looks convincing
- Users open a scam store
- Code injection in a trusted process (which most banker trojans use)
- MITM or any sort of connection manipulation
- Theft and loss of data through other means, for example grabbing from browser/password manager, clipboard
The only benefit slightly meaningful is that, if attackers take user to chasee.com instead of Chase, banking protection does not trigger, which should be an indicative that this is not a banking website. And even that will go unnoticed by many.