← Back to Attack / Defense Lab
OSI LAYER 1 // Physical Layer

Hardware Tampering

Hardware tampering changes, adds, or removes physical components to alter behavior or capture information.

01 // HOW IT WORKS

Mechanism

Examples include modified firmware, implants, replaced components, or unauthorized inline devices. Detection requires both physical and logical integrity controls.

02 // DETECTION

Indicators to watch

Unexpected hardware inventory changes, firmware differences, new USB/network devices, tamper alerts, or configuration drift.

03 // ATTACK FLOW

Concept diagram

01Authorized device↓
02Unauthorized component change↓
03Firmware / hardware integrity altered↓
04Trust weakened↓
05Inventory + secure boot
04 // PREVENTION

Defensive controls

Use asset inventory, tamper-evident controls, secure boot, signed firmware, restricted access, and integrity monitoring.

05 // SECURITY TOOL

Recommended security control

Asset inventory / secure boot attestation

Use spare lab hardware for demonstrations.

06 // DEFENCE PRACTICE LAB

Defence practice lab

The administrator has not attached a tool link yet. This slot will show “Build Soon” until an external link is configured.

Build Soon
◈
DEFENCE PRACTICE LAB // BUILD SOONThe administrator can add or edit an external defence practice lab link from the private admin portal.
07 // DEFENCE TECHNIQUES

Defence techniques

Defence techniques for this attack will be added by the administrator.

AUTHORIZED LEARNING

All attack descriptions are for defensive education. Test scanning, traffic generation, interception, wireless testing, and vulnerable applications only on systems and networks you own or are explicitly authorized to assess.