Trigger Action Platform Security Minimizer for Data Exposure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Trigger action platforms (TAPs) expose large amounts of user data, potentially leading to security vulnerabilities due to attribute level over-privilege, where unnecessary data is transmitted, and token level over-privilege requires frequent user authorization, complicating maintenance and user burden.

Innovation Solution

Implementing a minimizer program at the trigger service to filter out unnecessary attribute data based on auxiliary information generated during rule creation, using cryptographic signatures for security and transparency, without modifying existing TAP operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the TS sends all attribute data to the TAP upon trigger condition satisfaction, then the TAP has complete information to execute any rule, but the amount of user data exposed increases significantly creating security vulnerabilities

Engineering Contradiction:
Improverule execution capabilityVSAvoiddata exposure risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by having the user specify required attributes in advance when creating the rule. The user identifies exactly which attributes are needed for the rule to function, and this information is stored with the rule. When the trigger condition is satisfied, the TS uses this pre-specified attribute list to filter and send only those necessary attributes to the TAP, rather than sending all available attributes. This resolves the contradiction by maintaining complete rule execution capability while minimizing data exposure through pre-planned attribute selection.

Inventive Principle:
Principle #10Preliminary action

2Object-affected harmful factors

If the TS implements user rules without the TAP, then data exposure is reduced, but the independence between TS and AS is broken

Engineering Contradiction:
Improvedata exposureVSAvoidservice independence
Core Design Contradiction:
Object-affected harmful factorsVSAdaptability or versatility

Solution Approach 1:

The patent applies segmentation by dividing the rule execution functionality into two separate components: the TS handles trigger condition monitoring and attribute filtering based on user-specified attributes, while the TAP handles rule evaluation and action execution. This segmentation allows the TS to minimize data exposure by sending only necessary attributes, while the TAP maintains independence to execute rules without requiring the TS to implement the full rule logic. Each service operates independently with clearly defined responsibilities, resolving the contradiction between data exposure reduction and service independence.

Inventive Principle:
Principle #1Segmentation

3Object-affected harmful factors

If fine grain APIs are used to provide limited information for particular rules, then attribute level over-privilege is reduced, but API maintenance becomes more complex as services evolve

Engineering Contradiction:
Improveattribute over-privilegeVSAvoidAPI maintenance burden
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent applies universality by using a single, general-purpose attribute specification mechanism that works for all rules. Instead of creating specialized fine-grain APIs for different rule types, the system uses a universal approach where users specify required attributes using standard attribute paths (e.g., email.sender, email.subject) that work across all trigger conditions and rule types. This universal attribute specification mechanism reduces attribute over-privilege while avoiding the maintenance burden of multiple specialized APIs, as the same mechanism handles all attribute access needs.

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

4Object-affected harmful factors

If the user authorizes only specific APIs, then token level over-privilege is reduced, but the user burden increases significantly requiring re-authorization on every rule change

Engineering Contradiction:
Improvetoken over-privilegeVSAvoiduser authorization burden
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The patent applies preliminary action by having the user specify required attributes once when creating the rule, rather than requiring repeated authorization decisions. The user's attribute selection is stored with the rule and automatically applied whenever the rule is executed. This eliminates the need for the user to re-authorize or re-specify attributes on every rule change or execution, significantly reducing the authorization burden while maintaining precise control over data access. The preliminary attribute specification resolves the contradiction between preventing token over-privilege and ease of operation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11856000B2Method and apparatus for improved security in trigger action platforms
Publication Date: 2023.12.26 WISCONSIN ALUMNI RES FOUND
  • US11856000B2 patent drawing
  • US11856000B2 patent drawing
  • US11856000B2 patent drawing

AI summary

An apparatus and method for improving the security of trigger action platforms of a type providing interoperability between computer services send the trigger service additional information about an interoperability rule for the computer services so that the trigger service may implement a minimizer reducing the data communicated when the interoperability is implemented. Implementation of the minimizer may be done in a way that is transparent to the trigger action platform eliminating the need for disruption of existing interoperability services.