MétaCan
Menu
Back to cohort
Record W2342284646

Design, development, and implementation of a public key cryptosystem for automated teller machines: the toronto dominion bank case study

2006· article· en· W2342284646 on OpenAlexaboutno aff
Marlyn Kemper Littman, Tamer Aboualy

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicCryptographic Implementations and Security
Canadian institutionsnot available
Fundersnot available
KeywordsCryptosystemPublic-key cryptographyComputer scienceKey managementEncryptionComputer securityCryptographyKey (lock)
DOInot available

Abstract

fetched live from OpenAlex

The current method of distributing Automated Teller Machine (ATM) Data Encryption Standard (DES) keys involves manual distribution of the same DES key in component form to all ATMs in a bank's network. The components are entered into the ATM keyboard and combined to form the ATM Terminal Master Key (TMK) used for all ATM transactions. Public key cryptosystems can be used to distribute and manage ATM TMKs. However, existing cryptosystem implementations have numerous problems. Moreover, little research has targeted cryptosystem implementations that use tamper-resistant security modules (TRSMs). Almost all security attacks of cryptosystems utilizing security processors and cryptography are the result of weak implementation and deployment. This case study describes how a public key cryptosystem for distribution and management of ATM Triple Data Encryption Standard (3DES) TMKs may be successfully implemented. This case study was developed to offer a repeatable approach, design, and implementation for a public key cryptosystem for ATM 3DES TMK distribution and management. The study's design was based on a single case, using multiple sources of evidence and propositions. Using Toronto Dominion (TD) Bank as the unit of analysis, the study focuses on four main propositions relating to (a) system development processes (SDPs), (b) electronic data assurances, (c) key and certificate life cycle management, and (d) ATM key hierarchies. Results of the study show that SDPs provided a general framework for system development and were not tailored to specific needs of an ATM cryptosystem. Evidence shows that the ATM public key cryptosystem met all CAIN digital assurance and ATM key hierarchy requirements but did not meet all key and certificate life cycle requirements. The author recommends a modified SDP framework for ATM public key cryptosystems called cryptosystem SDPs. These consist of SDPs, an integration of ATM cryptosystem requirements, and software security best practices. This framework utilizes existing SDPs but adds four new phases to take into account ATM public key cryptosystem requirements.

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 distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.445
Threshold uncertainty score0.994

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.040
GPT teacher head0.327
Teacher spread0.287 · 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 teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designQualitative
Domainnot available
GenreEmpirical

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 topicCryptographic Implementations and SecurityFrench-language works237,207