A Cross Tenant Access Control (CTAC) Model for Cloud Computing

A Cross Tenant Access Control (CTAC) Model for Cloud Computing

ABSTRACT

Sharing of resources on the cloud can be achieved on a large scale since it is cost effective and location independent. Despite the hype surrounding cloud computing, organizations are still reluctant to deploy their businesses in the cloud computing environment due to concerns in secure resource sharing. In this paper, we propose a cloud resource mediation service offered by cloud service providers, which plays the role of trusted third party among its different tenants. This paper formally specifies the resource sharing mechanism between two different tenants in the presence of our proposed cloud resource mediation service. The correctness of permission activation and delegation mechanism among different tenants using four distinct algorithms (Activation, Delegation, Forward Revocation and Backward Revocation) is also demonstrated using formal verification. The performance analysis suggest that sharing of resources can be performed securely and efficiently across different tenants of the cloud.

SYSTEM REQUIREMENTS:

HARDWARE REQUIREMENTS:

•         System                 :  Pentium IV 2.4 GHz.

•         Hard Disk            :  40 GB.

•         Floppy Drive       :  1.44 Mb.

•         Monitor                :  15 VGA Colour.

•         Mouse                  :  Logitech.

•         Ram                     :  512 Mb.

SOFTWARE REQUIREMENTS:

•         Operating system           :  Windows XP.

•         Coding Language           :   JAVA

•         Data Base                       :  MYSQL

SYSTEM ANALYSIS

EXISTING SYSTEM:

Role based access control (RBAC) enables fine-grained access control (and generally in a single domain). Different extensions of RBAC have been proposed in the literature to support multi-domain access control. These approaches rely on a single body responsible for maintaining cross-domain policies. However, in a cloud environment, each user (individual or organization) may have one or more tenants and have a separate management infrastructure. Final year projects in chennai Therefore, it is likely that users are not able to agree on a single organization to manage access control on their behalf. With the increased trend of cloud services due to its various benefits (e.g. on-demand self-service model and resources sharing among tenants), it is essential for CSPs to provide mechanisms to segregate the data of the tenants

DISADVANTAGE:

Ø It is likely that users are not able to agree on a single organization to manage access control on their behalf

Ø The security of the approach was not provided.

Ø Specification level security is difficult to achieve at the user and provider ends.

PROPOSED SYSTEM:

Activation:

The activation algorithm is based on the activation query.  It authenticates a user for the activation of a particular permission. btech projects in chennai As defined earlier, a permission

activation request can be generated by an intra-tenant/cross tenant user. For a cross tenant user, a prior delegation of permission to cross-tenant user/tenant must exist.

User Revoke Algorithm:

we can revoke a previously granted permission from the cross-tenant user/cross tenant.

1) Revoke the permission from the service provider’s side.

2) Revoke the permission when the attributes of the user change and no longer match the published security policies on the CRMS.

ADVANTAGE:

·        The privacy of the Tenant is protected from another tenant .

·         Correctness and security of the current approach was proposed.