OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Re: Firewall ports
From: Henry Sieff (hsieffORTHODON.COM)
Date: Thu Jun 22 2000 - 14:39:07 CDT

No problem; check out Sam Stern's email; just browsed it and he gives
a good list of pointers to provide additional security. One thing I
didn't mention is that if you are providing full exchange services to
your roaming clients )(as opposed to just POP3 and SMTP, like I was
assuming) you'll want to take additional precautions to secure this.
Sam mentions some of them in his email.

Be sure to include some time/money to test your deployment plan in
your proposed action plan (he says, speaking from painful experience).

Henry

>-----Original Message-----
>From: Gene Gomez [mailto:ggomezverance.com]
>Sent: Thursday, June 22, 2000 2:25 PM
>To: 'Henry Sieff'; 'Focus on Microsoft Mailing List'
>Subject: RE: Firewall ports
>
>
>Henry,
>Thanks for the help...I'm in the pre-development/funds-request
>phase right
>now. As soon as I can show management that I've got an action plan
for
>deployment and security I'll probably get the go-ahead to put
>it in place.
>If I have any problems with the deployment I'll drop another
>line. Thanks!
>
>-Gene
>
>-----Original Message-----
>From: Henry Sieff [mailto:hsiefforthodon.com]
>Sent: Thursday, June 22, 2000 12:20 PM
>To: 'Gene Gomez'; 'Focus on Microsoft Mailing List'
>Subject: RE: Firewall ports
>
>
>Okay; that sounds like a classic DMZ scenario, in which case, what
you
>want is to open up those ports I listed between the exchange server
in
>Segment B and the Domain Controller in Segment A.
>
>Let me know if that works for you.
>
>Henry
>