MDM Agent Security Posture Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The 'bring your own device' (BYOD) model in enterprise computing lacks tight control over software installations, posing security concerns as users may install unsecured applications, leading to potential malware and data compromise when accessing enterprise data.

Innovation Solution

Implementing a mobile device management (MDM) agent that monitors and reports security posture changes to an MDM server, using SAML for joint user-and-device authentication to enforce real-time security updates and policy decisions, ensuring compliance with enterprise security policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users are allowed to install their own applications on mobile devices (BYOD model), then device autonomy and user convenience are improved, but security control and data protection deteriorate

Engineering Contradiction:
Improveuser convenienceVSAvoidsecurity control
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system segments security management by creating separate security zones or containers within the mobile device. The MDM agent establishes a secure enclave that isolates enterprise data and applications from user-installed applications, allowing users to install personal apps while maintaining security boundaries. This segmentation enables both user convenience and security control to coexist.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The MDM agent acts as an intermediary between the operating system and applications, mediating security policies and access controls. It monitors security posture changes and enforces policies without preventing users from installing applications, thus maintaining both user autonomy and security enforcement through the intermediary layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If continuous monitoring of security posture changes is implemented, then security response time is improved, but system resource consumption and complexity increase

Engineering Contradiction:
Improvesecurity response timeVSAvoidsystem complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

Instead of continuous monitoring, the system implements periodic security posture assessments triggered by specific events or time intervals. The MDM agent monitors for predefined security events (such as application installations, system updates, or configuration changes) and initiates assessments only when these events occur, reducing continuous resource consumption while maintaining timely security response.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system employs self-service mechanisms where the MDM agent automatically detects security posture changes and triggers appropriate responses without requiring constant external intervention. The agent maintains a baseline security state and autonomously identifies deviations, reducing system complexity while enabling rapid security response through automated self-monitoring.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP3238414B1Real-time mobile security posture
Publication Date: 2021.12.29 MCAFEE LLC
  • EP3238414B1 patent drawingFigure 1
  • EP3238414B1 patent drawingFigure 2~3
  • EP3238414B1 patent drawingFigure 4

AI summary

In an example, a system and method for real-time mobile security posture updates is provided. A mobile device management (MDM) agent may run on the mobile device, and may register with the operating system one or more mobile security posture change events that may affect the mobile security posture. These may include, for example, installation of an MDM agent, uninstallation of a program, connecting to a secured or unsecured network, or similar. When any such event occurs, the OS lodges the event with the MDM agent, which then communicates with an MDM server engine to potentially receive new security instructions. Lodging the event may include providing a joint user-and-device authentication to the MDM server, such as via SAML.