News

11:00 AM
Ron Shevlin, Senior Analyst, Aite Group (Boston)
Ron Shevlin, Senior Analyst, Aite Group (Boston)
News
Connect Directly
RSS
E-Mail
50%
50%

Banks Should Empower Recipients in the Fight Against E-Mail Fraud

In addition to implementing authentication protocols, banks should ensure that e-mail recipients understand e-mail dangers and control their own fates.

Ron Shevlin, Aite GroupBanks need to implement e-mail authentication protocols to help prevent e-mail fraud. Specifically, a bank should publish its Sender Policy Framework (SPF) record (a technical standard that helps prevent sender address forgery); implement cryptographic solutions, such as digital signatures and encryption; and control and monitor its brand domain names. Internet service providers (ISPs) often reject e-mail from derivative domains, so banks should standardize "from" lines.

Banks also should empower the customer/recipient in the fight against e-mail fraud. To do this, banks should provide easy and conspicuous access to preference pages and their privacy policies, allowing recipients to understand and control their preference information, including the ability to opt out or change messaging frequency and content. In addition, banks should incorporate e-mail change-of-address links and preference selection information in all messaging.

From a detection perspective, while many banks have incorporated fraud and spoofing education content onto their Web sites, they also should allow customers to report and/or submit suspicious e-mails. Banks should also implement internal systems to publish and communicate legitimate and fraudulent messaging to critical frontline employees who respond to customer questions/concerns.

There are two major initiatives that have been developed to address the requirement that senders of e-mail are authenticated: the Sender ID Framework (SIDF) and Domain Key Identified Mail (DKIM). The former is championed primarily by Microsoft and AOL, the latter by Yahoo and Google. Both provide a foundation for distinguishing legitimate e-mail, and thus a means of associating a verifiable identifier with a message.

While SIDF and DKIM fulfill a role in the sifting of wheat from chaff, a number of third-party solutions have been brought to market with the specific aim of providing some form of certificate of authenticity for delivered e-mails. A common characteristic of these solutions is to provide some form of mark for the end user to visually illustrate that an e-mail is trustworthy, such as a sealed envelope or a padlock.

Finally, to maximize productivity, banks should provide internal training on using e-mail; publish e-mail policies and best practices, including processes to assure the white-listing that is critical to business-to-business e-mail; and implement spam filtering solutions at the server level to reduce employee in-box clutter.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Janice, I think I've got a message from the code father!
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.