Procedures and Methodology · Topic 5 of 11

Bluetooth, IoT, OT and Multimedia Forensics, and Acquisition Basics

Forensics for Bluetooth, IoT, OT and multimedia evidence, plus the first acquisition steps: determine the best acquisition method and select the right tool.

  • 5 min
In a nutshell
  • Bluejacking sends messages, bluesnarfing steals data, bluebugging takes control.
  • IoT evidence is spread across device, companion app, cloud and network.
  • OT forensics avoids active probing and favors passive capture and logs.

What it is

Evidence now also comes from short range radio links, smart devices, industrial equipment and image, audio and video files. Each needs care because the device may be small, unusual or safety critical.

This page also starts the data acquisition methodology, a seven step plan used for every acquisition. Here you learn the first two steps: pick the method and pick the tool.

Determine methodbit stream, logical, sparseSelect toolAcquire volatileWrite protectAcquire nonvolatileContingencyValidate

How it works

Bluetooth forensics

Bluetooth links nearby devices. Classic Bluetooth and Bluetooth Low Energy (BLE) both identify a device by its hardware address (BD_ADDR).

Evidence sources:

  • paired and remembered devices on the phone or computer; on Windows, paired device records are kept in the registry under HKLM\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Devices
  • device names, addresses and last connection times
  • file transfer records and logs
  • nearby device scans captured with Bluetooth sniffing equipment

Attacks you should recognize: bluejacking (sending unsolicited messages), bluesnarfing (stealing data without permission) and bluebugging (taking control of a device). Forensic goals are to show a pairing existed, when, and with which device.

IoT forensics

Internet of Things devices include cameras, speakers, wearables, thermostats and sensors. They have little storage, proprietary formats and often store data in the cloud.

SourceExamples
The deviceFlash memory, firmware, configuration, local logs
The companion appAccount data, tokens, cached content on the phone
The cloudEvent history, recordings, user commands
The networkRouter logs, traffic to vendor servers

Methods include reading memory through debug ports such as UART or JTAG, extracting firmware, and requesting data from the vendor with legal process. Many devices lose data when powered off, so decide early whether to keep power on. Note the limits, because tool support is thin and results need extra validation.

OT forensics

Operational technology (OT) controls physical processes: industrial control systems, SCADA, PLCs and sensors. Its first priority is safety and availability, not data collection.

  • Coordinate with plant operators before touching anything.
  • Avoid active scanning or probing of live controllers, which can disrupt a process.
  • Use passive sources: network captures from a mirror port, historian databases, engineering workstation logs, and PLC project and change logs.
  • Common protocols such as Modbus and DNP3 often have no authentication, so command traffic must be correlated with operator actions.
  • Work on copies, and use the maintenance window where possible.

Multimedia forensics

Multimedia forensics examines images, audio and video to answer two questions: what do they show, and are they authentic.

TechniquePurpose
Metadata (EXIF)Camera model, date, GPS data, software used
Hash comparisonMatch files against known sets
Error level analysisSpot regions that were recompressed after editing. A lead only, since results are easy to misread.
Sensor pattern noiseLink an image to a specific camera
Frame and codec analysisCheck video structure, gaps and re-encoding
Deepfake detectionLook for synthetic artifacts in faces, audio and lighting

Metadata can be removed or altered, so it supports but does not prove authenticity. Always work on a copy and keep the original file hashed.

Data acquisition methodology

Acquisition makes a forensic copy of evidence without altering it. The methodology has seven steps:

  1. Determine the best acquisition method.
  2. Select the acquisition tool.
  3. Acquire volatile data.
  4. Enable write protection on the evidence media.
  5. Acquire nonvolatile data.
  6. Plan for contingency.
  7. Validate the acquisition.

Determine the best acquisition method

MethodWhat it copiesWhen
Bit stream disk to imageEvery sector into an image fileDefault for most cases
Bit stream disk to diskEvery sector onto another driveWhen an image file is not workable or a fast clone is needed
Logical acquisitionSelected files or foldersTime limited, or very large data where only some is relevant
Sparse acquisitionFragments of selected data, including some unallocated spaceVery large storage

Choose based on the size of the source, time available, the legal scope, whether the system can be taken offline, and how important deleted data is. A bit stream copy captures deleted files and slack space that a logical copy cannot.

Select the acquisition tool

Pick a tool that fits the media and has been validated. Consider: support for the file system and encryption, ability to write forensic image formats (raw, E01), built in hashing and logging, speed, and whether it works through a write blocker. Examples: FTK Imager, dd and dc3dd, Guymager, EnCase and Magnet acquisition tools. Tools in this category must not write to the source.

A worked example

A plant engineer reports odd valve commands. The investigator does not scan the PLC. Instead, a passive capture from the mirror port and the historian logs are copied, hashed and compared with the operator log.

Meanwhile, a smart camera in the plant is imaged through its debug port after approval.

How the exam asks about this

  • "Which Bluetooth attack steals data from a device?" → Bluesnarfing.
  • "What is the priority in OT forensics?" → Safety and availability of the process.
  • "Which acquisition captures deleted files and slack space?" → A bit stream copy.

What to remember for the exam

  • Bluejacking sends messages, bluesnarfing steals data, bluebugging takes control.
  • IoT evidence is spread across device, companion app, cloud and network.
  • OT forensics avoids active probing and favors passive capture and logs.
  • Multimedia authenticity uses EXIF, error level analysis and sensor noise.
  • Seven step acquisition: method, tool, volatile, write protect, nonvolatile, contingency, validate.
Watch out

EXIF metadata is easy to edit. Treat it as a lead to confirm, not as proof of origin.

Common mistakes

Scanning a live controller. Active probing in OT can halt a process and is not forensically sound.

Choosing logical acquisition by default. It misses deleted data and slack space.

Forgetting the cloud side of IoT. The device may hold almost nothing while the vendor holds the history.

Check yourself

  • Which acquisition step comes right after selecting the tool?

    Acquiring volatile data.

  • Name two passive evidence sources in OT.

    Mirror port network captures and historian or engineering workstation logs.

  • What does error level analysis help detect?

    Image regions that were edited and recompressed.

Topic 5 of 11 in Procedures and Methodology

Test yourself on Procedures and Methodology

The full EC-Council 312-49 question bank has 900 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by EC-Council. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.