topicsidentity & access3 numbers3 guides

edge device exposure

The box that lets your staff in from home also lets everyone else knock. When one of its flaws is used, the patch fixes the box and leaves whatever the intruder took with it.

in one lineEdge device exposure is when a firewall, VPN gateway, router or server at the network edge has a login or admin page that answers from the internet, so a flaw in it hands an outsider the accounts, sessions and keys the box holds.

the numbers

all the numbers →

1what it is

An edge device sits between the company network and the internet: the firewall, the VPN or remote-access gateway, the router, the storage box someone opened up for home access, sometimes an on-premises web server. The Canadian Centre for Cyber Security's guidance on edge devices, published in February 2025 with contributions from the UK, Australian, New Zealand and US agencies, names VPNs, firewalls and routers as the most common ones.

These boxes are built to answer from the outside. That is their job. Exposure begins when more of the box answers than needs to: an admin page on the public interface, a login portal for every staff member, a management port opened once for remote support. Behind those pages the box keeps the company's access: local admin and VPN accounts, the sessions of everyone signed in, the keys it signs things with, and the password it uses to look people up in the directory.

2why it accumulates

Each opening had a reason. Remote work needed the VPN. The IT provider needed the admin page from its own office. Those openings can stay after the reason ends, and the box gives no reminder.

The box lives outside the identity system. Its accounts are local, created on the box, and missed by offboarding and access reviews. The guide on the box at the edge walks through who holds those logins, and the IT provider guide covers the common case where only the provider knows the admin password.

The patch is treated as the end. When a vendor publishes a fix, the box gets updated and the ticket closes. The access the intruder took through the flaw is a separate thing, and nothing in the update touches it. Fortinet's advisory for CVE-2024-55591, published on 14 January 2025, lists what intruders did after bypassing the FortiOS login: they created an admin account and local users with random names, added those users to SSL VPN groups and then logged in through the VPN. The fix removes the flaw. The accounts stay until someone deletes them.

3what it costs you

Verizon's 2026 Data Breach Investigations Report, released on 19 May 2026, says 31% of breaches start with vulnerability exploitation, which overtook stolen credentials for the first time. CISA's Known Exploited Vulnerabilities catalog lists flaws with reliable evidence of use in real attacks. In the version released on 10 November 2026, 300 of its 1,779 entries concern firewalls, VPN gateways, routers or NAS boxes, counted by vendor and product name, since the catalog has no field for device type. In the firewall and VPN group, 56 of 149 entries carry CISA's flag for known ransomware use, against 361 of 1,779 across the whole catalog.

The bigger cost is what survives the fix. Four cases from 2025 each show a different thing that did:

  • Sessions. Citrix's bulletin for CVE-2025-5777 of 17 June 2025 asked owners to end ICA and PCoIP sessions after patching. The flaw also reached VPN, RDP proxy and sign-in setups, and researchers advised ending those sessions too. The CitrixBleed 2 page has the record.
  • Keys. Microsoft's guidance for on-premises SharePoint, revised on 20 July 2025, called it critical to rotate the servers' machine keys and restart IIS after updating, because copied keys kept working. See the ToolShell page.
  • Configuration files. SonicWall said on 8 October 2025 that an unauthorized party had accessed the cloud configuration backups of every customer who used the service, files holding encrypted credentials and configuration data. Customers had to reset the secrets inside. The cloud backup page lists them.
  • Knowledge of the box. CISA's Emergency Directive 26-01 of 15 October 2025, issued after F5 disclosed that its BIG-IP source code had been stolen, says exploitation could expose credentials and API keys embedded in the devices. The F5 page covers what that meant for customers.

The same shape appeared in 2023 with CitrixBleed. Session theft and tokens that outlive their reason are the wider problem behind it.

what it looks like when it goes wrong

Three ways this tends to go, each one taken from a real case.

your company
the gap nobody seesThe box at the edge holds more of your access than any user account, and patching it does not take back what was copied from it.a setting that leaves data open
  1. howA share link meant for one folder opens the whole storage account.
    what leavesbackups, passwords and private messageswho ends up with itanyone who finds the link
    it happenedMicrosoft AI data exposure, 2023
  2. howA default on a no-code app leaves its data readable without logging in.
    what leavespersonal records you collectedwho ends up with itanyone who looks
    it happenedPower Apps misconfiguration, 2021
  3. howA wrong setting is never rechecked and stays open for years.
    what leavescustomer data, over a long stretch nobody can account forwho ends up with itnobody knows, which is the problem
    it happenedToyota cloud exposure, 2023

4what works

  1. List what answers from outside. For every edge box, note which login and admin pages load from the internet. The Canadian-led guidance says network management interfaces should not be directly exposed to the internet. Fortinet's workaround for CVE-2024-55591 was to switch off the admin interface or limit the addresses that can reach it, and that control works before any patch exists.
  2. Move admin access off shared local accounts. The same guidance asks for default credentials to be changed, centralized authentication with role-based access, and phishing-resistant MFA on all administrative access. One shared admin login, as the shared admin accounts topic explains, leaves no record of who did what.
  3. Write the after-patch step down in advance. For each box, list what has to be ended or replaced after an urgent fix: every session type it issues, its keys, its local accounts, any configuration copy stored with the vendor. Then compare the list of local accounts with last month's.
  4. Know who reads the vendor's notices. The guidance tells owners to subscribe to them. Put the registration on a shared company address with a named owner, and agree in writing how fast the provider acts on one.

The router in the office cupboard counts too, as the office Wi-Fi guide shows. If an urgent fix for your firewall landed tomorrow, who would end the sessions, rotate the keys and check for accounts nobody created?

on the record

← all topics

your turn

what you can do about it

  1. this week

    From a phone off the office network, open the public address of your firewall and VPN gateway and note every login or admin page that loads.

    Each page that loads is reachable by every scanner on the internet. Close or restrict the admin pages, and for the ones that must stay open, ask who would rotate the box's passwords, sessions and keys after the next urgent patch.

  2. go deeper

  3. if you're not sure where to start

    Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.

    open the checklist →

the letter · every two weeks

one access gap in your inbox, with the fix.

Every issue takes one way access creeps in, shows a real incident where it went wrong, and ends with one thing to check that week. Written for the people who run the tools, without a security team behind them.

  • 1one mechanism, explained plainly
  • 2one real incident, taken apart
  • 3one step you can take on Monday

get the next issue

One email every two weeks. Your address stays here and is never passed to vendors. One click to unsubscribe. Privacy.