Downgrader Code Analysis for Information-Flow Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies lack an automated mechanism to check if Web applications adhere to security guidelines for information-flow security, particularly in enforcing downgraders, making it difficult to detect and categorize them, which is crucial for preventing security attacks.

Innovation Solution

A method and system for evaluating downgrader code in Web applications using string analysis mechanisms to identify and assess compliance with security guidelines, generating notifications for violations and providing recommendations for improvement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If information-flow security is strictly enforced with partitioning, then security is improved, but program functionality deteriorates

Engineering Contradiction:
Improveinformation-flow securityVSAvoidprogram functionality
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies preliminary action by performing downgrading operations before information flows to low-security contexts. The system identifies potential illicit flows in advance and applies appropriate downgraders (sanitization, validation, declassification) beforehand, allowing the program to maintain functionality while ensuring security compliance at critical points.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces downgraders as intermediary components between high-security and low-security contexts. These intermediaries (sanitizers, validators, declassifiers) transform information to make it safe for low-security usage, enabling functional flexibility while maintaining security boundaries through controlled transformation rather than rigid partitioning.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple specific downgraders are implemented for different functions, then security compliance is improved, but device complexity increases

Engineering Contradiction:
Improvesecurity complianceVSAvoiddowngrader implementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies universality by creating a unified downgrader management system that handles multiple types of downgraders (sanitization, validation, declassification) through a common framework. The system can identify and apply appropriate downgraders based on context, reducing the need for separate complex implementation mechanisms for each downgrader type while maintaining security compliance.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent segments the downgrader implementation into distinct categories (sanitization downgraders, validation downgraders, declassification downgraders) with specific identification rules for each. This segmentation allows the system to manage complexity by treating each downgrader type independently with its own identification and application logic, rather than handling all downgraders as a monolithic complex system.

Inventive Principle:
Principle #1Segmentation

3Extent of automation

If automated downgrader detection and evaluation is implemented, then security guideline enforcement is improved, but difficulty of detecting and measuring increases

Engineering Contradiction:
Improveautomated security enforcementVSAvoiddowngrader detection complexity
Core Design Contradiction:
Extent of automationVSDifficulty of detecting and measuring

Solution Approach 1:

The patent applies feedback by implementing an automated evaluation mechanism that analyzes downgrader code, determines compliance with security guidelines, and provides actionable feedback. The system evaluates downgrader processes, identifies violations, and generates recommendations, creating a closed-loop system that automatically enforces security guidelines while managing detection complexity through structured analysis and feedback mechanisms.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8667584B2Formal analysis of the quality and conformance of information flow downgraders
Publication Date: 2014.03.04 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8667584B2 patent drawing
  • US8667584B2 patent drawing
  • US8667584B2 patent drawing

AI summary

Mechanisms for evaluating downgrader code in application code with regard to one or more security guidelines are provided. Downgrader code in application code is identified, where the downgrader code is a portion of code in the application code that operates on an information flow of the application code to ensure confidentiality of information input to the downgrader code, in the output of the downgrader code. Processes of the downgrader code are evaluated against security guidelines to determine if the processes violate the security guidelines. A notification is generated in response to the evaluation indicating that the processes of the downgrader code violate the security guidelines. The notification is output to a computing device for consideration.