Firewall Protocol Classification Using RFC-Exception Database
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Firewall systems face insecurity due to allowing non-standard protocols, which can circumvent security policies, or being too restrictive and blocking commonly used communications, thereby breaking functionality of software applications.
Innovation Solution
A firewall system that identifies non-RFC-compliant data packets by determining if they match standard or RFC-exception protocols, allowing transmission based on associated policies, and sending unknown protocols to a support system for analysis and potential addition to the RFC-exception database.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the firewall blocks all non-RFC-compliant protocols, then security is improved, but functionality of commonly-used software applications is broken
Solution Approach 1:
The patent segments non-RFC-compliant protocols into two categories: known safe protocols (RFC-exception protocols) and unknown protocols. The firewall maintains separate handling paths for each category, allowing safe non-compliant protocols while blocking unknown ones, thus resolving the contradiction between security and functionality.
Solution Approach 2:
The patent performs preliminary classification of non-RFC-compliant protocols by comparing them against a database of known safe protocols before applying security policies. This preliminary action allows the firewall to distinguish between safe and dangerous non-compliant protocols, enabling functionality preservation for safe protocols while maintaining security against unknown protocols.
2Ease of operation
If the firewall allows all non-RFC-compliant protocols, then functionality of software applications is preserved, but security policies may be circumvented
Solution Approach 1:
The patent segments non-RFC-compliant protocols into known safe protocols (RFC-exception protocols) and unknown protocols, applying different security policies to each segment. This segmentation allows functionality preservation for known safe protocols while maintaining security controls for unknown protocols.
Solution Approach 2:
The patent implements a feedback mechanism where the firewall learns from classified protocols and updates its classification database. When an unknown non-RFC-compliant protocol is blocked, administrators can review and classify it as safe, creating a feedback loop that progressively improves functionality while maintaining security.
3Object-affected harmful factors
If the firewall uses a strict RFC-compliance check, then security against unknown protocols is improved, but commonly-used non-standard protocols are blocked
Solution Approach 1:
The patent segments protocol handling into strict RFC-compliance checking for unknown protocols and relaxed checking for known safe non-compliant protocols. This segmentation provides protection against dangerous protocols while maintaining adaptability for commonly-used non-standard protocols.
Solution Approach 2:
The patent performs preliminary classification of incoming non-RFC-compliant protocols against a database of known safe protocols before applying strict security policies. This preliminary action enables the firewall to adaptively handle non-standard protocols that have been previously identified as safe.
4Reliability
If the firewall blocks unknown non-RFC-compliant protocols, then security is maintained, but safe non-standard communications are prevented
Solution Approach 1:
The patent performs preliminary classification of non-RFC-compliant protocols by comparing them against a database of known safe protocols before blocking. This preliminary action prevents the loss of safe communications by identifying and allowing them while maintaining security against truly unknown protocols.
Solution Approach 2:
The patent implements a feedback mechanism where blocked unknown protocols can be reviewed and classified as safe by administrators. This feedback loop prevents the permanent loss of safe communications by allowing reclassification of protocols that were initially blocked as unknown.
Data Source
AI summary
A firewall system determines whether a protocol used by an incoming data packet is a standard protocol compliant with Request For Comment (RFC) standards. In the event the protocol is RFC compliant, the firewall transmits the packet to the recipient according to firewall policies regarding the standard protocol. If the protocol is not that of an RFC standard, the firewall determines whether the protocol matches an RFC-exception protocol in a RFC-exception protocol database. If the protocol does match an RFC-exception, the firewall may transmit the packet to the recipient according to firewall policies regarding the RFC-exception protocol. If it does not match an RFC-exception, the firewall may transmit the packet or protocol to a support system where it may be quarantined until it is approved based on a decision that the protocol is safe and/or widely adopted.