Integrity-Based Access Control for Data Objects

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional Mandatory Access Control (MAC) systems fail to distinguish between files labeled 'example' on integrity protected and unprotected file systems, allowing attackers to modify file contents during offline attacks, thereby compromising system integrity.

Innovation Solution

Expanding object class type permissions to include integrity-based permissions, such as 'read_signed' and 'read_unsigned', and creating distinct object classes for trusted and untrusted files, allowing policies to specify actions based on the integrity of file labels and contents, and using integrity verification techniques like cryptographic signatures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional MAC systems are used to restrict access to stored data, then access control is provided, but the system cannot distinguish between integrity-protected and unprotected files, allowing offline attacks to compromise system integrity

Engineering Contradiction:
Improvesystem integrityVSAvoidaccess control mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the object class permissions by creating distinct permission types for different integrity levels. It introduces separate permissions such as read_signed, read_unsigned, write_signed, and write_unsigned, allowing the system to differentiate between integrity-protected and unprotected files within the MAC framework. This segmentation enables fine-grained access control based on file integrity status.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by associating integrity properties with specific file objects rather than applying a uniform access control policy to all files. Each file can have its own integrity status (signed or unsigned) that determines the applicable permissions. This allows the access control mechanism to adapt locally to the integrity characteristics of individual files.

Inventive Principle:
Principle #3Local quality

2Reliability

If integrity verification is implemented to prevent unauthorized modifications, then data integrity is ensured, but the access control policy complexity increases

Engineering Contradiction:
Improvedata integrityVSAvoidpolicy definition
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces dynamic permission checking where the applicable permissions are determined at access time based on the file's integrity status. The system dynamically selects between signed and unsigned permission sets depending on whether the file is integrity-protected. This dynamic approach allows the policy to adapt to the specific integrity requirements of each file without requiring separate static policy definitions for every scenario.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10650152B2Data access control based on storage validation
Publication Date: 2020.05.12 MALIKIE INNOVATIONS LTD
  • US10650152B2 patent drawing
  • US10650152B2 patent drawing
  • US10650152B2 patent drawing

AI summary

A system and method to control access to data are disclosed. A request for a subject to perform an action on an object is received. A determination is made whether a policy for the subject limits the action to an object with integrity protection. The action is performed based on determining the object has integrity protection. The request is rejected based on determining the object does not have integrity protection.