Sensitive Data Protection via Code Transformation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for protecting sensitive data in web-based collaborative platforms are inadequate, as they fail to effectively secure sensitive information from unauthorized access by third-party entities integrated within these platforms.

Innovation Solution

A computer-implemented method that parses and transforms computer program code portions into secured data types by casting sensitive data into an intermediary alias data type, ranking based on a predicted sensitivity score, and converting it into a secured data type if the score meets a threshold, thereby making the data inaccessible to unauthorized access by third-party applications and programming libraries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional methods are used to protect sensitive data, then data protection is attempted, but the protection is inadequate and fails to secure sensitive information from unauthorized access

Engineering Contradiction:
Improvedata protection effectivenessVSAvoidunauthorized access by third-party entities
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary alias data type as a mediator between the original sensitive data and third-party applications. This intermediary type acts as a barrier that prevents direct access to sensitive data while still allowing authorized operations to proceed through controlled interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the data type parameter of sensitive information from its original form to a secured data type with modified access parameters. This transformation alters the fundamental characteristics of the data, making it inaccessible to unauthorized entities while preserving functionality for authorized operations.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If dynamic transformation of code portions is implemented to secure sensitive data, then unauthorized access is prevented, but operational complexity increases

Engineering Contradiction:
Improvedata securityVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent performs preliminary analysis and transformation of code portions before execution. By identifying and securing sensitive data portions in advance through parsing and type transformation, the system prevents security issues from arising during operation, thereby managing complexity through upfront actions rather than continuous monitoring.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service through automated parsing and transformation of code portions. The framework automatically identifies sensitive data, determines appropriate secured data types, and applies transformations without requiring manual intervention, thereby reducing operational complexity despite the added security functionality.

Inventive Principle:
Principle #25Self-service

3Reliability

If all computer program code portions are transformed into secured data types, then comprehensive protection is achieved, but processing time and resource allocation increase

Engineering Contradiction:
Improvecomprehensive data protectionVSAvoidprocessing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies local quality by transforming only those specific code portions that contain or handle sensitive data into secured data types, rather than transforming all code uniformly. This selective approach maintains comprehensive protection for sensitive information while avoiding the performance overhead of transforming unrelated code portions.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system implements partial action by applying security transformations only to the extent necessary - specifically to code portions identified as handling sensitive data. This partial transformation approach provides adequate protection without the excessive resource consumption that would result from transforming all code portions regardless of their sensitivity relevance.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20240330502A1Sensitive data protection
Publication Date: 2024.10.03 ATLASSIAN US INC
  • US20240330502A1 patent drawing
  • US20240330502A1 patent drawing
  • US20240330502A1 patent drawing

AI summary

Embodiments provide a sensitive data protection system for protecting sensitive data by augmenting one or more computer program portions to secure sensitive data associated with the one or more computer program portions. Embodiments include parsing one or more computer program code portions to identify one or more sensitive data portions, where the one or more sensitive data portions are associated with one or more respective sensitive data categories. Embodiments also include transforming the one or more computer program code portions into one or more respective secured data types such that the one or more sensitive data portions associated with the one or more respective secured data types are secured against unauthorized access by one or more third-party computer applications, web applications, services, end users, enterprises, and/or other third-party entities.