Dynamic Permission Testing for Code Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for testing user permissions in computing systems are rigid, time-consuming, and expensive, particularly when repeatability is required, as they involve setting up all dependencies beforehand and executing tests under a fixed permission set.

Innovation Solution

A method that dynamically changes the permission level of a computing system to match a specified permission set during code execution, allowing for the execution of code within those permissions and determining if the set includes sufficient permissions for performed actions, with the ability to use multiple permission sets and simulate real user activity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional permission testing methods are used with fixed permission sets and pre-configured dependencies, then testing can be performed with established permissions, but the testing process becomes rigid, time-consuming, and expensive

Engineering Contradiction:
Improvepermission testing accuracyVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies dynamics by enabling runtime modification of permission sets during test execution. Instead of using fixed permission sets configured beforehand, the system dynamically adjusts permissions based on actual user roles and scenarios being tested, making the testing process flexible and adaptable to different testing needs without requiring complete reconfiguration

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of permission levels from static to dynamic. By allowing permission sets to be modified during runtime based on test requirements, the system can efficiently test multiple permission scenarios without the time cost of reconfiguring the entire testing environment for each scenario

Inventive Principle:
Principle #35Parameter changes

2Reliability

If all dependencies are set up beforehand for permission testing, then complete testing scenarios can be executed, but the setup process becomes complex and repetitive

Engineering Contradiction:
Improvetest completenessVSAvoidtest setup complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-defining permission set templates and dependency configurations that can be automatically applied during testing. Instead of manually setting up all dependencies for each test scenario, the system has pre-configured permission structures ready to be activated, reducing setup complexity while maintaining test completeness

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates universal permission set templates that can serve multiple testing scenarios. A single permission set definition can be reused across different test cases by dynamically activating it, eliminating the need to create and maintain separate dependency configurations for each test scenario

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Stability of the object's composition

If fixed permission sets are used for testing, then consistent testing conditions are maintained, but the ability to test different user roles and scenarios efficiently is reduced

Engineering Contradiction:
Improvetesting consistencyVSAvoidpermission scenario flexibility
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system maintains testing consistency through controlled dynamic changes. Permission sets are modified during runtime based on predefined test scenarios, ensuring that each scenario is tested with appropriate permissions while maintaining overall test structure and consistency

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent enables parameter changes in permission levels during test execution. By allowing permission sets to be adjusted based on the specific scenario being tested, the system can efficiently test multiple user roles and permission scenarios while maintaining consistency through structured parameter management

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10360135B2Privilege test and monitoring
Publication Date: 2019.07.23 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10360135B2 patent drawing
  • US10360135B2 patent drawing
  • US10360135B2 patent drawing

AI summary

Testing code. A method includes identifying in code being executed on a computing system a specification of a permission set. The method further includes dynamically, as the code is running changing a permission level of the computing system to match the permission set. The method further includes executing code at the computing system within the permissions in the permission set. The method further includes during execution, for actions performed in the execution, determining if the permission set includes sufficient permissions for the action to be performed.