Hybrid Honeypot System for Cloud Network Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional automated honeypot generation in cloud environments often affects legitimate users and allows sophisticated attackers to easily identify valid environments, limiting the effectiveness of decoy environments to non-targeted attackers.

Innovation Solution

A hybrid-honeypot system is deployed, interweaving a honeypot system with the production system, allowing detected attackers to continue using the production system up to their point of entry while routing them to the honeypot system, maintaining the production system intact and minimizing impact on valid users.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional automated honeypot generation is deployed in cloud environments, then decoy environments are created to lure attackers, but legitimate users are affected and sophisticated attackers can easily identify valid environments

Engineering Contradiction:
Improvehoneypot effectivenessVSAvoidimpact on valid users
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system segments the cloud environment by creating multiple isolated container instances, where some containers are designated as honeypots and others as valid production environments. This segmentation allows the system to distribute traffic across multiple segments and selectively route malicious traffic to honeypot segments while directing legitimate traffic to valid environments.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary component that monitors container behavior and determines whether incoming traffic is legitimate or malicious. This intermediary layer sits between the external network and the container instances, dynamically routing traffic based on real-time analysis of user behavior patterns without requiring users to know which environment they are accessing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If honeypots are deployed to detect and analyze attacker activity, then security monitoring is improved, but the production system integrity may be compromised

Engineering Contradiction:
Improvesecurity monitoring capabilityVSAvoidproduction system integrity
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The system creates copies of the production environment in the form of honeypot containers that replicate the appearance and structure of valid systems. These copied environments are designed to be indistinguishable from the real production system to attackers, allowing security monitoring without exposing the actual production data or systems to potential compromise.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system extracts the honeypot functionality from the production environment by running it in separate, isolated container instances. This extraction ensures that the production system remains intact and unaffected by honeypot operations, while still enabling comprehensive security monitoring through the isolated decoy environments.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If multiple container instances are created for honeypot deployment, then attacker detection capability is enhanced, but system complexity increases

Engineering Contradiction:
Improveattacker detection capabilityVSAvoidcontainer management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements a universal container management approach where a single orchestration mechanism handles multiple container instances serving different functions (honeypots, valid environments, monitoring). This multi-functional system manages diverse container types through a unified interface, reducing the operational complexity that would otherwise arise from managing separate systems for each function.

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

Solution Approach 2:

The system dynamically changes parameters such as container routing decisions, traffic distribution ratios, and monitoring intensity levels based on detected attacker behavior. By adjusting these parameters in real-time, the system can enhance detection capability when threats are present while maintaining simpler operations during normal conditions, effectively managing complexity through adaptive parameter changes.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10666670B2Managing security breaches in a networked computing environment
Publication Date: 2020.05.26 KYNDRYL INC
  • US10666670B2 patent drawing
  • US10666670B2 patent drawing
  • US10666670B2 patent drawing

AI summary

Approaches for managing security breaches in a networked computing environment are provided. A method includes detecting, by at least one computer device, a breach of a production system in the networked computing environment, wherein the networked computing environment includes a decoy system interweaved with the production system. The method also includes receiving, by the at least one computer device, a communication after the detecting the breach. The method further includes determining, by the at least one computer device, the communication is associated with one of a valid user and a malicious user. The method additionally includes, based on the determining, routing the valid user to an element of the production system when the communication is associated with the valid user and routing the malicious user to a corresponding element of the decoy system when the communication is associated with the malicious user.