The process of establishing the service and the constraints under which the proposed system must operate can be defined as requirement analysis (Sommerville, 1995, p. 64).
The proposed system must provide a means of assisting a forensic examiner to prepare, investigate, analyse, document, present evidence in court or concern authorities and conduct post examination analysis in course of a forensic incident.
This section articulates the set of functions the proposed system should do rather than how it is done. The various available features of the proposed system i.e. System specific requirements, functional requirements and non-functional requirements are discussed in this section.
System Specific Requirements
These requirements are specific to the generic workflow presented in this research and describe what the proposed system should do:
- R1.1: The system should aim to support the forensic examiner to determine what happened, why it happened and who is to blame for database incident.
- R1.2: The system should support the initiation of a pre-examination stage from a manual or automatic trigger.
72 - R1.3: The system should integrate and support auditing every stages of evidence collection to establishing chain of custody, evidence validity and forensic soundness. Audits should not alter original records (NIST, 2009, pp. F-27).
- R1.4: The system should support a forensic examiner to collect and secure electronic evidence at all stages of the examination so that nothing in the original evidence is altered and the evidence should be legally admissible in Court of Law (US-CERT, 2008, p. 3).
- R1.5: The system should support a forensic examiner to create and maintain custody logs with information as to who is accessing the evidence, the time date and purpose of such access and if the evidence is removed, the time and date of return for all evidence collected during the examination (Standards Australia, 2003, p. 23).
- R1.6: The system should support and guide a forensic examiner in collecting evidence relevant to the incident, to avoid examiners from deviating from the actual incident.
- R1.7: The system should support the forensic examiner in controlled decision making at every stage of the examination process.
- R1.8: The system should support the forensic examiner to upload digital evidence into the system at all stages of the examination.
- R1.9: The system should support integrating network scanning tools such as NMAP to scan user network for host discovery, operating system identification, device type identification and other services on the host network and capture data from the logs into the system.
73 - R1.10: The system should enable a forensic examiner to view the status of an ongoing examination and produce status reports at any time during the examination.
- R1.11: The system should prompt forensic examiner to carry out critical operations such as crime scene securing, preservation, obtaining examination authorisation from internal and external stakeholders and record such actions.
- R1.12: The system should have communication shielding features that prevent unauthorised communication by a forensic examiner and other associated team members in accordance with the Telecommunications (Interception) Act 1979 and Workplace Surveillance Act (NSW & VIC) (Standards Australia, 2003, p. 23).
- R1.13: In the event of volatile evidence collection, the system should prompt the forensic examiner to record evidence from process listing, service listing, system information, logged on and registered users, network information including listening ports, open ports, closing ports, ARP (address resolution protocol) cache, auto start information, registry information and binary dump of memory. The system should not permit the examiner to proceed with the examination until all the above information is recorded (7safe & ACPO, 2007, p. 18).
- R1.14: The system should advise and prompt the forensic examiner in relation to all evidence that cannot be stored with the native database such as pedophile images and other evidence that is stored on devices that cannot be transferred into the database to be marked as restricted and stored in secure location to prevent evidence contamination. If the need arises to transfer these images during examination, the evidence should be exhibited on an encrypted disk that is password protected (7safe & ACPO, 2007, p. 29).
74 - R1.15: The system should permit controlled access to external consulting examiners and other forensic contractors as such they should be able to only view information directly related to the case they are involved (7safe & ACPO, 2007, p. 33).
- R1.16: The database associated with the system should be patched and free of vulnerabilities as discussed in the literature review.
- R1.17: The system should aid a forensic examiner to reconstruct crime scene based on evidence collected. This is a very critical aspect of examination especially in cyber-crime because the mere presence of an object does not prove that the owner of the computer is responsible for putting the object in it. Apart from the owner, the system or an intruder can generate the object automatically or virus program can plant the object, or the previous owner of the computer can leave the object. It is therefore important for an examiner to reconstruct event in the past that caused the presence of the object to determine who is responsible for its creation (Gladyshev, 2004, p. 25).
- R1.18: The system should prompt the forensic examiner to identify non-readable electronic records such as slack space of a disk drive that may contain deleted files or encrypted files and caution against altering or deleting such files or records (Standards Australia, 2003, p. 23).
- R1.19: The system should have the ability to segregate the final reports into technical and legal reports, the main objective in segregating reports and converting electronic evidence into human readable format is to persuade decision makers such as management, lawyers, judges etc. of the validity of the facts and opinions deducted from the evidence (Standards Australia, 2003, p. 25).
75 - R1.20: System should have the ability to function in the eventuality of server failure by having a load-balancing server or replicating server that can enhance and improve application availability, performance, quality of service, and examination continuity (Radharc, 2012, p. 7).
Functional and Non-Functional Requirements
Other than the system specific requirement, the proposed system should also meet the following generic functional and non-functional requirements.
Functional Requirements
Functional requirements capture the intended behavior of the system and may be expressed as services, tasks or functions the system is required to perform (Bredemeyer
& Bredemeyer, 2001).
- RF1.0: Authorised Access - The proposed system should only allow authorised users to access the system. A super user or administrator account has to be pre-configured during system development that can manage and perform various administrative tasks such as adding users, creating back up and running reports (International Council on Archives, 2008).
- RF1.1: Administration Functions - The proposed system should have the ability to perform administration functions such as the user management and report generation.
- RF1.2: Interface - The proposed system should have simple web interface and navigation tools to interacting with the users.
- RF1.3: Report Generation & Printing - The proposed system should have the ability to generate and print reports.
76 - RF1.4: Support & Maintenance - The proposed system should have support and
maintenance from the system developer or suitable technician.
- RF1.5: Business rules - The proposed system should have the ability to implement business conditions or constraints that define some or all aspect of the business that control or influence their behaviors (BRG, 2012).
- RF1.6: Easy to use - The proposed system should have simple web interface and navigation control buttons.
- RF1.7: Portability - The proposed system should be highly portable.
- RF1.8: Implementation - The proposed system should be easily implemented and should support multiple platforms.
- RF1.9: Adverse downtime - The proposed system should have 99.9 % uptime.
- RF1.10: Legal or Regulatory Requirements - The proposed systems should meet all the legal and regulatory requirements of the country or state.
- RF1.11: Error Handling - The proposed system should have the ability to handle system and hardware errors.
- RF1.12: Historical Data - The proposed system should have the ability to collect, manage and securely archive historical data (International Council on Archives, 2008).
Non-Functional Requirements
Non-functional requirements are system qualities the proposed system should possess (Easterbrook, 2005). Notable requirements are:
77 - RNF1.0: Reliability - The proposed system should generate accurate and
consistent report without errors from the database or web interface.
- RNF1.1: Assurance of fault tolerance - The proposed system should function without any faults or error after deployment.
- RNF1.2: Scalability - The proposed system should have the ability to expand data storage and system capabilities.
- RNF1.3: Security - The proposed system should not have any system, operating system and hardware vulnerabilities.
- RNF1.4: Personnel availability and Skill level - System usage training should be provided as part of deployment to the investigating team.
- RNF1.5: Maintainability - The proposed system should have regular maintenance from the system developer or suitable technician.
- RNF1.6: Availability - The availability of the proposed system should be appropriately high.
78