Cloud File Vault Access Using Client Indication and Hidden Secure Areas

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud storage systems lack efficient mechanisms to securely manage sensitive data, requiring users to apply security measures individually to each file or folder, leading to inefficiencies and inconsistent security implementations across different applications.

Innovation Solution

A secure area, referred to as a 'vault', within the cloud storage system that requires additional authentication measures like two-factor authentication to access, with applications needing to provide a special header and token for access, ensuring only authorized applications can access vault contents, and maintaining a consistent security layer without affecting non-vaulted files.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the secure area size is fixed and allocated in advance, then the file storage system can efficiently manage storage space, but it cannot adapt to dynamic client needs for varying secure storage requirements

Engineering Contradiction:
Improveadaptability to dynamic secure storage needsVSAvoidcomplexity of secure area management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic secure areas that can be created, resized, and deleted based on client needs. The secure area size is no longer fixed but can be dynamically adjusted through client requests, allowing the system to adapt to varying storage requirements while maintaining efficient management through automated allocation and deallocation processes

Inventive Principle:
Principle #15Dynamics

2Reliability

If all file storage space is made accessible and searchable, then the system provides maximum utility and ease of access, but it compromises security by exposing sensitive files to unauthorized viewing or copying

Engineering Contradiction:
Improvesecurity of sensitive filesVSAvoidease of file access and search
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent divides the file storage system into distinct secure areas and non-secure areas. Files are segmented into those requiring security (stored in secure areas with access controls) and those that don't (stored in non-secure areas with full accessibility). This segmentation allows the system to maintain high security for sensitive files while preserving ease of access for other files, eliminating the need to compromise either security or accessibility across the entire storage system

Inventive Principle:
Principle #1Segmentation

3Productivity

If secure areas are permanently allocated to clients, then clients have guaranteed storage capacity, but the system cannot efficiently reallocate space when clients' needs change or when secure areas are no longer needed

Engineering Contradiction:
Improvestorage space utilization efficiencyVSAvoidtime for secure area creation and activation
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements preliminary allocation of secure area definitions and templates that can be quickly instantiated when needed. Rather than requiring time-consuming creation processes, the system pre-configures secure area structures that can be rapidly deployed and activated upon client request, significantly reducing the time required to provide secure storage capacity while maintaining the ability to reallocate space efficiently when needs change

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3942767B1Hiding secure area of a file storage system based on client indication
Publication Date: 2026.04.29 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3942767B1 patent drawingFigure 1
  • EP3942767B1 patent drawingFigure 2
  • EP3942767B1 patent drawingFigure 3

AI summary

Data associated with a user account is stored at the cloud-based storage service. A portion of the data is associated with a heightened authentication protocol. A request for an application to access data that is associated with the heightened authentication protocol is received at the cloud-based storage service. The request may include an indication that the application is configured to interact with data with the heightened authentication protocol. The request is authenticated based on the heightened authentication protocol. In response to authenticating the first request, permission is granted to the application to access the data that is associated with the heightened authentication protocol. In response receiving requests that do not include the indication that the application is configured to interact with data with the heightened authentication protocol, data pertaining to the portion of the data with the heightened authentication protocol is hidden.