Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

Banks Ready for Compliance Deadline

With a week to go before the FFIEC deadline, most financial institutions are ready for multifactor authentication

Dec. 31, 2006 will bring out an array of party hats, confetti, and noisemakers across the globe. But in the recesses of data centers in many banks and financial institutions, that date may give IT workers another reason to pop the champagne cork.

New Year's Eve is the final deadline for financial organizations to meet multifactor authentication requirements outlined by the Federal Financial Institutions Examinations Council (FFIEC), which helps to govern security requirements for banks and other organizations that handle consumer funds. The FFIEC guidelines, which were issued in October of last year, require financial institutions to deploy a second form of user authentication by Dec. 31 or face fines of $10,000 and up.

And it looks like most banks will beat the deadline, experts say. "I would say about 80 percent of the industry is in full compliance right now," says Marne Gordan, director of regulatory affairs at Cybertrust. "Even among the organizations that aren't in compliance, most of them are in position to be compliant before the auditors start doing their examinations."

The Aite Group LLC, a research firm that follows the financial services industry, confirms that the majority of banks will achieve FFIEC compliance by the Dec. 31 deadline, though its numbers are less optimistic. In a report issued at the beginning of last month, The Aite Group estimated that 66 percent of financial institutions will be in compliance by the end of the year, with the rest following in 2007.

"Even for the organizations that don't make it, there's still some time," Gordan observes. The FFIEC will begin making its examinations in February, she notes, and even then, "they will probably give some grace to organizations that have made a good-faith effort to achieve compliance, but may have overlooked something in the process," she predicts.

Unlike other compliance guidelines, such as Sarbanes-Oxley or HIPAA, the FFIEC guidelines are fairly straightforward. They state that banks and financial institutions that do business online must implement a second factor of authentication -- besides the simple password -- by the end of the year.

That second factor of authentication could be a "security question" that is difficult for a phisher or identity thief to discover, or it could be a token, smart card or biometric signature that a thief cannot replicate.

With phishing and identity fraud running rampant -- and scaring away many online customers -- most banks and financial institutions were moving in the direction of multifactor authentication anyway, experts say. The Anti-Phishing Working Group reported a 50 percent increase in phishing sites between September and October (See Report: Phish Jump), and some banks have completely stopped using email as a means of communicating with customers.

"It's out of control," says Gordan. "Two-factor authentication won't solve the problem, but at least it will put a stop to the simplest phishing techniques, where the phisher just sends out a lot of spam and hopes that users will give up their passwords. Now, the phisher will have to get two pieces of information, and those pieces of information will be different from bank to bank."

There are a few financial organizations -- mostly smaller credit unions -- that still haven't done anything with FFIEC compliance, but most of the organizations are up to speed, Gordan says.

"This is one area where compliance makes good business sense," Gordan says. "Identity theft is such a huge problem. Meeting the FFIEC deadlines will help."

— Tim Wilson, Site Editor, Dark Reading

  • Cybertrust

    Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Oldest First  |  Newest First  |  Threaded View
    Commentary
    What the FedEx Logo Taught Me About Cybersecurity
    Matt Shea, Head of Federal @ MixMode,  6/4/2021
    Edge-DRsplash-10-edge-articles
    A View From Inside a Deception
    Sara Peters, Senior Editor at Dark Reading,  6/2/2021
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon Contest
    Write a Caption, Win an Amazon Gift Card! Click Here
    Post a Comment
    Current Issue
    The State of Cybersecurity Incident Response
    In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
    Flash Poll
    How Enterprises are Developing Secure Applications
    How Enterprises are Developing Secure Applications
    Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2021-21439
    PUBLISHED: 2021-06-14
    DoS attack can be performed when an email contains specially designed URL in the body. It can lead to the high CPU usage and cause low quality of service, or in extreme case bring the system to a halt. This issue affects: OTRS AG ((OTRS)) Community Edition 6.0.x version 6.0.1 and later versions. OTR...
    CVE-2021-23394
    PUBLISHED: 2021-06-13
    The package studio-42/elfinder before 2.1.58 are vulnerable to Remote Code Execution (RCE) via execution of PHP code in a .phar file. NOTE: This only applies if the server parses .phar files as PHP.
    CVE-2021-34682
    PUBLISHED: 2021-06-12
    Receita Federal IRPF 2021 1.7 allows a man-in-the-middle attack against the update feature.
    CVE-2021-31811
    PUBLISHED: 2021-06-12
    In Apache PDFBox, a carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
    CVE-2021-31812
    PUBLISHED: 2021-06-12
    In Apache PDFBox, a carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.