Optimized Multi-tenancy Secure mechanism in SPI Cloud Architecture

Transcription

1 Volume 1, No. 12, February 2013 ISSN The International Journal of Computer Science & Applications (TIJCSA) RESEARCH PAPER Available Online at Optimized Multi-tenancy Secure mechanism in SPI Cloud Architecture S.Bharanisethupandian 1, 1 Assistant Professor, Department of MCA, SOURASHTRA COLLEGE, Madurai, Tamilnadu, India 1 bharanisethupandian@yahoo.com Dr.M.Sumathi 2 2 Assistant Professor, Department of Computer Science, Sri Meenakshi Government College for Women, Madurai, Tamilnadu, India Abstract The era of digital media has made one of its most valuable computer concepts called "Cloud". This concept of computing makes the term Digital services work efficiently for its various computational tasks which it addresses as a whole. The computational process of cloud makes different services work on different platforms and finally address on unique solutions. The services of cloud were done with SPI architecture. In this paper we have proposed a mechanism that provides a secure firewall for every thin client services. The thin client services provided along with cloud deployable services were done along with API. We believe that such approach will provide secure and effective cloud services in SPI architecture through the thin client services. Keywords: Cloud Security, SPI architecture, Cloud model and services, Cloud API 1. Introduction The understanding of cloud and its services refers to the technology expertise that performs its various tasks over a network platform. A Cloud service [2][3] addresses both hardware and software which combines and provide valid information or required services in distributed approach. The cloud network can be broadly framed as private and public cloud. Both these approaches provide cloud computations depending on the type of services. This service can be either accessed locally or remotely. Hence cloud has its variety for addressing the same. Since cloud services can be provided either via hardware or software services, security level deployment can be on either of these two services. Nevertheless both these services address secure standards for effective cloud services. Fig 1 shows the cloud model where various users access the cloud for various services. 2013, - TIJCSA All Rights Reserved 11

2 Fig 1: Cloud deployable model A user can access cloud service for variety of services like storage, application and process etc. The cloud does the function for the user using cloud network services. The only way where a user can be authenticated is the cloud services entry phase. Only here a user should notify him for accessing cloud services. What all users need from the cloud, is the services where he can access the cloud services via thin client services. Thin client service is an individual user personal system that helps to get access cloud services. The interface between thin client and cloud repository where done with the assistance of interface/link. The interface has to provide user authentication to the cloud service. Further to the link established with the cloud, the thin client interface services are identified using API services. The technology evidence of cloud works on its routine and does prescribed function based on its services and deploy ability. This will overcome the traditional approaches used in many business organizations. Basically cloud infrastructure has two layer i.e. one layer posses the functionality of hardware and other is the software services. This model is quite different from traditional computing setup. The architecture services of cloud were deployed with SOA for its unique application services. The technology portion of cloud is addressed along with its information and was identified differently based on layer classification in cloud service model. Fig 2: Cloud Model Layer approach The functionality of cloud [1][2] were stimulated from various services. Every service is different in cloud. This addresses the concept of Multi-tenancy. One services can be used by more than a person in cloud architecture [3][5]. Then the services of cloud were shared consistently for all users. This concept adds efficiency to cloud since the services were shared, instead of deploying it to individual user. 2013, - TIJCSA All Rights Reserved 12

3 Multi-tenancy makes the services virtually available to the entire user and hence adds value to the cloud services. The Figure 3 shows the cloud shares three different services address different services for different users. Fig 3: Cloud shares three different services 2. Existing System The work of Miranda and Mowbary focuses on "A client based privacy manager for cloud computing" addresses the purpose of secure thin client architecture in effective cloud service. Further the work of Mather, T., Kumaraswamy, S., & Latif, S. (2009) influences the Cloud Security and Privacy dealing with third party security in cloud computing. Jinpeng Wei, Xiaolan Zhang, Glenn Ammons, VasanthBala and PengNing discusses on Managing security of virtual machine images in a cloud environment, November 2009 addressed on Virtualization in cloud computing. Transparent Cloud Protection System (TCPS) [10] identifies the protection system for early monitoring and reliability in cloud computing. All these work referred identify the security issues in cloud and also the other issues arise with the same. Our assumption is that security issues and its measures have to be deployed in the third party metrics not on the cloud architecture. This is due to the fact that cloud services were not transparent to client and clients were not given education for cloud services. 3. Proposed System Apart from the existing cloud model the proposed system address a deployed third party model enhanced with security measure for multi-tenancy problem. This model invokes self management strategy for addressing the current cloud security issues. Since the services of cloud were unnoticed and kept as secret for client, makes them hesitate to use cloud service. 3.1 Mapping cloud data 2013, - TIJCSA All Rights Reserved 13

4 The concept of mapping cloud was used now a day to address the secure flaws in cloud. This principle mechanism was deployed in the fourth model of cloud, apart from the existing SPI cloud architecture. The fourth model belongs to third party services. Via these services the secure mechanisms were deployed in to SPI architecture. SPI architecture provides the stack of secure service in cloud were traditional security mechanism are used to address the said problem. Fig 4: SPI and Secure cloud model Fig 4 address the third party cloud service for securing API. This type of model is available in all user location to ensure secure standards. The secure API is available in all user personalized location and was integrated via virtualization for sharing and deploying cloud services. Every user initiated services to cloud will be transferred via third party secured API using traditionally proven secure mechanism. This secure mechanism will invoke secure standard for every sent and received information services from Secure API to SPI cloud architecture to worth. The Secure services in cloud were invoked using secure API. This secure API was initiated via XML services. The code mentioned below invokes secure API for SaaS [3] <version xmlns=" xmlns:atom="h ttp:// id="v2.0" status="current" updated=" T11:33:21-06:00"> <media-types> <mediatype base="application/xml" type="application/vnd.openstack.identity+xml ;version=2.0"/> <mediatype base="application/json" type="application/vnd.openstack.identity+js on;version=2.0"/> </media-types> <atom:link rel="self" href=" > <atom:link rel="describedby" type="application/pdf" href=" cloudservice.com/auth/api/v2.0/auth-client-devguide-latest.pdf"/> <atom:link rel="describedby" type="application/vnd.sun.wadl+xml" href="h ttp://docs. cloudservice.com/auth/api/v2.0/auth.wadl"/> </version> 2013, - TIJCSA All Rights Reserved 14

5 This secure API works for SaaS services. Likewise different API was invoked on other services of PaaS and IaaS. Fig 5 shows data flow sequence carrying client data to SPI architecture via secure API Fig 5: Data flow from Client to SPI with encryption standards Here the encryption standards were provided by third party vendor like VeriSign to ensure secure transmission between clients to SPI [3]. Fig 6: Data flow from SPI to Client with decryption standards This mechanism will work for various users based on their services initiated to cloud services. Implementing security in API [6] [7] is done using traditional security algorithm like elliptical curve for providing effective and efficient services in cloud. 5. Conclusion and Future work In this work we have identified few API for all the three models of cloud. This API addresses the security issues in cloud and also for the effective cloud performance. The purpose of secure API is to invoke mapping services to the deployed Secure API and then to the client. This functionality will be reversed in due course. The future work will address a unique Secure API which will identify the potential instinct of all three models and its features. We believe that such approach will invoke efficient secure mechanism for sure. Reference [1] Mather, T., Kumaraswamy, S., & Latif, S. (2009). Cloud Security and Privacy. New York: O Reilly [2] Dinoor S (2010) Got Privilege? Ten Steps to Securing a Cloud-Based Enterprise. [3] Security and Economic Benefits of standardization for security as a service. September 2011 proceedings. [4] Cloud security Alliance, Defined Categories of service [5] A guide to security metrics. SANS Institute, June [6] Amazon Elastic Compute Cloud Developer Guide, [7] Amazon web services blog: Introducing amazon virtual private cloud (vpc), Amazon, August [8] CVSS A Complete Guide to the Common Vulnerability Scoring System, Version 2.0, 2007 [9] WeichaoWang,Zhiwei Li, Rodney Owens and Bharat Bhargava, Secure and Efficient Access to Outsourced Data, November 2009, Proceedings of the ACM workshop on Cloud computing security, pages [10] Flavio Lombardi and Roberto Di Pietro, Transparent Security for Cloud, March 2010, Proceedings of the 2010 ACM Symposium on Applied Computing, pages , - TIJCSA All Rights Reserved 15