◇ OpenCyber Academy
Engineering · Chapter 43 · English

Chapter 43 — Industry or public-service practice

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Chapter 43 — Industry or public-service practice

Lesson map

Lesson 43 published. Map, example, EX127.

flowchart TD
  N0["Learning outcomes"]
  N1["43.1 Placement"]
  N2["43.2 Confidentiality"]
  N3["43.3 Quality systems"]
  N4["43.4 Working with examiners"]
  N5["43.5 Courts"]
  N6["43.6 Reflection"]
  N7["43.7 Assessment"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
  N7 --> EX["Worked example"]
  EX --> Q["Exercise EX127"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["43.1 Placement"]
  N2["43.2 Confidentiality"]
  N3["43.3 Quality systems"]
  N4["43.4 Working with examiners"]
  N5["43.5 Courts"]
  N6["43.6 Reflection"]
  N7["43.7 Assessment"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX127"]

[Learning outcomes]
    |
    v
[43.1 Placement]
    |
    v
[43.2 Confidentiality]
    |
    v
[43.3 Quality systems]
    |
    v
[43.4 Working with examiners]
    |
    v
[43.5 Courts]
    |
    v
[43.6 Reflection]
    |
    v
[43.7 Assessment]
    |
    v
[Worked example] --> [Exercise EX127]

Learning outcomes

You will (1) work within a public-service forensic lab; (2) apply professional conduct on placement; (3) observe accreditation and quality practice; (4) reflect on practice.

43.1 Placement

Priya spends ten weeks at Northfield as a supervised engineering intern. She does not handle casework evidence; she supports infrastructure, testing and documentation using synthetic data.

Keeping her away from casework protects both the evidence and Priya: anything she touched could become part of a case record and bring her into court as a witness. Infrastructure, testing and documentation work still teaches how a working lab operates. Her supervisor agrees the tasks in writing at the start, with a review halfway through.

43.2 Confidentiality

She signs the lab's confidentiality agreement and vetting forms. Case names and details she overhears stay inside the lab and never enter her university reports.

Vetting checks that people with access to sensitive material are suitable to hold it. In practice, overhearing case discussion in a shared office is unavoidable, so the rule covers what she does with it. When she writes her placement report, she describes processes in general terms and has her supervisor confirm nothing identifies a case before submission.

43.3 Quality systems

Northfield works towards accreditation of its testing activities against an international laboratory competence standard. Priya observes document control, competence records, proficiency tests and internal audits, and sees how EvidenceDesk's records will feed audit evidence.

Document control ensures staff use the current procedure version; competence records show each examiner is trained for the methods they use; proficiency tests check results against known answers; internal audits check that the system works as described. EvidenceDesk's custody logs and validation records will become evidence for several of these, which shapes how Priya formats its reports.

43.4 Working with examiners

Examiners are busy and cautious about change. Priya schedules short sessions, shows the system on synthetic items, and records every concern.

Caution is reasonable: a new system that fails could compromise cases examiners are responsible for. Sessions of twenty minutes fit between other work. Every concern is written down with a response, even when the answer is no, and the list is shared back so examiners see they were heard. Several later design changes, including clearer error messages, come from those notes.

43.5 Courts

She attends a public court hearing where an examiner explains acquisition and verification under cross-examination, noting the questions asked about custody and hashing.

Defence counsel asks how the examiner knows the image matches the seized drive, who had access to it, and whether the hash function could produce the same value for different data. Priya notes that clear answers depend on records being complete and easy to produce. She adds two items to the export design: access history per image and a one-line explanation of the hash.

43.6 Reflection

A weekly reflective log records what she learned and how it changes her design.

Each entry has three parts: what happened, what she made of it, and what she will do differently. One week she records that she had assumed examiners wanted more automation, while what they asked for was fewer clicks in steps they already did. That changes her priorities for the remaining weeks from new features to streamlining existing ones. Her supervisor reads the log fortnightly and adds a question or two, which often leads to the most useful entries.

43.7 Assessment

Her supervisor assesses professionalism, technical contribution and communication.

Professionalism covers reliability, confidentiality and conduct with staff. Technical contribution is judged on delivered work and its quality, such as tests written and documentation accepted. Communication covers both written reports and how she explains technical points to non-engineers. The supervisor's comments are given at the midpoint as well as the end, so there is time to act on them. Priya also writes a self-assessment against the same three headings, and the differences between her view and her supervisor's become a discussion point at the final meeting.

43.8 Boundaries

When asked informally to "just check" a seized phone, Priya declines: she is not authorised or trained for casework.

The request is well meant, from an examiner short of time, but handling a seized device without authorisation could break the custody record and expose the case to challenge. Priya explains why she cannot help and suggests the examiner raise the workload with the duty supervisor. She mentions the incident to her placement supervisor, who confirms she acted correctly. Saying no politely is part of the job.

Mentoring

Hugo meets Priya weekly to review her log and challenge assumptions. When she proposes a feature examiners never asked for, he asks which interview or record supports it; she drops it. Mentoring keeps the engineering anchored to real forensic needs and to the evidence she has actually collected.

Worked example

At court, defence counsel asks the examiner whether anyone could have changed the image after acquisition. The examiner shows the acquisition hash, the verification record and the custody log. Priya notes that a clear, independent verification record answered the question in seconds — exactly what EvidenceDesk aims to produce.

Synthetic case. The placement and hearing are invented.

Errors and limits

One placement shows one lab's practice; others differ.

Exercises

Synthesis

Placement shows how quality systems, courts and examiners shape what forensic engineering must deliver.

Continue studying — chapter 43 of 50

← Chapter 42 (draft) · Course chapter index · Chapter 44 (draft) →