2018 4th IEEE International Conference on Big Data Security on Cloud
Big Data Security in Cloud Environment
Yenumula B Reddy
Department of Computer Science; Grambling State University, Grambling, LA 71245, USA
Email: ybreddy@gram.edu; URL: http://www.symbolicscience.com
Abstract - Big data conventionally coins large volume of
data that continuously increases in a real-time basis and difficult
to store, retrieve, and process in traditional database techniques.
But it is necessary to know that big data is unstructured and does
not follow the conventional storage retrieval methods. The
challenges are to store in a cloud, process, and develop
meaningful form so that it is useful to the businesses,
government, and customers. This paper discusses the current
challenges to store, retrieve, process, and implement security
requirements, and possible solutions. We further provide the
security model in a dynamic cloud environment to store,
process and retrieve the data.
KEYWORDs - Big data, cloud computing, big data issues, big data
security, access rights, cloud environment, authentication,
sensitive data.
1. INTRODUCTION
The word big data coined recently and became popular
due to its capabilities for storage (beyond the size of the
standard database), retrieval, analysis, and to produce useful
results. It is an unstructured, vast volume, continuously
growing on a real-time basis, and difficult to process.
Technology changes influence the classification changes of
such data over a period. Therefore, its definition changes time
to time and organization to organization (making it difficult
to have a perfect definition). Every organization has vested
interested in the classification of such unstructured data. As
the technology changed from computers to hand devices, the
processing became a big problem. Due to this reason, cloud
requirement exists. Cloud can store a large volume of data,
complex computations, and generation of customer output.
Cloud requirement for big data must consider its size, a
different type of data from multiple sources, the velocity of
its flow (incoming and outgoing), potential value if properly
classified and processed, and confidentiality. Cloud
computing is a paradigm with unlimited on-demand services.
It can virtualize hardware and software resources, high
processing power, storage, and pay-per-usage. Moreover, it
transfers cost calculation responsibilities to the provider and
minimizes the great setup of computing facilities at small
enterprises. It has negotiable natural resources and gets
978-1-5386-4399-0/18/$31.00 ©2018 IEEE
DOI 10.1109/BDS/HPSC/IDS18.2018.00033
computing power as required. Cloud services provide
infrastructure, software, and platform as services.
Cloud computing allows for the storing and processing of
sizable unstructured volume of continuously generated data,
resource availability, and fault tolerance through its various
hardware and software facilities. Many companies including
Nokia, RedBus, Google, IBM, Amazon, and Microsoft
provide consumers with on-demand services. The big
business decided to migrate to Hadoop distributed file system
(HDFS) that integrates data into one domain and uses
supplicated algorithms to get proper results to customers. The
advantage of using Hadoop is cheaper storage compared to
traditional databases. Currently, HDFS helps Nokia, RedBus,
Google, and other companies to fulfill their needs. The facility
supports these companies to concentrate on their businesses
rather than on technical details and requirements.
Big Data technology solves many problems irrespective
of volume, velocity, and source of generation. It is a
constantly changing technology, and many industries,
customers, and government agencies are involved in its usage
and management. Further, if the data is in a cloud
environment, the user access level management, privacy
policies, user accountability and service provider
accountability comes into the primary responsibility of cloud
management.
Due to this reason, we need to create security policies,
access rights, secure storage, and retrieval methods. Due to
continuously growing of data, control is required to keep the
valuable data. Therefore, we need to enforce data governance
policies like organizational practices, operational practices,
and relational practices.
Disaster recovery (in the case of dangerous accidents
including floods, earthquakes, fire, and accidental loss of
data) for valuable data is a requirement. The big corporations
define a set of procedures for a disaster recovery plan to
restore the data. In addition to security policies, disaster
recovery is strongly recommended (fault-tolerance depends
on disaster recovery). Other issues include the secure transfer
of data to the cloud, incorporating high-performance
computing, and data management. Big data in the cloud has
many research and practical challenges. Storing the data using
encryption technique takes extra time. Standardization of
100
procedures is required to minimize the impact of
heterogeneous data. Data governess, recovery plans, quality
of services for secure transfer of data, and petaflop computing
are some of the problems with implementation.
The successful deployment of big data on cloud requires
building a business case with an appropriate strategic plan to
use the cloud. The project must develop productivity, extract
more significant value, continuous improvement, customer
acquisition, satisfaction, loyalty, and security. Assessment of
a suitable cloud environment (private or public) and
development of a technical approach are also necessary. Next,
address the governance, privacy, security, risk, and
accountability requirements. Finally, the operational
environment can be developed. The provider meets many
challenges depending on the cloud data environment.
Security, cost factor, customer satisfaction, and service
reliability are primary issues.
2. LITERATURE REVIEW
Storage, processing, and retrieval of big data in the cloud
are significant problems in current research. Pedro et al. [1]
studied the overview of present and future issues. The
document discusses scalability and fault tolerance of various
vendors including Google, IBM, Nokia, and RedBus. The
authors further considered the security, privacy, integrity,
disaster recovery, and fault tolerant issues. The review of
current service models, import concepts of cloud computing,
and processing of big data are discussed in [2]. Elmustafa and
Rashid [3] presented the survey issues of big data security in
cloud computing.
Linda et al. [4] showed environmental examples of big
data use in government that includes Environmental
Protection Agency, Department of the Interior, Department of
Energy, and Postal Services. The study consists of the
government open access initiatives, federal data center
consolidation initiative, and enforcement of compliance
online. James [5] presented a roadmap to the success of big
data analytics and applications. The report discusses the
definition and description of unstructured data, relevant use
cases in the cloud, potential benefits, and challenges
associated with deploying in the cloud.
The impact of cloud computing on Healthcare studied in
[6]. The study explores on-demand access to computing and
large storage, supporting big data sets for electronic health
records and the ability to analyze and tracking the health
records. Keeso presented the environmental sustainability of
big data, barriers, and opportunities [7]. This research also
includes new opportunities for partnership based
101
collaboration, sustainability to organizations to big data
efforts, and emerging business models.
Yan et al. [8] discussed the access control in cloud
computing. The paper presents the temporal access control in
cloud computing using encryption techniques. Yuhong et al.
[9] examine data confidentiality in cloud computing. The
article uses the trust-based evaluation encryption model. In
this model, the trust factor decides the access control of user
status. Young et al. [10] discussed the security issues in cloud
computing and described the access control requirements,
authentication and ID management in the cloud.
Ali and Erwin [11] reviewed security and privacy issues
on big data and cloud aspects. They concluded that cloud data
privacy and safety is based on the cloud provider. They also
discussed big data security challenges and cloud security
challenges. Their paper examines the security policy
management and big data infrastructure and programming
models. They did not suggest any particular model but
discussed all possible solutions for the security of big data in
the cloud.
Marcos et al. [12] presented approaches and
environments to carry out big data computing in the cloud.
The paper discusses the visualization and user interaction,
model building, and data management. Venkata et al. [13]
examined issues in a cloud environment for big data. The
primary focus is security problems and possible solutions.
Further, they discussed MapReduce and Apache
environments in the cloud and needed for the security.
Saranya and Kumar [14] addressed the security issues
associated with big data in a cloud environment. They
suggested few approaches for the complicated business
environment. The paper discusses unstructured big data
characteristics, analytics, Hadoop architecture, and real-time
big data analytics. The authors did not present any particular
model in the article. They explained few concepts related to
security in a cloud environment.
Avodele et al. [15] presented issues and challenges for
deployments of big data in the cloud. They suggested
solutions that are relevant to organizations to deploy the data
in the cloud. The authors indicated the importance of
authentication controls and access controls.
Ramgovind and Smith [16] discussed the overall security
perspective and potential of cloud computing. They examined
cloud threats and security requirements including
identification and authentication, authorization,
confidentiality, integrity, non-repudiation, and availability.
They also provided the cloud delivery models for the private,
public and hybrid cloud. They did not develop any model in
this research.
Dimitrios and Dimitrios addressed the cloud computing
security issues [17]. They identified the security requirements
and discussed the viable solution to eliminate the potential
threats. To ensure authentication, integrity, and
confidentiality, they suggested a cryptography-based
solution.
Gai et al. [23 - 25] proposed a cloud-based approach to
secure sensitive data. The model dynamically assigns the data
packet to cloud resources based on security requirements. The
proposed model requires the third party to audit the
verification process. The authors also suggested fully
Homomorphic Encryption for Blend Operations (FHE-BO)
model. It uses tensor laws to carry the computations of blend
arithmetic operations over real numbers. The authors claimed
that the method concurrently deals with the adversarial
hazards and support computations on cipher-text.
The remaining paper discusses the problem formulation
that leads to the authentication model in the cloud in section
3, simulations in section 4, algorithms for access control on
sensitive data in section 5, and conclusions and future work
in section 6.
3. PROBLEM FORMATION
The security model involves the cloud customer data
security at storage, retrieval, transfer, processing, and updates
(insert, modify, delete). The security needs to set at the log
entry at user and cloud level. It also requires the automatic
validation of stored data status and verifies the trust level. The
framework of the proposed model includes the data
encryption, correctness, and processing. These three modes
depend upon the access rights of the user as discussed at the
beginning of the current section. For storage and retrieval of
data the basic encryption techniques AES, RSA, and
steganography model are sufficient. If the data requires
storage and processing the recommendations in [18] may be
useful. The paper discussed the various techniques to search
cipher text and query isolation (avoid the untrusted server).
Controlled searching, dealing with variable word lengths,
searching encrypted index, and support for hidden search is
part of the research. In this paper, the proposed access control
model with encrypted processing data is useful to avoid
untrusted provider and malicious users in the cloud.
The access control model for cloud storage incorporates
the authentication of user and user current access level. The
token identification (TID) is attached as soon as the user login
access in the cloud. The current TID model in equation (1)
explains with seven parameters.
TID = UID, IID, MDT, TA, PA, LGE, SA (1)
Where
UID User identification and access rights
IID Issue Date
MDT Maximum Date (expiration Date)
TA Time of Access
PA Place of Access (current place and node ID)
LGE Log Entry (UID, IID, MDT, TA, PA, LGE)
SA Security Alarm
The user is an owner of the data, or a user may be a
customer. In either case, the user is a client with different
access rights. Once the user logs into cloud network, the
authentication access token connects to the user account. The
token verifies the user’s access limits and allows or denies
appropriate file access. Further, the system does the entries in
user and cloud log table for each attempt of a user to a
particular file with all details. The various validation and
verification check the modifications help find unauthorized
access. The trustworthiness of provider or user can be
calculated using the log values.
The trustworthiness of a user can be calculated using trust
function in equation (2). For each entry of the user, the weight
‘W’ is assigned. The entry Wi,j means, the weight for ith user
௚
and jth entry. Let ܷ‫ܦܫ‬௜ǡ௝ be the user i entered jth time with good
௕
behavior (gj) and ܷ‫ܦܫ‬௜ǡ௝ is the user i entered jth time with bad
behavior (bj). The user trust depends on the number of times
entered in database with good behavior. Each time we
calculate the trusted behavior of the user. The weight will be
increased or decreased depending on the trust credit. As the
trust increases the credit weight increases.
The trustworthiness of a user can be calculated by
multiplying the user entry value with corresponding weight at
good or bad actions. The trustworthiness Ti of ith user
calculated as follows.
¦Tj
i, j = ¦ Wi , j * g j − Wi , j b j
j
(2)
¦T i, j

UIDTi =
j
is equal to
into the system. To maintain the security of data and its trust j
level, we have to define many control parameters to the user
௚ ௕
(ܷ‫ܦܫ‬௜ǡ௝ െ ܷ‫ܦܫ‬௜ǡ௝ )/j

102
 If UIDTi is greater than a set threshold, the user credit can
be approved to access otherwise false alarm alert the security
administrator. The user may be an independent customer or
part of the organization. The weight varies between 0 to 1, and
the number of accesses to the data (or data files) will be 1 to
n (for j n and n is an integer). If the user is good then g value
is 1 and b value is 0; otherwise, b=1 and g=0 which means
that the user crosses the access limits or user is a hacker.
Figure 1 represents a good user with successful attempts
to the database. The user has one failed attempt, and
remaining attempts are successful. This result shows that the
user is in good standing. Figure 2 shows the bad user
attempting to retrieve or access to the database. After nine (9)
attempts the user got success on the 10th try. The situation
created in the current program is not acceptable. If we
generate an alarm after three (3) failed attempts, the user will
be locked and reported to the security manager. Therefore, to
separate the bad user from good some policies are required in
the cloud database.
Figure 1: Good standing user for 10 continuous
attempts
Figure 2. Bad user or hacker; after 9 fail attempts got
success in 10th attempt.
The equation (2) does not include issue date of user ID,
expiration date, time of access, place of access, or other
parameters. These controls will be discussed in Section 5.
103
4. SECURITY OF CLOUD DATA
As the data increases, resources requires new
mechanisms that enable cost-effective management while
guaranteeing critical features like privacy and security. The
challenges arise from the redistribution of responsibilities
across cloud supply chains. The cost-effective resource is a
cloud. Moving the data to cloud arises many questions.
• Who can access the data and how it will be used
• The initial requirements, risks, and accountability
• Reliability to detect the incidents
• Control of each customer access
The access control of cloud data can be managed using
group key management system [16 – 18]. The authors in [22]
described the logical key hierarchy (LKH) protocol. In LKH
each member stores log2 (n) + 1 keys. In the traditional LKH
protocol, as the number of members increases the keys also
increase.
In the proposed model, each customer is assigned a key
with appropriate access limits concerning storing, updating,
retrieving, and processing. Depending on the sensitivity of the
information, we incorporate the time and place. The model
was provided in equation (1). Equation (2) helps the trust of
the customer to the cloud data.
5. ACCESS CONTROLS ON SENSITIVE DATA
Access to sensitive data cannot satisfy pure
trustworthiness. Along with honesty, the procedure requires
the user access limits, day, time of the day, and log entry for
validation. The UID contains access rights & user ID issue
date, expiration date, time of access, and location of access
(depends upon sensitiveness of data). Once the user logs into
the system, the cloud log and owner logs are automatically
registered entries. For hackers, only cloud log entry appears.
The various validation and verification checks reveal the
hacking. The token ID parameters in equation (1) is used in
objective function G.
G = {N , A, D,U} (3)
The objective function G replaces TID, N replaces UID
(contains IID, MDT, TA, and PA), D is a data file (or
database), and U replaces LGE. The security alarm will be
activated depending upon the hacker identification or trust
failure. Therefore the parameters are explained further as
below.
N the set of users (n1 , n2 ,.....nm )
A set of access rights (a1 , a2 ,.....a p )
 D set of allowed resources in file or database hui ⊇ ui + h ' di ( ui internal user), alarms security
(d1 , d 2 ,.....d q ) manager about internal hacker.

U the result of the query and log entries for verification

If Q(ni ,d i) ⊂ ui then exit;
and validation. else
Once the authenticated user ni (ni ∈ N ) logs into cloud if Q(ni ,d i) ⊄ ui & &Q(ni ,d i) ≅ hui then
environment, the cloud service attaches a service token to a
resource within its domain with a set of access types ai . The convert Q(ni ,d i) as Q(ni , hd i) and generate
limitation helps to control the user for resource access. For
every service requested by the user, the system generates a set
hui ⊇ ui + h d i '

of access permissions to the resources. The services required

should not exceed the user access limits. If the resource Store the user utility hui that contains ui + h' di and
requirements are outside the user boundaries, then the system inform security and keep the counter (log) in alert for further
alarms the security and denies the request. Whereas hacker is attempts.
a user that does not have any role in the system. An authorized
user will be treated as a hacker if the user tries to access The Algorithm 1 helps to detect the hacker if the user tries
unauthorized information. For example, the healthcare staff to gain the information with unauthorized access from the
member may be considered as an intruder if the user accesses database. The following query and Table I explains the
unauthorized data or misuses (for instance, printing and unauthorized access to information.
forwarding) the authorized information
If Q ( ni ,d i) ≡ Q ( hn i , d i ) ⊄ u i
In the proposed cloud environment the user with
complete authorization access is called a super user (S). The or
super user ‘S’ possesses access rights of all users S ⊇ * ai
i =1, n Q(hni , di ) ≈ hui
where ⊇ means contains. All accesses of super user on the
then
database must be recorded. The user that does not have

authorization to resource (s) is called hacker ( hi ) and Q(hni , di ) = hui , retrieve hui (utility from the Hacker
alarm to database) and alert the security alarm.
represented as H ( hi ∈ H ) and ∀H (hackers) the access
where hui is available in log or identified as a new hacker and
rights aih 6 di ≡ φ is true; aih is access rights of the logged as new entry. The log is provided in Table I.
hackers ( 6 implication to, and ≡ is equivalent to). Using
this information, we design two algorithms. Table I. User Log and Action
Algorithm 1: User Status Result Action
The successful user login includes the access rights to the
data. Any query generated by the user will be verified with ࢛૚ First Not available in Identified as
access rights for access and return results. time log enter as ݄‫ݑ‬ଵ new hacker,
login alarm
If the query Q ( ni , d i ) matches the ni as owner for token
identification (TokenID), then the corresponding utility ࢛૛ Repeated Available in log Alarm and
function ui will be generated, else the query reflects as login as ݄‫ݑ‬ଶ freeze
Q(ni , hd i) , where h is a hacker.
࢛૜ Internal Unauthorized Alarm and
User access freeze
If the hacker is an internal user then

104
 There is a chance that the hacker attempts to gain access
to database through various attempts at different trimming.
Trying to varying timings in a day can mislead the
implemented procedure of the log. If the log has user access
details with timings and attempts to gain access to the
database, then it will be easy to lock the hacker. Therefore,
the time attribute plays a vital role in detecting the hacker. The
Algorithm 1 needs to be modified with time attribute for the
detection of unauthorized smart users. The time and day
attributes are incorporated in Algorithm 1 and presented as
Algorithm-2.
Algorithm 2
The input to the algorithm is log entry. Once the user enters
then log will be created and related history will be
incorporated for analysis of user.
If Q(ni , ti ,d i) is genuine and attempted during duty times
then corresponding utility function ui will be generated,
else the query reflects as Q(ni , t j , hd i) then user will get
where hui is available in log or identified as a new hacker and
logged as a new entry. Table II provides the log entries.
Depending upon the security level, the Algorithm-2 will
be modified by adding the terminal type and log-on timings.
Terminal type and time of access attributes along with access
type attributes will protect the secret and top secret
information.
The real world applications include healthcare
environment, university grading system, financial systems and
critical infrastructure including chemical and defense. The
healthcare environment is discussed briefly.
Let us assume the hospital environment in the healthcare
system. A doctor and nurse have same access rights to
individual patient data (doctor prescribes the medicine and
implemented by the nurse). Then the attributes patient id, type
of medication, and scheduled time dose to be given to a patient
are accessible by the nurse. The same attributes are also
available to the doctor. Therefore, the system security
depends upon the merge and decomposition of two or more
users.

hui ⊇ ui + h'di (where ui is internal user information TABLE II. HACKER LOG AND DETECTION

and h ' d i is the hacker alarm at time t j ). User Status Time and Result Action
access limits

If Q(ni , ti ,d i) ⊂ ui then exit (user access accepted) ࢛૚ Internal Access Internal hacker Freeze
User outside access and alarm
else limits

if (Q(ni , t j ,d i) ⊄ ui ) & &(Q(ni , t j ,d i) ≅ hui ) ࢛૛ Repeated Access Verify the Alarm and
login outside time and log freeze
bounds and entries and
Convert Q(ni , t j ,d i) as Q ( ni , t j , hd i) and generate different identified as
times of the internal hacker
hui ⊇ ui + h ' d i (alarm alert to Security manager) day

ui + h' di and ࢛૜ New No log entries Unauthorized Alarm

Note: Store the user utility hui that contains User and try to access
alert security and keep the counter for further attempts. gain access

If the hacker is external then divert to the KDS. If the user

hacks with authentication then the time stamp will help to
detect the hacker. For example,
If Q(ni , t j ,d i) ≡ Q(hni , t j , di ) ⊄ ui or ⊆ hui
then
Q(hni , t j , di ) = hui , retrieve hui , and alarm the security;
6. CONCLUSIONS
The recent issues and challenges were discussed in big
data in the cloud [18] and other related papers [8-15, 19-25].
After evaluation of recent developments, it may be concluded
that it is necessary to develop a trust and access control
methodology in a cloud environment for big data processing.
Therefore, in the current research, an objective function was
proposed with a set of users, associated access rights,
resources and return result verification. The proposed model

105
is appropriate for storage, processing, and retrieval of big data
in a cloud environment. Further, two algorithms were
presented to detect the external and internal hackers in a cloud
environment. The tables provided the idea of log analysis to
identify the internal and external hackers. The user entry logs,
authentication, and access rights have a significant role in
providing the hacker information to the security
administrator.
Future work may improve the algorithms to protect
sensitive data in business and government through access
rights in a cloud environment. Further, incorporating
honeypots may be helpful to mislead the malicious users and
hackers at sensitive data places.
ACKNOWLEDGEMENTS
The research work was supported by the CMAST
program funded by NSF through award number 1719523 and
Department of Education P031B150020 - Title III
Cybersecurity. The author wishes to express appreciation to
Dr. Connie Walton, Director Sponsored programs at
Grambling State University and PI of NSF Big Data grant for
her continuous support. The author also wishes to appreciation
to Dr. Stacy Duhon, Dean, College of Arts and Sciences for
continuous encouragement.
REFERENCES
[1] Pedro Calderira Neves, Bradley Schmerl, Jorge Bernardino, and Javier
Camara., “Big Data in Cloud Computing: Features and Issues”,
International Conference on Internet of Things and Big Data, Jan 2016
[2] Richard Branch, Heather Tjeerdsma, Cody Wilson, Richard Hurley,
and Sabine McConnell., “Cloud Computing and Big Data: A Review
of Current Service Models and Hardware Perspectives”, Journal of
Software Engineering and Applications, 2014, 7, 686-693.
[3] Elmustafa Sayed Ali Ahmed and Rashid A. Saeed., “A Survey of Big
Data Cloud Computing Security”, International Journal of Computer
Science and Software Engineering (IJCSSE), vol 3, issue 1, December
2014, pp. 78-85.
[4] Linda K. Breggin, et al.(editors). “Big Data, big challenges in
Evidence-based policy making”, 2014, West Academic Press.
[5] James Kobielus., “Deployment in Big Data Analytics Applications to
the Cloud: Road Map for Success”, Cloud Standards Customer
Council, Technical report, 2014.
[6] “Impact of cloud computing on Healthcare, Version 2.0”, Cloud
Standards Customer Council, Technical Report, February 2017.
[7] Alan Keeso., “Big Data and Environmental Sustainability: A
Conversation Starter”, Smith School Working Paper series, working
paper 14-04, 2014.
[8] Yan Zh., Hongxin Hu, Gail-Joon Ahn, Dijiang Huang, and Shanbiao
Wang., ”Towards Temporal Access Control in Cloud Computing”,
Proceedings of IEEE INFOCOM, 2012.
106
[9] Yuhong Liu, Jung Ryoo, and Syed Rizvi., “Ensuring Data
Confidentiality in cloud Computing: An Enryption and Trust-based
Solution”, Proceedings of IEEE 23rd Wireless and Optimal
Communication Conference (WOCC), 2014.-
[10] Young-Gi Min, Hyo-Jin Shin, and Young Hwan Bang., “Cloud
Computing Security Issues and Access Control Solutions”, Journal of
Engineering, 9, 2, 2012.
[11] Ali Gholami and Ervin Laure., “Big Data Security and Privacy Issues
in the Cloud”, Int. J. of Network Security & its Applications (IJNSA),
vol. 8, No.1, Jan 2016, pp. 59-79.
[12] Marcos D. Asuncao, Rodrigo N. Calheiros, Silvia Bianchi, Marco A.
S. Netto, and Rajkumar Buyya., “Big Data Computing and Clouds:
Trends and future directions”, J. parallel Distributed Computing, 79-
80, 2015, pp.3 15.
[13] Venkata Narasimha Inukollu, Sailaja Arsi, and Srinivasa Rao Ravuri.,
“Security Issues Associated with Big Data in Cloud Computing”, Int.
J. of Netork Security & its Applications (IJNSA), Vol. 6, N0.3, May
2014, pp. 45-56.
[14] R. Saranya and V. P. Muthukumar., “Security issues associated with
big data in cloud computing”, Int. J. of multidisciplinary and
development, vol. 2, issue.4, April 2015, pp. 580-585.
[15] Avodele, O., Izang A. A., Kuyoro. S. O., and Osisanwo, F.Y., “Big
Data and Cloud Computing Issues”, Int. J. of Computer Applications
(0975 – 8887), vol 133, no.12, Jan 2016, pp.14 – 19.
[16] Ramgovind, S., and Smith, E., “The Management of Security in Cloud
Computing”, IEEE Information Security for South Africa (ISSA),
2010.
[17] Dimitrios Z., and Dimitrios, L., “Addressing cloud computing security
issues”, Future Generation Computer Systems 28 (2012) 583–592
[18] Dimitrios, Zissis. And Dimitrios, L., “Addressing cloud computing
security issues”, Future Generation Computer Systems, 28 (2012)
583–592.
[19] Dawn, x. S., David, W. and Adrian, P., “Practical Techniques for
Searches on Encrypted Data”, IEEE Symposium on Security and
Privacy, 2000, pp. 44-55.
[20] Jangala Sasi Kiran, M. Sravanthi, K. Preethi, and M. Anusha., “Recent
Issues and Challenges on Big Data in Cloud Computing”,
IJCCCSSST, Vol.6, issue.2, June 2015, pp. 98-102.
[21] Shehnila Z., Najeed A. K., and Mohsin Ali Memon., “Systematic
Analysis of Risks in Cloud Architecture”, Int. J. computer Science and
Information Security (IJCSIS), vol. 14, no.11, November 2016.
[22] D Wallner, E. Harder, and R. Agee, “Key Management for Multicast:
Issues and Architectures”, RFC 2627, June 1999.
[23] K. Gai, L. Qiu, M. Chen, H. Zhao, and M. Qiu., "SA-EAST: security-
aware efficient data transmission for ITS in mobile heterogeneous
cloud computing", ACM Transactions on Embedded Computing Systems,
Vol. 16, No. 2, Article 60, Publication date: January 2017.
[24] K. Gai and M. Qiu., "Blend Arithmetic Operations on Tensor-based
Fully Homomorphic Encryption Over Real Numbers", IEEE
Transactions on Industrial Informatics, December 2017.
[25] K. Gai, M. Qiu,and H. Zhao., "Privacy-Preserving Data Encryption
Strategy for Big Data in Mobile Cloud Computing", IEEE
Transactions on Big Data, May 18, 2017.