RBAC Scope Updates for Cloud Resource Access Changes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing RBAC systems require manual and time-consuming processes to update access control scopes, especially in cloud-based computing environments, leading to inefficiencies and delays in granting or revoking access to computing resources.

Innovation Solution

An automated system that uses a back-end application computer server to identify computing resource landscape changes and automatically update RBAC scope data stores, allowing for rapid and secure adjustments to access control rules without manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual processes are used to update RBAC access control scopes, then security control is maintained, but time consumption increases and productivity decreases

Engineering Contradiction:
Improvesecurity controlVSAvoidaccess update speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system enables self-service automation where the RBAC system automatically detects computing resource landscape changes and updates access control scopes without requiring manual intervention. The automated scope change mechanism monitors resource provisioning and decommissioning events, then autonomously adjusts role-based access permissions to reflect current infrastructure state, thereby maintaining security while dramatically improving update speed.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback loops that continuously monitor computing resource landscape changes and automatically trigger RBAC scope updates. The automated mechanism receives feedback about resource provisioning status, evaluates against defined policies, and executes corresponding access control changes, creating a closed-loop system that maintains security awareness while operating at high speed.

Inventive Principle:
Principle #23Feedback

2Measurement precision

If manual RBAC scope changes are processed, then access control accuracy is maintained, but time required increases to several days

Engineering Contradiction:
Improveaccess control accuracyVSAvoidupdate time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-defining access control policies and scope change rules before actual changes occur. When computing resources are provisioned or decommissioned, the system has pre-established the logic to automatically determine required RBAC scope adjustments, enabling rapid execution without manual analysis and ensuring both speed and accuracy of updates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces manual mechanical processes with automated electronic systems. Instead of human administrators manually processing RBAC scope changes through ticketing systems and spreadsheets, the invention uses automated software mechanisms that electronically detect resource changes, evaluate policies, and execute scope updates, reducing update time from days to hours while maintaining high accuracy through systematic algorithmic processing.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Productivity

If automated RBAC scope changes are implemented, then productivity increases, but system complexity increases

Engineering Contradiction:
Improveaccess update speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system achieves universality by implementing a multi-functional automated RBAC mechanism that handles multiple operations through a single integrated framework. The same automated scope change system manages both provisioning and decommissioning events, applies to multiple computing resource types (databases, storage, networking), and serves various role-based access scenarios, thereby improving productivity across the board without proportionally increasing complexity.

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

Solution Approach 2:

The patent introduces an intermediary automated scope change mechanism that acts as a mediator between computing resource provisioning systems and RBAC access control systems. This intermediary layer receives resource change events, translates them into appropriate RBAC scope modifications, and executes the updates, thereby simplifying the overall system architecture by creating a dedicated coordination layer rather than requiring direct complex integration between all components.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If manual processing is used for cloud database access updates, then control over access is maintained, but time consumption increases significantly

Engineering Contradiction:
Improveaccess controlVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary configuration of automated scope change rules and policy definitions before cloud database access updates are needed. When databases are provisioned or decommissioned in the cloud environment, the automated mechanism has pre-established the logic to immediately detect these changes and execute corresponding RBAC scope updates, reducing processing time from days to hours while maintaining reliable access control through pre-defined security policies.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12526280B2Automated role-based access control scope change
Publication Date: 2026.01.13 HARTFORD FIRE INSURANCE CO
  • US12526280B2 patent drawing
  • US12526280B2 patent drawing
  • US12526280B2 patent drawing

AI summary

An enterprise back-end application computer server may implement an access control system for an enterprise. A Role-Based Access Control (“RBAC”) scope data store may contain electronic records associated with a plurality of scopes for the enterprise. For each scope, the RBAC scope data store may include a set of computing resources that are accessible by roles associated with that scope. A computer processor of the back-end application computer server may identify a computing resource landscape change for the enterprise. Responsive to the identified computing resource landscape change, the computer server may automatically determine a modification to a set of computing resource access rules for at least one role. The system may then, responsive to the determination, automatically update the associated electronic record for the appropriate scope in the RBAC data store to reflect the computing resource landscape change.