Virtual Machine Security Enforcement via Life Cycle Agents

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud computing environments face significant security challenges in ensuring consistent security control over virtual machines throughout their life cycles, particularly due to vulnerabilities during state changes and the risk of data access by administrators with full privileges, as well as tampering during image transitions between hosts.

Innovation Solution

The implementation of a life cycle manager component in conjunction with local life cycle agents on virtual machines, which enforces security controls by validating authentication credentials, encrypting sensitive data, monitoring integrity, and managing state changes to prevent unauthorized access and tampering, ensuring that virtual machines adhere to defined security policies across various states such as inactive, active, out of sync, locked, and disposed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If administrators have full privileges to manage virtual machines, then system operability and maintenance are improved, but security risks increase due to potential unauthorized access and data tampering

Engineering Contradiction:
Improvesystem operabilityVSAvoidsecurity risks
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a life cycle agent as an intermediary component that runs within the virtual machine and a life cycle manager that operates outside the virtual machine. These intermediaries enforce security policies, validate state transitions, and monitor integrity without preventing administrators from performing necessary management tasks. The agent acts as a local security enforcer that mediates between administrator actions and system security requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary security validations before allowing virtual machine state transitions. The life cycle manager validates authentication credentials, checks policy compliance, and verifies integrity before permitting transitions between states such as inactive, active, locked, or disposed. This preliminary action prevents unauthorized access before it can occur.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If virtual machines can be freely copied or cloned, then productivity and flexibility are improved, but security control deteriorates due to potential unauthorized propagation and data theft

Engineering Contradiction:
Improvevirtual machine deployment efficiencyVSAvoidsecurity control consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The life cycle agent continuously monitors the virtual machine state and provides feedback to the life cycle manager. When a virtual machine is copied or cloned, the agent detects the new instance and reports it to the manager, which then validates the copy against security policies. This feedback mechanism ensures that productivity gains from cloning do not compromise security control consistency.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Before allowing virtual machine copying or cloning operations, the life cycle manager performs preliminary validation checks to ensure the operation complies with security policies. The system verifies authentication credentials and checks whether the copy operation is permitted under current security conditions, preventing unauthorized propagation before it occurs.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If security checks are performed at every virtual machine state transition, then security reliability is improved, but system complexity increases due to multiple validation points and states

Engineering Contradiction:
Improvesecurity enforcement consistencyVSAvoidlife cycle management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the security enforcement functionality into distinct components: the life cycle manager that handles high-level policy decisions and the life cycle agent that handles local execution and monitoring. This segmentation distributes complexity across multiple specialized components rather than concentrating all security logic in a single complex system, making the overall system more manageable and maintainable.

Inventive Principle:
Principle #1Segmentation

4Object-affected harmful factors

If virtual machines are monitored continuously for integrity, then data protection is improved, but use of energy increases due to constant monitoring and validation processes

Engineering Contradiction:
Improvedata protectionVSAvoidcomputational resource consumption
Core Design Contradiction:
Object-affected harmful factorsVSUse of energy by moving object

Solution Approach 1:

The life cycle agent performs integrity monitoring and security validations at periodic intervals and at key state transition points rather than continuously. The system checks integrity when virtual machines start, stop, or transition between states, and periodically during operation, rather than maintaining constant monitoring. This periodic action maintains data protection while reducing unnecessary computational resource consumption.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9389898B2System and method for enforcement of security controls on virtual machines throughout life cycle state changes
Publication Date: 2016.07.12 CA TECH INC
  • US9389898B2 patent drawing
  • US9389898B2 patent drawing
  • US9389898B2 patent drawing

AI summary

Systems and methods associated with virtual machine security are described herein. One example method includes instantiating a guest virtual machine in a virtual computing environment. The method also includes installing a life cycle agent on the guest virtual machine, assigning an identifying certificate, a set of policies, and an encryption key to the guest virtual machine, and providing the certificate, policies, and encryption key to the guest virtual machine. The certificate, policies, and encryption key may then be used by the guest virtual machine to authenticate itself within the virtual computing environment and to protect data stored on the guest virtual machine.