Testing the Comprehensive Digital Forensic Investigation Process Model (the CDFIPM)

Montasari, Reza (2017) Testing the Comprehensive Digital Forensic Investigation Process Model (the CDFIPM). In: Technology for Smart Futures. Springer, Cham, pp. 303-327. ISBN 978-3-319-60136-6

Full text not available from this repository. (Request a copy)

Abstract

The Comprehensive Digital Forensic Investigation Process Model (the CDFIPM), presented in Montasari (IJESDF 8(4)285–301, 2016), provides guidelines for carrying out digital investigations in the UK jurisdiction in a forensically sound manner. The CDFIPM is comprehensive in that it covers the entire digital forensic investigative process; it is generic such that it can be applied in the three fields of law enforcement, incident response and commerce. The model is also formal in that it synthesises, harmonises and extends the existing digital forensic investigation process models. The CDFIPM also needs to be subjected to an evaluation process in order to determine ‘whether the model has been built right’ and ‘whether the right model has been built’. To this end, the CDFIPM is applied to a case study in this paper to determine whether the model meets the two components of ‘utility’ and ‘usability’.

Item Type: Book Section
Uncontrolled Keywords: Digital forensics; Testing Investigative process; Process model; Generic model; Digital investigations; Computer forensics; Formal process
Subjects: G400 Computer Science
Divisions: Faculty of Computing, Engineering and the Built Environment
Faculty of Computing, Engineering and the Built Environment > School of Computing and Digital Technology
Faculty of Computing, Engineering and the Built Environment > School of Computing and Digital Technology > Cyber Security
UoA Collections > UoA11: Computer Science and Informatics
Depositing User: $ Ian McDonald
Date Deposited: 16 Oct 2017 08:13
Last Modified: 16 Oct 2017 08:13
URI: http://www.open-access.bcu.ac.uk/id/eprint/5218

Actions (login required)

View Item View Item

Research

In this section...