AQUA - A Modular Authentication Quality Modeling Framework

arXiv:2611.05660 · cs.CR, cs.SE · Submitted 2026-11-03 · Read on arXiv

Listen

Radio episode about this paper

Transcript

Introduction to the show: ident: Security Radio. Generated commentary on the latest security and cryptography papers.

Nadia: I'm Nadia.

Elias: And I'm Elias, here with Priya.

Nadia: We're looking at the paper: "AQUA - A Modular Authentication Quality Modeling Framework".

Elias: Here's the gist of the paper. Authentication solutions are key design, architectural, and implementation decisions that implement authentication security controls This paper presents AQUA, a modular quality modeling framework for authentication solutions Problem Statement Researchers often examine authentication quality but existing approaches do not distinguish which effects on quality stem from which aspect of authentication For example, multi-factor authentication solutions tend to be less usable because they combine multiple authenticators, whereas passkeys are more secure than passwords because of properties inherent to the authenticator itself Existing models do not distinguish whether a quality effect stems from the authenticator, from the way authenticators are employed, or from the concrete implementation This makes it impractical to trace how quality propagates from the authenticators through their employment to the solution as a whole AQUA Framework Decomposition AQUA decomposes authentication into four interrelated concepts: the authenticator, the authenticator employment, the authentication technique, and the authentication solution This decomposition separates three sources of quality effects: properties inherent to an authenticator, effects of how authenticators are combined, and effects of concrete implementation The four concepts are defined as follows: 1.

Nadia: Authenticator is the entity a user possesses or controls to perform authentication, e.g., a password 2.

Elias: Authenticator employment is a composition scheme for authenticators 3.

Nadia: Authentication technique is the concrete composition of authenticators under an authenticator employment 4.

Title and authors: Nadia: So, moving on to the title and authors of this paper, it’s "AQUA - A Modular Authentication Quality Modeling Framework," written by Alex R. Mattukat, Michael Zerbe, and Krisa Carka at RWTH Aachen University.

Elias: They are researchers working in the same area; Mattukat is focused on security controls like authentication, Zerbe and Carka work on software construction. It’s interesting to see how they're applying this modeling structure to the problem of authentication quality.

Nadia: Yeah, it shows a real effort to create a formal way to model these complex systems rather than just describing them vaguely in prose. They’re aiming for something that can be used systematically.

Priya: I’m curious about what they mean by "modular framework"; does that imply you can swap out parts easily without redesigning the whole system?

Elias: Precisely. The core of the paper is that they decompose authentication into four interrelated concepts: the authenticator, the employment, the technique, and finally, the authentication solution.

Nadia: That decomposition is key because it allows them to separate three distinct sources of quality effects: what’s inherent in an authenticator, how authenticators are combined, and what happens at the concrete implementation level.

Priya: So instead of one big quality score for a login system, they get different scores for each component that you can then look at individually?

Elias: That’s the point. They want to trace how quality propagates from those fundamental authenticators all the way through to the final product design. This is what makes it practical to understand where things go wrong.

The paper's summary: Nadia: The abstract explains that existing approaches don't tell you which part of an authentication solution is causing a quality dip, like whether it’s the multi-factor aspect or the specific authenticator itself.

Elias: AQUA tackles that by defining these four concepts—authenticator, employment, technique, and solution—to capture those different sources of quality effects. They use a usability metric called Ease of Use to show this propagation across the system.

Priya: The paper mentions calculating the EoU for a technique based on the authenticators and their employment schemes—like sequential or simultaneous ones—and then factoring in solution-specific design decisions like effort multipliers.

Nadia: Exactly. They demonstrate this by showing three initial definitional quality models, AQUA-A for authenticators, AQUA-T for techniques, and AQUA-S for solutions, based on the ISO SQuaRE model.

Elias: These models show how you can define dependencies between these concepts; for instance, they show how security factors might be shared across different levels of the model.

Priya: It sounds like they’re proving that you can build a structure where you can rigorously analyze authentication quality at each level, from the smallest component to the whole system.

Nadia: That’s what it does. They provide a foundation for modular quality modeling by ensuring these key authentication concepts are conceptually separated. This makes it possible to perform automated quality assessment later on.

The paper's improvements: Elias: The paper points out a few ways they can use this framework to actually improve things in practice. First, you can do automated quality assessment by applying AQUA models directly to specific design choices like authenticators or employment schemes.

Nadia: That’s huge for security auditing; it means you could trace a poor usability score right back to a specific choice of an authenticator or a particular way they are being combined.

Priya: And second, they suggest using this system to compare different authentication solution alternatives by estimating their quality based on the calculated Ease of Use metric derived from AQUA.

Elias: They also showed you can predict how changing components affects usability, for example, if you change a password length or switch to multi-factor authentication, you can calculate the resulting EoU using formulas like EoU of solution equals one minus a factor times the technique’s EoU adjusted by some other factors.

Nadia: That predictive element is what I find most useful. It moves it from just describing quality to actually estimating its impact before you even build it.

Priya: They also mention that this framework lets you define specific quality profiles for things, like separating the quality of generated passwords from self-chosen ones, which helps in ranking things by different criteria.

Conclusion: Nadia: So to wrap up, the core contribution of AQUA is providing a conceptual separation of key authentication concepts—authenticator, employment, technique, and solution—to enable modular quality modeling.

Elias: This structure allows for tracing quality effects from the authenticator through the technique to the final solution using a metric like Ease of Use. It’s a formal way to model this propagation.

Priya: For us in measurement, it means we have a structured way to look at usability and connect it systematically back to the design choices that affect it, which is something we often struggle with when looking at complex security systems.

Nadia: The limitation they state is that the models themselves are still definitional; they aren't exhaustive yet, and the Ease of Use metrics used in these demonstrations are illustrative rather than fully comprehensive.

Elias: They also flag that while they’ve shown how to model these relationships, developing actual assessment and prediction models for authentication solutions is still future work.

Priya: I think the most important thing here is getting this structure out there; it gives researchers a common vocabulary to talk about quality in a way that's actually traceable across the entire authentication stack.

Nadia: Yeah, so we have this AQUA framework for modular quality modeling of authentication solutions. It sets up a way to systematically analyze where usability issues come from in security controls.

RWTH Aachen University

cs.CR, cs.SE

Submitted: 2026-11-03

Updated: 2026-11-06

Comments: 11 pages, 3 figures, paper version 2 contains updated link to project website

Project page: https://aqua-authentication.github.io/AQUA/8

License: http://creativecommons.org/licenses/by/4.0/

Importance score: 83/100

The gist: Authentication solutions are key design, architectural, and implementation decisions that implement authentication security controls This paper presents AQUA…

Key concepts

Authenticator
This is the item or entity a user controls or possesses for authentication, such as a password, fingerprint, or PIN. It represents the fundamental proof of identity used during the process.
Authenticator Employment
This describes how multiple authenticators are combined into a system using 'slots.' It defines rules like whether authenticators must be used sequentially (one after another), simultaneously (at the same time), or conditionally.
Authentication Technique
This is the concrete assignment of which specific authenticator goes into which slot defined by the employment scheme. It specifies exactly how the chosen authenticators are put together to form a process.
Authentication Solution
This represents the final design, architecture, and implementation choices that realize an authentication technique. It is what a user actually interacts with in software or hardware.

Terminology

Summary

Authentication solutions are key design, architectural, and implementation decisions that implement authentication security controls This paper presents AQUA, a modular quality modeling framework for authentication solutions

Problem Statement

Researchers often examine authentication quality but existing approaches do not distinguish which effects on quality stem from which aspect of authentication For example, multi-factor authentication solutions tend to be less usable because they combine multiple authenticators, whereas passkeys are more secure than passwords because of properties inherent to the authenticator itself Existing models do not distinguish whether a quality effect stems from the authenticator, from the way authenticators are employed, or from the concrete implementation This makes it impractical to trace how quality propagates from the authenticators through their employment to the solution as a whole

AQUA Framework Decomposition

AQUA decomposes authentication into four interrelated concepts: the authenticator, the authenticator employment, the authentication technique, and the authentication solution This decomposition separates three sources of quality effects: properties inherent to an authenticator, effects of how authenticators are combined, and effects of concrete implementation

The four concepts are defined as follows:

  1. Authenticator is the entity a user possesses or controls to perform authentication, e. p. 1

    Where the paper says it

    Contribution: To close this gap, we developed AQUA, a modular quality modeling framework for authentication solutions. AQUA decomposes authentication into four interrelated concepts: the authenticator (the entity a user possesses or controls to perform authentication, e.

    g., a password

  2. Authenticator employment is a composition scheme for authenticators

  3. Authentication technique is the concrete composition of authenticators under an authenticator employment

  4. Authentication solution is the concrete design, architecture, and implementation that realizes a technique

Quality Propagation Modeling

The framework illustrates how quality propagates from the authenticators through techniques to solutions using a usability metric called Ease of Use (EoU) The EoU of an authenticator is defined as “the degree of how easy an authenticator can be inherently used by a human for authentication purposes” The EoU of a technique depends on the authenticators and their employment, calculated via specific formulas for single, sequential, simultaneous, and conditional employments Finally, the EoU of a solution is calculated as EoU(S) = min 1, EoU(T) · fin · (1 − fcs), where fin and fcs are effort multipliers reflecting solution-specific design decisions

Demonstration and Modeling

The paper demonstrates AQUA through three initial definitional quality models: AQUA-A for authenticators, AQUA-T for authentication techniques, and AQUA-S for authentication solutions These models are based on the ISO SQuaRE model and illustrate the structure of quality models built in AQUA The subfactors of these models are documented to show dependencies between concepts, such as how security factors might be shared across different levels

Conclusion and Future Work

The AQUA framework provides a foundation for modular quality modeling by ensuring the conceptual separation of key authentication concepts Limitations include the models being non-exhaustive and the EoU metrics being illustrative, but future work plans include extending models with additional quality factors and developing assessment and prediction models The framework also supports defining quality profiles for authenticators and techniques, such as separate profiles for generated versus self-chosen passwords

REFERENCE

B AQUA - A MODULAR AUTHENTICATION QUALITY MODELING FRAMEWORK

Ahornstraße 55 Aachen, Germany michael.zerbe@rwth-aachen. p. 0

Where the paper says it

rwth-aachen. de Michael Zerbe Research Group Software Construction RWTH Aachen University Ahornstraße 55 Aachen, Germany michael.

de Krisa Carka krisa. p. 0
Where the paper says it

zerbe@rwth-aachen. de Krisa Carka RWTH Aachen University Ahornstraße 55 Aachen, Germany krisa.

carka@rwth-aachen. p. 0
Where the paper says it

zerbe@rwth-aachen. de Krisa Carka RWTH Aachen University Ahornstraße 55 Aachen, Germany krisa.

de November 5, 2026

B This is the peer-reviewed, accepted version of a paper. It will appear in the proceedings of the 13th International Workshop on Quantitative Approaches to Software Quality (QuASoQ 2026), co-located with the 33rd Asia-Pacific Software Engineering Conference (APSEC 2026)

B ABSTRACT Authentication solutions are the key design, architectural, and implementation decisions that implement authentication security controls While researchers often examine authentication quality, existing approaches do not distinguish which effects on quality stem from which aspect of authentication This paper presents AQUA, a modular quality modeling framework for authentication solutions AQUA’s core idea is to decompose authentication into four interrelated concepts, enabling modular specification of authentication quality and tracing quality effects back to their source We demonstrate AQUA with initial definitional quality models that address the levels of authenticators, authentication techniques, and authentication solutions We further illustrate the interrelations between these concepts through concrete examples and a usability metric, showing how quality propagates across the concepts and ultimately affects the overall quality of an authentication solution Our results provide a foundation for future work, including designing assessment and prediction models for authentication solutions and automated quality assessments

B 1 Introduction Security controls are central to securing software systems. They are countermeasures that protect a software system’s confidentiality, integrity, and availability [1] Examples are authentication and Distributed Denial-of-Service (DDoS) prevention Security solutions exhibit quality properties, such as usability and performance Comparing the usability of an authentication solution with that of a DDoS-prevention solution makes little sense, as they depend on entirely different factors We focus on authentication, as it is one of the most widely used security controls [5] Moreover, authentication failures rank 7th on the OWASP1 Top Ten list [6]

B 2 Background Authentication is the process by which a subject—in the following referred to as the user—gives proof of the identity they claim using one or more authenticators [3] An authenticator is the entity that a user controls and possesses to prove their identity, such as a password or fingerprint [5] We refer to the key design, architectural, and implementation choices made to realize authentication as an authentication solution Authentication solutions exhibit quality properties Some effects stem from using multiple authenticators, others from inherent properties of the authenticator (a passkey is more secure than a password because it prevents users from choosing weak passwords), and still others from the technical implementation

B 3 The AQUA Framework Authentication Technique has Authenticator Employment Authenticator Quality has Authentication Technique Quality depends on Authentication Solution implements determines Authentication Solution Quality depends on conforms to As introduced above, AQUA decomposes authentication into four interrelated concepts

B 3.1 Authenticator An authenticator represents the most fundamental part of authentication In AQUA, an authenticator denotes the type level, e. p. 2

Where the paper says it

Figure 1 depicts AQUA’s concept model. 1 Authenticator An authenticator represents the most fundamental part of authentication.

g., a password or a fingerprint; its instances are concrete authenticators Examples include A password (pw), fingerprint (fp), iris (ir), PIN (pin) and one-time password (otp) as authenticators

B 3.2 Authenticator Employment Many authentication solutions do not use a single authenticator, but compose several authenticators together An employment is a composition scheme for authenticators built on “slots” A slot is a place that awaits exactly one authenticator Employments can specify cardinality and mode, such as Sequential employment (Eseq), Simultaneous (Esim), or Conditional (Econd) Nesting allows for recursive modes to model complex compositions

B 3.3 Authentication Technique An authentication technique defines the concrete assignment of which authenticator is assigned to which slot An authentication technique is formally defined as a pair T = (E,(a1,. p. 4

Where the paper says it

, each slot can be assigned an arbitrary authenticator. The authentication technique defines the concrete assignment of which authenticator is assigned to which slot.

.., ak)), where E is an employment with cardinality k and ai ∈ A an authenticator assigned to the i-th slot

B 3.4 Authentication Solution The authentication technique reflects the conceptual approach for how authentication is performed Its technical realization is an authentication solution, which aligns with NIST [2] as the key design, architectural, and implementation choices made to realize authentication

B 4 Quality Relationships As shown in Figure 1, authenticators, authentication techniques, and authentication solutions have qualitative properties These properties propagate from the authenticator to authentication techniques and then to authentication solutions Usability is one such quality factor for which the EoU is defined as “the degree of how easy an authenticator can be inherently used by a human for authentication purposes”

B 4.2 Authentication Technique Quality An authentication technique influences a solution’s EoU through the authenticators and their employment For sequential and simultaneous employments, the EoU is calculated as 1/Pn where Pn is the number of slots Conditional employments have an EoU equal to that of the sub-employment used

B 4.

Green — the paper says it, and the page is printed. Red — no passage carries it, so treat that sentence as unverified. The same check runs on your own text: check a summary against its source, $5.

Improvements for AI systems

  1. Automated quality assessment of authentication solutions can be performed by applying AQUA models to specific design choices such as authenticators, employment schemes, techniques, and solutions to trace quality effects back to their source.

  2. The improved system can compare different authentication solution alternatives by estimating their quality based on the calculated Ease of Use (EoU) metric derived from the AQUA framework.

  3. The system can predict how changes in authentication components, such as using a longer password or switching devices for MFA, will affect the overall usability of an authentication solution by calculating EoU using formulas like EoU(S) = min 1, EoU(T) · fin · (1 − fcs).

  4. The system can define quality profiles for specific authenticators and techniques, such as generated and self-chosen passwords, allowing for the ranking of memorability versus threat sensitivity.

Abstract

Authentication solutions are the key design, architectural, and implementation decisions that implement authentication security controls. An example is a password-based authentication solution. While researchers often examine authentication quality, existing approaches do not distinguish which effects on quality stem from which aspect of authentication. For example, multi-factor authentication solutions tend to be less usable because they combine multiple authenticators, whereas passkeys are more secure than passwords because of properties inherent to the authenticator itself. This paper presents AQUA, a modular quality modeling framework for authentication solutions. AQUA's core idea is to decompose authentication into four interrelated concepts, enabling modular specification of authentication quality and tracing quality effects back to their source. We demonstrate AQUA with initial definitional quality models that address the levels of authenticators, authentication techniques, and authentication solutions. We further illustrate the interrelations between these concepts through concrete examples and a usability metric, showing how quality propagates across the concepts and ultimately affects the overall quality of an authentication solution. Our results provide a foundation for future work, including designing assessment and prediction models for authentication solutions and automated quality assessments.

Sources

Related papers