Application-Level Sandboxing for Cyber Deception

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cyber security measures, such as perimeter-based defenses and traditional network traffic monitoring, are inadequate in detecting and preventing sophisticated cyber attacks, as they fail to provide adequate visibility into the cyberattack lifecycle and are easily detectable by advanced adversaries, while attackers exploit information asymmetry to find vulnerabilities.

Innovation Solution

The implementation of unprivileged, lightweight application sandboxing that transparently moves suspicious processes into a decoy sandbox for monitoring and analysis, using namespace facilities to create and manage isolated environments, allowing for on-demand deployment of booby traps and deception techniques without disrupting application workflows.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional network traffic monitoring and perimeter-based defenses are used, then network security can be maintained with simple deployment, but they cannot detect sophisticated cyber attacks and provide adequate visibility into the cyberattack lifecycle

Engineering Contradiction:
Improvedetection capabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the monitoring system into multiple specialized components: honeypots for attracting attackers, decoy services for interaction, sensors for detecting attack patterns, and analysis systems for processing attack data. This segmentation allows each component to specialize in specific detection tasks, improving overall reliability while maintaining manageable complexity through modular architecture

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediary elements such as honeypots and decoy services that act as mediators between attackers and the real system. These intermediaries attract and engage attackers, providing visibility into attack techniques without exposing the actual critical systems, thereby improving detection capability without requiring complex monitoring of all network traffic

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If honeypots are deployed to detect attacks, then attack visibility is improved, but they are easily detectable by advanced adversaries due to limited services and different traffic patterns

Engineering Contradiction:
Improveattack detectionVSAvoidhoneypot detectability
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent applies local quality by making different parts of the honeypot system have different characteristics. Decoy services present realistic local qualities (traffic patterns, service responses, system behaviors) that match genuine services, while the overall honeypot infrastructure maintains detection capabilities. This allows honeypots to blend in locally with real services while serving their detection function

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent employs parameter changes by dynamically adjusting honeypot characteristics such as service availability, response patterns, and system state transitions. Honeypots can change their operational parameters to match different attack scenarios and maintain realism, making them harder for adversaries to detect while preserving their detection effectiveness

Inventive Principle:
Principle #35Parameter changes

3Loss of information

If application-level deception with sandboxing is implemented, then attacker monitoring and analysis capability are improved, but system complexity increases due to namespace management and process isolation mechanisms

Engineering Contradiction:
Improvethreat intelligenceVSAvoidsandboxing infrastructure
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent makes the sandboxing infrastructure universal by designing namespace facilities and isolation mechanisms that can serve multiple functions: process isolation, attack containment, forensic analysis, and threat intelligence gathering. This multi-functionality reduces the need for separate specialized systems, thereby reducing overall system complexity while maintaining comprehensive threat intelligence capabilities

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

Solution Approach 2:

The sandboxing system implements self-service through automated namespace management, dynamic process isolation, and automatic forensic data collection. The system automatically handles the complexity of creating and managing isolated environments without requiring manual intervention, reducing the operational burden despite the underlying infrastructure complexity

Inventive Principle:
Principle #25Self-service

4Productivity

If lightweight unprivileged sandboxing is used, then performance overhead is reduced, but the ability to constrain attacker capabilities may be limited compared to privileged sandboxing

Engineering Contradiction:
Improvesystem performanceVSAvoidattacker constraint
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent extracts the essential constraint functions from privileged sandboxing and implements them through unprivileged mechanisms. By taking out only the necessary capability constraints and implementing them through namespace facilities and capability restrictions, the system achieves adequate attacker constraint without the performance overhead of full privileged sandboxing, maintaining both productivity and reliability

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10887346B2Application-level sandboxing
Publication Date: 2021.01.05 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10887346B2 patent drawing
  • US10887346B2 patent drawing
  • US10887346B2 patent drawing

AI summary

Rapid deployments of application-level deceptions (i.e., booby traps) implant cyber deceptions into running legacy applications both on production and decoy systems. Once a booby trap is tripped, the affected code is moved into a decoy sandbox for further monitoring and forensics. To this end, this disclosure provides for unprivileged, lightweight application sandboxing to facilitate monitoring and analysis of attacks as they occur, all without the overhead of current state-of-the-art approaches. Preferably, the approach transparently moves the suspicious process to an embedded decoy sandbox, with no disruption of the application workflow (i.e., no process restart or reload). Further, the action of switching execution from the original operating environment to the sandbox preferably is triggered from within the running process.