Colour theme
Book a consultation

Checking endpoint protection across device life

Check device protection from setup to retirement, including supported software, boot controls, alert response, recovery and verified removal of business data.

An illustration of a monitor showing a padlock bound with chains

Endpoint protection covers the whole life of the devices people use: setup, updates, access, incident response and retirement. The security app installed on each device is one part of it.

Check the arrangements by device type. A Windows workstation, phone, server and connected printer won’t support the same controls or produce the same evidence.

Confirm what’s covered

Compare the business’s device inventory with the management and security consoles. Identify missing, duplicated and inactive records before reporting coverage.

Record an owner, supported operating system, update process and intended access for each type. Seeing a device in a console tells you it’s enrolled. Check separately that its policies are current and that someone reviews its alerts.

Include firmware and the applications used for business. Plan replacement for components that can no longer receive required security fixes.

Understand the controls you enable

Microsoft’s Secure Boot and Trusted Boot guidance explains protections in the Windows startup process. Secure Boot, a TPM and disk encryption perform different jobs; a TPM isn’t a general malware scanner.

Before changing firmware or boot settings, save each device’s BitLocker recovery key somewhere you can reach it, such as Microsoft Entra ID, because the change can trigger a recovery prompt. Turn off booting from USB drives and set a firmware password where the hardware supports it, then test required software and peripherals.

Protecting the device doesn’t replace multi-factor authentication and sensible permissions in the services it reaches. Staff shouldn’t do everyday work with administrator rights on their own computers.

Check the response behind an alert

Confirm who receives security alerts, when they’re reviewed and who can contain an incident. Endpoint detection and response and managed response services have different responsibilities; check the agreement.

Use a harmless test the vendor supports, such as the EICAR test file or Microsoft Defender’s detection test. Verify the alert and follow-up path without introducing real malware into the environment.

Record exceptions and the systems they affect. When a protection feature is turned off, record why and when it’ll be reviewed. Don’t assume another tool covers the gap.

Prepare for loss and reassignment

Check encryption, backup and account revocation arrangements before a device is lost. A remote lock or wipe depends on platform support and connectivity; check that the request completed.

Follow the agreed ownership and privacy process for personal devices. Keep the business records you need before removing data or erasing the device.

At retirement, verify sanitization and remove obsolete device and service access. Keep a record of what was done, including any unresolved limitations.

Our managed IT work can help keep device coverage, response responsibilities and lifecycle records aligned.


Featured Image Credit