
Technologies
Security and Cisco ISE
Identity‑Driven Network Security That Scales
Technologies
Control Who and What Connects, Everywhere, With IPTel
Modern networks support employees, contractors, guests and IoT across wired, wireless and remote access. Security built purely on IP addresses, VLANs or locations is no longer enough.
Cisco Identity Services Engine (ISE) is Cisco's network access control and policy platform, the policy brain of the network. It enforces consistent access based on who or what is connecting, not just where they connect from.
ISE supports the full range of 802.1X methods, from certificate-based EAP-TLS and EAP-PEAP to legacy PAP CHAP authentication, and we plan upgrades around the Cisco ISE lifecycle. Read why Cisco ISE and our post on WPA2 Enterprise PEAP security.
How Does Your Network Measure Up Against ASD Essentials? Take our free ASD Essentials Network Readiness Assessment: 33 questions across eight network areas, with a rating for each area and a report setting out next steps in ASD's priority order.
Key Capabilities
What Cisco ISE Delivers
Central Authentication
Centralised authentication and authorisation with role-based access across wired and wireless.
Device Profiling
Visibility and classification of every connected device, including IoT and OT.
Identity-Centric Policy
Access based on user identity, device type and posture, authentication method and context.
Secure Onboarding
Employees, contractors, guests and personal devices each get only the access they need, automatically.
Security Ecosystem
Policy enforced through your network infrastructure, with context shared to security platforms.
Audit and Zero Trust
Ideal for compliance needs, diverse devices and organisations adopting zero trust.
How IPTel Helps
Security That Enables the Business
We design security architectures that balance risk reduction, usability and day-to-day operations.
Fit for Purpose
Designed around your environment and risk profile.
Scalable
Ready for new sites, users and device types.
Auditable and Sustainable
Clear policy your team can operate and auditors can follow.
Free tool
Is Your Network Protected Against AI-Speed Attacks?
Take our 15-question AI-Era Cyber Defence Readiness Check. See your score across Cisco's three pillars, your biggest gaps and what to fix first.
Healthcare
Network Access Control for Multi-Campus Healthcare Networks
Cisco Identity Services Engine (ISE) is network access control software that runs a multi-campus healthcare network from one set of policies. One ISE deployment identifies every staff device, medical device and guest at every hospital and places it on the right segment, so access is the same at every campus. IPTel designs, deploys and manages Cisco ISE for Australian healthcare organisations.
One Deployment Across Every Campus
ISE runs as a distributed deployment: primary and secondary administration nodes, monitoring nodes, and policy service nodes placed close to each campus or data centre to authenticate devices locally. A large deployment supports up to 50 policy service nodes and, on the largest appliances, up to 2 million concurrent active endpoints, and Cisco requires no more than 300 ms of latency between the primary administration node and every other node, which suits campuses across Australia. You write policy once and it applies everywhere.
Medical Devices That Can't Use 802.1X
Infusion pumps, patient monitors, location tags and imaging equipment often can't authenticate with 802.1X or run security software. ISE profiles them from attributes such as MAC address vendor, DHCP and network behaviour, then places each device type on a restricted segment that can only reach the clinical systems it needs. Identity PSK can give each device group its own Wi-Fi key on a shared SSID.
The Same Segments at Every Hospital
Cisco TrustSec security group tags mean "patient monitors", "clinical staff" or "contractors" are the same group at every campus, whatever the local VLAN numbering. Policy between groups follows the device, which keeps a compromised device contained wherever it connects. Paired with Cisco Catalyst Center templates, each campus is built to the same standard.
Clinicians Who Work Across Campuses
Hospital-owned phones, laptops and tablets use certificate-based EAP-TLS, so a clinician's device connects securely at any campus with the same access and no passwords to share. Patient and visitor Wi-Fi uses one guest portal across every site, kept separate from clinical systems.
Rolling Out Without Disrupting Care
We start ISE in monitor mode to build an inventory of every device at each campus without blocking anything, agree device groups and segments with clinical engineering and IT, then enforce policy campus by campus and ward by ward in agreed windows, with a fallback ready. See how this works in Hospital Wi-Fi Onboarding With Cisco ISE. For scale, IPTel designed and commissioned wireless upgrades across about 150 hospital sites for a national healthcare provider, each built to one standard design.
Managed After Go-Live
Once policy is enforced, new devices are onboarded by policy, not by ticket. IPTel can monitor, patch and manage your ISE deployment through Managed Cisco ISE, with your team keeping full administrative access.
Cisco ISE and Network Access Control: FAQs
What Network Access Control Software Works for Multi-Campus Healthcare Networks?
Cisco Identity Services Engine (ISE) is network access control software built for large, distributed networks. One ISE deployment applies the same policy at every hospital campus, identifies staff devices, medical devices and guests as they connect, and places each on the right segment. IPTel designs, deploys and manages Cisco ISE for Australian healthcare organisations.
Can One Cisco ISE Deployment Cover Several Hospitals?
Yes. ISE runs as a distributed deployment with policy service nodes placed near each campus or data centre. A large deployment supports up to 50 policy service nodes and up to 2 million concurrent active endpoints on the largest appliances, with policy written once and applied everywhere.
How Does ISE Handle Medical Devices That Can't Use 802.1X?
ISE profiles them using attributes such as MAC address vendor, DHCP and network behaviour, then places them on a restricted segment that can only reach the systems they need. Identity PSK can also give each device group its own Wi-Fi key on a shared SSID.
Does IPTel Manage Cisco ISE After Deployment?
Yes. Through Managed Cisco ISE, IPTel monitors, patches and manages your ISE deployment, while your team keeps full administrative access.
Need Cisco Security Hardware or Licences?
Cisco Secure Firewall, Cisco ISE and Secure Access licences, supplied and specified by our engineers.
From the Blog
Network Security Insights From the IPTel Blog
Practical guides to Cisco ISE, zero trust and securing your network.
Talk to an IPTel Engineer
Tell us about your site and what you need from your network. We'll come back with practical advice and a free quote.
.png?width=200&height=59&name=IPTellogo-byline-2020-dark-v2-pnd-optimised-500%20(1).png)