Zero Trust Policy Engine for External Resource Onboarding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Implementing a zero-trust architecture in computing environments poses challenges such as user frustration due to constant verification requirements and potential circumvention of security measures, leading to cybersecurity risks.

Innovation Solution

A method and system for providing external resources through a zero-trust environment, which involves receiving a request to access an external resource, detecting the associated domain, and configuring a policy engine to allow network traffic between the domain and a designated user account, based on the received request.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If constant verification and authentication are required in zero-trust architecture, then security is improved, but user experience deteriorates due to interruptions and frustration

Engineering Contradiction:
ImprovesecurityVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary authentication and verification actions before granting access to external resources. The policy engine pre-establishes trust relationships and access policies for authorized domains, so that once authenticated, users experience minimal interruptions during their workflow. The initial authentication captures user identity and device information, and subsequent access decisions are made automatically based on pre-configured policies.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The policy engine acts as an intermediary between the zero-trust environment and external resources. It mediates access requests by evaluating policies and making automated decisions, reducing the need for constant user verification. The intermediary handles authentication challenges and policy enforcement, allowing users to work smoothly while security requirements are met in the background.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If users are restricted to complete only certain actions in zero-trust environment, then security is improved, but user frustration increases leading to circumvention of measures

Engineering Contradiction:
ImprovesecurityVSAvoidcircumvention behavior
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The access control system is dynamic rather than static. The policy engine continuously evaluates user requests against current policies and context, allowing authorized actions without restriction while blocking unauthorized ones. This dynamic approach adapts to user needs in real-time, providing necessary flexibility for legitimate work while maintaining security boundaries, thereby reducing frustration and circumvention behavior.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where access decisions are based on continuous evaluation of user actions, device state, and policy requirements. When users attempt actions, the system provides immediate feedback through the policy engine that either permits or denies based on pre-established rules, rather than imposing arbitrary restrictions. This feedback-driven approach helps users understand security boundaries while maintaining productivity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250193153A1Techniques for onboarding web applications in a zero trust environment
Publication Date: 2025.06.12 HEWLETT PACKARD ENTERPRISE DEV LP
  • US20250193153A1 patent drawing
  • US20250193153A1 patent drawing
  • US20250193153A1 patent drawing

AI summary

A system and method for providing external resources through a zero trust environment includes recording a web session of a first user to generate a policy allowing a second user to access the resource used in the web session. The method includes receiving a request to initiate a network session with the zero trust environment, the request including login credentials, wherein the login credentials correspond to an authorizing user account; receiving a request to access a resource in a network environment which is external to the zero trust environment; detecting in the request a domain associated with the resource; and configuring a policy engine of the zero trust environment to generate a policy allowing network traffic between the domain and a designated user account, based on the received request.