IoT Application Firewall for Dynamic Profile-Based Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current security measures for M2M and IoT devices are inadequate in detecting anomalies and preventing attacks, especially in IoT messaging protocols like MQTT and CoAP, due to limited computing power and constrained packaging, which makes existing systems ineffective in identifying ill-behaving devices that send small or large messages.

Innovation Solution

A computer-implemented system and method using an IoT Application Firewall (IAF) that dynamically computes device profiles on a per-session or across sessions, compares them with initial and learned profiles, and triggers actions if they do not match, providing end-to-end security by temporarily revoking certificates based on device misbehavior, security vulnerabilities, and attacks like DoS and DDoS.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing security systems are deployed to protect IoT devices, then security coverage is provided, but the systems are ineffective in identifying ill-behaving devices due to limited computing power and constrained packaging

Engineering Contradiction:
Improvesecurity effectivenessVSAvoidcomputing power requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an Application Firewall as an intermediary component that sits between the IoT device and the network. This firewall performs the complex security analysis and device behavior monitoring functions, relieving the constrained IoT device from executing sophisticated security algorithms. The firewall mediates all communications, analyzing device profiles and detecting anomalies without requiring the IoT device itself to have high computing power.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces traditional signature-based or rule-based security mechanisms with a machine learning-based device profile analysis system. Instead of relying on predefined security rules that require complex matching logic, the system uses learned device profiles to automatically identify normal vs. abnormal behavior patterns, substituting mechanical rule-processing with adaptive intelligent analysis.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Difficulty of detecting and measuring

If device profiles are monitored to detect anomalies, then security detection capability is improved, but the system complexity increases due to dynamic computation and comparison processes

Engineering Contradiction:
Improveanomaly detection capabilityVSAvoidsystem architecture
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

The patent performs preliminary actions by establishing baseline device profiles during normal operation before security incidents occur. The system learns and stores what constitutes normal device behavior patterns, communication protocols, and data flow characteristics. When anomalies need to be detected, the system simply compares current behavior against these pre-established profiles, avoiding the need for complex real-time analysis of normal behavior patterns.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where the system continuously monitors device behavior, compares it against learned profiles, and uses the results to refine and update the device profiles over time. This feedback loop allows the system to adapt to legitimate behavior changes while maintaining detection of true anomalies, reducing false positives and improving detection accuracy without proportionally increasing system complexity.

Inventive Principle:
Principle #23Feedback

3Loss of time

If real-time security monitoring is implemented, then threat response time is reduced, but the processing overhead and computational load increase

Engineering Contradiction:
Improvethreat response timeVSAvoidcomputational energy consumption
Core Design Contradiction:
Loss of timeVSUse of energy by moving object

Solution Approach 1:

The patent segments the security monitoring function into distinct components: device profile establishment, real-time behavior comparison, and anomaly response. The heavy computational work of profile learning is performed during off-peak times or during normal device operation when bandwidth is available, while real-time monitoring only requires lightweight comparison operations. This segmentation allows real-time detection without sustained high computational load.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by focusing security monitoring only on critical communication patterns and data flows that are most likely to indicate security threats. Rather than analyzing every single packet or device operation in exhaustive detail, the system monitors key behavioral indicators and communication metadata, achieving effective threat detection with reduced processing overhead compared to complete deep packet inspection of all traffic.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20220311747A1Method and system for securing connections to IoT devices
Publication Date: 2022.09.29 AERIS COMM INC
  • US20220311747A1 patent drawing
  • US20220311747A1 patent drawing
  • US20220311747A1 patent drawing

AI summary

A computer-implemented method, system and computer program product for securing connections in systems including Machine to Machine (M2M) or Internet of Things (IoT) devices are disclosed. The computer-implemented method for providing end-to-end security to systems including M2M or IoT devices includes: receiving an initial device profile for at least one IoT device; learning a device profile based on data flow to and from the at least one IoT device; dynamically computing a device profile on a per-session basis or across sessions; comparing the dynamically computed device profile for the at least one IoT device with the initial device profile and/or the learned device profile for the at least one IoT device; and triggering an action if the dynamically computed device profile for the at least one IoT device does not match the initial device profile and/or the learned device profile for the at least one IoT device.