Kernel Mode Security Notification via User Mode Mediator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Operating systems face challenges in securing applications and hardware resources, particularly since kernel mode components cannot directly communicate with users, making it difficult to notify or solicit input for security enforcement actions.

Innovation Solution

A security system that uses a user mode host services component to notify or solicit user input on behalf of kernel mode security engines, enabling security policies to be enforced and user interaction even when the security engine executes in kernel mode.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a security engine executes in kernel mode to enforce security policies, then security enforcement capability is improved, but the ability to notify users or solicit user input deteriorates

Engineering Contradiction:
Improvesecurity enforcement capabilityVSAvoiduser notification capability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces a user mode host services component as an intermediary between the kernel mode security engine and the user interface. The security engine detects conditions and requests user interaction through this intermediary, which then presents notifications or solicits input from users in user mode. This resolves the contradiction by allowing the security engine to maintain its privileged kernel mode position while still enabling user communication through the mediator component.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If kernel mode components are given direct user interface capabilities, then user notification is improved, but system security and stability deteriorate

Engineering Contradiction:
Improveuser notification capabilityVSAvoidsystem security and stability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the system into distinct kernel mode and user mode components with clear boundaries. The security engine remains in kernel mode performing its security functions, while a separate host services component operates in user mode to handle user interface interactions. This segmentation allows each component to operate in its appropriate security context, preventing kernel mode components from directly accessing user interface resources and thus maintaining system security and stability.

Inventive Principle:
Principle #1Segmentation

3Reliability

If security policies require user input for enforcement actions, then security control is improved, but system response time deteriorates

Engineering Contradiction:
Improvesecurity controlVSAvoidsystem response time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements a caching mechanism where the host services component stores previously obtained user responses for similar security enforcement scenarios. When the security engine encounters a condition that requires user input, it first checks the cache for an existing response. If found, the cached response is used immediately without requiring new user interaction, thus maintaining security control while reducing system response time for recurring situations.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7530093B2Securing applications and operating systems
Publication Date: 2009.05.05 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7530093B2 patent drawing
  • US7530093B2 patent drawing
  • US7530093B2 patent drawing

AI summary

Techniques for securing applications and operating systems are provided. In an embodiment, the system notifies a user that a security enforcement action is being taken even though the condition prompting the action is detected by a security engine that executes in kernel mode. The security engine enforces security policies that help to ensure that a vulnerability of an application or operating system cannot be exploited. In an embodiment, the security system may solicit input from a user relating to a security enforcement action even though the condition prompting the action is detected by a security engine that executes in kernel mode. Security policies may be defined as sets of rules, each having a condition and an action. The security system thus enables kernel mode components to provide notifications to a user or solicit input from the user.