File Vault System for Secured Application Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern computing devices face challenges in securely managing access to sensitive data due to divergent policies of third-party applications, which can lead to unauthorized access and exposure of protected files when using unsecured applications.

Innovation Solution

A file vault system is implemented to regulate access to protected files by locking unsecured applications and restricting access to application data, ensuring only authorized users can access protected content through secure applications listed in a secured applications database.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If third-party applications are allowed to access application data, then application functionality and ease of operation are improved, but data security and access control are worsened

Engineering Contradiction:
Improveapplication functionalityVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces a file vault as an intermediary layer between applications and user data. The file vault manages access control by maintaining a secured applications database that tracks which applications are authorized to access protected files. When an application requests access to protected data, the file vault intercepts the request, verifies the application's security status, and either grants or denies access accordingly. This mediator approach allows legitimate application functionality while preventing unauthorized access to sensitive data.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If unsecured applications are permitted to run, then application versatility is improved, but unauthorized access to protected files is worsened

Engineering Contradiction:
Improveapplication versatilityVSAvoidunauthorized access
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements local quality by differentiating between secured and unsecured applications through a secured applications database. Each application is individually evaluated and assigned a security status. The file vault applies different access policies to different applications based on their security classification. Secured applications in the database are granted access to protected files, while unsecured applications are blocked. This allows the system to maintain versatility by permitting multiple applications to run while applying localized security controls to each application based on its trust level.

Inventive Principle:
Principle #3Local quality

3Reliability

If access control restrictions are implemented, then data security is improved, but ease of operation is worsened

Engineering Contradiction:
Improvedata securityVSAvoiduser control
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements self-service by enabling users to manually manage the secured applications database through the file vault interface. Users can add applications to the secured database, remove applications, or modify access permissions without requiring technical expertise or external assistance. The system provides a user-friendly interface that allows individuals to control which applications have access to their protected files, making security management intuitive and empowering users to maintain both security and operational ease according to their specific needs.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11204984B2Systems and methods for managing access to application data on computing devices
Publication Date: 2021.12.21 MALIKIE INNOVATIONS LTD
  • US11204984B2 patent drawing
  • US11204984B2 patent drawing
  • US11204984B2 patent drawing

AI summary

A method implemented by a computing device is disclosed. The method includes: detecting a change in state of an application that is managed using an applications manager, the change in state being based on a first action within the applications manager; in response to detecting the change in state of the application: identifying at least one list of a plurality of application event listings stored on the computing device independently of the applications manager; determining that the at least one list includes one or more first application event listings associated with the application; and in response to determining that the at least one list includes the one or more first application event listings: determining a second action to apply to only the one or more first application event listings; and applying the second action to the one or more first application event listings.