A Critical Review of Evidence Acquisition and Preservation in Software-as-a-Service Environments: Customer-Controlled Forensic Capabilities and Provider Dependencies

Main Article Content

Brian Mwangi

Abstract

Software-as-a-Service (SaaS) environments present distinctive challenges for digital forensic investigations because customers generally control user accounts, organizational configurations, and selected audit capabilities but do not control the underlying infrastructure. Consequently, the availability, completeness, and preservation of forensic evidence depend on both customer-managed settings and provider-operated systems. This critical narrative review examines the forensic implications of that division of control, focusing on evidence generation, accessibility, retention, preservation, and reliability. It evaluates the limitations of customer-accessible audit records, the significance of provider-controlled evidence, and the difficulties associated with acquisition through administrative interfaces and application programming interfaces. We distinguish routine administrative export from defensible forensic preservation and examine how licensing, retention settings, application design, and provider cooperation shape an investigation. A five-dimensional analytical framework is proposed to assess whether an organization can generate, access, retain, preserve, and substantiate evidence relevant to an incident. The framework can support forensic readiness assessments and incident investigations, but it is not a validated numerical scoring system. The analysis demonstrates that customer access to SaaS audit functionality does not establish complete forensic visibility and that reliable investigation requires a documented understanding of evidentiary boundaries, collection procedures, and provider dependencies

Article statistics

Abstract views
231
PDF Downloads
31
Total views
262
Citations

Downloads

Download data is not yet available.

Article Details

Section

Peer-reviewed Articles

How to Cite

Mwangi, B. (2026). A Critical Review of Evidence Acquisition and Preservation in Software-as-a-Service Environments: Customer-Controlled Forensic Capabilities and Provider Dependencies. International Journal of Security Sciences, 1(1), e003. https://doi.org/10.66261/51k68z79

References

[1] Pichan, A., Lazarescu, M., & Soh, S. T. (2018). Towards practical cloud forensics logging framework. Journal of Information Security and Applications, 42, 18–28. https://doi.org/10.1016/j.jisa.2018.07.008. DOI: https://doi.org/10.1016/j.jisa.2018.07.008

[2] Marty, R. (2011). Cloud application logging for forensics. Proceedings of the 2011 ACM Symposium on Applied Computing, 178–184. https://doi.org/10.1145/1982185.1982226 DOI: https://doi.org/10.1145/1982185.1982226

[3] Quick, D., & Choo, K.-K. R. (2013). Forensic collection of cloud storage data: Does the act of collection result in changes to the data or its metadata? Digital Investigation, 10(3), 266–277. https://doi.org/10.1016/j.diin.2013.07.001 DOI: https://doi.org/10.1016/j.diin.2013.07.001

[4] Martini, B., & Choo, K.-K. R. (2013). Cloud storage forensics: ownCloud as a case study. Digital Investigation, 10(4), 287–299. https://doi.org/10.1016/j.diin.2013.08.005 DOI: https://doi.org/10.1016/j.diin.2013.08.005

[5] Bowling, H., Seigfried-Spellar, K., Karabiyik, U., & Rogers, M. (2023). We are meeting on Microsoft Teams: Forensic analysis in Windows, Android, and iOS operating systems. Journal of Forensic Sciences, 68(2), 434–460. https://doi.org/10.1111/1556-4029.15208 DOI: https://doi.org/10.1111/1556-4029.15208

[6] Pichan, A., Lazarescu, M., & Soh, S. T. (2015). Cloud forensics: Technical challenges, solutions and comparative analysis. Digital Investigation, 13, 38–57. https://doi.org/10.1016/j.diin.2015.03.002 DOI: https://doi.org/10.1016/j.diin.2015.03.002

[7] Herman, M., Iorga, M., Salim, A. M., Jackson, R. H., Hurst, M. R., Leo, R. A., Lee, R., Landreville, N. M., Mishra, A. K., Wang, Y., & Sardinas, R. (2020). NIST Cloud Computing Forensic Science Challenges. NIST Interagency Report 8006. National Institute of Standards and Technology. https://doi.org/10.6028/NIST.IR.8006 DOI: https://doi.org/10.6028/NIST.IR.8006

[8] Dykstra, J., & Sherman, A. T. (2012). Acquiring forensic evidence from infrastructure-as-a-service cloud computing: Exploring and evaluating tools, trust, and techniques. Digital Investigation, 9, S90–S98. https://doi.org/10.1016/j.diin.2012.05.001 DOI: https://doi.org/10.1016/j.diin.2012.05.001

[9] Microsoft. (n.d.). Manage audit log retention policies. Microsoft Learn. https://learn.microsoft.com/en-us/purview/audit-log-retention-policies

[10] Kent, K., Chevalier, S., Grance, T., & Dang, H. (2006). Guide to Integrating Forensic Techniques into Incident Response. NIST Special Publication 800-86. National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-86 DOI: https://doi.org/10.6028/NIST.SP.800-86

[11] Martini, B., & Choo, K.-K. R. (2012). An integrated conceptual digital forensic framework for cloud computing. Digital Investigation, 9(2), 71–80. https://doi.org/10.1016/j.diin.2012.07.001 DOI: https://doi.org/10.1016/j.diin.2012.07.001

[12] Herman, M., Iorga, M., Salim, A. M., Jackson, R. H., Hurst, M. R., Leo, R. A., Mishra, A. K., Landreville, N. M., & Wang, Y. (2024). NIST Cloud Computing Forensic Reference Architecture. NIST Special Publication 800-201. National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-201 DOI: https://doi.org/10.6028/NIST.SP.800-201.ipd

[13] Alenezi, A., Atlam, H. F., & Wills, G. B. (2019). Experts reviews of a cloud forensic readiness framework for organizations. Journal of Cloud Computing, 8, 11. https://doi.org/10.1186/s13677-019-0133-z DOI: https://doi.org/10.1186/s13677-019-0133-z