Automated Control Layer Injection for User Tool Security

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

User tools within organizations often operate without appropriate IT controls, leading to data security breaches and requiring burdensome manual modifications to add necessary controls, which can be costly and time-consuming.

Innovation Solution

Implementing a common control layer across user tools through control code that includes access, version, and change control modules, automatically modifying user tools to ensure centralized and consistent implementation of controls.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual modifications are used to add controls to user tools, then controls can be implemented, but the process becomes time-consuming and costly

Engineering Contradiction:

Improvecontrol implementationVSAvoidmanual modification time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service by automatically modifying user tools to include control code. The processor receives user tools, automatically adds control code implementing a common control layer, and deploys controlled user tools without requiring manual intervention for each tool, thus resolving the time-consuming nature of manual control implementation

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by pre-configuring control code that implements a common control layer before deployment. The control code is prepared in advance with access control, change control, and version control modules, which are then automatically integrated into user tools, eliminating the need for time-consuming post-deployment manual modifications

Inventive Principle:

Principle #10Preliminary action

2Measurement precision

If individual manual checking of each user tool is performed to confirm controls, then control compliance can be verified, but the task becomes burdensome

Engineering Contradiction:

Improvecontrol verification accuracyVSAvoidverification efficiency

Core Design Contradiction:

Measurement precisionVSProductivity

Solution Approach 1:

The controlled user tools self-verify compliance through embedded control code that automatically implements and enforces the common control layer. The system provides centralized auditing capabilities that automatically log activities and report compliance status, eliminating the need for burdensome manual checking while maintaining verification accuracy

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms through centralized auditing capabilities that automatically monitor and report on control compliance. The control code embedded in user tools provides continuous feedback on access control, change control, and version control status, enabling automated verification without manual intervention

Inventive Principle:

Principle #23Feedback

3Stability of the object's composition

If controls are added consistently and centrally to user tools, then control implementation becomes standardized, but system complexity increases

Engineering Contradiction:

Improvecontrol consistencyVSAvoidsystem architecture complexity

Core Design Contradiction:

Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The system achieves universality by creating a common control layer that can be consistently applied across multiple different user tools. The control code is designed to be universally compatible and can be automatically integrated into various user tools, providing standardized control implementation without requiring separate solutions for each tool

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system segments control functionality into distinct control modules (access control, change control, version control) that can be independently managed and combined. This modular approach allows consistent control implementation across user tools while keeping the system architecture manageable through clear separation of control concerns

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS10095220B1Modifying user tools to include control code for implementing a common control layer

Publication Date: 2018.10.09 JPMORGAN CHASE BANK NA

AI summary

In certain embodiments, multiple user tools each comprise a script program implementing an operation for addition to a respective compiled software program deployed within a computing environment. A memory module stores control code for insertion into computer code of a particular user tool. The control code implements a common control layer, implementing control modules across the user tools. The control modules include access control for controlling access to the user tool, change control for controlling modification of the user tool, and version control for controlling use of an appropriate version of the user tool. A processor receives the particular user tool; to create a controlled particular user tool, automatically modifies, the computer code of the particular user tool to add the control code; and deploys the controlled particular user tool for use in the computing environment in a manner controlled by the control code of the controlled particular user tool.