Web Application Security Module for Risk-Aware Threat Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Emerging markup languages like HTML5 expose end-user platform components to web applications, leading to security concerns due to potential malware and unauthorized access, which existing security management systems inadequately address.

Innovation Solution

A security module that monitors web application API calls and aggregates interaction information from platform and remote data sources to generate a risk profile, detecting potential security threats and providing users with recommended actions to mitigate risks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If web applications use emerging markup languages like HTML5 to access platform components, then functionality and user experience are improved, but security risks increase due to potential malware and unauthorized access

Engineering Contradiction:
Improveweb application functionalityVSAvoidsecurity risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The security module performs preliminary risk assessment by monitoring API calls and aggregating interaction information before web applications execute potentially harmful operations. This allows the system to establish a baseline of normal behavior and detect deviations that indicate security threats, preventing malware from causing damage while allowing legitimate applications to function.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The security module acts as an intermediary between web applications and platform components. It intercepts and monitors API calls, aggregates interaction information from multiple sources, and provides risk profiles that mediate between application functionality and security protection, allowing safe access to platform components while blocking malicious operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If a security module monitors and aggregates data from multiple sources to generate comprehensive risk profiles, then threat detection accuracy is improved, but system complexity increases

Engineering Contradiction:
Improvethreat detection accuracyVSAvoidsecurity system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The security system is segmented into distinct functional modules: API call monitoring, interaction information aggregation from multiple data sources, risk profile generation, and threat detection. Each module handles a specific aspect of security analysis, allowing the complex task of comprehensive threat detection to be divided into manageable components that can be developed and maintained independently.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The security module is designed as a multi-functional system that performs multiple security tasks: monitoring API calls, aggregating interaction information from various sources, generating risk profiles, and detecting threats. This universal approach consolidates multiple security functions into a single integrated module, reducing overall system complexity while maintaining comprehensive threat detection capabilities.

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

Data Source

PatentEP2901354B1Security data aggregation for web applications
Publication Date: 2020.10.21 INTEL CORP
  • EP2901354B1 patent drawingFigure 1~3
  • EP2901354B1 patent drawingFigure 4
  • EP2901354B1 patent drawingFigure 5

AI summary

Systems and methods may provide for detecting a browser request for web content. Additionally, interaction information associated with a plurality of sources may be determined in response to the browser request, and a risk profile may be generated based on the interaction. The risk profile may include at least a portion of the interaction information as well as recommended control actions to mitigate the identified risk. In one example, the risk profile is presented to a user associated with the browser request as well as to a security control module associated with the platform.