Mathematical Problems in Engineering
Volume 2015 (2015), Article ID 238245, 15 pages
http://dx.doi.org/10.1155/2015/238245

Research Article

A Reputation-Based Identity Management Model for Cloud Computing

Lifa Wu,¹ Shengli Zhou,1,2 Zhenji Zhou,¹ Zheng Hong,¹ and Kangyu Huang¹

¹College of Command Information System, PLAUST, Nanjing 210007, China
²Information Department, Zhejiang Police College, Hangzhou 310000, China

Received 21 March 2015; Revised 27 May 2015; Accepted 30 May 2015

Academic Editor: Bao Rong Chang

Copyright © 2015 Lifa Wu et al. This is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.

Abstract.

In the field of cloud computing, most research on identity management has concentrated on protecting user data. However, users typically leave a trail when they access cloud services, and the resulting user traceability can potentially lead to the leakage of sensitive user information. Meanwhile, malicious users can do harm to cloud providers through the use of pseudonyms. To solve these problems, we introduce a reputation mechanism and design a reputation-based identity management model for cloud computing. In the model, pseudonyms are generated based on a reputation signature so as to guarantee the untraceability of pseudonyms, and a mechanism that calculates user reputation is proposed, which helps cloud service providers to identify malicious users. Analysis verifies that the model can ensure that users access cloud services anonymously and that cloud providers assess the credibility of users effectively without violating user privacy.

1. Introduction

Cloud computing is a computing model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and other services) that can be rapidly provisioned and released with minimal management effort or cloud service provider (CSP) interaction [1]. Large numbers of users may simultaneously engage in cloud computing services, making the “multitenant” feature an important property of cloud computing according to the Cloud Security Alliance (CSA) [2]. However, the multitenant property brings the following new problems:

(i)Privacy leaks because of external user data: in an open environment, users must be authenticated to access cloud services. If users employ their actual names (or fixed usernames) to log in, sensitive information such as login names or even long-term behavior may be revealed by data mining or other techniques and used illegally by the CSP.(ii)Management problems caused by an excessive number of tenants: to preserve privacy, users must employ different pseudonyms to access each cloud computing session. In this case, it is difficult for users to recall a large number of pseudonyms and passwords. Meanwhile single-use pseudonyms make no contribution to the development of a user’s reputation.(iii)Security threats to the CSP caused by multiple tenants: by accessing cloud services, malicious users may take the opportunity to attack the CSP through activities such as stealing data, performing vulnerability scanning, and launching denial of service (DoS) attacks. In particular, if allowed to log in by a pseudonym, malicious users can launch whitewash attacks, where the malicious user can continue to visit the CSP normally after an attack or initiate another attack by creating a new pseudonym.

Considering the above problems, traditional identity management mechanisms that store user identities in a database directly are no longer applicable [3]. In this paper, we design a new identity management model based on user reputation, which is herein denoted as reputation-based identity management (RIM). The main contributions of RIM are listed as follows:

(i)Anonymous user access: in RIM, we design a method in which each user takes a different pseudonym for each session when accessing cloud services. No link between a user identity and a corresponding pseudonym is provided, and no link is provided between the pseudonyms of a single user. Pseudonym usage does not affect user attestation, and it decreases the input of private user information, rendering it impossible for tenants to spy on each other.(ii)User attestation: in our model, users firstly register with an identity provider (IdP), which provides the user with a formal identity certificate. The identity certificate is the basis for the user to prove their legitimate status to the CSP.(iii)Reputation attestation: RIM records and determines user reputations as user activities accumulate with access to successive cloud computing sessions and provides proof of the reputation. The proof assures the credibility of the reputation, ensuring that the reputation indeed belongs to its owner. The proof also guarantees nonrepudiation; that is, a user cannot deny the reputation assigned to them. As such, the proof ensures unforgeability. Users cannot promote their reputation without the authorization of the IdP. The introduction of a reputation does not affect the anonymity of users.

The remainder of this paper is organized as follows. Section 2 describes related work. Section 3 introduces the background and technology of cloud computing along with identity management. Section 4 introduces the proposed RIM and describes its design and realization. Section 5 analyzes the correctness and security of our model. Finally, the last section concludes the paper and proposes future work.

2. Related Work

The focus of identity management for cloud computing is user privacy. In [4], the authors proposed an approach to preserve the privacy of users based on zero-knowledge proof protocols and semantic matching techniques. The approach also enhanced the interoperability across multiple domains. Although the study realized the goal of concealing user identities, the CSP could still obtain sensitive information through data mining techniques because user identities were consistent throughout the entire process. In [5], the authors proposed an entity-centric approach for identity management in cloud computing. The approach was based on personally identifiable information (PII) and on anonymous identification to mediate interactions between users and cloud services. Although the identification was anonymous, the PII released privacy related information. In [6], the authors took advantage of attribute-based encryption and signature technology to conceal user identities in cloud computing. However, because users must employ a single unchanging certificate to obtain authentication from the CSP, an attacker may ascertain a user’s identity easily through the static certificate. In [7], the authors improved the approach proposed in [4], where the registry center was not required to be online at all times. However, the improved approach had the same disadvantages with respect to user privacy protection as the original approach. In [8, 9], the authors designed and introduced a method that integrated blind signature and hash chain techniques to protect user privacy in cloud computing. However, in every session, users employ the same pseudonym to log in, which results in linkability between different sessions. Although the above studies achieve the goal of user identity concealment, the successive behaviors of individual users can be associated. Thus, through analyzing user behaviors, the CSP can potentially compromise user privacy. In [10], the authors proposed a method for anonymity using group digital signature technology. Because this method introduced no correlation between user signatures, this method is an improvement over the aforementioned methods. However, the use of group digital signature technology forbids members from joining and leaving a group dynamically, which conflicts with the openness of cloud computing.

In this paper, we propose an approach that achieves user identity anonymity. Moreover, by this approach, the CSP is unable to link user behavior to user identity. While the anonymity of identity protects user privacy, it tends to enable CSP attack by malicious users because the CSP is unable to trace the users involved in the attack. Therefore, our approach introduces trust management to address the shortcomings of identity anonymity. The approach determines user reputations and binds the reputation to user identity. The CSP utilizes user reputation to distinguish malicious users and to reduce the threat of attack by malicious users [11].

Previous reputation research has focused on peer to peer (P2P) systems, which has been developed into various systems, for example, the EigenTrust [12], the PeerTrust [13], and the PowerTrust [14] systems. Along with the development of electronic business, reputation research has had a service oriented focus, where the reputation of service providers has been evaluated to protect consumers. In [15, 16], reputation was employed as a means of choosing service providers. In cloud computing, most research has focused on protecting the CSP, such as what was done in [17, 18]. However, the use of a reputation model to manage users in cloud computing, such as that employed in this paper, has not been the subject of previous research. In [19], the authors designed an identity management model for a noncloud computing environment. The model supposed that users must be previously registered, which conflicts with the required openness of cloud computing. In [20, 21], the authors designed a reputation-based identity management model that used online systems for applications in, for example, electronic business and forums. The online system must recognize user identities or unique identifiers to accumulate reputation data. However, tracking user identities tends to leak user information, which threatens privacy. This is why these approaches cannot be applied to cloud computing. Our proposed RIM introduces reputation to manage users and simultaneously protects user privacy, which has not been investigated by other researchers.

User privacy protection requires a user identity to be anonymous such that it cannot be tracked. However, the determination of reputation must confirm user identity and track user transaction history. Therefore, reputation management and identity anonymity appear to be contradictory [22]. In [22], the authors alleviated this contradiction and designed an anonymous reputation system in a P2P environment using electronic cash technology to provide feedback to users according to behavior. However, according to this approach, the amount of feedback one user gives to another is restricted by the quantity of electronic coins in the former user’s possession. A user with no electronic coins is therefore barred from involvement in the transaction. As such, this method contradicts with the openness of cloud computing. In [23], the authors used blind signature technology to achieve a reputation-based identity management approach in the C-S mode. This approach provides the service provider with user reputations while guaranteeing user anonymity. However, under this approach, a service provider can confirm that orders derive from the same user and accumulate the history of user actions, resulting in the potential violation of user privacy. In [24], authors achieved an anonymous reputation system based on zero-knowledge authentication and digital signature technology. However, [4] the sessions between the user and service provider under this approach are linkable, enabling service providers to violate user privacy. From the above analysis, we can see that these last two examples [25] manage to provide user reputation only by divulging user identity. Our RIM overcomes these shortcomings by determining user reputation while ensuring that user identity and pseudonyms are unlinkable.

3. Technology Background

3.1. Cloud Computing Architecture

Cloud computing provides three main service delivery models to the public, including the following [2]:

(i)Software as a Service (SaaS): this is a software delivery model in which software and its associated data are hosted in the cloud and are typically accessed by users using a thin client.(ii)Platform as a Service (PaaS): this is the delivery of a computing platform and solution stack as a service, which provides all the facilities required to support the complete life cycle of building and delivering web applications and services from the Internet.(iii)Infrastructure as a Service (IaaS): this delivers computer infrastructure (typically a platform virtualization environment) as a service, along with raw storage and networks. Rather than purchasing servers, software, data-center space, or network equipment, clients purchase the resources as a fully outsourced service.

Based on the above approach, a number of similar abstract service models have been recently promoted, such as Hardware as a Service (HaaS), Data as a Service (DaaS), and Communication as a Service (CaaS). Cloud computing management services ensure the reliability, availability, and security of core services. Figure 1 [26, 27] illustrates the basic service architecture of cloud computing.

Figure 1: Cloud services architecture.

Cloud identity management takes charge of identity management throughout the entire cloud services stack. Identity management can be divided into three categories [28]: isolated user identity model, federated user identity model, and centralized user identity model, which are defined as follows:

(i)Isolated user identity model: in this model, the service provider acts as both credential provider and identifier provider to their clients. A user obtains separate unique identifiers from each service/identifier provider transacted with.(ii)Federated user identity model: this can be defined as the set of agreements, standards, and technologies that enable a group of service providers to recognize user identifiers and entitlements from other service providers within a federated domain.(iii)Centralized user identity model: this model employs a single identifier and credential provider that is used by all service providers to provide identifiers and credentials to users.

In the centralized user identity model, the job of identity management has been taken over by an identity provider from the service provider. This reduces the burden of the service provider and also reduces the number of certificates required by users to hold. In addition, the centralized user identity model facilitates the delivery of the identity management service from the CSP to the users. In an identity provider management domain, users first obtain a formal certificate and then access cloud services in the same domain using this certificate. This property makes the centralized user identity model suitable for cloud computing, and, therefore, we employ a centralized model in our design, as shown in Figure 2.

Figure 2: Centralized user identity model in cloud computing.

3.2. Basic Technology

We introduce identity-based signature, blind signature, and zero-knowledge authentication technology to implement RIM.

The identity-based signature was proposed by Shamir [29] in 1984. Here, a user’s identity is first disclosed as a public key and then used to generate a private key. In [29], the authors designed a conceptual model but did not provide for any real implementation. Since then, studies of the identity-based signature have been conducted, but no efficient and provable signature scheme was concluded until Boneh et al. [30, 31] promoted an identity-based encryption scheme. Identity-based signature comprises four stages: setup, private key extraction, signature, and verification. Using an identity as a public key has a natural legitimacy, which can simplify the process of key distribution.

The concept of blind signature was suggested by Chaum [32]. The approach ensures that the signer does not know the specific content of the message and that the message owner can obtain the signature of the message. Blind signature consists of three operations: blinding, signing, and blindness removal. Blind signature has many characteristics conducive to protecting user privacy such as blindness, where the signer does not know the specific content of the message to be signed and untraceability, where, if a signature is leaked, the signer has no idea of when and by whom the message was signed.

Zero-knowledge proof authentication technology refers to a prover’s assurance of ownership of some secret information, without revealing any useful knowledge about the secret information to the verifier. Well-known zero-knowledge authentication schemes mainly include the Feige-Fiat-Shamir [33] scheme, the Guillou-Quisquater [34] scheme, and the Schnorr [35] scheme.

The proposed RIM achieves an identity management model that is suitable for cloud computing by employing methods related to the above techniques that are most suitable for specific application scenarios. In Section 4.3, we give a detailed exposition of our design.

4. Model Design and Implementation

In this section we firstly give some assumptions for RIM and then explain the detailed implementation of the model.

4.1. Assumptions

We must make some reasonable assumptions to ensure proper RIM functionality. Firstly, we assume the existence of an independent arbitration agency whose function is similar to a governmental authority that can ensure user privacy while simultaneously providing a secure source of anonymous user information under very specific circumstances. As such, the agency proposed herein is different from a trusted third party in an ordinary sense. The agency need not have a continual online presence. Moreover, the agency does not collude with other users, and user information is protected from malicious users. Because cloud services are open to the public as a paid service, it is necessary to reveal anonymous user information when a CSP suffers an attack or has economic disputes with users. Therefore, RIM must be able to identify anonymous users to address these specific problems. If a CSP seeks anonymous information, it must provide a range of certificates and follow prescribed security protocols to ensure that the application submitted is legitimate.

Another important assumption is that the communication channel in RIM is secure. SSL and IPSec protocols can be used to ensure the security of the channel.

4.2. Model Design

Four roles are managed in RIM: User, CSP, IdP, and deanonymizing authority (DA), which are defined as follows:

(i)User: the consumer of cloud services who requests identity anonymity and benefits from the service.(ii)CSP: the service provider who, after the transaction between the User and CSP, provides feedback regarding the transaction.(iii)IdP: the service provider who not only provides registration services to the User but also determines the User reputation, which is indicative of the degree of trust, based on the feedback obtained from the CSP. The IdP issues the User reputation certificate.(iv)DA: an authority that can reveal User pseudonyms and provide User identity-related information to the CSP.

RIM has five stages, namely, Environment Initialization, User Registration, Identity Authentication, Reputation Computation, and Pseudonym Disclosure.

In the Environment Initialization stage, RIM first creates the public parameters of the IdP, DA, and CSP. It then generates the public and private keys used for signatures. The operations of key generation are as follows: is the security parameter, denotes the public key, and denotes the private key. The following describes the probabilistic polynomial time algorithm:

(i): it is a key-generation algorithm that takes as the input and outputs a pair of public and secret keys used by the IdP to sign the identity certificate.(ii): given the security parameter , it creates a pair of keys which is used by the IdP to generate a blind signature.(iii): it outputs a pair of keys which is used by the CSP to create a feedback certificate.(iv): it gives the DA a pair of keys which is used to encrypt and decrypt User identities.

Keys and can be combined into a single pair. However, in such a situation, if the keys are disclosed, the IdP will collapse. When they are separated, if one pair of keys is compromised, for example, if the blind signature key is compromised, only the credibility of the reputation is affected while the identity certificate remains valid. Owing to security considerations, we maintain these two key pairs as separate.

The Registration operation and Verification operation contained in the User Registration stage are defined as follows:

(i)Registration: the User initiates the operation to register with the IdP. The User obtains an identity () as the input and then receives the identity certificate , reputation (), and reputation certificate . Here, is the initial reputation value for new users given by the IdP.(ii)Verification: the operation is employed by the User to authenticate , , and . This operation takes the IdP public key as one of the inputs, which will confirm the legitimate source of these certificates. If verified, 1 will be returned as the result; otherwise, will be returned.

The first time a User enters the cloud service system, the User must register with the IdP using their own identity. The IdP will determine whether the identity is redundant or on the blacklist. If the answer is no, the verification is passed. The IdP gives the User an initial reputation value and issues an identity certificate and reputation certificate. The identity that registered to the IdP is known to the public. It can be a URL or e-mail address associated with the User. The public identity carries less privacy and is easily verified by the IdP. Because of the openness of cloud services, the rules for accessing cloud services cannot be overly strict. In RIM, all users that meet the basic safety requirements are allowed access. After Registration, the Verification operation is performed to verify the identity certificate and the reputation certificate. The above processes are illustrated in Step of Figure 3(a).

(a)

(b)

Figure 3: Schematic of the anonymous access and reputation update process.

After the User has a recognizable valid identity, access is granted to the CSP using the pseudonym generated according to this valid identity, and the CSP will authenticate the pseudonym. The Identity Authentication stage includes the Pseudonym Generation operation and Authentication operation shown in steps and of Figure 3(a), which are described as follows:

(i)Pseudonym Generation: taking , the User identity certificate , and as the inputs, the operation outputs the User pseudonym , which is the only identification presented to the CSP.(ii)Authentication: the operation is used to authenticate the User identity through by the CSP. This operation is also used to confirm the credibility of the User reputation.

The Pseudonym Generation operation encrypts Id using the public key provided by the DA. As such, if a dispute arises between the User and the CSP, RIM would decrypt with the private key provided by the DA to restore the User Id. The Authentication operation applies the -protocol to conduct the authentication. During the process, the CSP can extract , , and but not the User Id.

After the transaction between the User and the CSP, RIM enters the Reputation Computation stage, where the User rep is updated on the basis of feedback provided by the CSP. This stage includes a series of operations including the Reputation Backfeeding operation, Blinding operation, Applying for Reputation Update operation, Blind signing operation, and Reputation Update Confirmation operation, which are defined as follows:

(i)Reputation Backfeeding: the CSP calls and provides reputation feedback and its certificate according to the performance of . The guarantees that is from the CSP.(ii)Blinding: randomly selects the blind factor as the input of the operation to obtain the blinded value Nonce_blind.(iii)Applying for Reputation Update: given the inputs , calls to apply for reputation updating. The IdP verifies the reputation feedback based on and . A successful operation returns 1; otherwise, it returns .(iv)Blind Signing: the IdP calls to generate the blind signature of the value Nonce_blind.(v)Reputation Update Confirmation: the User removes the blindness of and obtains the certificate of Nonce. Then, the User calls to submit the request for confirming the update of reputation to the IdP. If the IdP successfully updates the User rep, it returns 1; otherwise, it returns .

The CSP provides feedback to using the Reputation Backfeeding operation, as illustrated by Step in Figure 3(b). The Applying for Reputation Update Confirmation operation submits the reputation feedback and a blinded random value to the IdP and expects that the IdP will update . This operation is illustrated by Step in Figure 3(b). The IdP verifies the feedback and determines that it is valid. However, the IdP cannot determine for whom the feedback is designated because the IdP cannot track the feedback to the User . The IdP uses the Blind Signing operation to sign and gives the result back to , as illustrated by Step in Figure 3(b). Because the User generates directly, the User can locate their own . The User obtains through and then removes the blindness of to obtain . The User subsequently calls the Reputation Update Confirmation operation and submits to the IdP to confirm the updating of rep, which is illustrated by Step in Figure 3(b). The IdP verifies , and, if passed, the value of is updated. The IdP cannot link to , which is why the blind signature is introduced. This method ensures that, even in the case of collusion between the IdP and CSP, the IdP cannot obtain the User through .

The aforementioned processes address the entire process of new user access to cloud services, including User Registration, accessing services, and reputation update. The User who is already registered must first call the Reputation Withdrawal operation to acquire a value for from the IdP and then follow all subsequent operations, as the aforementioned. The Reputation Withdrawal operation is illustrated in Figure 4(a), which is described as follows:

(i)Reputation Withdrawal: the User acquires and by the operation using its own .

(a)

(b)

Figure 4: Schematic of the standard access process and Pseudonym Disclosure.

The last stage is the Pseudonym Disclosure stage. If the User has done harm to the CSP, the CSP must gain access to the User . This stage includes the Anonymity Removal operation and the Identity Mapping operation, which are described as follows:

(i)Anonymity Removal: when the operation is called, the DA opens using its private key . The output of this operation is not the User itself but , which is generated by the IdP, where is one of the public parameters.(ii)Identity Mapping: IdP calls to map to the User and then resolves the disputes offline.

The CSP submits a malicious behavior report for the User and pseudonym to the DA and applies for opening a pseudonym, as illustrated in Step in Figure 4(b). The DA uses the Anonymity Removal operation to open and obtains . The DA submits to the IdP. Then the IdP calls the Identity Mapping operation and retrieves the User , as illustrated by Step in Figure 4(b). Therefore, for security considerations, the DA does not recover the directly. This is one of the methods that ensure user privacy and prevent the misuse of a user’s identity.

The above provides an overview of RIM. The following provides a concrete realization of our model.

4.3. RIM Realization

In this section we provide a description of the concrete realization of RIM based on Hidden Identity-Based Signaturesproposed by Kiayias and Zhou [36]. Hidden Identity-Based Signatures meet user requirements for anonymity in a cloud computing environment, but they do not satisfy the need for a unique user pseudonym for each session. We therefore extended Hidden Identity-Based Signatures by introducing reputation and blind signature to fulfill the requirements mentioned above. In RIM, we achieve blind signature using the Schnorr scheme [25]. The public parameters discussed previously [25, 36] are identical, so the RIM is made more comprehensive by combining the two techniques.

In the Environment Initialization stage, we generate public parameters , where and are cyclic groups of prime order , is a generator for and , is a bilinear map, , and . is selected from randomly. is a hash function, . The operation randomly selects and computes , , where the public and private key pairs are given as , . Similarly, the operation generates the key pair , , where and . generates the key pair , for feedback signature using the same method described above. The key pair generation of is more complicated. It randomly selects , and , resulting in , which provides the key pair , . After the keys are generated, RIM publishes the public keys and keeps the private keys secret.

In the User Registration stage, the IdP provides the User with the identity certificate, reputation, and reputation certificate. We introduce the technology of short signatures [37] to issue these certificates. The IdP randomly selects and then issues identity certificate and reputation certificate , noting that and denote the identifier and reputation belonging to the User. After that, the IdP gives the User a triple .

The User verifies these certificates using the IdP public key. When the equation holds, the User accepts the identity certificate. In the same way, the User verifies the reputation certificate. If the two certificates are both valid, the operation returns 1. If either certificate is invalid, both certificates are discarded.

The Pseudonym Generation and Authentication operations in the Identity Authentication stage are usually carried out together in practice. In this paper, we extend the method introduced in [36] to authenticate the User identity, User identity certificate, and the link between the User identity and identity certificate. Our approach requires verification that the reputation generated from the pseudonym belongs to the User we have just authenticated. The specific process is described as follows:

(i) The User employs linear encryption [37] to commit in . It satisfies the constraints , , , where and are randomly selected: .

(ii) The User commits in (); that is, and , where and are randomly selected: .

(iii) The User authenticates their identity using the zero-knowledge proof technique [35], as described in Figure 5. Finally, if the equation holds, the User is assured of possessing a legitimate identity, although the CSP would have no knowledge of that identity.

Figure 5

(iv) The process of authenticating the User identity certificate is described in Figure 6. If the equations hold, the User is assured of possessing a legitimate identity certificate, although the CSP would have no knowledge of that certificate.

Figure 6

(v) It must also be verified that the identity and the identity certificates belong to the same User. The verification process is described in Figure 7. If the equations are true, the identity is bound to the identity certificate.

Figure 7

(vi) Moreover, the legitimacy of the reputation and that the reputation belongs to the User must also be verified. The reputation is open to the public, so it is authenticated using the IdP public key. When verifying that the reputation belongs to the User, the User identity is hidden. To this end, a secret message is selected, and ownership of the reputation certificate can be verified only if the User has the secret message, as described in Figure 8(a). Linkability between the reputation certificate and the User identity is then verified, as described in Figure 8(b). If the equations hold, the reputation and reputation certificate are concluded to belong to the User.

(a)

(b)

Figure 8

(vii) Finally, we verify that the encrypted identity certificate is from the IdP according to the encrypted identity.

We assume that

where, if , the abovementioned conclusion is verified because if the IdP private key is input, we obtain the output .

Thus far, the legitimacy of the , , , and has been verified. Moreover, the linkability between the and the and has been verified. Though the has been encrypted, it can be verified that the derives from the IdP.

Together with the verification of the legitimacy of the reputation, all of the above comprise the operation . Because the reputation need not be secret, the reputation can be authenticated simply by inputting the IdP public key.

Next, we address the operation . Here, the pseudonym is just the random challenge used by the CSP for authenticating the User. meets cloud computing security requirements. The security analysis will be conducted in the next section.

Our implementation of the Reputation Computation stage is described as follows:

(i)Reputation Withdrawal: the operation returns the reputation certificate, which is signed by the IdP. The specific implementation of the reputation certificate is equivalent to that of the identity certificate.(ii)Reputation Backfeeding: we continue to use the short signature [38] to sign the feedback given by the CSP; that is, , where is randomly selected: .(iii)Blinding: this operation is performed by the User and the IdP. The IdP possesses the key pair , where . The IdP randomly selects and computes . Then, obtains from the IdP and selects a random number that is to be signed. computes , , and , where . The User assigns as the blind signature of ; that is, .(iv)Applying for Reputation Update. The IdP verifies the reputation feedback, which is signed by the CSP. If the equation holds, we conclude that the verification has passed.(v)Blind Signing: the IdP computes and . This is also the process of signing the blind random number . The IdP does not know the plaintext of throughout the process.(vi)Reputation Update Confirmation: the User removes the blindness of (i.e., ) through computing . Then, the pair is obtained, which is the signature of denoted by . Finally, the User calls to confirm the update of the reputation. The IdP determines if the equation holds. If so, the IdP then examines the equation . When both equations hold, the IdP concludes that the signature is valid.

After verifying the blind signature, the IdP performs the actual reputation updating operation. We introduce the feedback based reputation calculation method [39] to estimate the User reputation. Here, three factors determine the total value of User trustworthiness, that is, , where represents the new reputation feedback the CSP provides after the transaction, is the history feedback provided by the previously accessed CSP, and is the overall reputation the User had prior to the current transaction. After accessing the service, the User reputation is calculated by . To regulate the value of the reputation, we let be normalized to values in . denote the new feedback weight, the updated history feedback weight, and the updated overall reputation weight prior to the current transaction, respectively. All the weights have values in and satisfy the constraint . The details have been described in [39].

In the Pseudonym Disclosure stage, the DA and IdP decrypt the User pseudonym and then restore the User Id. The details of the two operations are as follows:

(i)Anonymity Removal: the DA decrypts the secret information using the secret key in the possession of the DA to restore ; that is, .(ii)Identity Mapping: the IdP maps to the User Id using the internal mapping table that is built at the beginning.

Through the abovementioned operations, we can deliver an identity management service. The User generates a pseudonym using this service and then employs the pseudonym as the identity for accessing cloud services without exposing any real identity information. The User reputation, within a certain range, indicates to what extent the CSP can trust the user, based on the possibility that the User may carry out malicious activities.

5. Model Analysis

In this section, we verify the correctness and provide a detailed security analysis of the proposed model.

5.1. Correctness of the Model

The correctness of the model includes User Registration correctness, Reputation Calculation accuracy, Identity Authentication correctness, and Pseudonym Disclosure correctness.

Definition 1. User Registration correctness is described as follows. If the identity certificate and the reputation certificate can be verified with a probability of 1, then one concludes that the User Registration is correct. This is given by the following:

Theorem 2. RIM User Registration is correct.

Proof. If the above probability is 1, then the output of each operation must be correct, and the identity certificate and the reputation certificate can pass the verification using the public keys in the possession of the IdP. The validity of the identity certificate was verified in [38], and we need only to verify the validity of the reputation certificate. The following formula confirms that , verifying the reputation certificate is valid. Consider

Definition 3. Identity Authentication correctness is described as follows. The CSP authenticates the User through the User pseudonym . If all the operations return correct outputs with a probability of 1, we conclude that the Identity Authentication is correct. This is given by the following:

Theorem 4. RIM Identity Authentication is correct.

Proof. The CSP must authenticate the User identity, the validity of the identity certificate, the linkability of the identity and identity certificate, the validity of the reputation certificate, and the linkability of the identity and reputation certificate. All of the above have been proven in [25] with the exception of the linkability of the and reputation certificate. Therefore, we only verify here the linkability of the and reputation certificate. The verification follows the same approach as that of formula but is conducted by the CSP. Verifying the linkability of the and reputation certificate follows according to formula , which indicates that the User owns the reputation certificate, and formulas and , which verify that the User identity is linked with reputation certificate. Consider

The Reputation Computation accuracy involves two aspects: the correctness of the operations such as reputation acquisition, reputation feedback, and reputation update; and the fact that the reputation evaluation algorithm can accurately calculate the user degree of trustworthiness. The accuracy of the evaluation algorithm has been verified in [39]. Therefore, in this paper, we only define the correctness of the operations.

Definition 5. Reputation Calculation correctness is described as follows. If the reputation-related operations return correct outputs with a probability of 1, one concludes that the Reputation Calculation is correct. This is given by the following:

Theorem 6. RIM Reputation Calculation operations are correct.

Proof. The operation and the subsequent verification steps of the reputation are equivalent to the registration operations. The verification of the reputation feedback is similar to that given in formula . Because the correctness of the registration operations has been proven in Theorems 2 and 4, we here prove only the correctness of the blind signature. Formula removes the blindness of the signature, obtaining the intermediate value . If the equation holds, we conclude that the blind signature is correct. Along with Theorems 2 and 4, the proof verifies the correctness of the reputation operations. One has

Definition 7. Pseudonym Disclosure correctness is described as follows. The DA decrypts the pseudonym to restore the User Id with a probability of 1. This is given by the following:

Theorem 8. RIM Pseudonym Disclosure is correct.

Proof. Operations conducted prior to the Pseudonym Disclosure process have been proven in Theorems 2, 4, and 6. The correctness of decrypt has been proven in [36]. Finally, the IdP queries the mapping table to obtain the User Id. Therefore, we conclude that the Pseudonym Disclosure is correct.

5.2. Security of the Model

5.2.1. Security of Reputation

Before discussing the security of reputation, we assume that the private keys of the IdP, CSP, and User have not been leaked. If the private keys were leaked, the RIM would be open to the public. The data of the IdP are stored in a cloud environment, and the cloud service is open to the public. Therefore, an attacker can obtain an and reputation pair, thereby conducting a plaintext attack by analyzing them. In this paper, we will not consider a situation where an attacker modifies the reputation through the cloud underlying infrastructure, and the attacks are all chosen as plaintext attacks.

Unforgeability of reputation refers to the fact that an unauthorized user has no way of modifying their own or another’s reputation value. If the attacker (or Adversary; ) wishes to modify a reputation value without permission, the must forge a reputation certificate issued by the IdP or a feedback certificate signed by the CSP. Next, we provide a formal definition of reputation unforgeability.

Definition 9. If a probabilistic polynomial-time adversary has the advantage , which is negligible in , then one concludes that the reputation value is unforgeable. The experiment is defined as follows:

(i) is given the public parameters , as described in the Environment Initialization stage. The register random oracle provides with a User identity, reputation value, and reputation certificate. The feedback random oracle provides with reputation feedback and the feedback certificate. The pseudonym random oracle provides with the User pseudonym .(ii)The generates and .(iii)The challenger randomly selects from ; that is, . Then, the challenger calls and to acquire the pair and .(iv)The gives a guess , and if , then output is 1; otherwise, output is 0.

Now, we reduce this to an adversary for the BB signature. Firstly, initializes a hash table for the simulation of the random oracles and that are employed by . If queries or , would resort to . If the query has already been on the table, would return the corresponding value; if not, would sample a or and place it in and return it in the end. When queries a reputation signature included in or , forwards the query to BB-signing oracle and returns the response. After sufficient queries, challenges the challenger using , , or , . extracts the pair () or () and challenges the BB-signing challenger. The BB-signing challenger picks a number in . then returns or to . makes a guess of and gives it to the BB-signing challenger through . If , then not only does have the ability to forge a reputation certificate but also can forge a BB signature. According to the above mentioned method, we reduce to , and we conclude that if the BB signature is secure, then the reputation certificate cannot be forged.

Verifiable Reputation means that the reputation indeed belongs to the authenticated user. If the adversary can forge a pseudonym and the pseudonym can pass verification by the CSP while the DA cannot open the pseudonym or only open it as an unregistered identity, then we conclude that the adversary is successful. This property is guaranteed by Hidden Identity-Based (HIB) Signatures [25].

Definition 10. If a probabilistic polynomial-time adversary has the advantage , which is negligible in , then one concludes that the reputation value is verifiable. The experiment is defined as follows:

(i)The register random oracle provides with a User identity, reputation value, and reputation certificate, and the pseudonym random oracle provides with a User pseudonym . obtains the public parameters as described in the Environment Initialization stage.(ii) generates the pair and and then gives it to the challenger.(iii)The challenger randomly selects from ; that is, . Then, he calls to acquire the pseudonym .(iv) gives a guess of , and if , and hold, and then output is 1; otherwise, output is 0.

Now, we assume that an adversary is against the HIB signature. Using three random oracles, namely, the registration random oracle , the User identity random oracle , and the signature oracle , acquires the User identity, identity certificate, and the signature of a message signed by the User. Moreover, these three random oracles can simulate and . In [36], the random oracle was used for disclosing a pseudonym to perform a cipher text attack. However, in this paper, we assume that the DA is trustworthy. Therefore, we simulate only a plaintext attack. If can disclose a pseudonym, then must be able to break the HIB signature. Now, we begin the process of reducing to . removes the part relevant to reputation from and provided by and then proceeds with the HIB signature process. During the authentication process, we maintain a constant challenge factor . The reputation was included when was generated. By analyzing the -protocol, we know that is randomly selected, so its value does not affect the final result of authentication. Finally, takes as a pseudonym and returns it to . contains the information regarding a User identity. gives a guess of , and if can successfully forge a pseudonym, then can crack the HIB signature with the same probability.

Nonrepudiation means that, under any circumstances, the User must admit that the reputation that has been submitted belongs only to the User, and, therefore, regardless of how low the reputation value, the User can never deny ownership. If the adversary has the ability to forge a pseudonym and the DA opens it to find that it corresponds to a legitimate registered user identity, then we conclude that the adversary is successful.

Definition 11. If a probabilistic polynomial-time adversary has the advantage , which is negligible in , then one concludes that the reputation value has the property of Nonrepudiation. The experiment is defined as follows:

(i) is given the public parameters as described in the Environment Initialization stage. The register random oracle provides with a User identity, reputation value, and reputation certificate. The pseudonym random oracle provides with a User pseudonym .(ii) generates and and then gives it to the challenger.(iii)The challenger randomly selects from ; that is, . Then, the challenger calls to acquire the pseudonym .(iv) gives a guess , and if , and are true, and then output is 1; otherwise, output is 0.

The method that reduces to an adversary for the HIB signature is equivalent to the method used in the analysis of Verifiable Reputation. We therefore omit the reducing process.

5.2.2. Secure Anonymity

In addition to the aforementioned reputation security, it is necessary to consider the security of anonymity. To this end, we assume that the IdP is not safe; namely, its private keys can be leaked. Also, we assume that the IdP and CSP can collude together to compromise anonymity. These assumptions comply with the actual situation, for the IdP and CSP may belong to the same institution. However, in the Reputation Calculation process, we assume that private keys in the possession of the IdP cannot be leaked to the User but can be leaked to the CSP because reputation is used to constrain the User, and the IdP and User are antithetical.

Anonymity security includes the unlinkability not only between pseudonyms (denoted as -unlinkability) but also between a pseudonym and a User (denoted as --unlinkability). -unlinkability includes the unlinkability between the pseudonyms of the same user and the unlinkability between the pseudonyms of different users.

With regard to the probability , if the two pseudonyms and given in Definition 12 are negligible, then we conclude that and are unlinkable.

A number of factors make one pseudonym different from another. Firstly, for different users, their identities are different, and the randomly selected parameter ensures that the identity certificates are different. Moreover, the parameters used for encrypting the identity and identity certificate are different, making , , , , and different. The parameters used for authentication are also different. Finally, the reputation of each user is different in most cases. The above factors constitute the challenge factor σ (i.e., ). If an association exists between pseudonyms, the one-way hash function used to generate pseudonyms will be compromised, although this is impossible. Secondly, for the pseudonyms of the same user, the parameters used to generate σ, excluding the identities, are different. Therefore, in this case, the pseudonyms are unlinkable.

--unlinkability ensures that a user identity cannot be inferred from the user pseudonym. In the process of user authentication, , , , , and , which are the cipher text of a user identity and identity certificate, generate the pseudonym along with other factors. The unlinkability between and the user identity is guaranteed by the strength of linear encryption.

Definition 12. If a probabilistic polynomial-time adversary has the advantage , which is negligible in , then we conclude that a User identity and corresponding pseudonym are unlinkable. The experiment is defined as follows:

(i) is given the public parameters , as described in the Environment Initialization stage. The register random oracle provides with a User identity, reputation value, and reputation certificate. The pseudonym random oracle provides with a User pseudonym .(ii) generates and and then gives them to the challenger.(iii)The challenger randomly selects from ; that is, . Then, the challenger calls to acquire the pseudonym .(iv) gives a guess of , and if then output is 1; otherwise, output is 0.

Nonrepudiation and Verifiable Reputation are based on the unlinkability between a User identity and pseudonym. Therefore, in the analysis of nonrepudiation and Verifiable Reputation, we have proved that a User identity and pseudonym are unlinkable.

5.2.3. Reputation and Anonymity

The introduction of reputation will influence User anonymity. The CSP can obtain User identity information through reputation in three ways: () reputation feedback; reputation submitted by ; and changes of reputation. Subsequent analysis indicates that all three ways will fail, provided the blind signature is not compromised, greater than 50 users are registered in the IdP, and the CSP is not synchronized with the IdP.

The introduction of the blind signature ensures that the process of updating a reputation will not disclose User identity information. submits the to the IdP to apply for modification of the reputation value. The User (the generator of ) submits the signature of to the IdP to confirm the reputation update. The technology of blind signature ensures the unlinkability between both signatures of and . Therefore, even collusion between the IdP and CSP cannot reveal User identity information.

When the number of Users registered in the IdP is greater than 50, the CSP cannot locate a User through their reputation value. We assume that the number of users registered in the IdP is and divide the interval of reputations, say , into independent values from which these users choose reputations independently (User reputation values are calculated independently of each other, and the reputation values can be considered uniformly distributed on the interval.). The probability distribution of two users with an equivalent reputation is then (http://en.wikipedia.org/wiki/birthday_Problem). As we can see from , when , the probability that two users have equivalent reputation values increases rapidly with increasing . When approaches 50, the probability resides very close to 1. When , as the number of users approaches 60, the probability continues to reside very close to 1. For simplicity, we take in this paper. Therefore, when is greater than 50, a set of users will have equivalent reputations, making it difficult for the CSP to locate a User based upon their reputation. To make the model more general, we assume that is the collection of users that have the same reputation; that is, for (at least one user in the collection provides a reputation). To mine user privacy, the CSP must continuously track users. Assuming the CSP seeks to track user for , after the next transaction between and the CSP, the CSP will acquire a set of users based on the reputation provided by the User through the corresponding pseudonym . The CSP will obtain the solution , , or regardless of whether or not the reputation is identical in these two steps. Therefore, when , the CSP cannot obtain User identity information from the reputation value. The openness of cloud computing ensures that will be far greater than 50, so that, in practice, the reputation will not disclose User identities.

Through disrupting the synchronization of the IdP and CSP, the CSP cannot locate a User through an update of the reputation value. For the aforementioned user set , when the CSP gives feedback to a pseudonym, the CSP would monitor the reputation changes in the IdP and then link the pseudonym to a user identity. In this case, the CSP must be synchronized with the IdP. For example, suppose a pseudonym of user accesses the CSP with reputation . After that, the CSP grants feedback to to increase the reputation value. Then, the CSP monitors the users in set whose reputation has been increased, links to , and then records the operations of . With a long-term monitor, the CSP will eventually record all the actions of the user and compromise the user’s privacy. To solve this problem, the User can choose a random waiting time to confirm the reputation value update so that the synchronization will be disrupted; thus, the CSP cannot determine if the pseudonym that the CSP has just granted belongs to the user whose reputation value has changed.

6. Conclusions

In this paper, we designed and implemented RIM, an identity management model for cloud computing that enables users to access cloud services using pseudonyms so as to ensure the unlinkability not only between different pseudonyms but also between a user and their corresponding pseudonym. In this way, user privacy can be protected. In addition, by calculating the reputation of users, RIM can assist CSPs to identify malicious users. RIM compensates for the shortcomings of identity management introduced by the multitenant feature and openness of the cloud computing environment.

In this paper, we assumed that the CSP honestly provides credible reputation feedback to users. However, in fact, malicious CSPs that provide dishonest assessments of user behavior may exist. In addition, a CSP may violate service level agreements (SLA). The various security vulnerabilities of CSPs pose a threat to users. Therefore, our future goal is to assess the credibility of CSPs and improve the reputation evaluation mechanism so as to provide better protection of user privacy. The access control mechanism in the cloud environment by means of reputation is also a valuable research topic that can be explored in the future.

Conflict of Interests

The authors declare that there is no conflict of interests regarding the publication of this paper.

References

P. Mell and T. Grance, The NIST Definition of Cloud Computing, National Institute of Standards and Technology, Gaithersburg, Md, USA, 2011.

P. Mell and T. Grance, “The NIST definition of cloud computing,” Special Publication 800-145, National Institute of Standards and Technology, 2011.

E. Olden, “Architecting a cloud-scale identity fabric,” Computer, vol. 44, no. 3, pp. 52–59, 2011.

E. Bertino, F. Paci, and R. Ferrini, “Privacy-preserving digital identity management for cloud computing,” IEEE Data Engineering Bulletin, vol. 32, no. 1, pp. P21–P27, 2009.

P. Angin, B. Bhargava, R. Ranchal et al., “An entity-centric approach for privacy and identity management in cloud computing,” in Proceedings of the 29th IEEE Symposium on Reliable Distributed Systems (SRDS '10), pp. 177–183, New Delhi, India, November 2010.

S. Ruj, M. Stojmenovic, and A. Nayak, “Privacy preserving access control with authentication for securing data in clouds,” in Proceedings of the 12th IEEE/ACM International Symposium on Cluster, Cloud and Grid Computing (CCGrid '12), pp. 556–563, IEEE, Ottawa, Canada, May 2012.

S. S. M. Chow, Y.-J. He, L. C. K. Hui, and S. M. Yiu, “SPICE—simple privacy-preserving identity-management for cloud environment,” in Applied Cryptography and Network Security: Proceedings of the 10th International Conference, ACNS 2012, Singapore, June 26–29, 2012, vol. 7341 of Lecture Notes in Computer Science, pp. 526–543, Springer, Berlin, Germany, 2012.

J. Xiong, Z. Yao, J. Ma, X. Liu, Q. Li, and T. Zhang, “PRAM: privacy preserving access management scheme in cloud services,” in Proceedings of the International Workshop on Security in Cloud Computing (Cloud Computing '13), pp. 41–46, ACM, Hangzhou, China, May 2013.

K. Ren, W. Lou, K. Kim, and R. Deng, “A novel privacy preserving authentication and access control scheme for pervasive computing environments,” IEEE Transactions on Vehicular Technology, vol. 55, no. 4, pp. 1373–1384, 2006.

K. Govinda and P. Ravitheja, “Identity anonymization and secure data storage using group signature in private cloud,” in Proceedings of the International Conference on Advances in Computing, Communications and Informatics (ICACCI '12), pp. 129–132, ACM, ind, August 2012.

T. H. Noor, Q. Z. Sheng, S. Zeadally, and J. Yu, “Trust management of services in cloud environments: obstacles and solutions,” ACM Computing Surveys, vol. 46, no. 1, article 12, 2013.

S. D. Kamvar, M. T. Schlosser, and H. Garcia-Molina, “The eigentrust algorithm for reputation management in P2P networks,” in Proceedings of the 12th International Conference on World Wide Web (WWW '03), pp. 640–651, ACM, May 2003.

L. Xiong and L. Liu, “PeerTrust: a trust mechanism for an open peer-to-peer information system,” IEEE Transactions on Knowledge and Data Engineering, vol. 16, no. 7, pp. 843–857, 2004.

R. Zhou and K. Hwang, “PowerTrust: a robust and scalable reputation system for trusted peer-to-peer computing,” IEEE Transactions on Parallel and Distributed Systems, vol. 18, no. 4, pp. 460–473, 2007.

N. K. Sharma, V. Gaur, and S. K. Muttoo, “A dynamic reputation system with built-in attack resilience to safeguard buyers in e-market,” ACM SIGSOFT Software Engineering Notes, vol. 37, no. 4, pp. 1–19, 2012.

I. Pranata, R. Athauda, and G. Skinner, “Modeling decentralized reputation-based trust for initial transactions in digital environments,” ACM Transactions on Internet Technology, vol. 12, no. 3, article 8, 35 pages, 2013.

R. Shaikh and M. Sasikumar, “Trust framework for calculating security strength of a cloud service,” in Proceedings of the International Conference on Communication, Information and Computing Technology (ICCICT' 12), October 2012.

T. H. Noor and Q. Z. Sheng, “Trust as a service: a framework for trust management in cloud environments,” in Web Information System Engineering—WISE 2011, vol. 6997 of Lecture Notes in Computer Science, pp. 314–321, Springer, Berlin, Germany, 2011.

F. G. Mármol, J. Girao, and G. M. Pérez, “TRIMS, a privacy-aware trust and reputation model for identity management systems,” Computer Networks, vol. 54, no. 16, pp. 2899–2912, 2010.

A. Post, V. Shah, and A. Mislove, “Bazaar: strengthening user reputations in online marketplaces,” in Proceedings of the 8th USENIX Conference on Networked Systems Design and Implementation (NSDI '11), pp. 183–196, 2011.

L.-H. Vu and K. Aberer, “Effective usage of computational trust models in rational environments,” ACM Transactions on Autonomous and Adaptive Systems, vol. 6, no. 4, article 24, 25 pages, 2011.

E. Androulaki, S. G. Choi, S. M. Bellovin, and T. Malkin, “Reputation systems for anonymous networks,” in Privacy Enhancing Technologies, vol. 5134 of Lecture Notes in Computer Science, pp. 202–218, Springer, Berlin, Germany, 2008.

H. Rifà-Pous, “Anonymous reputation based reservations in e-commerce (AMNESIC),” in Proceedings of the 13th International Conference on Electronic Commerce (ICEC '11), ACM, August 2011.

M. H. Au and A. Kapadia, “PERM: practical reputation-based blacklisting without TTPs,” in Proceedings of the ACM Conference on Computer and Communications Security, pp. 929–940, ACM, October 2012.

T. Okamoto, “Provably secure and practical identification schemes and corresponding signature schemes,” in Advances in Cryptology—CRYPTO' 92, vol. 740 of Lecture Notes in Computer Science, pp. 31–53, Springer, Berlin, Germany, 1993.

J.-Z. Luo, J.-H. Jin, A.-B. Song, and F. Dong, “Cloud computing: architecture and key technologies,” Journal on Communications, vol. 32, no. 7, pp. 3–21, 2011.

S. Subashini and V. Kavitha, “A survey on security issues in service delivery models of cloud computing,” Journal of Network and Computer Applications, vol. 34, no. 1, pp. 1–11, 2011.

A. Josang and S. Pope, “User centric identity management,” in Proceedings of the AusCERT Conference, 2005.

A. Shamir, “Identity-based cryptosystems and signature schemes,” in Advances in Cryptology, vol. 196 of Lecture Notes in Computer Science, pp. 47–53, Springer, Berlin, Germany, 1985.

D. Boneh and M. Franklin, “Identity-based encryption from the Weil pairing,” in Advances in Cryptology—CRYPTO 2001, vol. 2139 of Lecture Notes in Computer Science, pp. 213–229, Springer, Berlin, Germany, 2001.

D. Boneh, B. Lynn, and H. Shacham, “Short signatures from the weil pairing,” in Advances in Cryptology—ASIACRYPT 2001, vol. 2248 of Lecture Notes in Computer Science, pp. 514–532, Springer, Berlin, Germany, 2001.

D. Chaum, “Blind signatures for untraceable payments,” in Advances in Cryptology: Proceedings of Crypto 82, pp. 199–203, Springer, New York, NY, USA, 1983.

U. Feige, A. Fiat, and A. Shamir, “Zero-knowledge proofs of identity,” Journal of Cryptology, vol. 1, no. 2, pp. 77–94, 1988.

L. C. Guillou and J.-J. Quisquater, “A practical zero-knowledge protocol fitted to security microprocessor minimizing both transmission and memory,” in Advances in Cryptology—EUROCRYPT '88, vol. 330 of Lecture Notes in Computer Science, pp. 123–128, Springer, Berlin, Germany, 1988.

C. P. Schnorr, “Efficient signature generation by smart cards,” Journal of Cryptology, vol. 4, no. 3, pp. 161–174, 1991.

A. Kiayias and H. Zhou, “Hidden identity-based signatures,” in Financial Cryptography and Data Security, vol. 4886 of Lecture Notes in Computer Science, pp. 134–147, Springer, Berlin, Germany, 2007.

D. Boneh, X. Boyen, and H. Shacham, “Short group signatures,” in Advances in Cryptology—CRYPTO 2004, vol. 3152 of Lecture Notes in Computer Science, pp. 41–55, Springer, Berlin, Germany, 2004.

D. Boneh and X. Boyen, “Short signatures without random oracles,” in Advances in Cryptology—EUROCRYPT 2004, vol. 3027 of Lecture Notes in Computer Science, pp. 56–73, Springer, Berlin, Germany, 2004.

B.-X. Li, L.-F. Wu, Z.-J. Zhou, and H.-B. Li, “Design and implementation of trust-based identity management model for cloud computing,” Computer Science, vol. 41, no. 10, pp. 3-21.144–3-21.148, 2014.