Intercept IT All articles
Cybersecurity

The Flat Network Habit: Why One Wi-Fi Password Shouldn't Open Your Whole Office

Intercept IT
The Flat Network Habit: Why One Wi-Fi Password Shouldn't Open Your Whole Office

Photo: United States Small Business Administration, Public domain, via Wikimedia Commons

A visitor asks for the Wi-Fi. Someone behind reception reads out the password from a sticky note, and the job is done. It feels like hospitality. What it actually is, in a surprising number of small UK offices, is a seat on the same network as your file server, your cloud backup agent, the till, the CCTV recorder and the printer that still has last month's invoices sitting in its queue.

That is not a dramatic worst case. It is the default outcome of how most small offices get built: one internet connection, one router from the ISP, one or two Wi-Fi names, and everything that can connect, connecting to it. The technical term is a flat network. The practical term is a building with no internal doors.

What flat actually means in practice

On a flat network, every device can usually talk to every other device. Your laptop can see the printer, which is convenient. The printer can also see your laptop, which is less convenient. The guest's phone can see the CCTV box. The smart TV in the meeting room can see the accounts share. None of this requires anyone to be clever or malicious; it just requires everything to be on the same address range with nothing in between.

The reason this matters is that a huge proportion of real-world incidents start with one boring device being compromised — a cheap camera with old firmware, a personal phone with a dodgy app, a laptop that picked something up on a home connection. On a flat network, that one device becomes a starting point rather than a dead end.

Why the guest network often isn't one

Plenty of routers offer a guest network that is genuinely separate. Plenty of others offer a guest network that is really just a second Wi-Fi name with a different password, running on the same internal network with client isolation turned off. The label says guest. The wiring says otherwise.

There are three common reasons this happens. The ISP-supplied router defaults to the simple version. Whoever set it up had fifteen minutes and no reason to dig into the advanced menus. And nobody has ever tested it, because from the outside everything works — the visitor gets online, the printer prints, the tills ring up.

The 45-minute audit

You do not need to understand VLANs to run this. You need a phone, a browser and the willingness to be a bit nosy about your own building.

1. Write down what is actually on the Wi-Fi (10 minutes)

Walk the office with a notepad, or open the admin app for your router if it has one, and list everything connected wirelessly. Include the boring items: printers, the CCTV hub, the door access controller, the smart TV, the warehouse scanners, the heat pump app bridge, the fridge if it has one. Include personal devices that staff have connected — phones, tablets, the Xbox that appeared in the breakout room in 2024 and never left.

Most owners find between five and fifteen devices they had genuinely forgotten about. That list is the foundation of everything else.

2. Test whether isolation is really on (10 minutes)

Join the guest Wi-Fi from your phone. Then try to reach something you know is on the main network — the printer's web page, the NAS, the CCTV app on the local address. A free network scanner app on your phone will list other devices it can see on the same network. If it shows you a row of devices that are not your own, you have your answer: the guest network is not isolated.

Do the reverse test too. From a staff laptop, see whether you can see the visitor's phone. If you can, so can anything else that gets onto that network.

3. Open the router and look for the switch (10 minutes)

Log into your router or access point admin page. Look for settings named client isolation, AP isolation, guest network isolation, or network separation. If your kit supports VLANs and you have a managed switch, this is where the real separation lives — but even a basic business router will usually have a guest isolation toggle.

If you cannot get into the admin page because the installer kept the password, that is the first thing to fix. Ask your IT supplier for the admin credentials in writing, or ask them to change the settings while you watch.

4. Rotate the passwords and stop the group chat leak (10 minutes)

Change the guest password today. Change the staff Wi-Fi password too, ideally once a quarter. Move the guest password off the sticky note and into a small printed card at reception, and change it after big events or when a contractor leaves.

While you are in there, check who is on the network. Most routers will show a list of connected devices with names and MAC addresses. Anything you do not recognise deserves a question, not a shrug.

5. Decide what should never be on Wi-Fi (5 minutes)

Some kit simply should not be wireless, and definitely should not be on the same network as visitors. CCTV recorders, NAS boxes holding client files, tills and card terminals, and the machine running your accounts package are the usual suspects. Where you can, wire them. Where you cannot, put them on a separate network with a firewall rule between them and everything else.

The devices nobody budgets for

The audit almost always turns up the same cast: a smart TV with a factory default password, a cheap indoor camera from an online marketplace, a personal iPad logged into a staff member's work email, a 3D printer in the workshop running firmware from 2019. None of these is a crisis on its own. Put together on a flat network, they are the side door nobody locked.

Where this shows up in the paperwork

Cyber Essentials asks questions about boundary firewalls and secure configuration, and network separation is the sort of thing an assessor will probe if your setup looks thin. Cyber insurers have started asking similar questions, and a claim can be complicated by a network where the guest Wi-Fi and the finance share were effectively the same thing. It is much easier to answer those questions when you have actually checked, rather than assumed.

What good looks like without a rebuild

You do not need to rip out the building. A reasonable small-office setup in 2026 looks like this: a business-grade router or access point with proper guest isolation, two or three separate Wi-Fi names for staff, guests and devices, WPA3 where your kit supports it, WPS switched off, remote administration disabled, firmware updated when the vendor ships a patch, and a written list of what is allowed on which network.

That is it. No drama, no enormous invoice. Just internal doors where previously there was one open corridor.

The short version

If you take one thing from this, take the test in step two. Sit in reception with your phone, join the guest Wi-Fi, and see whether you can spot anything that belongs to the business. If you can, so can anyone else who has ever been handed that password — and there are more of them than you think.

All Articles

Related Articles

The Rule You Didn’t Write: Finding Silent Forwarding in Microsoft 365 and Google Workspace

The Rule You Didn’t Write: Finding Silent Forwarding in Microsoft 365 and Google Workspace

The Unlisted Attendee: Auditing the AI Note-Taker Before Your Next Client Call

The Unlisted Attendee: Auditing the AI Note-Taker Before Your Next Client Call

The Browser Tab You Didn't Approve: A Plain-English AI Data Audit

The Browser Tab You Didn't Approve: A Plain-English AI Data Audit