ML Anomaly Detection for Embedded Software Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Embedded software applications in physical systems are vulnerable to security attacks due to the limitations in detecting anomalies, especially in resource-constrained environments where traditional methods fail to accurately characterize normal and abnormal behavior.

Innovation Solution

A machine learning-based anomaly detection system that trains models using application-specific parameters such as execution times and instruction counts, allowing for real-time identification of abnormal behavior by correlating activity measures with application context, thereby providing resource-efficient anomaly detection mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If traditional anomaly detection methods are used in embedded systems, then device complexity is reduced, but measurement precision and reliability of anomaly detection deteriorate due to inability to accurately characterize normal and abnormal behavior

Engineering Contradiction:
Improveanomaly detection accuracyVSAvoiddetection system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system performs preliminary characterization of normal application behavior during a learning phase before actual anomaly detection begins. By pre-collecting performance data and establishing baseline models of normal behavior, the system prepares detection capabilities in advance, enabling accurate anomaly identification without requiring complex real-time analysis infrastructure.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The anomaly detection system is divided into distinct functional components: a learning phase for data collection and model training, and a detection phase for actual anomaly identification. This segmentation allows each component to be optimized independently, with the learning phase focusing on accurate characterization and the detection phase on efficient comparison and identification.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If resource-constrained embedded environments are considered, then ease of operation is improved, but measurement precision and detection capability worsen due to limited computational resources

Engineering Contradiction:
Improvebehavior characterization accuracyVSAvoidcomputational resource consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The system extracts and monitors only specific performance counters and behavioral metrics that are most indicative of anomalies, rather than analyzing all possible system parameters. By selecting and focusing on key performance indicators such as instruction counts, cycle counts, and memory access patterns, the system achieves accurate anomaly detection with minimal resource consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system changes the parameters being monitored from raw performance data to normalized behavioral characteristics that capture essential application patterns. By transforming performance counters into meaningful behavioral metrics and using these as input features for anomaly detection, the system achieves high measurement precision while keeping computational requirements manageable for embedded systems.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If application-specific parameters are incorporated into anomaly detection, then reliability and measurement precision improve, but device complexity increases due to need for task-specific models

Engineering Contradiction:
Improveanomaly detection reliabilityVSAvoidmodel management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system employs a universal anomaly detection framework that can handle multiple application types and tasks through a common detection mechanism. Rather than requiring completely separate detection systems for each application, the universal framework adapts to different applications by using their specific performance characteristics as input, thereby improving reliability without proportionally increasing overall system complexity.

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

4Productivity

If real-time anomaly detection is implemented, then productivity and speed of detection are improved, but measurement precision may worsen due to time constraints in resource-constrained environments

Engineering Contradiction:
Improvedetection speedVSAvoidanomaly identification accuracy
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

By pre-characterizing normal application behavior and establishing baseline models during the learning phase, the system eliminates the need for complex real-time analysis. The preliminary models enable fast comparison operations during actual detection, achieving both high productivity through rapid anomaly identification and high measurement precision through accurate baseline matching.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3918500B1Machine learning-based anomaly detections for embedded software applications
Publication Date: 2024.04.24 SIEMENS INDUSTRY SOFTWARE INC
  • EP3918500B1 patent drawingFigure 1
  • EP3918500B1 patent drawingFigure 2
  • EP3918500B1 patent drawingFigure 3

AI summary

Systems, methods, logic, and devices may support machine learning-based anomaly detections for embedded software applications. In a learning phase, an anomaly model training engine may construct an anomaly detection model, and the anomaly detection model configured to provide a determination of whether the embedded software application exhibits abnormal behavior based on activity measure and application parameter inputs. In a run-time phase, an anomaly detection engine may sample the embedded software application to obtain an activity measure and application parameters during the run-time execution and provide, as inputs to the anomaly detection model, the activity measure and the application parameters sampled during the run-time execution. The anomaly detection engine may further determine whether the embedded software application exhibits abnormal behavior based on an output from the anomaly detection model for the provided inputs.