\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={Safeguarding the Liabilities of Data Accessing in Cloud Computing},
 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{Safeguarding the Liabilities of Data Accessing in Cloud Computing}
\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]{Kethan Harish  Yekula}

             \author[2]{Dr.  Y.Venkateswarlu}

             \author[3]{Suneel Kumar  Badugu}

             \affil[1]{  Jawaharlala Nehru Technological University Kakinada(JNTUK)}

\renewcommand\Authands{ and }

\date{\small \em Received: 7 April 2013 Accepted: 2 May 2013 Published: 15 May 2013}

\maketitle


\begin{abstract}
        


Cloud computing is the process of providing the virtualized services over the internet. The space in the web commonly known as Cloud has been monitored by service provider. In a real time scenario, a user registers for a particular service and shares his data as well as access credential policies with CSP (cloud service provider). Though cloud computing has got major flexibility in data accessing, users are very much concerned about their data security as it may be mislead by service providers. They may share the owner?s data to unauthenticated persons. This is a big threat to the data owners. In this paper a modern approach, is proposed namely Cloud Information Accountability (CIA) framework, and based on the notion of data liability. We identify the common requirements and develop several guidelines to achieve data accountability in the cloud. Once the data owner provides data, the service provider will have full access and permission rights, on the data. Using traditional access control mechanisms, after data rights are permitted, the data is in the hands of the service provider. We propose an algorithm, which gives the details of people accessing the data using the automated logging details through the JAR files.

\end{abstract}


\keywords{cloud computing, logging, privacy, security, data sharing, information accountability framework.}

\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& 	 	 		 \par
he Cloud Information Accountability framework (CIA) proposed in this work conducts automated logging and distributed auditing of relevant access performed by any object, carried out at any point of time at any CSP's. The CIA concept has two major components: logger and log harmonizer. The JAR file holds a set of simple access control rules specifying whether and how the cloud servers and possibly other data stakeholders are authorized to access the content. Once the login credentials are matched, the service provider accesses the data hidden in the JAR. Based on the settings mentioned during creation, the Java Archive file gives usage control along with log options, for every log, the data is accessed and the JAR generates a record. Cloud computing presents a replacement thanks to resources. The consumption model for IT services on the net, by providing support for ad-hoc increasable randomly virtualizing resources are used as a service over the internet. Knowledge handling is outsourced by the direct cloud service supplier (CSP) to different entities within the cloud and theses entities forward the applications to others, and so on. And, permissions are provided to enter and leave the cloud storage. As a result, knowledge handling within the cloud goes through a posh and dynamic hierarchal service chain that does not exist in standard environments.\par
To overcome the above mentioned issues, we tend to propose a unique approach, specifically Cloud information Accountability (CIA) framework, supporting the notation of knowledge responsibility. Some of the common needs are determined and various tips are suggested to attain knowledge answerability within the cloud. For example A user, United Nations agency signed to an explicit cloud service, typically has to send his/her knowledge moreover as associated access management policies to the service supplier. Once the info is received, the CSP can get access permission rights, like scan, write, and copy, on the info exploitation standard access management mechanisms, once the access rights are granted, the info are going to be totally offered at the service supplier.\par
The CIA framework projected during this work conducts machine-controlled work and distributed auditing of relevant access performed by any entity, applied at any purpose to any cloud service applies its two major components: logger and log harmonizer.\par
The JAR file includes a group of straightforward access management rules specifying whether or not and the way the cloud servers and presumably different knowledge stakeholders are approved to access the data. After the verification is done, the service suppliers are given the permission to access the information closed within the JAR looking on the configuration settings outlined at the time of creation, the JAR can offer usage management related to work. Whenever the associates access the information from cloud, The JAR automatically generates a log report.  
\section[{V i e w}]{V i e w}\par
Author : Jawaharlala Nehru Technological University Kakinada (JNTUK). E-mail : kethan.harish@gmail.com Kethan Harish Yekula ? , Dr. Y. Venkateshwarlu ? \& Suneel Kumar Badugu ? support for tracking provenance, especially when data moves among databases. This paper investigates general-purpose techniques for recording provenance for data that is copied among databases. We describe an approach in which we track the user's actions while browsing source databases and copying data into a curate database, in order to record the user's actions in a convenient, query able form. We present an implementation of this technique and use it to evaluate the feasibility of database support for provenance management. Our experiments show that although the overhead of a native approach is high, it can be decreased to an acceptable level using simple optimizations.\par
b) The Advantages of Elliptic Curve Cryptography for Wireless Security Kristin Lauter, Microsoft Corporation\par
This article provides an overview of elliptic curves and their use in cryptography. The focus is on the performance advantages to be obtained in the wireless environment by using elliptic curve cryptography instead of a traditional cryptosystem like RSA. Specific applications to secure messaging and identity-based encryption are discussed. We propose a fully functional identity-based encryption scheme (IBE). The scheme has chosen cipher text security in the random oracle model assuming an elliptic curve variant of the computational Diffe-Hellman problem. We give precise definitions for secure identity based encryption schemes and give several applications for such systems. ? We propose a modern approach, namely Cloud Information Accountability (CIA) framework, based on the notion of data liability. ? The suggested CIA framework provides end-to end accountability in a highly distributed fashion. ? A detailed security analysis is provided, strengths and reliabilities are discussed and our robust architecture in the face of various nontrivial attacks implements Java Running Environment. ? Apart from creating a class file which authenticates the servers or the users, another class file generates the correct inner JAR, a third class file which checks the JVM's validity using oblivious hashing. ? To limit the access for security purpose, timer mechanism is proposed ? Securing the JVM for making software tamper resistance capabilities to JAR file. It provides integrity, confidentiality to JAR. 
\section[{c) Advantages}]{c) Advantages}\par
? The novel features of the CIA framework lies in its ability to maintain lightweight and powerful accountability that combines aspects of access control, usage control and authentication. ? This technique defends against man in the middle attack, dictionary attack, Disassembling Attack, Compromised JVM Attacks. ? It is suitable for limited and large number of storages. The JAR file contains a set of access control policies mentioning whether and how the cloud servers and possibly other data interested party (users, companies) are authorized to access the information. Depending on the configuration settings, the JAR will provide usage control combined with login credentials. 
\section[{Global}]{Global} 
\section[{b) Logger Creation}]{b) Logger Creation}\par
To conduct automated logging, the programming capabilities of the JAR files are leveraged. User's info and related data items are stored in nested Java JAR file, which is a logger component. The outer JAR provides authentication to entities for accessing the data stored in the JAR file. In this situation, the data owners do not know the exact CSPs who handle data. Hence, authentication is mentioned based on the server's functionality. The data owner can give permissions in user-centric terms as opposed to the usual code-centric security offered by Java, using its Authentication and Authorization Services. Moreover, the outer JAR is also heads the selection of correct inner JAR according to the identity of the entities that requests the data. 
\section[{c) Log Record Generation}]{c) Log Record Generation}\par
Logger component generates the log records. Logging occurs at any access to the data in the JAR, and consecutively adds the entities in the order of creation LR= (r1; . . . ; rki. Each record is encrypted one by one and updated to the log file. During the read-only request, the inner JAR decrypts the data and a temporary decrypted file is created. This file is shown to the entity using the Java application viewer and suppose it is displayed to a user. Presenting the data in the Java application, he un checks the methods that copy by using hot keys such as Print Screen. 
\section[{a) Mode Setting}]{a) Mode Setting}\par
The data owners are timely and accurately informed about their data usage, our distributed logging mechanism complements an unique auditing mechanism. We support two complementary auditing modes: i Push mode ii Pull mode.\par
? Push Mode: In this mode, the harmonizer pushes the logs to the data owner (or auditor) in a timely manner. The push action is invoked by either type of the following two events: one is that the time elapses for a certain period according to the temporal timer inserted as part of the JAR file; the other is that the JAR file exceeds the size stipulated by the content owner at the time of creation.\par
? Pull Mode: This mode allows auditors to retrieve the logs anytime when they want to check the recent access to their own data. 
\section[{b) Algorithm}]{b) Algorithm}\par
The concept of push-pull strategies is very beneficial when more amounts of data are accessed in short time. At this scenario, if the data is not sent out random enough, the logging file becomes huge, which increases the operation expenses like data copying. The data owners prefer the push mode and want to keep track of the data usage consistently over time. For such data owners, receiving the logs automatically can lighten the load of the data analyzers. The maximum size at which logs are pushed out is a parameter which can be easily configured while creating the logger component. The pull strategy is most needed when the data owner suspects some misuse of his data; the pull mode allows him to monitor the usage of his content immediately. A hybrid strategy can actually be implemented to benefit of the consistent information offered by pushing mode and the convenience of the pull mode. To conduct the automated logging, the programming capabilities of the JAR file are leveraged.. A logger component is a nested Java JAR file holds a user's data items and related log files. The outer JAR takes care of authentication of entities for accessing the data stored in the JAR file. In this scenario, the data owners may not know the exact CSPs who hold the data. Hence, authentication is specified according to the servers' workability For example, a policy may state that Server X is allowed to download the data if it is a storage server. As discussed below, the outer JAR may gain access control to enforce the data owner's parameters, mentioned as policy of java, which is implemented on the data.\par
What permissions are available to access a particular code in the Java Environment is taken care by the Java policies. These access rights represent the same File System Permissions. However, the data owner can mention the access permissions in usercentric terms as inverse to the usual code-centric security in Java, using its authorization and authentication Services. Moreover, the outer JAR takes the responsibility of selecting the correct inner JAR according to the identity of the entity who requests the data.\par
To facilitate retrieval of log files and display enclosed data in a suitable format, and to maintain a log file for each encrypted item, Each inner JAR holds the encrypted data, class files. Here two options are supported:\par
? Pure Log : Its records every access to the data and are used for pure auditing purpose ? Access Log : It performs two methods logging actions and enforcing access control. In case if a request is denied, the JAR records the request made time If the access request is granted, the JAR record the access information additionally along with the allowed time period access.\par
These two logging methods provokes the data owner to implement certain access conditions either proactively (in case of Access Logs) or reactively (in case of Pure Logs). For example, services like billing require use of Pure Logs. Access Logs are needed by services, which compel service-level agreements such as limiting the access to sensitive information. To perform these tasks, the inner JAR writes the log record using the class files and another class file agrees with the log harmonizer, the third class file which is an encrypted file that displays or copies the data from the server downloading the data (based on whether we have a Pure Log, or an Access Log), and the public key of the IBE key pair that is necessary for encrypting the log records.\par
System never stores the secret keys. The outer JAR may contain one or more inner JARs, apart from that a class file for authenticating the servers or the users, and the another one used to find the correct inner JAR, a third class file using oblivious hashing, checks the JVM's validity. Moreover, class file manages the Graphical User Interface for user authentication and the Java Policy. 
\section[{e) Log Record Generation}]{e) Log Record Generation}\par
Logger Component generates log records. Any access to the data in the JAR requires logging information, and new log entries are added in a consecutive manner, in order of creation LR= (r1; . . . ; rki). Each record ri is encrypted one by one and added to the log file. To make sure that the log records are correct, Access time, locations as well as actions are verified. In particular, the time of access is determined using the Network Time Protocol (NTP) \hyperref[b15]{[15]} to avoid suppression of the correct time by a malicious entity. By using the IP address, the Cloud Service Providers location is traced out. The JAR performs IP lookup and finds the most probable location of the CSP using the IP address range. For determining locations, advanced techniques are implemented \hyperref[b10]{[10]}. Similarly, if a trusted time stamp management infrastructure can be set up or leveraged, it can be used to record the time stamp in the accountability log \hyperref[b1]{[2]}. The most critical part is to log the actions on the users' data. In the current system, we support four types of actions, i.e., Act has one of the following four values \hyperref[b0]{[1]}: view, download, timed access, and Location-based access. For each action, we propose a specific method to correctly record or enforce it depending on the type of the logging module, which are elaborated as follows: 
\section[{?}]{?} 
\section[{View}]{View}\par
The entity (e.g., the cloud service provider) has only read permissions and cannot save the raw information permanently. In this type of activity, pure log edits the log record about the access while the Access Logs using the enclosed access control module compels the action. We know that the inner JAR stores and encrypts the data. When the access request is read only, on the fly a temporary decrypted file of data is created by inner JAR. In case the human user accesses the file, by using the Java application viewer the hidden file is shown to the entity viewer. Utilising the Java Applications data, viewer uncheck the copying methods by using some keys such as print screen. And, the data will be hidden to prevent to avoid the usage of some print screen capture software when the application viewing screen focus goes out. When the content is presented to Cloud Service Provider he sees it on the command line using the headless mode in Java 
\section[{Download}]{Download}\par
The entity is allowed to save a raw copy of the data and the entity will have no control over this copy neither log records regarding access to the copy. If Pure Log is adopted, the user's data will be directly downloadable in a pure form using a link. When an hyperlink is clicked and downloaded, the JAR file combines the data, decrypts and give it to the entity in raw form. In case of Access Logs, the entire JAR file will be given to the entity. Depending upon the entity the jar file can be accessed. 
\section[{?}]{?} 
\section[{Timed access}]{Timed access}\par
The view-only access works on the time basis and provides data for a limited period. The access starting time and duration are recorded by the pure log, meanwhile the Access Log is also utilised in a given time frame. By using the Network Time Protocol, the duration of access time is calculated. Based on the calculations, the time limit of Access Log records are determined. This timed access is compelled only it is combined with view access and download. 
\section[{?}]{?} 
\section[{Location based access}]{Location based access}\par
In this case, the Pure Log will record the location of the entities. The Access Log will verify the location for each of such access. The access is granted and the data are made available only to entities located at locations specified by the data owner. 
\section[{Dependability of Logs}]{Dependability of Logs}\par
First, the intruder stores the JARs remotely to disturb auditing mechanism by, corrupting the JAR, or hides it to make the communication not possible for the user. Second, he gets the control of JRE that runs JAR files 
\section[{JARs Availability}]{JARs Availability}\par
To protect offline JARs from the attackers, Cloud Information Accountability provides log harmonizer, which has two main tasks: dealing JAR copies and corrupt logs recovery.\par
Each log harmonizer maintains logger components copies holding similar data items. And the harmonizer being represented as a JAR file does not hold the user's data items for audition, but it allows client and server to communicate with logger components by providing the class file to them. Error correction information received from its logger components are stored by the harmonizer, and using the IBE, decryption key duplicate log records are found out from copies of the people's information JARs. As they are strictly combined with the logger component in a data JAR file, the user's data is copied along with the logger as it is strongly mixed with component. In sequence, the new copy of the logger also holds the old log records with respect to the usage of data in the original data JAR file. Because of old records redundancy is aroused and makes the data unfit for the new copies. The harmonizer merges copies from all log records and presents a clear view to the data owner by removing the redundancy. 
\section[{Log Correctness}]{Log Correctness}\par
To maintain the log records correctly the JRE present in the logger component should not be modified. To check the logger component integrity, we depend on two-step process \hyperref[b0]{[1]}: 1. We repair the JRE before the logger is launched and any kind of access is given, so as to provide guarantees of integrity of the JRE. 2. We insert hash codes, which calculate the hash values of the program traces of the modules being executed by the logger component. This helps us detect modifications of the JRE once the logger component has been launched, and are useful to verify if the original code flow of execution is altered.\par
The system suggests some novel approaches for automatically logging any access to the data in the cloud together with an auditing mechanism. This mechanism allows the data owner to not only audit his content but also enforce strong back-end protection. Moreover, one of the main features of our work is that it enables the data owner to audit even those copies of its data that were made without this knowledge.  \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-2.png}
\caption{\label{fig_0}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-3.png}
\caption{\label{fig_1}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-4.png}
\caption{\label{fig_2}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-5.png}
\caption{\label{fig_3}?}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-6.png}
\caption{\label{fig_4}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-7.png}
\caption{\label{fig_5}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-8.png}
\caption{\label{fig_6}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-9.png}
\caption{\label{fig_7}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-10.png}
\caption{\label{fig_8}}\end{figure}
 			\footnote{© 2013 Global Journals Inc. (US) Year} 			\footnote{© 2013 Global Journals Inc. (US) Year} 			\footnote{© 2013 Global Journals Inc. (US) Year} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Corin et al.]{b7}\label{b7} 	 		‘A Logic for Auditing Accountability in Decentralized Systems’.  		 			R Corin 		,  		 			S Etalle 		,  		 			J I Hartog 		,  		 			G Lenzini 		,  		 			I Staicu 		.  	 	 		\textit{Proc. IFIP TC1 WG1},  				 (IFIP TC1 WG1)  		 	 
\bibitem[Pearson et al. ()]{b15}\label{b15} 	 		‘A Privacy Manager forCloud Computing’.  		 			S Pearson 		,  		 			Y Shen 		,  		 			M Mowbray 		.  		 \url{http://www.ntp.org/,16}  	 	 		\textit{Proc. Int'l Conf. Cloud Computing (CloudCom)},  				 (Int'l Conf. Cloud Computing (CloudCom))  		2009. p. .  		 			NTP: The Network Time Protocol 		 	 
\bibitem[Pearson and Charlesworth ()]{b13}\label{b13} 	 		‘Accountability as a WayForward for Privacy Protection in the Cloud’.  		 			S Pearson 		,  		 			A Charlesworth 		.  	 	 		\textit{Proc. First Int'l Conf. Cloud Computing},  				 (First Int'l Conf. Cloud Computing)  		2009.  	 
\bibitem[Kailar (1996)]{b17}\label{b17} 	 		‘Accountability in Electronic Commerce Protocols’.  		 			R Kailar 		.  	 	 		\textit{IEEE Trans. Software Eng}  		May 1996. 22  (5)  p. .  	 
\bibitem[Chun and Bavier ()]{b4}\label{b4} 	 		‘Decentralized Trust Management and Accountability in Federated Systems’.  		 			B Chun 		,  		 			A C Bavier 		.  	 	 		\textit{Proc. Ann. Hawaii Int'l Conf. System Sciences (HICSS)},  				 (Ann. Hawaii Int'l Conf. System Sciences (HICSS))  		2004.  	 
\bibitem[Ammann and Jajodia (1993)]{b1}\label{b1} 	 		‘Distributed Timestamp Generation in Planar Lattice Networks’.  		 			P Ammann 		,  		 			S Jajodia 		.  	 	 		\textit{ACM Trans. Computer Systems}  		Aug. 1993. 11 p. .  	 
\bibitem[Sundareswaran et al. ()]{b2}\label{b2} 	 		‘Ensuring Distributed Accountability for Data Sharing in the Cloud’.  		 			Anna C Sundareswaran 		,  		 			Squicciarini 		,  		 			Ieee Member 		,  		 			Dan Lin 		.  	 	 		\textit{Proc IEEE transactions on dependable and secure computing},  				 (IEEE transactions on dependable and secure computing)  		2012. 9.  	 
\bibitem[Sundareswaran et al. (2012)]{b0}\label{b0} 	 		‘Ensuring Distributed Accountability for Data Sharing in the Cloud Author’.  		 			Smitha Sundareswaran 		,  		 			Anna C Squicciarini 		,  		 			Ieee Member 		,  		 			Dan Lin 		.  	 	 		\textit{IEEE Transactions on Dependable and Secure Computing}  		July/August 2012. 9  (4) .  	 
\bibitem[Boneh and Franklin ()]{b18}\label{b18} 	 		‘Identity-Based Encryption from theWeil Pairing’.  		 			D Boneh 		,  		 			M K Franklin 		.  	 	 		\textit{Proc. Int'l Cryptology Conf. Advances in Cryptology},  				 (Int'l Cryptology Conf. Advances in Cryptology)  		2001. p. .  	 
\bibitem[Barka and Lakas ()]{b11}\label{b11} 	 		‘Integrating Usage Control with SIP-BasedCommunications’.  		 			E Barka 		,  		 			A Lakas 		.  	 	 		\textit{J. Computer Systems, Networks, and Comm}  		2008. 2008. p. .  	 
\bibitem[Hightower and Borriello (2001)]{b10}\label{b10} 	 		‘Location Systems for UbiquitousComputing’.  		 			J Hightower 		,  		 			G Borriello 		.  	 	 		\textit{Computer}  		Aug. 2001. 34  (8)  p. .  	 
\bibitem[Lin et al. (2004)]{b14}\label{b14} 	 		‘Method for Authenticating a Java Archive (jar) for Portable Devices’.  		 			J H Lin 		,  		 			R L Geiger 		,  		 			R R Smith 		,  		 			A W Chan 		,  		 			S Wanchoo 		.  	 	 		\textit{US Patent}  		July 2004. 6 p. 353.  	 
\bibitem[Chen ()]{b3}\label{b3} 	 		‘Oblivious Hashing: A Stealthy Software Integrity Verification Primitive’.  		 			Y Chen 		.  	 	 		\textit{Proc. Int'l Workshop Information Hiding, F. Petitcolas},  				 (Int'l Workshop Information Hiding, F. Petitcolas)  		2003. p. .  	 
\bibitem[Ateniese et al. ()]{b5}\label{b5} 	 		‘Provable Data Possession at Untrusted Stores’.  		 			G Ateniese 		,  		 			R Burns 		,  		 			R Curtmola 		,  		 			J Herring 		,  		 			L Kissner 		,  		 			Z Peterson 		,  		 			D Song 		.  	 	 		\textit{Proc. ACM Conf. Computer and Comm. Security}  		2007. p. .  	 
\bibitem[Crispo and Ruffo ()]{b9}\label{b9} 	 		‘Reasoning about Accountability within Delegation’.  		 			B Crispo 		,  		 			G Ruffo 		.  	 	 		\textit{Proc. Third Int'l Conf. Information and Comm. Security (ICICS)},  				 (Third Int'l Conf. Information and Comm. Security (ICICS))  		2001. p. .  	 
\bibitem[Security Assertion Markup Language (saml) 2.0 ()]{b6}\label{b6} 	 		\textit{Security Assertion Markup Language (saml) 2.0},  		 \url{http://www.oasis-open.org/committees/tchome.php?wgabbrev=security}  		2012.  		 			OASIS Security Services Technical Committee 		 	 
\bibitem[Jagadeesan et al. ()]{b12}\label{b12} 	 		‘Towards a Theory of Accountability and Audit’.  		 			R Jagadeesan 		,  		 			A Jeffrey 		,  		 			C Pitcher 		,  		 			J Riely 		.  	 	 		\textit{Proc. 14th European Conf. Research in Computer Security (ESORICS)},  				 (14th European Conf. Research in Computer Security (ESORICS))  		2009. p. .  	 
\bibitem[Mather et al. ()]{b19}\label{b19} 	 		‘Towards AccountableManagement of Identity and Privacy: Sticky Policies and Enforceable 21. Tracing Services’.  		 			T Mather 		,  		 			S Kumaraswamy 		,  		 			S Latif ; Mont 		,  		 			S Pearson 		,  		 			P Bramhall 		.  	 	 		\textit{Proc. Int'l WorkshopDatabase and Expert Systems Applications (DEXA)},  				 (Int'l WorkshopDatabase and Expert Systems Applications (DEXA))  		2003. p. .  	 	 (Cloud Security and Privacy: An Enterprise Perspective on Risks and Compliance (Theory in Practice)) 
\bibitem[Holford et al. ()]{b16}\label{b16} 	 		‘Using Self-Defending Objects to Develop Security Aware Applications in Java’.  		 			J W Holford 		,  		 			W J Caelli 		,  		 			A W Rhodes 		.  	 	 		\textit{Proc. 27th Australasian Conf. Computer Science},  				 (27th Australasian Conf. Computer Science)  		2004. 26 p. .  	 
\bibitem[Workshop Formal Aspects in Security and Trust ()]{b8}\label{b8} 	 		\textit{Workshop Formal Aspects in Security and Trust},  				2005. p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
