Hi,
Does anybody on here have any experience on section 5.4 of the ISO Accreditation 17025 - Validation and Testing?
My company is starting this phase and was wondering if anybody can point me in the right direction of how to deal with the validation and verification process when it comes to mobile phone forensics and the associated tools which we use.. XRY, Cellebrite, IOS Toolkit etc?
Are people buying test phones, inputting relevant data and conducting extractions on various different makes and models of phones or are you concentrating on different mobile platforms?
Thank you in advance for your help.
Kelly
Hi Kelly1,
My previous company CCL Forensics give training in preparing for ISO17025 I believe
http//
They have held the accreditation for the mobile device lab for a good few years now.
I am sure they would be happy to help )
Cheers,
Logan
Hi,
Does anybody on here have any experience on section 5.4 of the ISO Accreditation 17025 - Validation and Testing?
My company is starting this phase and was wondering if anybody can point me in the right direction of how to deal with the validation and verification process when it comes to mobile phone forensics and the associated tools which we use.. XRY, Cellebrite, IOS Toolkit etc?
Are people buying test phones, inputting relevant data and conducting extractions on various different makes and models of phones or are you concentrating on different mobile platforms?
Thank you in advance for your help.
Kelly
ISO/IEC 17025 adopts the words 'method' and 'procedures' but the standard appears to use them interchangeably. In reality that doesn't work in practice. Both are better considered as separate entities but combined their objective is to produce consistent results, to avoid non-compliances.
The capability of the tool/s (are you agreeing use of tool/s with your customer?) you intend to deploy should be guiding you as to the tests to be conducted
a) Make and Model
b) Mobile platforms
c) Applications
.
.
.
Test phones are needed and a well defined set of reference test data for input. Also may also be helpful to define DUT (device under test) and EUT (equipment under test).