Managed Honeypot Intrusion Detection via User Trust Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Service providers face challenges in managing honeypot resources to differentiate between malicious and non-malicious users, potentially impacting legitimate customers and requiring sophisticated configuration and monitoring to prevent unauthorized access.

Innovation Solution

A system that allows customers to provision and configure honeypot resources within computing resource services, where policies determine user access and interactions, enabling the presentation of honeypot resources only to untrusted users and monitoring their interactions to generate notifications for remedial actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If honeypot resources are presented to all users, then malicious users can be detected and neutralized, but trusted users may be negatively impacted

Engineering Contradiction:
Improvedetection of malicious usersVSAvoidimpact on trusted users
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system applies different presentation qualities of honeypot resources to different user groups. Trusted users receive a filtered view where honeypot resources are hidden or presented differently, while untrusted users receive the full presentation including honeypot resources. This local differentiation resolves the contradiction by protecting trusted users while maintaining detection capabilities against malicious users.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system introduces an intermediary component that mediates between honeypot resources and users, controlling which users can access or interact with honeypot resources. This intermediary evaluates user trust levels and selectively presents honeypot resources, thereby preventing harmful impacts on trusted users while maintaining the ability to detect malicious users.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If honeypot resources are configured to detect malicious users, then security monitoring capability is improved, but system complexity increases

Engineering Contradiction:
Improvesecurity monitoring capabilityVSAvoidhoneypot configuration and management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system uses virtual or simulated copies of honeypot resources rather than requiring multiple physical instances. These virtual honeypot resources can be replicated and distributed across the network with minimal overhead, reducing the complexity of configuration and management while maintaining effective security monitoring capability.

Inventive Principle:
Principle #26Copying

3Reliability

If honeypot resources are made accessible to untrusted users, then malicious user detection is enhanced, but customer control over resource presentation is reduced

Engineering Contradiction:
Improvemalicious user detectionVSAvoidcustomer control over resource presentation
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system implements dynamic control mechanisms that allow customers to adjust honeypot resource presentation based on changing requirements. Customers can modify which users are considered trusted, adjust honeypot visibility settings, and adapt the system to different security scenarios, thereby maintaining both malicious user detection capability and customer control.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10110629B1Managed honeypot intrusion detection system
Publication Date: 2018.10.23 AMAZON TECH INC
  • US10110629B1 patent drawing
  • US10110629B1 patent drawing
  • US10110629B1 patent drawing

AI summary

A honeypot resource management service receives a request to provision one or more honeypot resources. In response to the request, the service identifies at least one computing resource service that is to be used to present the one or more honeypot resources. The service generates configuration information that is transmitted to the at least one computing resource service to cause the computing resource service to present the one or more honeypot resources to users in accordance with a set of parameters specified in the configuration information.