MétaCan
Menu
Back to cohort
Record W2993441608

Countdown to FFIEC Fitness: As Authentication Deadline Nears, Banks Consider All Options

2006· article· en· W2993441608 on OpenAlexaboutno aff
Lauren Bielski

Bibliographic record

VenueABA banking journal · 2006
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBanking Systems and Strategies
Canadian institutionsnot available
Fundersnot available
KeywordsCountdownConfusionBusinessAuthentication (law)Computer securityLawPolitical scienceFinanceComputer scienceEngineering
DOInot available

Abstract

fetched live from OpenAlex

Like early birds with worms, banks that began to revamp their online authentication process prior to regulatory prodding have been validated by the powers that be and are in a relaxed state of waiting. Zions Bank, for one, opted to beat any mandates related to the Federal Financial Institutions Examination Council's strong authentication guidance, dated October 2005 and with an action date of January 2007. The Utah-based regional powerhouse had begun thinking about the issue a year and a half ago, says Lee A Carter, president of online banking for Zions. It was done because it is the right thing to do, the executive says simply. Opting for a device-profiling solution, Zions launched its enhanced front door, after extended fanfare and customer education on July 20. Vasco, with U.S. offices in Chicago, is the largest global provider of authentication, and as such, is familiar with other early adopters. Adam Dolby, business development manager, financial sector, indicates clients that include ABN Amro, Sovereign, and Wachovia all say, it on, when it comes to prospect of facing more demanding examiners. is really a global issue, says Dolby. It's been interesting to see the use of improved authentication methodology and software migrate from Europe and Canada to Asia and now--largely because of FFIEC--to the U.S., he explains. FFIEC confusion Now, with a December 30 deadline on matters related to authentication closing in, it's time for the laggards to get in the groove. The question is, how best--and how exactly--to supplement the lowly, now largely discredited, password? There are many options, even too many, to choose among. Meanwhile, some confusion still exists about what is actually required even as most experts believe that what a guidance-related project can't be is significantly underdone at the dawn of 2007. Still, the penalties aren't yet clear and rumors are circulating of an extended grace period throughout next year. Against this backdrop, banks are figuring out how to proceed. Banks are on a measured course of action with this, notes Beth Robertson, research director with Gartner, Stamford Conn. She admitted surprise at the attendance levels at June conferences and webinars that discussed preparation for FFIEC guidance. Robertson notes that most institutions are still figuring out what will be best for their needs, target markets, and transaction risk profiles. Even though Zions is good on the authentication front, for example, executives there are already thinking about what else needs to be done to protect riskier transactions, according to Carter. Dennis Maicon, vice-president, Digital Resolve, Norcross, Ga., also sees bankers (particularly from the larger institutions) thinking through the security issues and broader requirements only obliquely referred to by the guidance, which, admittedly, dovetails with the company's 360 degree marketing message. Among my perspective customers, the thinking is, this is also an opportunity to address fraud comprehensively, Maicon explains. This would include the ability to monitor channel activity and stop suspect transactions, for instance, while creating audit trails useful for reporting purposes and for working with authorities when the inevitable investigation arises. Gartner's Robertson agrees that most banks want to solve root issues of transaction and data protection as well as address multiple potential avenues of fraud. But she points out, anything that gets re-engineered has to also be financially feasible and make sense in terms of the institution's net risk profile. We bring this up because there are many who say that too much emphasis is at the front-door, mostly due to a misinterpretation of what FFIEC's authentication guidance suggests more broadly about how to best engineer online security. Instead, these advocates believe, the emphasis ought to be on increasing consumer confidence in the channel and, in fact, making it safer. …

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.019
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Commentary · Consensus signal: none
Teacher disagreement score0.377
Threshold uncertainty score0.889

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.019
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.001
Science and technology studies0.0070.002
Scholarly communication0.0120.007
Open science0.0010.004
Research integrity0.0080.008
Insufficient payload (model declined to judge)0.3770.234

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.020
GPT teacher head0.256
Teacher spread0.236 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

Study designNot applicable
Domainnot available
GenreCommentary

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2006
Admission routes1
Has abstractyes

Explore more

Same venueABA banking journalSame topicBanking Systems and StrategiesFrench-language works237,207