News

Cisco Puts an Expiration Date on Infrastructure Privilege

Cisco introduced Privileged Infrastructure Access, an approach to infrastructure administration that gives people and artificial intelligence agents temporary, task-specific permissions instead of leaving standing privileges available after their work is done.

In an Oct. 26 blog post, Cisco's Matt Caulfield described a system that uses cryptographic identity to connect an administrator or agent to the infrastructure needed for a particular task. Access is governed by short-lived privileges, with session recording providing a record of the work performed.

"If there is no work being done, no privilege exists," Caulfield wrote. Cisco positions the offering as a way to bring identity controls directly into infrastructure operations while reducing dependence on static credentials, shared secrets and broad access.

The announcement follows Cisco's previously announced Teleport partnership and its Infrastructure Identity concept, which connects the identity of a person or machine with the resources it can access, the actions it performs and the permissions governing those actions.

Closing the Infrastructure Identity Gap
Caulfield described a gap between the controls organizations apply to workforce applications and those used to administer network infrastructure. Companies have invested in single sign-on, multifactor authentication and risk-based controls for application access, he wrote, but those protections often do not follow an engineer logging into a router or switch.

Instead, infrastructure access may depend on long-lived credentials, shared accounts or separate policy systems. According to Cisco, that separation makes it harder to enforce least privilege and establish which person or system performed a particular action.

The company illustrates the problem with an administrator updating hundreds of switches during a maintenance window. If some updates fail, the administrator needs to troubleshoot before the window closes. The permissions available to handle that work, however, may cover more infrastructure and remain active longer than the task requires.

Traditional privileged access management can reduce risk through credential vaulting and rotation, Caulfield wrote. But he argued that operational friction can undermine those controls when teams create exceptions to complete urgent work. Those exceptions can leave credentials and privileges usable after the immediate need has passed.

Cisco's stated objective is to give infrastructure teams a consistent route to the devices they manage while providing security teams with policy enforcement, temporary permissions and a record of activity. The company describes operational convenience as part of the design, rather than treating access governance solely as a credential-management problem.

Temporary Sessions, Existing Network Context
Privileged Infrastructure Access makes access an on-demand action, according to the announcement. Cryptographic identity establishes the actor, and the resulting connection provides only the privileges needed to complete the task. Those privileges expire when the task concludes.

For customers using Cisco Identity Services Engine (ISE) and Terminal Access Controller Access-Control System Plus (TACACS+), the offering can draw on existing policy and device context to govern access to Cisco routers and switches. Cisco says customers can extend the same access model to other infrastructure, including servers, Kubernetes clusters and cloud resources.

In the maintenance-window example, the administrator reaches the necessary devices through a temporary session tied to that administrator's identity. The session is recorded, and the associated privilege ends when the work is complete. Cisco says this gives security teams a record of who accessed which resources, the policy governing access and what changed during the session.

"That is access delivered just in time, with just enough privilege, and for just enough time," Caulfield wrote.

The company also describes a single workflow that reaches devices without separate hops or detours. Its stated goal is to reduce the need for workarounds while allowing engineers to troubleshoot and maintain service availability. The post does not provide performance measurements for that workflow.

The Same Controls for Agents and Scripts
The access model also covers delegated AI agents and automation scripts. Cisco says each can operate with task-specific permissions, with activity attributed to the actor that performed it. Agents receive the privileges required for their work rather than inheriting broad, unmanaged infrastructure access.

Caulfield framed the announcement around the risks posed by AI-assisted attacks, arguing that sophisticated attack capabilities are becoming faster and more accessible. Cisco's response is to extend identity beyond application access to the people, machines and agents operating critical network infrastructure.

So, for cloud and infrastructure teams, the announced scope includes both interactive administration and automated operations. Cisco describes temporary privilege and attributable activity as common controls across those workflows, with routers and switches serving as a starting point for an access model that also reaches other infrastructure resources.

About the Author

David Ramel is an editor and writer at Converge 360.

Featured

Subscribe on YouTube