Reputation Management for Distributed Service-Oriented Architectures

Abstract

Nowadays, several network applications require that\ud consumer nodes acquire distributed services from unknown service providers on the Internet. The main goal of consumer nodes is the selection of the best services among the huge multitude provided\ud by the network. As basic criteria for this choice, service cost and Quality-of-Service (QoS) can be considered, provided that the underlying Service-Oriented Architecture (SOA) be augmented in\ud order to support the declaration of this information. The correct behavior of such new SOA platforms, however, will depend on the presence of some mechanisms that allow consumer nodes to\ud evaluate trustworthiness of service providers. This work proposes a new methodology for discouraging antisocial behaviors of malicious service providers that declare QoS higher than the real one. The architecture is fully distributed over the network and\ud emulates a decentralized hierarchical trusting authority capable of managing reputation values and of providing correct QoS assessments

Smart Assistance for Students and People Living in a Campus

“…We also noticed that, in some cases, out-of-scope questions could be asked by untrustworthy users, that are interested on testing/stressing the system by providing unpredictable inputs. To overcome this limitation, a trust management mechanism could be adopted [6], [2].…”

Twitter analysis for real-time malware discovery

“…Finally, we want to investigate the adoption of more sophisticated techniques to estimate the trustworthy of the users and, consequently of their feedbacks. To this aim, we plan to provide the system with a reputation management algorithm, such as those reported in [19], [20], in order to ensure the robustness of reputable systems against attacks on their security [21], [22].…”

Towards Trust-Aware and Self-adaptive Systems

“…As an example of the first situation, Conner et al [2] present a feedback-based reputation framework to help service providers to determine trust in incoming requests from clients. As an example of the second approach, Crapanzano et al [3] propose a hierarchical architecture for SOA where there is a so-called super node overlay that acts as a trusting authority when a service consumer looks for a service provider.…”

“…Once the developer has annotated the classes with both Kevoree and trust information, maven 2 is used to call both the Kevoree and the trust frameworks. These frameworks generate code according to the annotation information passed to them by the Maven Kevoree and Maven Trust plugins 3 .…”

“…http://maven.apache.org3 The Maven plugin for Kevoree already exists and does not need to be modified. We just introduce the plugin for the trust framework 4.…”