Feeds

ICANN urged to cut phishing trawl with banking domain

.Safe harbour

SANS - Survey on application security programs

Security watchers are calling on net governance body ICANN to adopt a new top level domain name to be used exclusively by registered banks and financial organisations.

A .safe or .sure domain name would give consumers increased piece of mind that they are dealing with a legitimate financial institution while potentially making it easier to identify rogue sites.

If ICANN introduced a .safe domain (or .sure or .bank), which could only be used by registered financial institutions, it would allow security providers to create better software to protect the public, according to F-Secure.

The idea has been in existence for some time, but the massive rise in phishing attacks over recent months has renewed interest. According to figures from UK banking organisation APACS released earlier this month, online banking fraud losses in the UK alone came to £33.5m in 2006, up from £23.2m in 2005. This 44 per cent year-on-year increase was largely driven by an increase in phishing incidents, which went up from 1,713 in 2005 to 14,156 last year.

"While a .safe domain name won’t prevent phishing attacks, it will help banks and security providers to keep their customers safe,” said Mikko Hyppönen, chief research officer at F-Secure. "Using a secure domain name such as .safe will give customers the reassurance they need when banking online.

"It’s true this will mean banks have to pay a premium to be able to use the domain name, but it will reduce the number of successful phishing sites that have been tricking many customers out of their hard earned cash," Hyppönen continued.

Recent months have seen the launch of numerous services and enhancements to browser software packages and searching sites designed to warn users that they might be visiting dodgy domains. Hyppönen reckons these efforts are all well and good but don't go far enough. "Right now, customers have no good way of automatically being able to tell whether or not a bank website belongs to the bank," he said.

A .safe domain only available to financial institutions would be comparable to top level domains such .gov, which is only available to government institutions. Anecdotal evidence suggests this approach might lead to a more controlled environment for internet banking. A recent study based on results from SiteAdvisor, a free "safe searching" tool from McAfee that catalogues and warns users about unsafe sites, found that .gov was the only tested domain for which SiteAdvisor found no risky sites. ®

High performance access to file storage

More from The Register

next story
Obama allows NSA to exploit 0-days: report
If the spooks say they need it, they get it
Samsung Galaxy S5 fingerprint scanner hacked in just 4 DAYS
Sammy's newbie cooked slower than iPhone, also costs more to build
Snowden-inspired crypto-email service Lavaboom launches
German service pays tribute to Lavabit
Mounties always get their man: Heartbleed 'hacker', 19, CUFFED
Canadian teen accused of raiding tax computers using OpenSSL bug
One year on: diplomatic fail as Chinese APT gangs get back to work
Mandiant says past 12 months shows Beijing won't call off its hackers
Call of Duty 'fragged using OpenSSL's Heartbleed exploit'
So it begins ... or maybe not, says one analyst
prev story

Whitepapers

Top three mobile application threats
Learn about three of the top mobile application security threats facing businesses today and recommendations on how to mitigate the risk.
Combat fraud and increase customer satisfaction
Based on their experience using HP ArcSight Enterprise Security Manager for IT security operations, Finansbank moved to HP ArcSight ESM for fraud management.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Five 3D headsets to be won!
We were so impressed by the Durovis Dive headset we’ve asked the company to give some away to Reg readers.
SANS - Survey on application security programs
In this whitepaper learn about the state of application security programs and practices of 488 surveyed respondents, and discover how mature and effective these programs are.