Behavior-Based Data Access Restriction for Unauthorized Requests

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data security systems fail to track and analyze user-specific data access patterns, leading to unauthorized access to data beyond a user's historical access rights, as they grant access based solely on initial permissions without considering historical access trends.

Innovation Solution

A system that logs and analyzes data access events to generate user profiles with historical access patterns, compares current access events to these profiles, and takes actions such as generating alerts, denying access, or restricting data based on compliance with these patterns.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If conventional data security systems grant access based solely on initial permissions, then ease of operation is improved, but data security deteriorates because users can access data beyond their historical access patterns

Engineering Contradiction:
Improvedata accessVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system continuously monitors and logs data access events, analyzing historical access patterns to dynamically adjust access control decisions. This feedback mechanism compares current access requests against established user profiles, allowing the system to maintain security while permitting legitimate access patterns.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system pre-establishes user profiles by analyzing historical access data before making access control decisions. By proactively creating these behavioral baselines, the system can quickly evaluate new access requests against known patterns, improving both security and operational efficiency.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If data security systems monitor and track all data access events, then data security is improved, but device complexity increases due to logging and analysis requirements

Engineering Contradiction:
Improvedata securityVSAvoidmonitoring system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts only the essential access control functionality from the logging and analysis processes. By separating the core access decision-making from comprehensive monitoring, the system maintains security through pattern comparison while reducing unnecessary complexity in the access control mechanism.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If conventional systems grant access based on permission sets, then productivity is improved, but loss of information occurs because unauthorized access patterns go undetected

Engineering Contradiction:
Improvedata access efficiencyVSAvoidunauthorized access detection
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system introduces user profiles as an intermediary layer between permission sets and actual access decisions. These profiles capture historical access patterns and serve as a mediator that enhances detection of unauthorized access while maintaining efficient access for legitimate users, preventing information loss from undetected breaches.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20260089164A1Data security systems and methods
Publication Date: 2026.03.26 STATE FARM MUTAL AUTOMOBILE INSURANCE COMPANY
  • US20260089164A1 patent drawing
  • US20260089164A1 patent drawing
  • US20260089164A1 patent drawing

AI summary

A system for data security includes a processor and a computer-readable storage medium having instructions stored thereon that cause the processor to perform operations including: (i) logging data access events initiated by a user; (ii) generating a user profile of the user, the user profile including a size and a type of data accessed by each data access event; (iii) receiving a new data access event initiated by the user including a size and a type of data requested by the new data access event; (iv) comparing the size and the type of the requested data of the new data access event to the user profile; (v) determining that the new data access event initiated by the user does not correspond to the data included in the user profile; (vi) restricting the requested data associated with the new data access event; and (vii) transmitting the restricted data to the user.