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.

Perimeter

9/24/2011
10:00 AM
Commentary
Commentary
Commentary
50%
50%

New FFIEC Authentication Guidance Calls For Layers

Increased threats and weaknesses in certain accepted authentication mechanisms, FFIEC warns

At the end of June, the Federal Financial Institutions Examination Council (FFIEC) issued a supplement to the Authentication in an Internet Banking Environment guidance, which was originally released in October 2005. The substance of the guidance is that financial institutions should base their choices of authentication methods on risk assessments, and that high-risk transactions should be based on layered mechanisms.

The guidance (PDF) paints a somber and accurate picture of the threats facing institutions doing business on the Internet: It cites increasingly sophisticated criminal groups that target financial institutions, broadly available tools that allow unskilled fraudsters to perpetrate attacks, and the availability of detailed information on how to circumvent standard authentication and antifraud mechanisms as key threats to today’s financial institutions. Because of the increased number and severity of the threats, the FFIEC believes the guidance it gave in 2005 needed to be reinforced and strengthened.

The FFIEC has maintained from the start that security controls should be chosen based on results from a thorough risk assessment. The guidance recommends conducting a risk assessment not only at the initial deployment of a service, but also when threats change (e.g., known attack methods, identified vulnerabilities in mechanisms), when customer types and behavior change (e.g., increases in user sophistication or unanticipated increase in use of the service), when features of the service change (e.g., higher transaction limits or more automation), and after incidents (e.g., identity theft or fraud).

It stands to reason that an assessment of the risk of low-frequency, low-value consumer transactions would pose less a risk to financial institutions and their customers than commercial transactions that occur at high frequency or involve large sums of money.

Consequently, the FFIEC recommends increasing the strength of authentication mechanism as the assessed risk rises. And consistent with its previous recommendations, it continues to recommend multifactor authentication for high-risk transactions. However, in recognition of some of the high-profile compromises that have occurred in the past few years, the guidance points out that virtually every authentication mechanism can be compromised. It even goes as far as to say that specific techniques recommended in 2006 are vulnerable to attack. The punch line of the guidance is that organizations shouldn’t rely entirely on a single authentication method to protect them. Good security is based on layered defenses that consist of both technical and business mechanisms. The report lists various layered mechanisms (which will be discussed in more detail in a future post), but identifies two customer situations where these layers are necessary: account registration (and initial authentication) and transfer of funds to other parties. This shouldn’t surprise anyone in the financial community because these two activities are the easiest to perpetrate fraud.

The FFIEC guidance is an excellent short paper on the threat landscape, the effectiveness of popular authentication methods, and the need for layered defenses, particularly in specific types of customer interactions and transactions. Every security professional should seriously consider the advice the FFIEC provides.

Richard Mackey is vice president of consulting at SystemExperts Corp.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest 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
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-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.
CVE-2021-32552
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-16 package apport hooks, it could expose private data to other local users.