Operating System Data Scrubbing for Unauthorized Access Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Operating systems fail to effectively prevent unauthorized access to data when permissions are not explicitly granted, as data can be embedded within types of information that applications are authorized to access, leading to potential security breaches.

Innovation Solution

A computing system identifies and prevents unauthorized data access by scrubbing, blocking, or prompting users to manage data access, using mechanisms such as stripping metadata, blocking data transfer, or replacing sensitive information with identifiers, ensuring that applications only receive authorized data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If an application program is granted permission to access a type of data (e.g., audio data from microphone), then the application can receive and process that data, but the application may also inadvertently receive embedded sensitive data (e.g., location data, contact information) that it does not have permission to access

Engineering Contradiction:
Improvedata access capabilityVSAvoidunauthorized data access
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system extracts and removes embedded sensitive data (such as location information, contact data, or other protected information) from data structures before providing them to application programs. This extraction process separates authorized data from unauthorized embedded data, allowing applications to access only the data they have permission to use while preventing inadvertent access to sensitive embedded information

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The operating system acts as an intermediary between data source applications and requesting applications. It mediates data access by intercepting data flows, analyzing embedded content, and selectively blocking or removing sensitive data portions. This intermediary role enables the system to enforce permission boundaries even when data is embedded within authorized data structures

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If the operating system blocks all data transfer to prevent unauthorized access, then data security is improved, but legitimate data access and application functionality are hindered

Engineering Contradiction:
Improveunauthorized data accessVSAvoiddata access efficiency
Core Design Contradiction:
Object-affected harmful factorsVSProductivity

Solution Approach 1:

Instead of blocking entire data transfers, the system extracts only the specific embedded sensitive data portions that violate permission rules. This selective extraction preserves the legitimate authorized data for application access while removing only the unauthorized embedded portions, maintaining both security and productivity

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies different access controls to different portions of the same data structure. Authorized data portions are made accessible to applications with appropriate permissions, while embedded sensitive data portions are restricted or removed. This local differentiation allows simultaneous data access efficiency and security

Inventive Principle:
Principle #3Local quality

3Object-affected harmful factors

If the operating system monitors and checks all data transfers for embedded sensitive information, then data security is enhanced, but system complexity and processing overhead increase

Engineering Contradiction:
Improveunauthorized data accessVSAvoidpermission management system
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The system performs preliminary analysis and classification of data structures before they are transferred to applications. By pre-identifying and flagging embedded sensitive data portions, the system avoids the need for complex real-time analysis during data transfer, reducing processing overhead while maintaining security

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3320477B1Protecting data from unauthorized access
Publication Date: 2021.02.17 GOOGLE LLC
  • EP3320477B1 patent drawingFigure 1
  • EP3320477B1 patent drawingFigure 2A~2B
  • EP3320477B1 patent drawingFigure 3

AI summary

In general, the subject matter described in this disclosure can be embodied in methods, systems, and program products for identifying that an application program does not have permission to access a first type of data that is provided by a first application program. A computing system identifies that a second application program has permission to access the first type of data. The second application program provides a second type of data and is able to modify the second type of data to include the first type of data. The computing system identifies that the application program has permission to access the second type of data. The computing system determines that the second type of data includes the first type of data. The computing system performs an action to prevent the first type of data from being provided from the second application program to the application program without user authorization.