Insights

Separate your network before a compromised device connects the dots

9 October 2026

Use network segmentation to separate guest Wi-Fi, cameras, phones and business systems, restrict traffic and assign monitoring responsibility.

Cisco has outlined why businesses should use their networks to enforce security controls, rather than simply carry traffic. For Australian small and medium businesses, the practical starting point is network segmentation: separating devices by purpose and controlling which connections can cross those boundaries.

In its September 2026 networking article, Cisco describes an approach that brings network infrastructure, traffic protection and operational oversight together. The useful question for an SMB is straightforward: if a visitor’s laptop, camera or desk phone is compromised, what else could it reach?

Start network segmentation with a device and service map

Before changing firewall rules, identify what is connected and what each device needs to do. A list of laptops is not enough. Include wireless access points, switches, printers, cameras, door controllers, desk phones, payment terminals and equipment installed by contractors.

Record the device’s owner, location, support provider, update status and required connections. Include remote access tools and vendor support arrangements. An unknown device should trigger investigation, not a permanent exception because nobody wants to unplug it.

Ask your IT provider for a simple diagram showing:

  • Internet connections, firewalls, switches and wireless access points.
  • Existing network segments and their assigned devices.
  • Local servers, storage and business applications.
  • Connections to other sites and remote users.
  • Equipment administration interfaces and who can access them.

The goal is a usable map, not an elaborate document. It should show where a device connects, which boundary protects it and who owns that boundary.

Separate guests, cameras, phones and business systems

A virtual local area network, or VLAN, creates a logical separation between groups of devices. However, VLANs alone do not define a secure policy. Traffic routed between them still needs explicit restrictions.

Use the following as a starting point, then adjust it to your applications and equipment:

| Network group | Connections normally required | Connections to restrict | | --- | --- | --- | | Guest Wi-Fi | Internet access and essential supporting services | Internal systems, equipment administration and other guest devices where supported | | Cameras and recording | Approved recorder, time service and necessary update or cloud services | Staff computers, finance systems and unrelated cameras or devices | | Business phones | Approved call platform, provisioning and supporting services | General access to servers, cameras and staff devices | | Staff devices | Approved business applications, printing and internet services | Infrastructure administration unless specifically authorised | | Business servers | Defined application, backup and management connections | Unnecessary access from guest, camera or phone networks | | Network management | Authorised administration tools and administrators | Ordinary user and guest access |

Door controllers and other building systems may need their own group rather than sharing with cameras. Follow the supported design and test changes with the security installer.

Network segmentation should follow risk and function, not simply departments. Finance staff may use the same cloud applications as everyone else, while a backup server needs tightly controlled access regardless of who owns its budget.

Make cross-network access an exception

Start with a policy that blocks traffic between groups unless there is a documented business need. Introduce it through a planned change, not an untested switch during business hours.

For every permitted connection, record:

  • Source: the device or group initiating the connection.
  • Destination: the specific system or approved service.
  • Service: the necessary protocol and port, rather than unrestricted access.
  • Reason: the business function supported.
  • Owner: who can approve, review and remove the rule.

For example, viewing camera footage does not necessarily require every staff laptop to reach every camera. Access to the recorder or an approved viewing service may be sufficient. Verify this with the installer before changing the rules.

Phones also need more than a generic internet allowance. Confirm calling, provisioning and media requirements with the phone provider. Network segmentation must preserve call quality and legitimate functionality. The multi-location phone systems checklist can help identify operational dependencies before changes.

Avoid broad temporary exceptions. Give each exception an expiry date and review its usage. Where devices remain on the same segment, inter-network firewall rules may not control their direct communication; client isolation or additional controls may be needed.

Test the boundaries from an ordinary device

A different Wi-Fi name does not prove isolation. Two wireless networks can still connect to the same internal network, or a firewall can permit more traffic than intended.

Have your provider test from representative devices in each group. Record both successful business connections and blocked unauthorised ones.

Useful checks include:

  • A guest device cannot reach internal printers, servers or equipment login pages.
  • A camera cannot initiate connections to a staff laptop or finance server.
  • A phone can make and receive calls but cannot browse infrastructure administration interfaces.
  • An ordinary staff account cannot administer switches or wireless access points.
  • Remote vendor access reaches only the supported equipment, not the whole site.

Test wired ports as well as Wi-Fi. An unused wall socket should not silently provide unrestricted business access.

Repeat the checks after significant network changes. Keep the results with the configuration records so network segmentation remains something you can demonstrate, rather than assume.

Assign responsibility for monitoring and response

Cisco’s emphasis on operational oversight matters because a well-designed network can drift. Devices move, installers add exceptions and equipment eventually falls out of support.

Name a person or service provider responsible for reviewing security-relevant network events. Define coverage hours and escalation arrangements explicitly; do not assume a managed service includes continuous security monitoring.

Agree on which events require attention:

  • Repeated blocked connections between device groups.
  • New or unexpected devices joining sensitive networks.
  • Changes to firewall rules or administrator accounts.
  • Unusual remote administration sessions.
  • Equipment no longer sending logs or receiving supported updates.

Centralise relevant logs, synchronise device clocks and set retention according to investigation needs, privacy obligations and available capacity. An alert needs a recipient, a response procedure and an escalation path.

Decide who can isolate a device and when business approval is required. Disconnecting a camera or phone service can have operational consequences. Align these decisions with your ransomware response plan, including an alternative contact method if normal communications are affected.

Roll out changes without losing essential services

Network segmentation is not a substitute for patching, strong authentication, endpoint protection or tested backups. It limits reachable systems when another control fails.

Before rollout, back up configurations and document a rollback procedure. Pilot changes on a small group, then verify printing, calls, camera recording, access control and business applications with their owners.

Prioritise obvious exposure first: guest access to internal systems, publicly reachable administration interfaces and unrestricted contractor connections. Then address more complex dependencies in scheduled maintenance windows.

Use your downtime and recovery priorities to decide which services need the most careful testing. Review the design after an office move, application change, equipment replacement or new vendor connection.

Tech Engine can review your cyber security and design and manage business Wi-Fi and networks across Australia, coordinating phones and physical security requirements. To discuss your network boundaries and monitoring responsibilities, call 1300 088 324 or email sales@techengine.au.

Want this applied to your business?

Request an AI Blueprint and we will map the processes worth automating first.

Request an AI Blueprint