A Kernel-Based Communication Fault Injector for Dependability Testing of Distributed Systems

Drebes, Roberto Jung; Jacques-Silva, Gabriela; Trindade, Joana Matos Fonseca da; Weber, Taisy Silva

doi:10.1007/11678779_13

Cited by 14 publications

(23 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Figure 2 shows the textual representation of the WTLS attack tree according to step 3 of our methodology. For our experiments we used Firmament [2] fault injector, used in previous work [12]. Firmament is capable of performing the following actions: intercept, corrupt, drop, delay, duplicate, store, and set.…”

Section: Attack Modelingmentioning

confidence: 99%

“…In our case, a trigger is an external event, such as the reception of a specific messagecorresponds to second attack pattern element. The condition may be established in terms of the message field content, or state variables [2] -it can be assigned to third attack pattern element. Considering the defined attacker capabilities, we can establish the actions that the injector can perform: intercept, corrupt, drop, duplicate, delay, and impersonate -it can be also assigned to third attack pattern element.…”

Section: • Step 5: Refine Attacks Scenariosmentioning

confidence: 99%

“…This technique allows deliberate introduction of faults and errors into a software system either at compile-time or during runtime. SWIFI is a powerful technique that has been used in various application domains, including communications protocols [1], [2]. Conventional communication fault injectors generally emulate low-level hardware faults, such as link or processor failures.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Security Protocol Testing Using Attack Trees

Morais

Martins²,

Cavalli³

et al. 2009

2009 International Conference on Computational Science and Engineering

View full text Add to dashboard Cite

In this paper we present an attack injection approach for security protocol testing aiming at vulnerability detection. We use attack tree model to describe known attacks and derive injection test scenarios to test the security properties of the protocol under evaluation. The test scenarios are converted to a specific fault injector script after performing some transformations. The attacker is emulated using a fault injector. This model based approach facilitates the reusability and maintainability of the generated injection attacks as well as the generation of fault injectors scripts. The approach is applied to an existing mobile security protocol. We performed experiments with truncation and DoS attacks; results show good precision and efficiency in the injection method.

show abstract

Section: Attack Modelingmentioning

confidence: 99%

Section: • Step 5: Refine Attacks Scenariosmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Security Protocol Testing Using Attack Trees

Morais

Martins²,

Cavalli³

et al. 2009

2009 International Conference on Computational Science and Engineering

View full text Add to dashboard Cite

show abstract

“…FIAT [15] tests the dependability of real-time distributed systems by injecting events into the source code at the compile-time. NIST Net [16], Dummynet [17], and ComFIRM [18] also rely upon packet capture for event-injection but support neither distributed nor time-based injection capabilities. Cesium [19] is a simulation tool that allows events to be injected into the protocol at runtime.…”

Section: Related Workmentioning

confidence: 99%

Transparent Network Protocol Testing and Evaluation

Wang

Agham

Munishwar

et al. 2013

2013 22nd International Conference on Computer Communication and Networks (ICCCN)

View full text Add to dashboard Cite

Abstract-Network protocol developers typically go through a tedious and error-prone process of testing and debugging their protocol implementation for various settings. They perform a number of tasks manually such as configuration of numerous network settings, controlled reproduction of unexpected protocol behavior, and traffic capture and analysis. We present a Protocol Testing and Evaluation System (PTES) to assist developers in transparently testing their protocol implementations. PTES enables a protocol developer to construct and execute various controlled and repeatable testing scenarios. The developer can use simple iptables-like rules to specify various local and distributed network events and actions. During protocol execution, PTES triggers these events and actions in a coordinated manner and records the protocol responses to these events which can later be examined by the developer. We present the design and implementation of three variants of PTES for native, simulated, and emulated platforms for both wired and wireless networks. We demonstrate the utility of PTES by automating the testing of TCP/IP and Optimized Link State Routing (OLSR) protocols.

show abstract

“…Some work also address communication faults in parallel or distributed systems [3,8,9,14], usually aiming at transmission errors in the transport or lower layers. In this paper, we also consider networked systems, but address the injection of interaction faults -i.e.…”

Section: Introductionmentioning

confidence: 99%

Injecting Inconsistent Values Caused by Interaction Faults for Experimental Dependability Evaluation

Nassu

Uehara

Nanya

2008

2008 Seventh European Dependable Computing Conference

View full text Add to dashboard Cite

Interaction faults caused by a flawed external system designed by a third party are a major issue faced by interconnected systems. Fault injection is a valuable tool for evaluating the dependability of such scenarios. Several types of errors caused by interaction faults may be injected by existing approaches, even though previous work focused on other types of faults, such as hardware and software faults. This is not the case of inconsistent values -data that is correctly received and syntactically correct, but inconsistent with what it should represent. In this paper, we propose a novel methodology to inject inconsistent values caused by interaction faults, including hand-defined, random and semantically significant values. We also describe a simulation tool which implements the proposed mechanism to aid dependability evaluation in a system that uses the Universal Plug and Play standard to communicate.

show abstract

A Kernel-Based Communication Fault Injector for Dependability Testing of Distributed Systems

Cited by 14 publications

References 7 publications

Security Protocol Testing Using Attack Trees

Security Protocol Testing Using Attack Trees

Transparent Network Protocol Testing and Evaluation

Injecting Inconsistent Values Caused by Interaction Faults for Experimental Dependability Evaluation

Contact Info

Product

Resources

About