Trusted Application Profile Verification for Shared Library Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems lack a comprehensive solution to ensure that only trusted applications can access shared code libraries, particularly for sensitive operations like encryption and decryption, by verifying the application's authorization and execution environment.

Innovation Solution

An administrative server creates and manages trusted application configurations, comparing customer application profiles to predefined properties and constraints to authorize access to shared libraries, with ongoing monitoring and auditing for security adherence.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If shared code libraries are made accessible to multiple applications, then code reusability and system efficiency are improved, but security risks increase due to potential unauthorized access

Engineering Contradiction:
Improvecode reusabilityVSAvoidunauthorized access risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary verification mechanism that sits between applications and shared code libraries. This intermediary checks application profiles against trusted application configurations before allowing access, thus enabling code reusability while preventing unauthorized access through systematic verification

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If strict access verification is implemented for shared libraries, then security is improved, but system complexity increases due to additional verification steps

Engineering Contradiction:
ImprovesecurityVSAvoidverification system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-defining trusted application configurations with required properties and constraints before access attempts occur. When applications need to access shared libraries, the system simply checks whether their profiles match these pre-established configurations, avoiding complex real-time analysis and simplifying the verification process

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If application profiles are thoroughly verified against trusted configurations, then access control accuracy is improved, but processing time increases due to detailed property comparison

Engineering Contradiction:
Improveaccess control accuracyVSAvoidverification processing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent implements partial action by verifying only the essential properties defined in trusted application configurations rather than analyzing all possible application attributes. The system checks specific required properties and constraints outlined in pre-defined configurations, achieving sufficient access control accuracy without exhaustive verification of every application detail

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11960590B2Enforcing trusted application settings for shared code libraries
Publication Date: 2024.04.16 PROTEGRITY US HLDG LLC
  • US11960590B2 patent drawing
  • US11960590B2 patent drawing
  • US11960590B2 patent drawing

AI summary

Access to a shared library API is restricted for a customer application by a security system. A profile for each of a plurality of trusted applications is generated and stored in a security database. When a customer application attempts to access the shared library API, the customer application is verified by extracting a customer application profile for the customer application, comparing the customer application profile with each stored trusted application profile, and verifying that the customer application can access the shared library API based on the comparison. Based on the verification, the customer application may be allowed to or access to the shared library API or may be prevented from accessing the shared library API.