\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={TPA Ensuring Data Integrity in Cloud Environment},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2013-01-15 (revised: 15 January 2013)}
\def\TheID{\makeatother }
\def\TheDate{2013-01-15}
\title{TPA Ensuring Data Integrity in Cloud Environment}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Jasmeet  Singh}

             \affil[1]{  RIMT-IET, Mandi Gobindgarh/ Punjab Techincal University}

\renewcommand\Authands{ and }

\date{\small \em Received: 9 December 2012 Accepted: 2 January 2013 Published: 15 January 2013}

\maketitle


\begin{abstract}
        


Cloud computing is an internet based computing where virtual shared servers provide software, infrastructure, platform and other resources to customers on a pay-as-you-use basis. In one of the services offered by cloud viz. Storage as a Service, users outsource their data to cloud without having direct possession or control on it. Storage of large data in cloud reduces costs and maintenance. But the customer is unaware of the storage location. Here risk involved is modification of data or tampering of data. In this paper we propose a data correctness scheme in which Third Party can audit the data stored in the cloud and assure the customer that the data is safe. Hence we implemented a scheme for verifying integrity of data. Such verification systems prevent the cloud storage archives (storage) from misrepresenting or modifying the data stored by using frequent checks on the storage archives.

\end{abstract}


\keywords{audit, cloud, integrity, station to station protocol, SHA-2, third party auditor, XOR.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{INTRODUCTION}]{INTRODUCTION}\par
loud Computing is emerging as the next evolution of computing for its numerous contribution to the IT enterprise. In contrast to traditional solutions, Cloud Computing has a number of essential characteristics, such as: on-demand self-service, ubiquitous network access, location independent resource pooling, rapid elasticity, and measured service. \hyperref[b2]{[3]} Figure  {\ref 1} : Cloud Computing Author ? : Jaspreet Kaur Lecturer, Thapar Polytechnic College M.TECH (Computer Science and Engineering) RIMT-IET, Mandi Gobindgarh, Punjab India. e-mail: kkhushi12@yahoo.co.in Author ? : Jasmeet Singh Asst. Professor(CSE Department) RIMT-IET, Mandi Gobindgarh, Punjab India. e-mail: jasmeetgur m@gmail.com Data outsourcing, one of the fundamental components of Cloud Computing, centralizes users' data to the cloud server (CS). Users including both individuals and enterprises move their data or store their data in cloud storage centers to minimize the costs and enjoy benefits, such as: release the pressure from storage management, universal data access with independent geographical locations. \hyperref[b3]{[4]} Despite these distinct advantages outsourcing brings, there are also many security issues. 1. Firstly, although the cloud service provider (CSP) can provide more powerful and reliable infrastructures than users, a huge mass of data storing in the CS makes it more vulnerable to active attack. 2. Secondly, towards the cloud users, the CSP may deliberately distort the status of users' outsourced data for some benefits. For example, the CSP may discard the data that users rarely or never access to save costs, or even hide data loss incidents for the sake of reputation . \hyperref[b3]{[4]} So we can see, although data outsourcing can bring advantages and convenience to users, it can not ensure the integrity of data. But integrity monitoring is essential in cloud storage for the same reasons that data integrity is critical for any data center. Data corruption can happen at any level of storage and with any type of media. The truth is that data corruption can happen anywhere within a storage environment. Data can become corrupted simply by migrating it to a different platform, i.e., sending your data to the cloud. Cloud storage systems are still data centers, with hardware and software, and are still vulnerable to data corruption.  {\ref [13]} Generally speaking, users like to outsource a huge mass of data in the CS, so simply downloading the data to verify the integrity is not a feasible solution. To solve the security problems of data outsourcing mentioned above, researchers proposed auditing protocols to ensure the correctness of the outsourced data. The integrity of data should be guaranteed in a relatively low computation and communication overhead through an efficient auditing protocol. \hyperref[b3]{[4]} So he appoints a Third Party Auditor to check the availability of data and its correctness without devotion of their computation resources. \hyperref[b0]{[1]} TPA checks the correctness of data stored in the cloud and communicates this with the client. Whenever the client needs the data the cloud returns the data with full guarantee of delivery, availability and correctness. As TPA verifies for its correctness and availability he considers the data is safe.\par
Figure \hyperref[fig_1]{2} represents data outsourcing in cloud environment where user delegates task of monitoring integrity to third party auditor(TPA). In Cloud Computing, it is difficult to maintain data integrity because the user usually has no control over the security mechanisms that are used to protect his/her data. User cannot trust cloud service provider to handle the data by himself as he himself can modify or delete the original data and integrity may be lost. If any intruder attacks and steals the data and modifies it then in some cases the modification is not even noticed by the cloud server or data loss or corruption is intentionally hidden. So, user can rely on a trusted third party auditor to check for the integrity of his data. To trust third party entity authentication is needed. For auditing (on user's request or at regular intervals), strong and secure cryptographic hash function is required to check for integrity of cloud data and informs the user about data corruptions or loss if any. 
\section[{III. Methodology}]{III. Methodology}\par
We propose a data correctness scheme which involves verifying integrity of data with the help of third part auditor as shown in figure  {\ref 3}.\par
For ensuring the integrity of the data we will be using combination of three approaches-1. Station-to-Station protocol (based on Diffie-Hellman key exchange algorithm) generates mutual key which is known to both user and auditor. It also provides entity authentication to both.\par
2. Exclusive-OR (XOR) to perform a xor operation between the message and the key generated using Station-to-Station protocol. 3. Secure Hashing Algorithm (SHA-2) to generate a digest by passing the original message to the hash function. This is done by both the user and the auditor and the value obtained from the hash function by both of them is compared and hence the data integrity is verified.  The steps of implementation are as follows- 
\section[{V. Results}]{V. Results}\par
The results of the above mentioned system are shown in Table \hyperref[tab_0]{1} and Figure \hyperref[fig_4]{7}. A secret key generated using STS protocol (that is known to both user and auditor. Also, mutual authentication is done using this protocol. 2. XOR operation is done between the data and the key generated to create cipher text which is stored in cloud. 3. Separately the data is passed in a hash function (using SHA-2) and the hash value is obtained by the user. 4. Auditor gets the cipher text from the cloud and performs an XOR operation with the secret key generated by the station to station protocol and gets a plain text. 5. Auditor passes this plain text to the same hash function (using SHA2) and obtains a hash value. 6. He then compares this hash value with the hash value received from the user .If both the values are identical then the data integrity is maintained else data is tampered. storage services. This scheme reduces the computational and storage overhead of the client as well as the computational overhead of the cloud storage server.. We are trying to improve the scheme for auditing multiple files from multiple clients simultaneously as with the increasing development of Cloud Computing technologies, it is believed that more and more users will prefer to store their data in the cloud. \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-2.png}
\caption{\label{fig_1}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{34}\includegraphics[]{image-3.png}
\caption{\label{fig_2}Figure 3 :CFigure 4 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5}\includegraphics[]{image-4.png}
\caption{\label{fig_3}Figure 5 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{7}\includegraphics[]{image-5.png}
\caption{\label{fig_4}Figure 7 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1} \par 
\begin{longtable}{P{0.425\textwidth}P{0.17708333333333334\textwidth}P{0.07083333333333333\textwidth}P{0.085\textwidth}P{0.09208333333333334\textwidth}}
\tabcellsep \multicolumn{3}{l}{File Size( in Bytes)}\tabcellsep \\
\tabcellsep 28\tabcellsep 99\tabcellsep 124\tabcellsep 205\\
\multicolumn{2}{l}{Encryption Time 16}\tabcellsep 94\tabcellsep 141\tabcellsep 211\\
\multicolumn{2}{l}{Decryption Time 31}\tabcellsep 141\tabcellsep 187\tabcellsep 265\\
Hash Time\tabcellsep 63\tabcellsep 78\tabcellsep 93\tabcellsep 108\\
Collision Point\tabcellsep 0\tabcellsep 0\tabcellsep 0\tabcellsep 0\end{longtable} \par
 
\caption{\label{tab_0}Table 1 :}\end{figure}
 			\footnote{© 2013 Global Journals Inc. (US) Global Journal of Computer Science and Technology} 			\footnote{© 2013 Global Journals Inc. (US)} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Jeyadevan et al. (2012)]{b10}\label{b10} 	 		‘A DATA INTEGRITY VERIFICATION IN CLOUD COMPUTING’.  		 			S Jeyadevan 		,  		 			. S Dr 		,  		 			Patel 		.  	 	 		\textit{International Conference on Computing and Control Engineering},  				13 April,2012. 12.  	 	 (ICCCE 2012) 
\bibitem[Madhuri et al. (2013)]{b2}\label{b2} 	 		‘A Protocol for Ensuring Data Integrity in Cloud Environment’.  		 			N Madhuri 		,  		 			T V Suneetha 		,  		 			A Haritha 		,  		 			P V S Lakshmi 		.  	 	 		\textit{International Journal of Advanced Research in Computer Science and Software Engineering}  		April 2013. 3  (4) .  	 
\bibitem[Malathi]{b0}\label{b0} 	 		‘A Scheme for Checking Data Correctness in the Cloud’.  		 			Murugesan Malathi 		.  	 	 		\textit{International Conference on Information and Network Technology},  				 	 	 (ICINT 2012) 
\bibitem[Patel and Patel (2012)]{b9}\label{b9} 	 		‘Achieving Secure Cloud Data Storage without using a Trusted Third Party Auditor-A Review’.  		 			Hiren Patel 		,  		 			Dhiren Patel 		.  	 	 		\textit{International Journal of Computer Applications}  		Nov.2012.  	 
\bibitem[Mohta and Kumar Awasthi (2012)]{b6}\label{b6} 	 		‘Cloud Data Security while using Third Party Auditor’.  		 			Abhishek Mohta 		,  		 			Lalit Kumar Awasthi 		.  	 	 		\textit{International Journal of Scientific and Engineering Research}  		June-2012. 3.  	 
\bibitem[Xu Chun-Xiang et al. ()]{b3}\label{b3} 	 		\textit{Cryptanalysis of auditing protocol proposed by Wang et al. for data storage security in Cloud Computing},  		 			Xu Chun-Xiang 		,  		 			Daniel Xiao-Hu 		,  		 			Abraha 		.  		2006.  		 			School of Computer Science and Engineering, University of Electronics Science and Technology of China 		 	 
\bibitem[Govinda and Sathiyamoorthy ()]{b4}\label{b4} 	 		‘Data Auditing in Cloud Environment using Message Authentication Code’.  		 			K Govinda 		,  		 			E Sathiyamoorthy 		.  	 	 		\textit{International Conference on Emerging Trends on Advanced Engineering Research (ICETT)},  				2012.  	 
\bibitem[Attas and Batrafi]{b11}\label{b11} 	 		‘Efficient integrity checking technique for securing client data in cloud computing’.  		 			Dalia Attas 		,  		 			Omar Batrafi 		.  	 	 		\textit{International Journal of Electrical \& Computer Sciences (IJECS-IJENS)}  		11 p. 5.  	 
\bibitem[Miss et al. (2013)]{b1}\label{b1} 	 		‘Improving data integrity on cloud storage services’.  		 			. M Miss 		,  		 			Sowparnika1 		,  		 			. R Prof 		,  		 			Dheenadayalu2 		.  	 	 		\textit{International Journal of Engineering Science Invention(ISSN)}  		February. 2013. 2  (2) .  	 
\bibitem[Saibabu et al. ()]{b7}\label{b7} 	 		‘Security Provision in Publicly Auditable Secure Cloud Data Storage Services using SHA-1 Algorithm’.  		 			Akkala Saibabu 		,  		 			T Satyanarayana 		,  		 			Murthy 		.  	 	 		\textit{International Journal of Computer Science and Information Technologies (IJCSIT)}  		2012. 3  (3) .  	 
\bibitem[Reenu Sara Georeg and Sabitha (2013)]{b8}\label{b8} 	 		‘Survey on Data Integrity in Cloud Computing’.  		 			Reenu Sara Georeg 		,  		 			S Sabitha 		.  	 	 		\textit{International Journal of Advanced Research in Computer Engineering \& Technology (IJARCET)}  		January 2013. 2  (1) .  	 
\bibitem[Govinda et al. (2012)]{b5}\label{b5} 	 		‘Third Party Auditing for Secure Data Storage in Cloud through Digital Signature using RSA’.  		 			K Govinda 		,  		 			V Gurunathprasad 		,  		 			H Sathishkumar 		.  	 	 		\textit{International Journal of Advanced Scientific and Technical Research}  		August 2012. 4  (2) .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
