RE: [fw-wiz] HTTPS, proxies, and remote developers.
From: Melson, Paul (PMelson_at_sequoianet.com)
Date: 06/16/03
- Previous message: Gregory Austin: "Re: [fw-wiz] VA vs PT tool"
- Maybe in reply to: Devdas Bhagat: "[fw-wiz] HTTPS, proxies, and remote developers."
- Next in thread: Hilal Hussein: "RE: [fw-wiz] HTTPS, proxies, and remote developers."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
To: "Firewall-Wizards" <firewall-wizards@honor.icsalabs.com> Date: Mon, 16 Jun 2003 08:36:51 -0400
Take the connections off a public network. It may be time to explore a T1, ISDN, dial-up, or other "private" connection. Then that connection should be filtered similarly to what you allow across the Internet.
PaulM
> -----Original Message-----
> What would be the easiest way to handle this situation? How would you
> resolve a policy issue if one of your clients requires that you use
> unencrypted traffic outbound from their network into yours.
> (Their need to know for traffic on their network against your need for
> security).
_______________________________________________
firewall-wizards mailing list
firewall-wizards@honor.icsalabs.com
http://honor.icsalabs.com/mailman/listinfo/firewall-wizards
- Previous message: Gregory Austin: "Re: [fw-wiz] VA vs PT tool"
- Maybe in reply to: Devdas Bhagat: "[fw-wiz] HTTPS, proxies, and remote developers."
- Next in thread: Hilal Hussein: "RE: [fw-wiz] HTTPS, proxies, and remote developers."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|