Cloud Account Correlation for Credential Reuse Risk Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud computing environments face significant cybersecurity risks due to the use of multiple user accounts by a single user across different environments, leading to credential reuse and privilege escalation, which complicates security monitoring and increases the attack surface.

Innovation Solution

A system is configured to detect and correlate events across software containers in a cloud environment, using unique identifiers to apply controls and detect cybersecurity risks, and initiate remediation actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple user accounts are used across different cloud environments, then operational boundaries and least privilege principle are maintained, but credential reuse and privilege escalation risks increase

Engineering Contradiction:
Improvesecurity controlVSAvoidcredential reuse risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent merges multiple user accounts across different cloud environments (development, staging, production) by detecting common identifying information such as email addresses, phone numbers, or physical addresses. This creates a unified view of a single user's accounts, enabling the system to identify credential reuse patterns and apply coordinated security controls across all associated accounts, thereby maintaining operational boundaries while mitigating credential reuse risks.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If separate IAM configurations and virtual networks are used, then environment isolation is achieved, but security monitoring complexity increases

Engineering Contradiction:
Improveenvironment isolationVSAvoidsecurity monitoring complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal security monitoring system that operates across multiple isolated cloud environments (development, staging, production) by detecting and correlating user accounts through common identifying information. This multi-functional approach enables the system to maintain environment isolation through separate IAM configurations while simultaneously providing unified security monitoring, threat detection, and coordinated response capabilities across all environments, thereby reducing monitoring complexity without compromising isolation.

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

3Ease of operation

If relaxed authentication mechanisms are used in development environments, then operational flexibility is improved, but attack surface increases

Engineering Contradiction:
Improveoperational flexibilityVSAvoidattack surface
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary anti-action by proactively identifying user accounts with relaxed authentication mechanisms in development environments and detecting their association with accounts in more secure environments (staging, production). The system preemptively flags these connections and applies coordinated security controls, such as alerting security personnel or automatically enforcing stricter policies, to prevent attackers from using the relaxed development account as an entry point to compromise higher-value targets in secured environments.

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS12563058B1Techniques for cross entity correlation of user accounts in cloud computing environments
Publication Date: 2026.02.24 WIZ INC
  • US12563058B1 patent drawing
  • US12563058B1 patent drawing
  • US12563058B1 patent drawing

AI summary

A system and method for cross-entity correlation of software containers in a cloud computing environment is presented. The method includes detecting in a log an event record related to a software container platform utilized in a cloud computing environment; extracting from the event record a software container identifier and a principal identifier; cross-referencing the software container identifier with a unique software container identifier list based at least on the principal identifier; associating in a security database the event record and the unique software container identifier; and applying a control based on the event record and the unique software container identifier.