\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={Monitoring Data Integrity while using TPA 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-05-15 (revised: 15 May 2013)}
\def\TheID{\makeatother }
\def\TheDate{2013-05-15}
\title{Monitoring Data Integrity while using TPA 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]{k khushi  }

             \author[2]{Jasmeet Singh  }

             \affil[1]{  Punjab Technical University}

\renewcommand\Authands{ and }

\date{\small \em Received: 12 April 2013 Accepted: 5 May 2013 Published: 15 May 2013}

\maketitle


\begin{abstract}
        


Cloud Computing is the arising technology that delivers software, platform and infrastructure as a service over a network. Cloud minimizes the burden of users by allowing them to remotely store their data and eliminates the need of local storage and maintenance. Even though benefits are higher but while storing data in cloud, correctness of data and security are major concerns as there are many chances for CSP to behave unfaithfully towards users regarding the status of their outsourced data. In order to overcome the threat of integrity, user can entrust third party auditor to assess the risk of outsourced data when needed .For this, in our proposed scheme we are using SHA-2 which is cryptographic hash function to verify integrity of data along with XOR mechanism, Station-to-Station key protocol for key generation and mutual authentication with TPA.

\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 a forthcoming revolution in IT industry due to its advantages-on demand service, location independent resource pooling, rapid resource elasticity and usage based pricing. Cloud Computing is collection of scalable and virtualized resources and provide service based on payas-you-use strategy.\par
Cloud services are broadly divided into three categories as shown in figure  {\ref 1:} 1. SAAS(Software as a service) SaaS is a model of software deployment that enables software to be delivered from host source over the network as opposed to installations or implementations. 2. PAAS (Platform as a service) -This is a model in which operating system and middleware services are provided to the consumer by the cloud. 3. IAAS (infrastructure as a service) -This is a model in which service provider delivers the entire infrastructure as a service including storage, hardware, servers and networking components. \hyperref[b6]{[7]} Figure  {\ref 1} : Cloud Service Models From user's perspective, including both individuals and enterprises, outsourcing data in the cloud in a flexible on-demand manner as shown in figure \hyperref[fig_0]{2} brings appealing benefits-? Relief of the burden of the storage management.\par
? Universal data access with independent geographical locations.\par
? Avoidance of capital expenditure on hardware, software and personnel maintenance.  The first issue is data integrity. In computer security, data integrity can be defined as "the state that exists when computerized data is the same as that in the source document and has not been exposed to accidental or malicious alterations or destruction". Integrity of data stored at the entrusted cloud server is not guaranteed.\par
The second issue is unfaithful cloud server providers (CSP). There are many reasons why CSPs are not always trustworthy like, for saving money and storage space, CSPs may discard the data that has not been accessed for long time (which belongs to ordinary client) or sometimes even hide data losses or corruptions to maintain a reputation. \hyperref[b0]{[1]} To ensure integrity of outsourced data, data owner delegate the auditing task to trusted third party auditor. The persona of TPA is listed as follows-\par
? Reduces the owner burden in managing the data.\par
? Ensure the client that the data stored in the cloud is intact and data integrity is maintained. ? Aid in achieving high economies of scale through customer satisfaction. \hyperref[b4]{[5]} The TPA is an independent authority that has expertise and capabilities to monitor the integrity of cloud data outsourced by the following two fundamental requirements have to be met: 1. TPA should be able to audit the cloud data storage efficiently without asking for the local copy of data thereby reducing the on-line burden of cloud users. 2. The third party auditor informs user about data corruption or loss, if any. To securely introduce an effective third party auditor (TPA), the auditing process should not affect user data privacy. \hyperref[b0]{[1]} Figure  {\ref 3} represents the cloud data storage service which consists of three different entities: Users, Cloud Storage Server, Third Party Auditor (TPA).\par
1. User : Users are the data owners who have the large amount of data to be stored in the cloud and relies on cloud storage server for data computation and maintenance, can be either individual consumers or organizations.\par
2. Cloud Storage Server : A cloud storage server (CSS) is an entity that is managed by cloud service provider (CSP). It provides space to the user for data storage and computation.\par
3. Third Party Auditor (TPA) : An TPA is an entity who has expertise and capabilities that user don't have, is trusted to access or expose the risk of cloud storage services on behalf of client upon request. \hyperref[b7]{[8]} Figure  {\ref 3} : Architecture of cloud data storage service II. 
\section[{Problem Formulation}]{Problem Formulation}\par
When we talk about Cloud Security, maintaining data integrity is one of the most important and difficult task. In this case, user cannot trust cloud service provider to handle the data by himself as he himself can modify 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. So in this case, user can rely on a trusted (authenticated) third party auditor to check for the integrity of his data. For this, strong cryptographic hash function is required by the auditor to check for integrity of cloud data.\par
For ensuring the integrity of the data we will be using combination of three approaches- 1. 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.\par
a) Algorithms i. STS Protocol Key exchange should be linked to authentication so that a party has assurances that an exchanged key (which might be used to facilitate privacy or integrity and thus keep authenticity alive) is in fact shared with the authenticated party, and not an impostor. 
\section[{Station-to-Station (STS)}]{Station-to-Station (STS)}\par
Protocol is efficient authenticated key exchange protocol. The STS protocol consists of Diffie-Hellman key establishment followed by an exchange of authentication signatures. the specification of a particular cyclic group and the corresponding primitive element ?) are fixed and known to all users.\par
? Also, the public portion of this key pair may be shared prior to session establishment.\par
Steps-1. The protocol begins with one party, Alice, creating a random number x and sending the exponential ? x to the other party, Bob.\par
3. Alice computes K, decrypts the token using K, and verifies Bob's signature using Bob's public key.\par
Alice sends to Bob her corresponding encrypted signature on the exponentials, E K (s A \{ ? x , ? y \}).\par
4. Finally, Bob similarly verifies Alice's encrypted signature using K and Alice's public key.\par
Alice and Bob are now mutually authenticated and have a shared secret. This secret, K, can then be used to encrypt further communication. \hyperref[b5]{[6]} The basic form of the protocol is formalized in the following three steps:\par
1. Alice ? Bob: ? x 2. Alice ? Bob: ? y , E K (s B \{ ? y , ? x \}) 3. Alice ? Bob: E K (s A \{ ? x , ? y \}) Exclusive or Operation XOR is an operation in which same bits produce a resultant bit as 0 whereas different bits produce a resultant 1. In this, a XOR operation is done at original text along with secret value which gives cipher text. The original text can be obtained by performing an XOR operation between the secret key and resultant cipher text. \hyperref[b3]{[4]} b) SHA-2 This family of hashing algorithms known as SHA-2, use larger digest messages than SHA-1, making them more resistant to possible attacks and allowing them to be used with larger blocks of data, up to 2 128 bits, e.g. in the case of SHA512. The SHA-2 hashing algorithms are same for SHA256, SHA224, SHA384, and SHA512 hashing functions, differing only in the size of the operands, the initialization vectors, and the size of the final digest message.\par
The figure \hyperref[fig_4]{5} describes the SHA-2 algorithm applied to the SHA256 hash function.  The SHA256 Hash function produces a final digest message of 256 bits, that is dependent of the input message, composed by multiple blocks of 512 bits each. \hyperref[b2]{[3]} i. Message Padding and Parsing\par
The binary message to be processed is appended with a '1' and padded with zeros until its length ? 448 mod 512. The original message length is then appended as a 64-bit binary number. The resultant padded message is parsed into N 512-bit blocks, denoted M (1) , M (2) , ??. M (N) . These M ( i ) message blocks are passed individually to the message expander. 
\section[{ii. Message Expander}]{ii. Message Expander}\par
The message expander (also called the message scheduler) takes each M ( i ) and expands it into 64 32-bit W t blocks. \hyperref[b1]{[2]} iii. Message Compression The W t words from the message expansion stage are then passed to the SHA compression function, or the 'SHA core'. The input block is expanded and fed to the 64 cycles of the SHA256 function in words of 32 bits each .In each round of the SHA-2 algorithm the introduced data is mixed with the current state. This data scrambling is performed by additions and logical operations, such as bitwise logical operations and bitwise rotations as shown in Figure \hyperref[fig_4]{5}.\par
The 32-bit values of the A to H variables are updated in each round and the new values are used in the following round. The initial values of these variables is given by the 256-bit constant value, this value is only set for the first data block. The consecutive data blocks use the intermediate hash value, computed for the previous data block. Each 512 data block is processed for 64 rounds, after which the values of the variables A to H are added to the previous digest message, in order to obtain partial digest message. To better illustrate this algorithm a pseudo code representation is depicted in table 1.\par
for each data block i do W = expand(data block) A = DM 0 ; B = DM 1 ; C = DM The final Digest Message (DM) for a given data stream, is given by the result of the last data block. \hyperref[b2]{[3]}  
\section[{IV. onclusion}]{IV. onclusion}\par
Cloud Computing is an emerging commercial paradigm that promises to eliminate the need for maintaining expensive hardware. As market grows threat on data also grows. In this paper to ensure that our data are intact we addressed the construction of an efficient audit service where user can delegate the integrity checking task to third party auditor and be worry-free to use cloud storage services. We believe that advantages of proposed scheme will shed light on economies of scale of cloud computing. \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4}\includegraphics[]{image-3.png}
\caption{\label{fig_2}?BFigure 4 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-4.png}
\caption{\label{fig_3}? 2 .}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5}\includegraphics[]{image-5.png}
\caption{\label{fig_4}Figure 5 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-6.png}
\caption{\label{fig_5}}\end{figure}
 			\footnote{© 2013 Global Journals Inc. (US) Global Journal of Computer Science and Technology} 			\footnote{BMonitoring Data Integrity while using TPA in Cloud Environment} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Dhiyanesh and Thiyagarajan ()]{b7}\label{b7} 	 		‘A Novel Third Party Auditability and Dynamic Based Security in Cloud Compuitng’.  		 			B Dhiyanesh 		,  		 			A Thiyagarajan 		.  	 	 		\textit{International Journal of Advanced Research in Technology(IJART)}  		2011. 1  (1) .  	 
\bibitem[Diffie and Wiener ()]{b5}\label{b5} 	 		‘Authentication and Authenticated Key Exchanges’.  		 			Whitfield Diffie 		,  		 			Michael J Wiener 		.  	 	 		\textit{Codes and Cryptography}  		1992. Kluwer Academic Publishers. 2 p. .  	 	 (Appeared in Designs) 
\bibitem[Govinda and Sathiyamoorthy]{b3}\label{b3} 	 		\textit{Data Auditing in Cloud Environment using Message Authentication Code},  		 			K Govinda 		,  		 			E Sathiyamoorthy 		.  		 	 	 (International Conference on Emerging) 
\bibitem[Miss et al. (2013)]{b4}\label{b4} 	 		‘Improving Data Integrity on Cloud Storage Services’.  		 			. M Miss 		,  		 			Sowparnika 		,  		 			. R Prof 		,  		 			Dheenadayalu 		.  	 	 		\textit{International Journal of Engineering Science Invention (IJESI)}  		February 2013. 2  (2) .  	 
\bibitem[Chaves and Sousa ()]{b2}\label{b2} 	 		‘Improving SHA-2 Hardware Implementation’.  		 			Ricardo Chaves 		,  		 			Leonel Sousa 		.  	 	 		\textit{International Association for Cryptographic Research}  		2008.  	 
\bibitem[Mcevoy et al. (2006)]{b1}\label{b1} 	 		‘Optimisation of the SHA-2 Family of Hash Functions on FPGAs’.  		 			Robert P Mcevoy 		,  		 			Francis M Crowe 		,  		 			Colin C Murphy 		,  		 			William P Marnane 		.  	 	 		\textit{IEEE Emerging VLSI Technologies and Architectures},  				2-3 March 2006. 00.  	 
\bibitem[Rajak and Verma (2012)]{b6}\label{b6} 	 		‘Secure Data Storage in the Cloud using Digital Signature Mechanism’.  		 			Shobha Rajak 		,  		 			Ashok Verma 		.  	 	 		\textit{International Journal of Advanced Research in Computer Engineering and Technology}  		June 2012. 1  (4) .  	 
\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[Kaur and Singh ()]{b0}\label{b0} 	 		‘Survey on Efficient Audit Service to ensure Data Integrity in Cloud Environment’.  		 			Jaspreet Kaur 		,  		 			Jasmeet Singh 		.  	 	 		\textit{Global Journal of Computer Science and Technology (GJCST)}  		2013. 13  (4) .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
