A Secure Framework in Brokerage of Heterogeneous Cloud ...

A Secure Framework in Brokerage of Heterogeneous Cloud Environment for Multiple Cloud Providers Vikas Pardesi Assistant Professor School Of Computer Engineering Lovely Professional University Punjab, India

Aditya Khamparia Assistant Professor School of Computer Engineering Lovely Professional University Punjab, India

Abstract—In Cloud Computing Resources are allocated to customers based on their requests and prioritization, but sometimes a non-cloud provider organization wants to share their spare resources to same customers through Cloud Brokers so in this type of system a heterogeneous environment is created between regular cloud providers, Non- cloud provider organization, cloud broker and customers. In this paper we proposed an algorithm for maintaining this communication secure, reliable, and authentic between cloud providers and customer. Here we generated a link between customer and cloud provider through Cloud broker for secure service till session expiration. By implementation of this algorithm on CloudSim, we noticed better results in terms of better resource utilization, Connection reliability, Session handling and in fault tolerance. Keywords—Cloud Computing; Cloud Broking; Heterogeneous Cloud Management; Session management.

I. INTRODUCTION Cloud Computing is a new and vast field for research. Cloud Computing is a refined approach after grid computing and utility computing. It includes PaaS (platform as a service), SaaS (software as a service), IaaS (Infrastructure as a service) as basic facilities. Many other fields are open for research in cloud computing as Cloud monitoring, Cloud security, Cloud governance, Cloud Performance, Cloud scalability, Cloud broking. In this paper we presented cloud brokerage heterogeneity [1] security protocol for multiple cloud providers. Cloud broking coins for brokering in clouds. A cloud broker keeps all the services of different-2 cloud providers and provides these services to the end user at single place. Now a measurable difference in cloud brokering i.e. heterogeneity. A broker always contacts to those companies which have all functionality related to cloud computing such as PaaS, IaaS, SaaS but there are some organizations which are having some resources such as space, Infrastructure, Platform, Communication etc they also can contribute as a service provider through cloud broker. So this is called the heterogeneity in multiple cloud providers. Nowadays some organizations want to put their space, platform, Infrastructure

c 978-1-4799-4236-7/14/$31.00 2014 IEEE

Narendra Kr Bagde Assistant Professor School Of Computer Engineering Lovely Professional University Punjab, India

etc on cloud for effective utilization of the resources so cloud broker is the best way to achieve this goal. The main complexity arises in this area is the reliability and security between cloud provider and customer. Focus in this paper for implementing a secure protocol between cloud providers, end users and cloud broker with all the constraints such as reliability between cloud broker and cloud provider, reliability between cloud broker and customer and finally security between cloud provider and customer through cloud broker. There are some organizations providing private cloud for their work centre, some of them are interested for providing their resources to public but they are unable to do this because all the previous cloud providers also providing full featured cloud to their customers directly. Here they need a cloud broker for taking their resources and provides to end users. Specified work for the cloud broker is to aggregate all the resources from old cloud providers and some partial resource cloud provider and present it to the customers. The main concern is security and reliability between customers and cloud providers, i.e. done by the cloud broker. Here we implement a secure protocol between customer, cloud provider and cloud broker. In this secure protocol three entities are involved customer, cloud provider and cloud broker. First a request is generated by customer to the cloud broker, after identifying or registering as a new customer cloud broker generates a ticket number to customer and send one copy of ticket number to the desired cloud provider for which user requested. After this step a link is generated in customer’s E-mail ID for payment of requested service, in this process user will give their unique ticket number which is matched by the cloud provider and payment is given to cloud broker and after payment cloud broker generates a session for a limited period between cloud provider and customer. Now customer and cloud provider is directly connected to each other. After the completion of session connection gets closed between customer and cloud providers and again customer will have to contact to cloud broker. Benefits to customer in this protocol are aggregation of the resources at one place no needs to run to providers for different-2 services. All the offers and services are available at

854

same place. Benefits to cloud provider is, no need to search customers for their services. In this environment each providers has to provide full reliability and security to customers because this kind of environment is fully competitive. By this protocol we completed our two tasks first is heterogeneity of new cloud providers with existing one and security, reliability between customers and cloud providers. In next section we will see the issues related to cloud brokering. II. CLOUD BROKERING ISSUES Cloud Broker provides a very good level of abstraction between end user and cloud provider for a combined view of services provided by the providers. Cloud broker does not provide any kind of cloud service, the only work for cloud broker is just like a mediator for an efficient management of cloud services. Another duty of cloud broker is to deploy end user services on different-2 cloud platform. Following benefits are provided by the cloud providers• There is only one interface for interaction with multiple cloud providers. • Monitoring and controlling of clouds are done by the cloud broker but some time it depends on the capability of the cloud broker whether they are supporting this feature or not. • Fault notification and fault tolerance are also done by the cloud brokers but this activity can also be done by cloud provider so this is repetitive in nature. • From both public cloud and private cloud it can move the resources which lie on it. Here are some cloud brokers which are providing solutions for many cloud providers they are as follows. 1) APPIRIO provides solution for amazon.com, google.com, salesforce.com. 2) AppreGatta provides solution for mid-level size companies. 3) BOOMI provides services for Microsoft, amazon, Google, Quicbooks.com, Azzure, Netsuite, Taleo. Here cloud brokers are APPIRIO, Appregata, BOOMI and remaining companies are cloud providers. Nowadays cloud brokers are providing many solution on its site as cloud monitoring, session tracking, cloud security [7], cloud governance etc depending upon the budget allowed by the companies personnel. Some issues related to cloud security [6],[7] and reliability are remaining to discuss they are as follows1) Cloud monitoring as well as cloud security is very much needed because if you are able to monitor some threat and not to able to take any action so no use. 2) Reliability between new customers and new cloud provider is also an issue of discussion. 3) Cloud governance is most important feature here for governing the cloud between end user and cloud provider. 4) To handle the complexities between new providers and old providers.

5) To provide integration and aggregation [3], [4] between services and service providers. So all the issues are discussed through this algorithm and briefly heterogeneity in cloud is explained in next section. III. HETEROGENEOUS CLOUD BROKERAGE Many organization are nowadays are providing cloud services like amazon.com, Microsoft.com, google.com, salesforce.com etc. these companies are providing many services on cloud like SaaS, PaaS, IaaS, CaaS and many more, but there are some companies which are running their own personal clouds for their organization only (this type of cloud is called private cloud). This private cloud’s organization has much space and much software for their own purpose. But some times in a year we do not use full resources of our company. Sometimes these resources remain unallocated to any activity. At this time we need a broker which can take our free resources

Fig 1- Heterogeneous cloud forming and maintenance IV. PROPOSED SECURITY PROTOCOL In Cloud Computing environment security [5] is the main feature that must be available in all the scenarios whether it is cloud monitoring, cloud governance, cloud distribution or cloud framework etc. In proposed security framework there

2014 5th International Conference- Confluence The Next Generation Information Technology Summit (Confluence)

855

are some entities like cloud broker, cloud provider and customer. This algorithm is briefly described in steps, they are as followsStep 1- In this step customer will request for any kind of service to the cloud broker like SaaS, IaaS, PaaS. Cloud broker will receive this request and serve it to customer in next step. In this step broker will also search for the appropriate desired service for the customer in available providers and show to the customer for their best option. Step 2- This is processing step, When broker will receive the request then broker will generate an unique ID and supply it to both customer and service provider for future verification step and further details. Step 3- Link Generation step, in this cloud broker programmatically generates a link and delivers it to customer’s email ID and cloud provider’s Email ID. Both of them anyone can start the link and can connect with each other. In this process broker governs all the activity which is happening between customer and provider. In mean time cloud broker also monitors some main issues in this kind of story. Step 4- Verification and validation step, In this process verification is done by the customer as well as cloud provider. Here customer will enter that unique ID which was generated in step 2 and cloud provider will match that it with their own records. When verification is done by the cloud provider then validation process, in this process customer will be validated for the desired service by the cloud provider. With which actual service demanded by the customer that is validated by the cloud provider because this detail is already being sent to the cloud provider.

In this step a session is created by the cloud broker, it means that after verification and validation process when cloud provider will issue any service to customer then a session is created by the broker for a limited period. When the timer expires then session is automatically expired and connection between customer and cloud provider get crashed. For renewal of service customer can request again to broker. By this kind of framework security is maintained between illegal uses of services by the customer from cloud provider. All the things are measured by the cloud broker. According to this monitoring of events cloud broker can take their decisions related to customers and providers. Advantages- This framework results in many advantages. 1) Broker can make their decision about providers and customers. 2) Monitoring and security [5] both are being done by the broker simultaneously. 3) Clod governance is also being performed over heterogeneous clouds. 4) Quality of services and availability of services is improved due to link generation. 5) Traffic-managerial issues are solved due to hybridness in service. V. IMPLEMENTATION RESULTS AND ANALYSIS Above discussed algorithm is implemented in CloudSim tool, it is a tool for simulation of cloud computation. After setting all the parameters and allocate different-2 resources to different-2 cloud we got some results. This result is divided in some parameters in which we can judge a cloud provider and cloud broker in cloud environment. Here we provided a graphical result by which we can understand our configuration of this algorithm is right or not.

Fig 3- Observation Results based on some parameter Fig 2- Proposed Algorithm for Resource Allocation

856

2014 5th International Conference- Confluence The Next Generation Information Technology Summit (Confluence)

Below mentioned parameters are the main entities by which we can judge this algorithm correctness. These results are generated with 10 times observation on tool. 1) Connection Reliability- by the graph we can see easily 8 times out of 10, connections maintained successfully. 2) Session Forming & Authentication- according to graph we are able to judge that 100% success we got in this phase. 3) Link generation and Resource Allocation- in this phase we also got 100 % success rate. This algorithm generated link and resource allocation 10 times out of 10 observations. 4) Fault tolerance- Fault tolerance is the biggest feature of this algorithm because sometimes due to any kind of failure how much time our algorithm effective is. 5) Utilization of resources- there are many kinds of cloud providers and their resources is allocated and utilized in better way by this algorithm. In this phase also we got approximate 95 % success rate. In future some work may be done in this phase related to priority of resource allocation from different-2 cloud providers. VI. BENEFITS, COMPLEXITIES AND FUTURE WORK In heterogeneous type of environment Advantages• One place for all the required services such as SaaS, PaaS, IaaS, CaaS etc. • Heterogeneous environment for multiple cloud providers. • Non-profitable organizations and some private cloud can also be included in this environment. • Sharing of resources between cloud providers through brokers becomes much easier. • Flexibility in integration and aggregation of cloud services. • Addition and removal of cloud provider became much easier. Complexities• Structure became little complex due to heterogeneous clouds addition. • To handle the security mechanism is much more complex between all the entities. • To import and exportation between private and public clouds. • Monitoring the services between clouds. In future computing will become more portable and cloud computing is the best option for this. But there are many issues on which work is being carried out. Main concerned areas are in cloud computing are security, integration, reliability, governance and monitoring of clouds. Cloud

computing is also known as next generation computing instead of this it is a part of grid computing. Cloud localization is also a very much interesting area because nowadays public and private clouds are merged that is called hybrid cloud and security in this kind of environment is a big issue. So in further research work we will contribute some articles related to cloud security in more detail. Resource allocation prioritization may be a work of future for more research. In these field complexities of resource allocation to different-2 cloud provider and repetition of resource allocation, these are the two areas in which a lot of work can be done. VII. CONCLUSION Cloud brokering works as a middleware between cloud provider and customer. Many cloud providers implemented some secure protocols between customers and themselves without including cloud brokers. But this procedure is much tedious for end user. Nowadays customers are curious about latest and full-fledged services at one place and this can be provided only by cloud broker. Broking the commodity is just like a market where all customers come and get their best desired service or product. Security is the main concern for broker for making transparency between customer and cloud provider. Even it is believed that security protocols are not implemented at broker side but all the security algorithms has to pass through cloud broker. So it is beneficial for the cloud broker that implements the protocol by itself. Here we presented a protocol that is enough secure for the broker to implement between customer and cloud provider. REFERENCES [1] [2] [3] [4] [5] [6] [7]

M. Almorsy, A.S. Ibrahim, “Colaboration based Cloud computing security,” CLOUD by IEEE, pp. 364-371, April 2011. Amanatullah, Y.,”Toward cloud computing refernce architecture: cloud service management perspective”, ICISS by IEEE., 2013, pp.01-04. Chalse R, “A new technique of data integrity for analysis of the cloud computing security,” 5th CICM by IEEE, 2013, pp. 469-473. Kretzschamar M, “Security Management interoperability challenges for collaborative clouds,” 4th DMTF workshop by IEEE 2010,pp 43-49 Wenatau Lio, “Research on cloud computing security: problem and strategy,” 2nd CECnet by IEEE 2012, pp. 1216-1219. Bouayad A, “Cloud Computing: security and challenges” CIST 2012 Colloquium by IEEE, pp. 26-31. Kretzschamar M, “Security Management areas in the inter cloud,” 9th SERVICES 2013 IEEE,pp 762-763.

2014 5th International Conference- Confluence The Next Generation Information Technology Summit (Confluence)

857