Standard Implementation in Cloud Forensics PDF
Standard Implementation in Cloud Forensics PDF
net/publication/278849067
CITATION READS
1 361
3 authors, including:
SEE PROFILE
Some of the authors of this publication are also working on these related projects:
All content following this page was uploaded by Mladen Đuro Veinović on 21 June 2015.
Abstract: Apstrakt:
Everyday use of cloud services has exponentially increased primarily Prisutan je porat u svakodnevnoj upotrebi usluga distriburanog
because of its popular price and because it is more convenient than the internet računarstva (Cloud services) pre svega zbog popularne cene
alternative physical computing services. Unfortunately, good marketing i brojnih pogodnosti u odnosu na alternativne usluge fizičkog raču-
and lack of knowledge have lead many companies to enter the cloud narstva. Nažalost, dobar marketing i nedostatak znanja primorali su
without first performing a risk and security analysis. What happens mnoge kompanije da koriste ovakve usluge bez prethodno sprovedene
when the cloud gets compromised is that you suffer a breach, and you procene rizika i bezbednosti. Ukoliko je virtuleno okruženje (oblak)
find yourself in a position of having to conduct digital forensics and kompromitovano, vi snosite štetu, i primorani ste da spovedete digi-
collect some data? What to do then? Is there an option to acquire data? talnu forenzičku istragu i povratite podatake. Šta raditi u tom slučaju?
Do you even know the location of your data? Can you tell if someone Postoji li način da se povrate podaci? Da li znate gde se nalaze vaši
else has access to your data? Is the data located in the cloud service podaci? Da li znate da li još neko ima pristup vašim podacima? Da
provider’s data center or they have a data storage service with the 3rd li se podaci nalaze u bazi podataka u virtulenom okruženju (oblaku)
party? It is recommended to consider these issues before the actual pružaoca usluga ili uslugu čuvanja podataka pruža treća strana? Po-
incident has happened. But what can you actually do? This paper željno je pozabaviti se ovim pitanjima pre nego što do problema zaista
shows the standards that can be implemented in Cloud forensics and dođe. Šta zapravo možemo uraditi? Ovaj rad upućuje na standarde
procedures and contracts that will facilitate analysis on a daily basis. koje možemo primeniti u Cloud forenzici (Cloud forensics) kao i na
procedure koje bi olakšale redovno sprovođenje analize.
Ključne reči:
Key words: Softver kao usluga (SaaS), Platforma kao usluga (PaaS), Infrastruktura
SaaS, PaaS, IaaS, SLA, SLO, ISO 27037. kao usluga (IaaS), SLA, SLO, ISO 27037.
1. INTRODUCTION The end-users do not have control over the physical in-
frastructure such as the network, servers and operating
Cloud computing has become a dominant know- how in systems and do not have control over the source code of
information technology, but with its many exciting features and the application in use. All those things limit customer’s
low price for both enterprises and governments come unique ability to analyze log files and do forensics. Nowadays,
and very serious security challenges. SaaS solutions require that very detailed application logs
Cloud itself presents a multi-tenant environment and highly are implemented on each application in cloud and rely
virtualized environment, where processes for conducting foren- on cloud service providers’ support. Quite often, both
sic investigations are not fully developed and implemented. sides must agree on the details about forensics, which is
called Service Level Agreement (SLA).
In this paper, we shall focus on the analysis of the issues
related to cloud forensics, connecting international standards b) PaaS model represents that the customer controls the
with cloud forensics, and focusing on the current integration of entire development platform and all source code ne-
cloud forensics into service level agreements (SLAs). ver leaves the development platform. Given these cir-
cumstances, the customer has a space to install any fo-
rensic tool and implement forensic options within his
2. FORENSIC REQUIREMENTS own application. Remote log collection servers can be
installed and automatic logging option in applications
Law enforcement agencies and government agencies will can be implement creating a single repository of all logs
require more proactive and reactive forensic support. The Cloud and events, where multiple users can access and read
Service Providers will be obliged to log all the activities and have logs, write-once, read-many (called WORM) principle.
forensic support for all services offered and used by the custo- Although application logs cover all the logging needs
mer. Different service distribution models (Software as a Service of end user, some logs in PaaS deployment cloud mo-
- SaaS, Platform as a Service - PaaS, Infrastructure as a Service del need to be done in cooperation with cloud service
- IaaS) offer basic terms of cloud forensics for everyday users. provider. Nevertheless, the end user is responsible for
a) SaaS model represents a model where the customizati- the functionality of the application, while the cloud ser-
on options and preferences of the customer are limited. vice provider should guarantee that the application is
139
E-mail: [email protected] DOI: 10.15308/Synthesis-2015-139-142
SYNTHESIS 2015 Applied informatics and education
available and operational. In that case, customer needs question life expectancy represents the foundation for digital
to create responsibility boundaries between end- users forensics. Nowadays, evidence mostly exists in the form of the
and cloud service providers when there is a need for fo- volatile data located on the machines, and there is no reason to
rensic data. These responsibilities and boundaries must think that that data will be collected as digital evidence repre-
be documented in SLA between the end-user and cloud senting an important evidence for some case.
service provider.
SLAs may detail some procedures when accessing noti-
fication logs, identification logs, preservation logs, and
access to all potential evidence sources (servers, switches,
routers…).
c) IaaS deployment model, unlike SaaS and Paas, gives the
user the greatest options for configuration along with
great logging features and high level of control. Altho-
ugh end-user controls most of the components of the
system including all log sources, some valuable informa-
tion might only be reached from the inside of the cloud
service provider infrastructure. This triggers the need to
create a SLA between end users and cloud service provi-
ders and devote special attention to forensic data collec- Figure 1: Implementation of ISO standards into the Digital Fo-
tion and logging. rensics process
142
DOI: 10.15308/Synthesis-2015-139-142
View publication stats