A network engineer is halfway through a firewall change when a question lands in the incident channel: who made the last configuration change on the switch upstream? The device is reachable, the service is still running, but the team cannot confidently connect the change to a person, an approval or a command history. That is not just an audit headache. It makes troubleshooting slower and turns routine administration into a trust exercise.
Network infrastructure needs its own access-control discipline. A shared administrator password may get the job done, but it makes individual accountability difficult. A stronger design separates who can reach a device, what that person can do once connected and how the activity is recorded.
Three questions every admin session should answer
For switches, routers, firewalls and other network appliances, start with the familiar AAA model: authentication, authorisation and accounting.
- Authentication: Is this the named administrator, using an approved identity and a strong sign-in method?
- Authorisation: Which devices and commands is that administrator allowed to use? Read-only troubleshooting should not automatically carry the same privileges as a configuration change.
- Accounting: What did the administrator actually do, on which device and at what time? A login record alone is not a useful substitute for command-level evidence.
Centralising these decisions helps avoid a different local account and password policy on every device. It also gives the security team a consistent way to remove access when roles change or a contractor’s engagement ends.
Why TACACS+ is relevant to infrastructure teams
TACACS+ is commonly used to centralise authentication, authorisation and accounting for network-device administration. Its command-authorisation model is particularly useful when an organisation wants to distinguish between viewing a configuration, running diagnostic commands and changing production settings.
Portnox describes its cloud-delivered TACACS+ service as a way to centralise authentication and granular command authorisation for routers, switches, firewalls and other critical systems, with detailed session logging. That gives network teams a route to more consistent controls without treating every device as a separate identity-management island.
RADIUS and TACACS+ are sometimes discussed together because both appear in network access architectures, but they are not interchangeable in every deployment. RADIUS is widely used for user and device network authentication, while TACACS+ is often selected when administrators need more granular control and accounting for commands executed on network equipment. Map the actual use cases before deciding which protocol belongs at each enforcement point.
Keep the management plane separate from everyday connectivity
One common mistake is to treat an administrator’s access path as just another user connection. The management plane deserves tighter controls than ordinary browsing or office Wi-Fi.
Use individual administrator identities wherever possible. Define role-based command sets for network operations, security engineering, service providers and read-only auditors. Keep emergency access separate, tightly monitored and tested. If a supplier needs to maintain one firewall, do not give that account the same reach as an internal infrastructure lead.
Also review the surrounding controls: multi-factor authentication or certificate-backed identity where supported, a restricted management path, device posture checks for the administrator’s endpoint, and a documented approval process for high-impact changes. Centralised command accounting is most valuable when it can be matched with a change ticket and a named owner.
Do not confuse device administration with remote application access
Network teams often need to secure more than a switch command line. They may also connect to server consoles, remote desktops or management applications. Those are related problems, but they are not the same enforcement point.
In a 10 February 2026 announcement, Portnox said its passwordless Zero Trust Network Access capabilities were expanding to console-based applications, including RDP, SSH, VNC and Telnet. The announcement described certificate-based authentication, continuous device-posture checks and risk-adaptive policies for those connections.
That ZTNA layer can complement infrastructure AAA: use application-level access controls to govern who can establish a remote console session, and use TACACS+ where network-device command authorisation and accounting are required. Keep the boundaries clear in the architecture so a successful remote login is not mistaken for approval to run every privileged command.
Make the audit trail useful during a real incident
Logs are only valuable if responders can answer practical questions quickly. Decide what evidence should be retained, who can review it and how it connects to your change-management process. For critical devices, the record should help an investigator identify the administrator, target device, command activity and session timing without stitching together screenshots and chat messages.
Test the failure cases too. What happens if the central authentication service is unavailable? Which emergency accounts remain available, who can use them and how is their use reviewed afterwards? A resilient design should not force engineers to choose between restoring a service and following a security policy.
A focused rollout beats a network-wide switch flip
Start with a small group of non-critical devices and a handful of administrator roles. Inventory the platforms and firmware versions, identify the protocols they support, define read-only and change-capable command sets, then test normal access, denied commands, emergency access and log review.
Before expanding, confirm that the process works for internal staff and approved service partners. Measure how quickly access can be granted and revoked, whether the audit trail answers the questions an incident responder would ask, and how much manual administration has been removed.
A TACACS+ solution should make network administration more accountable without turning every maintenance task into a paperwork marathon. When identity, command permissions and session records line up, teams can troubleshoot with greater confidence and prove who changed what when it matters.
About Portnox
Portnox provides simple-to-deploy, operate and maintain network access control, security and visibility solutions. Portnox software can be deployed on-premises, as a cloud-delivered service, or in hybrid mode. It is agentless and vendor-agnostic, allowing organizations to maximize their existing network and cybersecurity investments. Hundreds of enterprises around the world rely on Portnox for network visibility, cybersecurity policy enforcement and regulatory compliance. The company has been recognized for its innovations by Info Security Products Guide, Cyber Security Excellence Awards, IoT Innovator Awards, Computing Security Awards, Best of Interop ITX and Cyber Defense Magazine. Portnox has offices in the U.S., Europe and Asia. For information visit http://www.portnox.com, and follow us on Twitter and LinkedIn.。
About Version 2 Limited
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.
Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.












