Detecting occasional reputation attacks on cloud services

Talal H. Noor, Quan Z. Sheng, Abdullah Alfazi

Research output: Chapter in Book/Report/Conference proceedingConference proceeding contribution

2 Citations (Scopus)


Cloud service consumers' feedback is a good source to assess the trustworthiness of cloud services. However, it is not unusual that a trust management system experiences malicious behaviors from its users. Although several techniques have been proposed to address trust management in cloud environments, the issue of how to detect occasional reputation attacks on cloud services is still largely overlooked. In this paper, we introduce an occasional attacks detection model that recognizes misleading trust feedbacks from occasional collusion and Sybil attacks and adjusts trust results for cloud services that have been affected by these malicious behaviors. We have collected a large collection of consumer's trust feedbacks given on real-world cloud services (over ten thousand records) to evaluate and demonstrate the applicability of our approach and show the capability of detecting such malicious behaviors.

Original languageEnglish
Title of host publicationWeb Engineering
Subtitle of host publication13th International Conference, ICWE 2013, Aalborg, Denmark, July 8-12, 2013. Proceedings
EditorsFlorian Daniel, Peter Dolog, Qing Li
Place of PublicationHeidelberg
PublisherSpringer, Springer Nature
Number of pages8
ISBN (Print)9783642391996
Publication statusPublished - 2013
Externally publishedYes
Event13th International Conference on Web Engineering, ICWE 2013 - Aalborg, Denmark
Duration: 8 Jul 201312 Jul 2013

Publication series

NameLecture Notes in Computer Science
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349


Other13th International Conference on Web Engineering, ICWE 2013


  • Attacks Detection
  • Cloud Computing
  • Occasional Attacks
  • Trust Management

Fingerprint Dive into the research topics of 'Detecting occasional reputation attacks on cloud services'. Together they form a unique fingerprint.

Cite this