Dynamic Sensitive Information Masking for UI Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for protecting sensitive information in user interfaces, such as obscuring characters, are often inconvenient and ineffective in preventing over-the-shoulder attacks, particularly in public settings where vulnerabilities persist due to temporary exposure of plain text.

Innovation Solution

A system and method for controlling the presentation of sensitive information in a user interface, where fields are identified as sensitive, users are registered, and access is granted based on authentication levels, allowing users to request unmasking and re-masking of this information dynamically, enhancing security and convenience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Object-affected harmful factors

If sensitive information is obscured or masked using replacement characters, then security against over-the-shoulder attacks is improved, but user convenience deteriorates due to inability to verify entered information

Engineering Contradiction:
Improvesecurity against over-the-shoulder attacksVSAvoiduser convenience
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The patent implements dynamic masking where the sensitivity of information fields can change based on user authentication level. Initially masked fields become unmasked after successful authentication, allowing the system to adapt its security behavior based on the user's verified identity, thus resolving the contradiction between security and usability

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the display parameter of sensitive information based on authentication status. The same field transitions from a masked state (displaying replacement characters) to an unmasked state (displaying actual values) after authentication, allowing users to verify their input while maintaining security for unauthenticated users

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If sensitive information is displayed in plain text for user input, then user convenience is improved, but security against over-the-shoulder attacks deteriorates due to temporary exposure

Engineering Contradiction:
Improveuser convenienceVSAvoidvulnerability to over-the-shoulder attacks
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent applies different display qualities to different parts of the interface based on authentication status. Authenticated users see unmasked sensitive information while unauthenticated users see masked information, allowing local customization of information visibility based on user credentials

Inventive Principle:
Principle #3Local quality

3Object-affected harmful factors

If authentication levels are implemented to control access to sensitive information, then security is improved, but device complexity increases

Engineering Contradiction:
Improvesecurity controlVSAvoidsystem complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent segments information fields by sensitivity level and controls their visibility based on user authentication level. The system divides fields into those that remain masked and those that can be unmasked after authentication, creating a structured approach to security that manages complexity through organization

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10121023B2Unveil information on prompt
Publication Date: 2018.11.06 ORACLE INT CORP
  • US10121023B2 patent drawing
  • US10121023B2 patent drawing
  • US10121023B2 patent drawing

AI summary

Embodiments of the invention provide systems and methods for controlling presentation of sensitive information in a user interface of an application. More specifically, embodiments of the present invention provide for masking the sensitive information when being entered by the user. However, if the user wants to verify the entry or display the sensitive information in readable text, the information can be displayed or unmasked upon request. For example, in response to the user clicking a button or other control of the user interface associated with the sensitive information or by another mouse or keyboard event, the requested sensitive information can be unmasked and displayed in the clear, for example as a tool tip or in the originally presented element of the user interface. The user can then close the tooltip or mask the information, e.g., after verification of what he/she typed.