Hardware

Hardware is the physical layer of an IT environment: the computers people work on, the servers that run business systems, the switches, and access points that carry their traffic, and the disks and printers attached to them. It is one kind of asset an organization owns, and the only kind that can be lost on a train or left in a hotel room.

Most hardware risks have nothing to do with the device itself. They come from not knowing that it exists, who holds it, or which configuration it runs. Treating hardware as a record that must stay accurate is what lets a security team act on it.

• Endpoints: workstations, laptops, and servers, which run applications and hold business data.
• Network equipment: routers, switches, and access points that connect endpoints and carry their traffic.
• Peripherals: monitors, keyboards, and printers, which depend on the endpoint they are attached to.
• Storage: internal and external disks and memory, which hold data or run active processes.
• Mobile devices: laptops and removable media that regularly leave the controlled office.

Hardware is often confused with two neighboring layers. Software has no physical form, but it needs a license and a version. Firmware is low-level code built into a component, such as the BIOS or UEFI of a computer or the code inside a network card. It ships with the device but is updated like software, through its own channel.

The three layers depend on each other and are managed separately. Software is tracked through software asset management, while hardware is tracked by serial number and physical location.

A security program can only protect the hardware it knows about. A device missing from the register cannot be patched on schedule, checked against its approved configuration, or traced when it disappears.

Two blind spots appear again and again in incident reviews: unapproved devices plugged into the network, and company equipment quietly reused for personal work. A spreadsheet updated once a quarter misses both, so hardware change detection that runs continuously is treated as a baseline control, not an occasional audit.

Hardware is managed from purchase to disposal. It is never a static line in a spreadsheet:

1. 1

   Procurement

   The organization decides what it needs, buys or leases it, and records the item in the register before it reaches a desk.

2. 2

   Deployment

   The device is commissioned and given an owner, a status, and a location. Its expected configuration is fixed as a baseline.

3. 3

   Operation

   The device is used every day. Its load, health, and connected components are monitored and serviced as needed.

4. 4

   Change and relocation

   The device moves between employees, departments or offices, and its status changes between in use, in service and not in use.

5. 5

   Disposal

   The device leaves service and its storage is sanitized. The record is closed without losing its history.

In the Anexet Inventory module, the Devices tab of each card lists the components that agents found, with device type and manufacturer. On a server card, warning icons mark connected devices that are not on the list of expected devices for that machine, so an unexpected adapter stands out at once.

Most inventories fail in the same places. The register is built once during a hardware refresh and then left to age, so new devices and reassignments never reach it.

Automatic discovery removes most of these errors, because the register is refreshed from the devices themselves rather than from memory.

• Recording serial numbers without an owner or location, so a found device cannot be returned.
• Closing a record before the storage is wiped, which leaves data on a disk that nobody tracks.
• Relying on purchase lists, which never show equipment added to the network without approval.

Start with the devices that hold the most data or reach the most networks, such as servers and laptops that leave the office, and get their records right first.

Then add discovery, so the register keeps up without anyone typing in a serial number. Keep each record linked to a person, a location and a configuration, and keep its history. A register is only as useful as its last update.