DNS Mapping Update for Network Policy Enforcement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computer networking systems lack efficient mechanisms to dynamically update and enforce network policies based on changing DNS mappings, leading to potential security vulnerabilities and inaccuracies in resource-to-IP address mappings.

Innovation Solution

A method and system that monitor DNS responses to generate and update mappings of resources and IP addresses, allowing for the identification and application of network policies to client requests by intercepting and inspecting communications, ensuring that only requests with applicable policies are inspected.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If DNS mappings are manually updated, then mapping accuracy is maintained, but system adaptability deteriorates due to inability to reflect real-time DNS changes

Engineering Contradiction:
Improvemapping accuracyVSAvoidreal-time DNS change reflection
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary actions by maintaining a local cache of DNS mappings that are proactively updated before actual DNS changes affect network operations. The DNS monitoring component continuously checks for changes and updates the local mapping data structure in advance, ensuring both accuracy and real-time adaptability without manual intervention.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where DNS monitoring continuously observes DNS responses and compares them against the local mapping cache. When discrepancies are detected, the system automatically updates the mapping data structure and triggers policy re-evaluation, creating a closed-loop feedback system that maintains both precision and adaptability dynamically.

Inventive Principle:
Principle #23Feedback

2Reliability

If all client requests are inspected, then network security is improved, but system productivity deteriorates due to excessive inspection overhead

Engineering Contradiction:
Improvenetwork securityVSAvoidrequest processing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system applies local quality by differentiating inspection requirements based on the specific resource being accessed. Instead of uniformly inspecting all requests, the system identifies resources associated with the client device and applies targeted inspection only to those specific requests. This selective approach maintains security for critical resources while reducing overall inspection overhead and improving processing efficiency.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system employs partial action by inspecting only a subset of requests that are deemed necessary based on policy associations. The DNS monitoring and mapping system identifies which resources require policy enforcement, and only those corresponding requests undergo inspection. This partial inspection approach achieves adequate security coverage without the excessive overhead of universal inspection.

Inventive Principle:
Principle #16Partial or excessive action

3Measurement precision

If DNS monitoring is implemented, then mapping accuracy is improved, but device complexity increases due to additional monitoring and update mechanisms

Engineering Contradiction:
ImproveDNS mapping accuracyVSAvoidsystem architecture complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system achieves universality by designing the DNS monitoring component to serve multiple functions simultaneously. The same monitoring mechanism not only updates DNS mappings but also validates policy associations, triggers security evaluations, and maintains the mapping data structure. This multi-functional approach improves mapping accuracy without proportionally increasing system complexity, as one component performs multiple critical tasks.

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

Solution Approach 2:

The system merges previously separate functions into integrated components. The DNS monitoring, mapping update, and policy enforcement mechanisms are combined into a unified system where a single data structure stores both DNS mappings and associated policies. This consolidation reduces overall system complexity while maintaining accurate and up-to-date resource-to-IP address mappings with their policy contexts.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9525602B2Maintaining IP tables
Publication Date: 2016.12.20 IBOSS INC
  • US9525602B2 patent drawing
  • US9525602B2 patent drawing
  • US9525602B2 patent drawing

AI summary

Data including a set of one or more resources and one or more associated IP addresses is updated based on monitored DNS responses. A request is received from a client device for a resource identified by an IP address. The IP address is matched to one of the IP addresses in the set of one or more IP addresses. A particular resource associated with the matched IP address is identified. A particular network policy that applies is identified. The identified particular network policy is applied to the received request.