Join our Newsletter — 33% off our NHI Course
Home› Guides› Endpoint Security Executive Briefing: Questions, Metrics and a…
Executive Briefing Endpoint Security

Endpoint Security Executive Briefing: Questions, Metrics and a 90-Day Plan for Boards

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 12 min read
On this page

Laptops, desktops, servers and phones are where attackers run their code, steal the passwords and session tokens that unlock everything else, and launch ransomware, yet boards usually see endpoint security only as an antivirus licence count. This briefing is for board members, chief executives and the executives who answer to them for technology and operational risk. It explains what endpoint risk means in business terms, why unpatched and unsupported devices, local administrator rights and personal devices drive incidents, why the security software on every device is itself a concentration risk, and the questions and red flags that show whether management has the estate under control. It stays at board level: the technical controls are in the Endpoint Security Guide and the staged capability detail in the Endpoint Security Maturity Model.

The risk in one paragraph

Every device a member of staff uses is a place where an attacker can run software, record keystrokes and copy the credentials and tokens that open email, cloud and finance systems. Most compromises of devices come from three conditions management can measure: software that is not updated, users who have administrator rights they do not need, and devices the organisation does not know about or does not manage. Detection and response tools reduce the time an attacker has, but they do not compensate for an unmanaged estate, and they bring their own risk because they run with the highest privileges on every machine. The board's job is to insist on a complete inventory, patching within agreed deadlines, removal of unnecessary administrator rights, a plan for unsupported systems, and evidence that the organisation could recover if a bad update or an attacker disabled thousands of devices at once.

Why this is a board-level issue now

  • Exploited software is the leading way in: Verizon's 2026 Data Breach Investigations Report page states that 31% of breaches now start with the exploitation of software vulnerabilities, ahead of stolen passwords, and that ransomware is involved in 48% of breaches. Both depend heavily on devices and servers that can be reached and are not patched. See the Ransomware Executive Briefing.
  • Security software can stop the business on its own: in July 2024 a faulty update to a widely used endpoint security product crashed about 8.5 million Windows devices, by Microsoft's estimate less than one percent of all Windows machines. No attacker was involved. Endpoint agents are now an operational resilience dependency, not only a security control.
  • Large parts of many estates are now unsupported: Microsoft ended support for Windows 10 on 14 October 2025. Devices without Extended Security Updates no longer receive security fixes. The NCSC states that the only fully effective way to mitigate the risk of an obsolete product is to stop using it.
  • Personal and developer devices hold corporate keys: in the LastPass breach, attackers exploited vulnerable media software on a senior engineer's home computer, installed a keylogger and captured the master password to a vault holding cloud access and decryption keys, which led to theft of customer vault backups.
  • Baseline schemes now set explicit deadlines: the UK Cyber Essentials requirements (v3.2, April 2025) require critical and high-risk updates within 14 days of release, removal of unsupported software, separate administrator accounts that are not used for email or web browsing, and anti-malware or application allow listing on every in-scope device. See the Cyber Essentials Guide.

Where endpoint risk sits in business terms

Endpoint risk is not one problem. Different device groups carry different exposure and need different owners.

Device groupWhy attackers want itTypical gapWhat management should have in place
Staff laptops and desktopsEmail, browser sessions, saved passwords, access to files and SaaSUsers with local administrator rights; slow patching of browsers and third-party appsManaged configuration, rapid updates, no standing admin rights, detection and response agent
Administrator and developer workstationsPrivileged sessions, cloud keys, code signing and deployment credentialsSecrets stored in files and tools; personal devices used for workDedicated hardened devices, secrets in vaults, phishing-resistant MFA
ServersData, line-of-business systems, a base to spread across the networkExceptions to patching, broad service accounts, unsupported operating systemsPatch deadlines by criticality, application control, monitored service accounts
Mobile phones and tabletsEmail, MFA approvals, messaging, corporate appsUnmanaged personal devices with corporate dataMobile device management or app-level protection, minimum operating system versions
Unsupported and unknown devicesKnown flaws that will never be fixedNot in the inventory, so not in any metricDiscovery, replacement plan, isolation where replacement must wait

What the board should understand about the controls

  • Prevention comes before detection: patching, removing administrator rights and allowing only approved software stop most commodity attacks before a detection tool has to act. See the Patch Management Guide, the Endpoint Privilege Management Guide and App Control for Business (WDAC).
  • Detection and response needs people: an endpoint detection and response (EDR) tool produces alerts; value depends on someone triaging them at any hour, in house or through a managed service. See the EDR Guide and EDR vs MDR.
  • Attackers target the security tools: ransomware crews routinely try to disable or blind endpoint agents before acting, sometimes by loading vulnerable signed drivers. Management should monitor for agents going silent. See the Bring Your Own Vulnerable Driver and EDR Killers Guide.
  • Agents are privileged software from a third party: they update often and run at the deepest level of the operating system, so the vendor's update practices, your ability to stage updates and your recovery plan for mass device failure all matter.
  • Encryption and management protect lost devices: full-disk encryption and remote wipe turn a lost laptop from a reportable data breach into an equipment loss. See the Disk Encryption Guide: BitLocker and FileVault.

Where identity fits

Endpoints are where identities are stolen. Infostealer malware copies saved passwords and browser session cookies, which let attackers skip MFA entirely; the board-level view is in the Infostealer Executive Briefing. Devices also carry their own non-human identities: shared local administrator passwords, management and patching service accounts, and the cloud keys and tokens developers keep in files and tools. A single local administrator password reused across thousands of machines lets one compromise spread everywhere. Ask that local administrator passwords are unique and rotated, that the service accounts of management tools are treated as privileged, and that developer secrets move into vaults. See the Local Administrator Password Solution (LAPS) Guide, Developer endpoints as NHI stores and Device Trust and Posture Guide.

Five questions for the board to ask

  1. Do we know every device that can reach our data? Show us the inventory, how it is reconciled against network and identity records, and how many devices are unmanaged or unknown.
  2. How quickly do we fix flaws that are being exploited? What are our patch deadlines by severity, what share of devices meets them, and how many exceptions are open and for how long?
  3. Who has administrator rights on their own machine, and why? How many users and shared accounts hold local administrator rights, and are local administrator passwords unique per device?
  4. What still runs on unsupported software? How many devices and servers run end-of-life operating systems such as Windows 10 without extended updates, what is isolated, and when will each be replaced?
  5. What happens if our endpoint security tool fails or is turned off? Would we notice an agent going silent, can we stage vendor updates, and how long would it take to recover thousands of devices that will not start?

Red flags in management answers

  • "We have EDR on every device": coverage is stated from licence counts, not reconciled against an independent inventory.
  • Patch compliance reported only for the operating system: browsers, office suites and third-party apps are not measured.
  • Administrator rights kept "for productivity": large numbers of users with standing local admin and no request process.
  • Unsupported systems with no end date: exceptions renewed every year with no funded replacement plan.
  • Personal devices with full access: staff and contractors reach email and SaaS from unmanaged machines with no device checks.
  • No recovery plan for mass device failure: business continuity assumes devices will start.

What good looks like

  • An approved endpoint security standard covering configuration baselines, patch deadlines, administrator rights, encryption and supported operating systems. See the Endpoint Hardening Checklist.
  • A reconciled inventory of every laptop, desktop, server and mobile device, each managed and assigned an owner.
  • Exploited and critical flaws fixed within agreed deadlines, with exceptions approved, time-limited and tracked.
  • No standing local administrator rights for ordinary users; unique, rotated local administrator passwords.
  • Application control on high-value systems, and detection and response monitored around the clock with alerts on agents going silent.
  • Conditional access that lets only managed, compliant devices reach sensitive services. See the BYOD Security Programme.
  • Staged deployment of security tool and operating system updates, and a tested plan to recover devices at scale. See the EDR Tampering and BYOVD Response Playbook.

Where to invest first

  1. Inventory and management: you cannot patch or protect a device you do not know about.
  2. Patching of exploited flaws: agree deadlines tied to active exploitation and fund the tooling and staff time to meet them. See the Vulnerability and Exposure Management Executive Briefing.
  3. Administrator rights: remove standing local admin and deploy unique local administrator passwords.
  4. Unsupported systems: fund replacement, and isolate what cannot yet be replaced.
  5. Detection, response and recovery: monitored EDR coverage with tamper alerts, and a rehearsed plan for mass device recovery.

Metrics to track

MetricWhat it tells the board
Managed devices as a percentage of all devices found by independent discoveryHow much of the estate is actually under control
Percentage of devices patched for known exploited flaws within the agreed deadlineExposure to the leading initial access route
Users and accounts with standing local administrator rightsHow easily a single infection becomes a full compromise
Devices running unsupported operating systems, and the age of each exceptionRisk that can never be patched away
Percentage of devices with a healthy, reporting EDR agent, reconciled against inventoryReal detection coverage and silent agents
Time to restore a representative group of devices in the last recovery exerciseResilience to a bad update or destructive attack

Where this sits in the frameworks

FrameworkReferenceWhat the board should see
NIST CSF 2.0ID.AM-01An inventory of hardware the organisation manages
NIST CSF 2.0PR.PS-02Software maintained, replaced and removed in line with risk, including end-of-life systems
NIST CSF 2.0PR.PS-05Installation and execution of unauthorised software prevented
NIST CSF 2.0DE.CM-09Devices and software monitored for adverse events
NIST SP 800-53 Rev. 5SI-2 Flaw Remediation, SI-3 Malicious Code ProtectionPatch deadlines and anti-malware or EDR coverage
NIST SP 800-53 Rev. 5AC-6 Least Privilege, CM-7 Least FunctionalityRemoval of administrator rights and unnecessary software
UK Cyber Essentials v3.2Security update management, user access control, malware protection14-day patching of critical and high-risk updates, separate admin accounts, anti-malware or allow listing

A 90-day plan

  1. Days 1 to 30: management presents a reconciled device inventory, patch compliance for exploited flaws including third-party apps, the count of local administrators and the list of unsupported systems with owners.
  2. Days 31 to 60: set and approve patch deadlines by severity; begin removing standing administrator rights and deploy unique local administrator passwords; enforce device compliance for access to email and sensitive SaaS; turn on alerts for silent EDR agents.
  3. Days 61 to 90: fund and schedule replacement of unsupported systems with interim isolation; agree staged update rings for operating system and security tool updates; run a mass device recovery exercise; the board receives the first metrics pack. See the Board Cyber Risk Reporting Guide.

Common failure patterns

  • Licence count mistaken for coverage: agents are bought for every device but never installed, broken or silent on a share of them.
  • Third-party software ignored: operating systems are patched promptly while browsers, media players and utilities stay vulnerable for years, as the home computer in the LastPass case shows.
  • Permanent exceptions: servers excluded from patching "temporarily" stay excluded until they are exploited.
  • Shared local administrator passwords: one stolen password unlocks every machine built from the same image.
  • Security tools trusted without resilience planning: no staging of agent updates and no plan for devices that will not start, so a single faulty update becomes a business outage.

Practitioner checklist

  • Reconcile the device inventory against identity, network and EDR records monthly.
  • Set patch deadlines by severity and exploitation status, covering third-party applications.
  • Remove standing local administrator rights and deploy unique, rotated local administrator passwords.
  • Track every unsupported system with an owner, isolation measures and a funded replacement date.
  • Enforce full-disk encryption and remote wipe on laptops and mobile devices.
  • Apply application control on servers and administrator workstations first.
  • Monitor EDR health and alert on agents that stop reporting or are tampered with.
  • Stage operating system and security tool updates through pilot rings and keep a mass recovery runbook.
  • Require managed, compliant devices for access to email and sensitive SaaS.

Standards and references

How NHI Mgmt Group can help

We provide independent identity and non-human identity risk assessments and board briefings, including how local administrator accounts, device management service accounts and developer secrets on endpoints are governed. Our NHI Foundation Level Training Course helps security and IAM teams govern service accounts, API keys and secrets. Contact us to arrange a briefing.

Related NHI Mgmt Group resources: Endpoint Security Guide · Endpoint Security Maturity Model · EDR Guide · Infostealer Executive Briefing

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.