Shared PRA Session Pause-Resume Control for Zero-Trust Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The traditional enterprise network perimeter-based security model is inadequate in the era of cloud-based applications and mobile users, leading to increased security risks from unsecured devices and unmanaged access to the Internet, especially for OT/IOT/IIOT infrastructure.

Innovation Solution

A cloud-based system providing zero-trust access through lightweight connectors, enabling secure remote access for OT/IOT/IIOT infrastructure with pause and resume functionality for privileged remote access sessions, ensuring only authorized users can access specific applications while blocking unauthorized commands.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If pause and resume functionality is implemented for shared PRA sessions, then session management control and security are improved, but system complexity increases

Engineering Contradiction:
Improvesession management controlVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A pause command mechanism is introduced as an intermediary control between users and the application. When a pause command is received, the system blocks commands from reaching the application while maintaining the session connection, allowing controlled interruption without full termination. This intermediary layer enables pause/resume functionality while preserving session state.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If commands are blocked during pause state, then security is improved by preventing unauthorized access, but user productivity decreases due to session interruption

Engineering Contradiction:
Improveunauthorized access preventionVSAvoiduser productivity
Core Design Contradiction:
Object-affected harmful factorsVSProductivity

Solution Approach 1:

The system dynamically transitions between operational and paused states based on received commands. In the paused state, command blocking is selectively applied while maintaining connection integrity. The session can be dynamically resumed by sending a resume command, allowing flexible control over when security restrictions are applied versus when normal operations continue.

Inventive Principle:
Principle #15Dynamics

3Device complexity

If session termination and re-initiation is required instead of pause/resume, then system complexity is reduced, but time loss increases due to session re-establishment

Engineering Contradiction:
Improvesystem complexityVSAvoidsession re-establishment time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The pause command is processed in advance to block commands before they reach the application, preventing unauthorized or unintended actions. The session state is preserved during this preliminary blocking phase, and the resume command restores normal command flow without requiring session re-establishment, saving time compared to full termination and re-initiation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12634284B2Systems and methods for pause and resume functionality for shared privileged remote access (PRA) sessions
Publication Date: 2026.05.19 ZSCALER INC
  • US12634284B2 patent drawing
  • US12634284B2 patent drawing
  • US12634284B2 patent drawing

AI summary

Systems and methods for pause and resume functionality for shared Privileged Remote Access (PRA) sessions. The methods include steps of, responsive to determining one or more users are allowed to access an application associated with infrastructure, determining the one or more users' security and access policies, and creating a Privileged Remote Access (PRA) session for the one or more users; brokering a connection between one or more user devices associated with the one or more users and the application through a lightweight connector, and enabling the one or more users to send commands to the application; receiving a pause command from one of the one or more users; and responsive to receiving the pause command, blocking commands from the one or more users from reaching the application.