Perimeter
10/18/2011
07:02 PM
Commentary
Commentary
Commentary
50%
50%

FFIEC Goes Beyond Traditional Authentication

The FFIEC recommends that organizations provide additional business and fraud detection controls to offset weaknesses in authentication technology

The FFIEC's recommendations for layered protection include mechanisms other than authentication to detect and prevent fraud. It is important to use information about customer location and behavior as an aid in detecting fraud.

In my previous post, I provided an overview of the supplement to the Authentication in an Internet Banking Environment guidance.

The FFIEC authentication supplement gives specific examples of fraud detection and monitoring systems that financial institutions should consider. It recommends monitoring customer transaction history and behavior. For example, it might be a sign of fraud when a customer who has never transferred funds to an nonaffiliated account does so for the first time. Address changes, changes to banking instructions for funds, and changes to beneficiaries are other important activities that should be verified through multiple contact methods.

The guidance also suggests institutions use multiple communication channels for confirmation of important transactions. For example, confirming password changes by email, telephone, and/or surface mail can provide more reliable authentication and might help to expose fraud attempts to customers. Another effective technique for preventing fraud is to require waiting periods after important account modifications, like address changes and banking instructions. While not foolproof, this approach provides more of an opportunity for customers to play a part in recognizing fraudulent activity.

The use of multiple layers of security is nothing new in the financial industry. Almost all of these methods are commonly implemented in mutual-fund companies and banks. In fact, any organization that extends credit (even the car dealership down the street) is supposed to be on the lookout for activities that would suggest that identity has been stolen and someone is attempting to perpetrate fraud.

The FTC’s Red Flag Rules require organizations to have controls in place to detect apparently fraudulent activities. Examples of “red flags” include mismatches of personal identifying information, incorrect signatures, mismatched addresses, and use of known stolen identities. The use of such nontechnical information is not just a suggestion -- it’s a requirement.

All organizations, whether they are financial institutions, merchants, or health care companies, should consider the types of activities that might signal identity theft, fraud, and misuse of accounts as components of their security control arsenal.

Richard Mackey is vice president of consulting at SystemExperts Corp.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-8142
Published: 2014-12-20
Use-after-free vulnerability in the process_nested_data function in ext/standard/var_unserializer.re in PHP before 5.4.36, 5.5.x before 5.5.20, and 5.6.x before 5.6.4 allows remote attackers to execute arbitrary code via a crafted unserialize call that leverages improper handling of duplicate keys w...

CVE-2013-4440
Published: 2014-12-19
Password Generator (aka Pwgen) before 2.07 generates weak non-tty passwords, which makes it easier for context-dependent attackers to guess the password via a brute-force attack.

CVE-2013-4442
Published: 2014-12-19
Password Generator (aka Pwgen) before 2.07 uses weak pseudo generated numbers when /dev/urandom is unavailable, which makes it easier for context-dependent attackers to guess the numbers.

CVE-2013-7401
Published: 2014-12-19
The parse_request function in request.c in c-icap 0.2.x allows remote attackers to cause a denial of service (crash) via a URI without a " " or "?" character in an ICAP request, as demonstrated by use of the OPTIONS method.

CVE-2014-2026
Published: 2014-12-19
Cross-site scripting (XSS) vulnerability in the search functionality in United Planet Intrexx Professional before 5.2 Online Update 0905 and 6.x before 6.0 Online Update 10 allows remote attackers to inject arbitrary web script or HTML via the request parameter.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.