| Yes, create a proxy for any tcp-based application. I'm assuming this
is what possible with a 'packet filtering' router/firewall - protocol
filtering. Customer has this now and considers it a trade-off in
flexibility vs. security. We're trying to convince them otherwise.
Customer has a firewall based on a 'dynamic packet filtering'
architecture. Any thoughts on this vs. an application-level gateway?
It seems to have better flexibility than the applications gateways and
offers better security than the straight packet filters.
Regards,
|
| Some Packet filtering implementations have the capabilities of "remembering"
outgoing UDF packets that they have seen. They can then allow only
corresponding packets back in through the filtering mechanism. The router,
in essence, had the ability to modify the filtering rules on the fly to
accomodate returning packets. The rules created are time-limited; they only
last a few seconds or minutes. Dynamic packet filtering is used for any
situation in which the packet filtering rules change without somebody
explicitly changing the configuration in the router.
Checkpoint, Blackhole, SecureConnect Router, and karlBridge/KarlRouter are a
few examples of companies using this technology. It appears that this is the
way the industry, Router philosophy, are moving.
I believe that some companies are modifying their dynamic packet filtering
firewalls to operate at the application-level e.g., ftp. Checkpoint I believe
allows this.
There was some information about this in the June 1996 issue of LAN Times. It
was a special Internet issue. I think this is where I read this.
Regards,
|