IoT Device Class Validation via Behavioral Model Deviation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

IoT networks face challenges in authenticating devices and distinguishing between different classes of IoT devices, leading to potential security vulnerabilities as malicious entities can claim false device classes for additional network privileges.

Innovation Solution

Implementing a machine learning-based approach to validate device classes by applying access policies and behavioral models to traffic data, identifying deviations, and performing mitigation actions when abnormal behavior is detected, thereby ensuring secure network operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If IoT devices assert device class claims without strong authentication, then device integration is simplified and ease of operation is improved, but network security deteriorates as malicious entities can claim false device classes

Engineering Contradiction:
Improvedevice integrationVSAvoidnetwork security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary actions by establishing behavioral models for different device classes before devices connect to the network. These models capture normal traffic patterns, communication protocols, and operational behaviors. When a device asserts a class claim, the system has already prepared validation criteria to verify the claim against observed device behavior, preventing malicious entities from successfully impersonating legitimate devices.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements continuous feedback mechanisms by monitoring device traffic and comparing observed behavior against the established behavioral models. The network controller receives ongoing traffic data, validates it against the claimed device class, and provides feedback by accepting or rejecting the device class assertion. This feedback loop enables dynamic security validation while maintaining ease of device integration.

Inventive Principle:
Principle #23Feedback

2Measurement precision

If behavioral models are trained using only authorized traffic data, then measurement precision of device class validation is improved, but the quantity of training data required increases

Engineering Contradiction:
Improvedevice class validation accuracyVSAvoidtraining data volume
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The system extracts only the essential and most discriminative features from authorized traffic data to build behavioral models. Instead of using complete raw traffic captures, the system identifies and extracts key behavioral characteristics such as communication patterns, protocol sequences, timing intervals, and data flow characteristics. This extraction process maintains high validation precision while significantly reducing the volume of training data needed.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies local quality by focusing training efforts on specific critical behavioral aspects that are most indicative of device class identity. Rather than uniformly processing all traffic data, the system identifies and emphasizes locally important features such as authentication sequences, command-response patterns, or device-specific protocols. This selective focus improves measurement precision while minimizing the overall training data requirement.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11909741B2Validating a device class claim using machine learning
Publication Date: 2024.02.20 CISCO TECHNOLOGY INC
  • US11909741B2 patent drawing
  • US11909741B2 patent drawing
  • US11909741B2 patent drawing

AI summary

In one embodiment, a device in a network receives an access policy and a class behavioral model for a node in the network that are associated with a class asserted by the node. The device applies the access policy and class behavioral model to traffic associated with the node. The device identifies a deviation in a behavior of the node from the class behavioral model, based on the application of the class behavioral model to the traffic associated with the node. The device causes performance of a mitigation action in the network based on the identified deviation in the behavior of the node from the class behavioral model.