Bot-chain ledger for secure self-sovereign data access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems fail to securely allow virtual agents or bots to access specific data points within a distributed data repository without exposing sensitive information, leading to potential harmful data exposure.

Innovation Solution

Implementing a bot-chain ledger system that registers bots, generates read approval tokens, and issues single-use access tokens to ensure secure access to self-sovereign data, preventing unauthorized access by allowing only permitted data access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a bot is granted access to a central repository, then the bot can access data, but the bot may access sensitive information beyond its authorization

Engineering Contradiction:
Improvedata access capabilityVSAvoidharmful data exposure
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent segments data access by creating a distributed data repository where data is divided into discrete data points with individual access controls. Instead of granting blanket access to a central repository, each data point can be independently accessed or restricted based on specific authorization rules, preventing bots from accessing unauthorized sensitive information while maintaining access to permitted data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary access control layer between bots and the data repository. This intermediary system processes access requests, validates authorization rules, and mediates data point access. The intermediary prevents direct unauthorized access to sensitive information while enabling legitimate data retrieval through controlled pathways.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a distributed data repository is used, then data access is restricted to specific data points, but bots cannot access permitted data without exposing sensitive information

Engineering Contradiction:
Improvedata access controlVSAvoiddata retrieval capability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements preliminary action by pre-configuring authorization rules for each data point in the distributed repository before access requests occur. Access control policies, data point classifications, and bot permission sets are established in advance, enabling the system to automatically and efficiently grant or deny access based on pre-evaluated authorization criteria rather than requiring complex real-time access control decisions.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If all data in a central repository is accessible, then data availability is high, but security risk increases

Engineering Contradiction:
Improvedata accessibilityVSAvoidsensitive information exposure risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies local quality by assigning different access permissions and security attributes to different data points within the repository based on their sensitivity and authorization requirements. Each data point can have its own access control list, encryption level, and permission structure, allowing highly sensitive data to be tightly restricted while less sensitive data remains broadly accessible, optimizing both security and availability locally at each data point.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11431503B2Self-sovereign data access via bot-chain
Publication Date: 2022.08.30 KYNDRYL INC
  • US11431503B2 patent drawing
  • US11431503B2 patent drawing
  • US11431503B2 patent drawing

AI summary

An approach for securely accessing self-sovereign data via a bot-chain ledger may be provided. A bot may request access to a piece distributed data at a bot-chain client. A bot registry service may validate the requesting bot is registered with the bot-ledgering client. The bot-ledgering client may generate a token for the requesting bot and provide the identity of a data bot with permission to access the piece of distributed data. A data bot may request to read the piece of distributed data at the bot-ledgering client. The bot-ledgering client may verify the data bot is registered with the bot-chain. The bot-ledgering client may generate an access token and send it to the data bot.