Scenario-Based Digital Forensics Challenges in Cloud Computing
Abstract
:1. Introduction
- Summary of ISO/IEC 27000-series.
- Survey of recent literature in the topic.
- Description of the challenges with a hypothetical scenario.
- Classification of the challenges in technical, legal and architectural issues.
- Solutions for the challenges investigators face.
2. Background
2.1. Digital Forensics
- Criminal Damage cases include damage of another’s belongings and threats to destroy property [4].
- Industrial Espionage includes patents, inventions and trade secret theft, which is a highly profitable crime.
- Financial Investigations are usually related to economic matters like money laundering and credit card or insurance fraud.
- Corporate Policy Violation includes email abuse, misconduct and employment termination investigations.
- Child Abuse cases are criminal offences such as child grooming and possession of indecent child media content.
- “Defence-in-depth” is an approach to network security. The ability of performing forensic investigations can enhance the overall integrity and survivability of a business infrastructure [2].
2.2. Forensic Investigation Types
2.3. Challenges
● Legal and Administrative Issues
● Technical Issues
2.4. Investigation Activities
- Plan: A scenario-based planning approach tailored to the investigators needs is recommended. The idea is to plan scenarios that investigators might face.
- Prepare: Forensic practitioners should put all essential services in place in order to support future cases. This includes preparing tools, techniques and safeguards.
- Respond: This is when the incident has happened and the forensic practitioners start determining the scope of the event like what the situation is, the nature of the case and its details. This step is important because helps determining the characteristics of the incident and defining the best approach to carry out the investigation.
- Identify: Here is where the investigators start gathering information about the specific event or incident. Notes describing the systems to be analysed, their network position and general configurations may be taken at this stage.
- Collect: This third step, after the incident has been identified, aims to maximise the collection of evidence as well as minimising the impact to the victim. Recording of the scene is also included on this step.
- Acquire: The most important task here is to maintain the integrity of the evidence and provide assurance that the evidence has not been changed. This is carried out by maintaining a chain of custody of all evidence, ensuring that they have been collected and protected by legally acceptable processes.
- Preserve: Isolation, securing and preservation of the original evidence is comprised in this step. The main aim is to prevent any cross-contamination.
- Understand: In this step, investigators need to determine the significance of reconstructed data and draw conclusions.
- Report: Here a summary, explanation of findings and conclusions are reported. The reports should be written such that they are legally admissible. In addition, a 3rd forensic investigation team should reach the same conclusions following the investigation steps in the report.
- Close: In the last step, practitioners need to ensure evidence is returned to rightful owner or securely stored if needed.
2.5. ISO/IEC Standards
2.6. Cloud Computing
- Software as a Service (SaaS): Providers offer access to their applications that are hosted on their own servers and consumers make use of them [22]. Common examples include file storage, social networking and email.
- Infrastructure as a Service (IaaS): Consumers buy raw computing and storage space and they can control and manage the underlying infrastructure like the operating systems, software and network [22]. Examples are Amazon EC2 and Rackspace Cloud Services.
2.7. The Trouble with Cloud Forensics
2.8. Defining What Constitutes a Challenge
3. Related Work
4. Case Study
Snake Jailbird is a criminal who traffics with stolen goods and sells them on a website hosted in a cloud provider. He pays his cloud provider, Krusty Cloud, with different stolen credit cards. Police have learnt about the website and need to prosecute the criminal.
- ●
- Respond: Here forensic practitioners start determining the scope of the event.Action: PC Wiggum has already been briefed on the case and the details. He knows the investigation will need to be carried out in a cloud environment and as such the first thing to do is to find out where Krusty Cloud is registered to confirm if he has jurisdiction to investigate the case. Then, he will need to apply for a search warrant.
- ○
- Challenge: Extraterritorial Jurisdiction (ETJ)
- ●
- Identify: Here is where the investigators start gathering information about the specific event or incident.Action: PC Wiggum needs to take notes of the systems to be analysed, their configuration and networks. However, he might not have physical access to the systems and may need to rely on the competence of the cloud staff.
- ○
- Challenge: No physical access
- ●
- Collect: In this step, practitioners aim to maximise the collection of evidence as well as minimising the impact to the victim.Action: PC Wiggum has requested Krusty Cloud for cooperation and now he needs to locate the data to start collecting it. However, data collection in cloud cases comes with many challenges.
- ○
- Challenge: Data Location and Collection
- ●
- Acquire: The most important task here is to maintain the integrity of the evidence and provide assurance that the evidence has not been changed while it is being acquired.Action: PC Wiggum needs to start acquiring the identified evidence without compromising or contaminating it.
- ○
- Challenge: Massive volume of data
- ●
- Preserve: Isolation, securing and preservation of the original evidence is comprised in this step. The main aim is to prevent any cross-contamination.Action: The collected evidence needs to be protected from any contamination. PC Wiggum must ensure that the original evidence is not altered in any way.
- ○
- Challenge: Make a forensic copy
- ●
- Understand: In this step investigators need to determine the significance of reconstructed data and draw conclusions.Action: Now that PC Wiggum has the evidence, he needs to examine it and draw conclusions. However, he will need to decrypt files and recover any deleted data.
- ○
- Challenge: Recovery of deleted data
- ●
- Report: Here, a summary, explanation of findings and conclusions are reported.Action: PC Wiggum needs to produce investigation reports including what he has found and his conclusions. Additionally, he needs to include his investigation steps so a reviewer can come to the same conclusion. Once he has everything ready, he needs to bring his findings to court.
- ○
- Challenge: Investigation report
- ●
- Close: In the last step, practitioners need to ensure evidence is returned to rightful owner or securely store if neededAction: PC Wiggum might need to return any seized evidence and securely delete or store as needed.
- ○
- Challenge: Evidence return and Secure deletion
5. Results
6. Discussion
7. Future Work
8. Conclusions
Acknowledgments
Author Contributions
Conflicts of Interest
References
- McKemmish, R. What Is Forensic Computing? Australian Institute of Criminology: Canberra, Australia, 1999.
- United States Computer Emergency Readiness Team (US-CERT), Computer Forensics. Available online: https://www.us-cert.gov/sites/default/files/publications/ forensics.pdf (accessed on 14 May 2016).
- Kruse, W.G., II; Heiser, J.G. Computer Forensics: Incident Response Essentials, 14th ed.; Pearson Education: Indianapolis, IN, USA, 2010. [Google Scholar]
- UK Legislation, Criminal Damage act 1971. Available online: http://www.legislation.gov.uk/ukpga/1971/48/contents (accessed on 8 May 2016).
- Sridhar, N.; Bhaskari, D.L.; Avadhani, P.S. Plethora of cyber forensics. Int. J. Adv. Comput. Sci. Appl. 2011, 2, 110. [Google Scholar] [CrossRef]
- Council of the European Union. ENFOPOL 413 COPEN 342. Available online: http://register. consilium.europa.eu/doc/srv?l=EN&f=ST%2017537%202011%20INIT (accessed on 21 May 2016).
- International Organization for Standardization, ISO/IEC 27000:2016. Available online: http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?csnumber=66435 (accessed on 18 May 2016).
- TOR Project. Available online: https://www.torproject.org/ (accessed on 11 May 2016).
- Metasploit. Available online: https://www.metasploit.com/ (accessed on 11 May 2016).
- Al Fahdi, M.; Clarke, N.L.; Furnell, S.M. Challenges to digital forensics: A survey of researchers & practitioners attitudes and opinions. In Proceedings of the Information Security for South Africa, Johannesburg, South Africa, 14–16 August 2013; pp. 1–8.
- ISO/IEC 27037:2012. Guidelines for Identification, Collection, Acquisition and Preservation of Digital Evidence; The International Organization for Standardization (ISO); The International Electrotechnical Commission (IEC) ISO/IEC: Geneva, Switzerland, 2012. [Google Scholar]
- ISO/IEC 27042:2015. Guidelines for the Analysis and Interpretation of Digital Evidence; The International Organization for Standardization (ISO); The International Electrotechnical Commission (IEC) ISO/IEC: Geneva, Switzerland, 2015. [Google Scholar]
- ISO/IEC 27041:2015. Guidance on Assuring Suitability and Adequacy of Incident Investigative Method; The International Organization for Standardization (ISO); The International Electrotechnical Commission (IEC) ISO/IEC: Geneva, Switzerland, 2015. [Google Scholar]
- International Organization for Standardization, about ISO. Available online: http://www.iso.org/iso/home/about.htm (accessed on 17 June 2016).
- ISO/IEC 27038:2014. Specification for Digital Redaction; The International Organization for Standardization (ISO); The International Electrotechnical Commission (IEC) ISO/IEC: Geneva, Switzerland, 2014. [Google Scholar]
- ISO/IEC 27040:2015. Storage Security; The International Organization for Standardization (ISO); The International Electrotechnical Commission (IEC) ISO/IEC: Geneva, Switzerland, 2015. [Google Scholar]
- ISO/IEC 27043:2015. Incident Investigation Principles and Processes; The International Organization for Standardization (ISO); The International Electrotechnical Commission (IEC) ISO/IEC: Geneva, Switzerland, 2015. [Google Scholar]
- Grispos, G.; Storer, T.; Glisson, W.B. Calm before the storm: The Challenges of cloud computing in digital forensics. Int. J. Digit. Crime Forensics 2012, 4, 28–48. [Google Scholar] [CrossRef]
- Catteddu, D. Cloud computing: Benefits, risks and recommendations for information security. In Web Application Security; Springer: Berlin/Heidelberg, Germany, 2010; p. 17. [Google Scholar]
- Armbrust, M.; Fox, A.; Griffith, R.; Joseph, A.D.; Katz, R.H.; Konwinski, A.; Lee, G.; Patterson, D.A.; Rabkin, A.; Stoica, I.; et al. Above the Clouds: A Berkeley View of Cloud Computing; University of California at Berkeley: Berkeley, CA, USA, 2009. [Google Scholar]
- Bush, G.W. USA Patriot Act 2001 (H.R. 3162); The U.S. Congress: Washington, DC, USA, 2001; pp. 107–156.
- Mell, P.; Grance, T. The NIST definition of cloud computing. Commun. ACM 2010, 53, 50. [Google Scholar]
- Google, Google App Engine Documentation. Available online: https://cloud.google.com/appengine/docs (accessed on 5 May 2016).
- Microsoft, Microsoft Azure. Available online: https://azure.microsoft.com/en-gb/ (accessed on 5 August 2016).
- Eurostat, Cloud Computing-Statistics on the Use by Enterprises. Available online: http://ec.europa.eu/eurostat/statistics-explained/index.php/Cloud_computing_-_statistics_on_the_use_by_enterprises (accessed on 18 May 2016).
- Amazon, Quarterly Results. Available online: http://phx.corporate-ir.net/phoenix.zhtml?c= 97664&p=irol-reportsother (accessed on 18 May 2016).
- Martini, B.; Choo, K.-K.R. Cloud forensic technical challenges and solutions: A snapshot. IEEE Cloud Comput. 2014, 1, 20–25. [Google Scholar] [CrossRef]
- Ruan, K.; Carthy, J.; Kechadi, T.; Baggili, I. Cloud Forensics Definitions and Critical Criteria for Cloud Forensic Capability: An Overview of Survey Results. Digit. Investig. 2013, 10, 34–43. [Google Scholar] [CrossRef]
- Alqahtany, S.; Clarke, N.; Furnell, S.; Reich, C. Cloud forensics: A review of challenges, solutions and open problems. In Proceedings of the 2015 International Conference on Cloud Computing (ICCC), Riyadh, Saudi Arabia, 27–28 April 2015; pp. 1–9.
- Zawoad, S.; Hasan, R. Cloud Forensics: A Meta-Study of Challenges, Approaches, and Open Problems. Available online: https://arxiv.org/abs/1302.6312 (accessed on 5 February 2013).
- Quick, D.; Martini, B.; Choo, K.-K.R. Cloud Storage Forensics; Syngress Publishing: Amsterdam, The Netherlands, 2013. [Google Scholar]
- Ab Rahman, N.H.; Cahyani, N.D.W.; Choo, K.-K.R. Cloud incident handling and forensic-by-design: Cloud storage as a case study. Concurr. Comput. Pract. Exp. 2016, in press. [Google Scholar] [CrossRef]
- Quick, D.; Choo, K.-K.R. Forensic collection of cloud storage data: Does the act of collection result in changes to the data or its metadata? Digit. Investig. 2013, 10, 266–277. [Google Scholar] [CrossRef]
- Daryabar, F.; Dehghantanha, A.; Choo, K.-K.R. Cloud storage forensics: MEGA as a case study. Aust. J. Forensic Sci. 2016, 1–14. [Google Scholar] [CrossRef]
- Quick, D.; Choo, K.-K.R. Big forensic data reduction: Digital forensic images and electronic evidence. Clust. Comput. 2016, 19, 723–740. [Google Scholar] [CrossRef]
- Cahyani, N.D.W.; Martini, B.; Choo, K.-K.R.; Al-Azhar, A.K.B.P. Forensic data acquisition from cloud-of-things devices: Windows smartphones as a case study. Concurr. Comput. Pract. Exp. 2016, in press. [Google Scholar] [CrossRef]
- Do, Q.; Martini, B.; Choo, K.-K.R. A cloud-focused mobile forensics methodology. IEEE Cloud Comput. 2015, 2, 60–65. [Google Scholar] [CrossRef]
- National Institute of Standards and Technology (NIST). Cloud Computing: Forensic Science Challenges; NIST Cloud Computing Forensic Science Working Group Information Technology Laboratory: Gaithersburg, MD, USA, 2014. [Google Scholar]
- Teing, Y.-Y.; Dehghantanha, A.; Choo, K.-K.R.; Yang, L.T. Forensic investigation of P2P cloud storage services and backbone for IoT networks: BitTorrent Sync as a case study. Comput. Electr. Eng. 2016, in press. [Google Scholar] [CrossRef]
- Stigall, D.E. Ungoverned spaces, transnational crime, and the prohibition on extraterritorial enforcement jurisdiction in international law, Notre Dame J. Int’l & Comp. L. 1, 2013. Available online: http://ssrn.com/abstract=2211219 (accessed on 5 August 2016).
- Regulation (EC) No 44/2001. 2000. Available online: http://eur-lex.europa.eu/LexUriServ/ LexUriServ.do?uri=CELEX:32001R0044:en:HTML (accessed on 5 August 2016).
- Doyle, C. Extraterritorial Application of American Criminal Law; DIANE Publishing: Collingdale, PA, USA, 2010. [Google Scholar]
- Dykstra, J. Seizing electronic evidence from cloud computing environments. In Cybercrime and Cloud Forensics: Applications for Investigation Processes; IGI Global: Hershey, PA, USA, 2013; pp. 156–185. [Google Scholar]
- Dykstr, J.; Sherman, A.T. Acquiring forensic evidence from infrastructure-as-a-service cloud computing: Exploring and evaluating tools, trust, and techniques. Digit. Investig. 2012, 9, S90–S98. [Google Scholar] [CrossRef]
- Ghemawat, S.; Gobioff, H.; Leung, S.-T. The Google file system. ACM SIGOPS Oper. Syst. Rev. 2003, 37, 29–43. [Google Scholar] [CrossRef]
- Damshenas, M.; Dehghantanha, A.; Mahmoud, R.; Shamsuddin, S.B. Forensics investigation challenges in cloud computing environments. In Proceedings of the 2012 International Conference on Cyber Security, Cyber Warfare and Digital Forensic (CyberSec), Kuala Lumpur, Malaysia, 26–28 June 2012; pp. 190–194.
- Peng, J.; Choo, K.-K.R.; Ashman, H. User profiling in intrusion detection: A review. J. Netw. Comput. Appl. 2016, 72, 14–27. [Google Scholar] [CrossRef]
- Mahdian, B.; Saic, S. Using noise inconsistencies for blind image forensics. Image Vis. Comput. 2009, 27, 1497–1503. [Google Scholar] [CrossRef]
- Sindhu, K.K.; Meshram, B.B. Digital forensics and cyber crime datamining. J. Inf. Secur. 2012, 3, 196–201. [Google Scholar] [CrossRef]
- De Vel, O.; Anderson, A.; Corney, M.; Mohay, G. Mining e-mail content for author identification forensics. SIGMOD Rec. 2001, 30, 55–64. [Google Scholar] [CrossRef]
- The New York criminal law blog, criminal found via facebook. Available online: http://newyorkcriminallawyersblog.com/2010/03/assault-criminal-who-was-found-via-facebook-is-back-in-ny.html (accessed on 19 May 2016).
- Chung, H.; Park, J.; Lee, S.; Kang, C. Digital forensic investigation of cloud storage services. Digit. Investig. 2012, 9, 81–95. [Google Scholar] [CrossRef]
- Wen, Y.; Man, X.; Le, K.; Shi, W. Forensics-as-a-service (FaaS): Computer forensic workflow management and processing using cloud. In Proceedings of the Fourth International Conference on Cloud Computing, GRIDs, and Virtualization, Valencia, Spain, 27 May–1 June 2013; pp. 208–214.
- van Baar, R.B.; van Beek, H.M.A.; van Eijk, E.J. Digital forensics as a service: A game changer. Digit. Investig. 2014, 11, S54–S62. [Google Scholar] [CrossRef]
- Giannelli, P.C. Chain of custody and the handling of real evidence. Am. Crim. Law Rev. 1982, 20, 527–568. [Google Scholar]
- Birk, D.; Wegener, C. Technical issues of forensic investigations in cloud computing environments. In Proceedings of the 2011 IEEE Sixth International Workshop on Systematic Approaches to Digital Forensic Engineering (SADFE), Oakland, CA, USA, 26 May 2011; pp. 1–10.
- Citrix, xenserver: Understanding snapshots. Available online: http://support.citrix.com/article/CTX122978 (accessed on 2 August 2016).
- Proxmox, live snapshots. Available online: https://pve.proxmox.com/wiki/Live_Snapshots (accessed on 2 August 2016).
- VMware, understanding virtual machine snapshots. Available online: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015180 (accessed on 2 August 2016).
- Roussev, V.; McCulley, S. Forensic analysis of cloud-native artifacts. Digit. Investig. 2016, 16, S104–S113. [Google Scholar] [CrossRef]
- Google, security. Available online: https://support.google.com/work/answer/6056693?hl=en (accessed on 1 August 2016).
- Peng, J.; Choo, K.-K.R.; Ashman, H. Bit-level n-gram based forensic authorship analysis on social media: Identifying individuals from linguistic profiles. J. Netw. Comput. Appl. 2016, 70, 171–182. [Google Scholar] [CrossRef]
- Ruan, K. Cybercrime and Cloud Forensics: Applications for Investigation Processes: Applications for Investigation Processes; IGI Global: Hershey, PA, USA, 2012. [Google Scholar]
- Jones, R. Safer Live Forensic Acquisition; University of Kent: Canterbury, UK, 2007. [Google Scholar]
- Norouzizadeh Dezfouli, F.; Dehghantanha, A.; Eterovic-Soric, B.; Choo, K.-K.R. Investigating social networking applications on smartphones detecting Facebook, Twitter, LinkedIn and Google+ artefacts on Android and iOS platforms. Aust. J. Forensic Sci. 2016, 48, 469–488. [Google Scholar] [CrossRef]
- Quick, D.; Choo, K.-K.R. Big forensic data management in heterogeneous distributed systems: Quick analysis of multimedia forensic data. Softw. Pract. Exp. 2016, in press. [Google Scholar] [CrossRef]
- Martini, B.; Choo, K.-K.R. Remote programmatic vCloud forensics: A six-step collection process and a proof of concept. In Proceedings of the 2014 IEEE 13th International Conference on Trust, Security and Privacy in Computing and Communications, Beijing, China, 24–26 September 2014; pp. 935–942.
- INTERPOL, member countries. Available online: http://www.interpol.int/Member-countries/World (accessed on 4 August 2016).
Standard | Description | Activity |
---|---|---|
27037 [11] | Guidelines for identification, collection and/or acquisition and preservation of digital evidence | Respond, Identify, Collect, Acquire, Preserve |
27038 [14] | Specification for digital redaction | Report, Close |
27040 [15] | Storage security | Collect, Preserve, Close |
27041 [12] | Guidance on assuring suitability and adequacy of investigation methods | All activities |
27042 [16] | Guidelines for the analysis and interpretation of digital evidence | Understand, Report, Close |
27043 [17] | Investigation principles and processes | All activities |
Challenge | References |
---|---|
Jurisdiction | [28,29,30,31] |
Lack of international collaboration | [28,30,31] |
Lack of law/regulation and law advisory | [27,28,31] |
Investigating external chain of dependencies of the cloud provider | [28,31] |
Dependence in cloud providers | [29,30,31] |
Time analysis and evidence correlation for multiple sources | [29,30,31] |
Lack of control of the environment | [29,31] |
Jury’s technical comprehension | [29] |
Large volume of data | [30,31] |
DFaaS | [30] |
Chain of custody | [30,31] |
Crime scene reconstruction | [30] |
Tools | [27,30,31,37,38,39] |
Log visualisation | [30,31] |
Virtualisation | [32,33] |
Geographical location | [32,33] |
Data and metadata changes | [34,35] |
Challenge | Category | Potential Solution |
---|---|---|
Respond | ||
Extraterritorial jurisdiction | Legal | Stronger international cooperation |
Search warrant | Legal | Legal training |
Identify | ||
No physical access | Architectural | Ask cloud provider for cooperation |
Competence and trustworthiness | Architectural | Provide documentation and Ensure forensic procedures are followed |
Collect | ||
Data location and collection | Architectural | Mobile forensics and Data Profiling |
Multi-tenancy and resource sharing | Architectural | Ask cloud provider for cooperation |
Large and changing systems | Architectural | Cloud provider knowledge and Live forensics |
Acquire | ||
Massive volume of data | Technical | Data Mining and Social Networks Forensics and Mobile forensics |
Volatility | Architectural | Live Forensics and DFaaS |
Chain of custody | Legal | Training and Legal advice |
Preserve | ||
Make a forensic copy | Architectural | Snapshots |
Data integrity | Technical | Live forensic training |
Understand | ||
Recovery of deleted data | Architectural | Backups and Repositories and Snapshots and Mobile forensics |
Cryptography | Technical | Brute-force and Mobile forensics |
Data correlation issues | Technical | Data mining and User Profiling |
Lack of interoperability | Architectural | Cloud provider cooperation |
Partial Evidence | Legal | Return to early stages of investigation |
Report | ||
Investigation report | Legal | Training |
Choosing the right court | Legal | Legal advice |
Close | ||
Evidence return and Secure deletion | Legal | Legal training and Legal advice |
© 2016 by the authors; licensee MDPI, Basel, Switzerland. This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC-BY) license (http://creativecommons.org/licenses/by/4.0/).
Share and Cite
Miranda Lopez, E.; Moon, S.Y.; Park, J.H. Scenario-Based Digital Forensics Challenges in Cloud Computing. Symmetry 2016, 8, 107. https://doi.org/10.3390/sym8100107
Miranda Lopez E, Moon SY, Park JH. Scenario-Based Digital Forensics Challenges in Cloud Computing. Symmetry. 2016; 8(10):107. https://doi.org/10.3390/sym8100107
Chicago/Turabian StyleMiranda Lopez, Erik, Seo Yeon Moon, and Jong Hyuk Park. 2016. "Scenario-Based Digital Forensics Challenges in Cloud Computing" Symmetry 8, no. 10: 107. https://doi.org/10.3390/sym8100107
APA StyleMiranda Lopez, E., Moon, S. Y., & Park, J. H. (2016). Scenario-Based Digital Forensics Challenges in Cloud Computing. Symmetry, 8(10), 107. https://doi.org/10.3390/sym8100107