Multi-tiered DNS Architecture for Malicious Traffic Mitigation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for detecting network security events, particularly in DNS systems, face challenges in distinguishing between anomalous and normal traffic patterns due to the rarity of malicious events and the complexity of Internet traffic, often resulting in false alarms and the inability to differentiate between benign and malicious traffic.
Innovation Solution
A multi-tiered DNS architecture using machine learning to assign reputation scores to source devices, with a two-stage encoder-decoder neural network for anomaly detection and classification, redirecting queries from a first-tier to a second-tier DNS server based on status changes identified through anomalous traffic patterns.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If conventional fixed signatures are used for attack detection, then detection simplicity is maintained, but detection accuracy deteriorates as attack patterns evolve
Solution Approach 1:
The patent implements dynamic detection by transitioning from static fixed signatures to adaptive machine learning models that continuously learn and update attack patterns. The system dynamically adjusts detection parameters and retrain models based on evolving traffic characteristics, enabling the detection mechanism to adapt to new attack patterns while maintaining operational simplicity through automated updates.
2Measurement precision
If volumetric based approach with numerous measurements is used, then anomaly detection capability is improved, but false alarm rate increases due to over-fitting
Solution Approach 1:
The patent extracts and focuses on the most critical features from the volumetric dataset, removing irrelevant and redundant measurements that cause over-fitting. The machine learning models identify and retain only the essential traffic characteristics needed for accurate anomaly detection, thereby maintaining high detection capability while eliminating the source of false alarms through feature selection and dimensionality reduction.
3Measurement precision
If anomalous behavior is described with many features, then detection accuracy is improved, but system complexity and false blocking increase
Solution Approach 1:
The patent applies local quality by assigning different levels of analysis to different traffic characteristics. Rather than uniformly processing all features with high complexity, the system identifies specific local patterns and anomalies in traffic behavior that are most indicative of malicious activity, focusing computational resources on these critical local characteristics while simplifying processing of less important features.
4Device complexity
If mitigation efforts block traffic based on limited parameters, then system simplicity is maintained, but malicious traffic penetration increases
Solution Approach 1:
The patent introduces machine learning models as intermediary components between traffic monitoring and mitigation actions. These intermediary models analyze traffic patterns using multiple parameters and provide refined classification decisions, enabling the system to maintain operational simplicity at the decision-making layer while incorporating sophisticated multi-parameter analysis in the intermediate processing stage, thereby blocking malicious traffic more effectively without increasing overall system complexity.
Data Source
AI summary
A processing system having at least one processor may obtain domain name system (DNS) traffic records of a DNS platform, the DNS traffic records associated with a source device having a first status and that is submitting DNS queries, where a first-tier DNS authoritative server of the DNS platform is configured to forward the DNS queries from the source device to at least a first second-tier DNS authoritative server of the DNS platform designated for the first status. The processing system may further detect anomalous DNS traffic records from the DNS traffic records, identify a change of the source device from a first status to a second status, based upon the detecting the anomalous DNS traffic records, and reconfigure the first-tier DNS authoritative server to redirect the DNS queries from the source device to at least a second second-tier DNS authoritative server designated for the second status.


