File Whitelist Analysis for Application Store Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for managing application releases in electronic devices lack effective mechanisms to ensure secure and controlled access to device resources, particularly through file whitelists, which are crucial for preventing malicious applications from accessing sensitive files and resources.

Innovation Solution

A system and method for using a file whitelist that involves analyzing application data, including a resource manifest and file whitelist, to determine approved access to device resources, ensuring that only authorized files and operations are accessible, and denying access to unauthorized requests, thereby enhancing security and control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional methods for managing application releases are used, then application deployment is simple and fast, but security control over device resources is insufficient

Engineering Contradiction:
Improvesecurity controlVSAvoidresource management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by requiring application developers to submit a file whitelist during the application submission phase, before the application is installed on the device. The system pre-analyzes and approves the whitelist, storing it in the application package. This ensures that security controls are established in advance, preventing unauthorized file access while maintaining a relatively simple runtime enforcement mechanism.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If file whitelist analysis is implemented for all applications, then security against malicious applications is improved, but the application approval process becomes more time-consuming

Engineering Contradiction:
Improveapplication securityVSAvoidapproval time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies partial action by implementing file whitelist analysis selectively rather than uniformly for all applications. The system can perform basic whitelist validation for all applications while reserving more intensive analysis for applications requesting sensitive resource access or showing suspicious patterns. This approach ensures security for critical cases while maintaining faster processing for routine applications.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If strict file access control is enforced, then protection against unauthorized access is improved, but application functionality may be restricted

Engineering Contradiction:
Improveaccess controlVSAvoidapplication functionality
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements local quality by granting file access permissions on a per-file or per-directory basis rather than applying uniform restrictions. The approved file whitelist specifies exact paths and resource types that applications can access, allowing legitimate functionality to proceed while blocking only unauthorized access attempts. This granular approach ensures that applications retain necessary functionality while maintaining strict security controls where needed.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10298586B2Using a file whitelist
Publication Date: 2019.05.21 GOOGLE LLC
  • US10298586B2 patent drawing
  • US10298586B2 patent drawing
  • US10298586B2 patent drawing

AI summary

A method and/or system for using a file whitelist may include receiving a request to approve an application for release in an application store. The request may comprise application data. The application data may comprise a resource manifest and/or a file whitelist. The resource manifest may comprise, for example, one or more resource items. The file whitelist may comprise, for example, one or more file items. The request may be analyzed based on application data. A determination may be made whether the applications may be released in the application store based on the analyzing of the applications data. A request to access a particular file may be received. A determination of whether to grant the request may be based on a resource manifest and/or a file whitelist associated with the application.