Click here to get back home

is ssl secure enough ?

 HomeNewsGroups | Search | About
 microsoft.public.windows.server.security    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
is ssl secure enough ? Peter Baumann 06-15-2005
Posted by Peter Baumann on June 15, 2005, 11:33 pm
Please log in for more thread options
hi,

a general question :-) do you think that ssl is secure enough ?
following situation:

[Mobile Client] ---> SLL ---> [FIREWALL with SLL open] --> [Exchange OMA
(SSL) //no Frontend Server//]

OK - the communication between the client and the server is secure - but i
think this is nevertheless a problem, because sll is open on the firewall
and a sll "stream" is able to terminate in my lan. i beleive ssl is the same
as http (only encrypted) - and we know that every evil thing can be done
over http ;-)
so i think if the ssl port is open on my firewall - mr. "hacker" is able to
to bad things in my lan - with sll instead of http.

im wrong ? - or i understand something wrong ?

greetings.
Peter Baumann




Posted by Mark Gamache on June 15, 2005, 3:09 pm
Please log in for more thread options
assuming that you only allow the SSL to the Exchange OMA front end and you
follow best practices in locking down the server, its all acceptable.

The weak point in the security model has nothing to do with your question
(SSL). The weak point is the IIS server that runs OMA. SSL is bullet
proof.

Cheers,


--
Mark Gamache
Certified Security Solutions
http://www.css-security.com



> hi,
>
> a general question :-) do you think that ssl is secure enough ?
> following situation:
>
> [Mobile Client] ---> SLL ---> [FIREWALL with SLL open] --> [Exchange OMA
> (SSL) //no Frontend Server//]
>
> OK - the communication between the client and the server is secure - but i
> think this is nevertheless a problem, because sll is open on the firewall
> and a sll "stream" is able to terminate in my lan. i beleive ssl is the
> same
> as http (only encrypted) - and we know that every evil thing can be done
> over http ;-)
> so i think if the ssl port is open on my firewall - mr. "hacker" is able
> to
> to bad things in my lan - with sll instead of http.
>
> im wrong ? - or i understand something wrong ?
>
> greetings.
> Peter Baumann
>
>




Posted by James Butler on June 16, 2005, 6:13 am
Please log in for more thread options
SSL is fine, in fact better than traditional VPN's in some ways because SSL
wouldn't keep cached copy of your mails after you're done reading em, In an
Internet café you shouldn't be bothered that somebody else would be able to
read your mails after you've gone.

The thing you should be concerned with is your method of authentication, a
two factor mode of authentication is always good, however not cheap.

Also, a design consideration, make sure the OWA server seats behind a
reverse proxy server. So that your outside users talk directly to the
reverse proxy server, and the proxy server talks to the OWA on their behalf.


> assuming that you only allow the SSL to the Exchange OMA front end and you
> follow best practices in locking down the server, its all acceptable.
>
> The weak point in the security model has nothing to do with your question
> (SSL). The weak point is the IIS server that runs OMA. SSL is bullet
> proof.
>
> Cheers,
>



Posted by S. Pidgorny on June 16, 2005, 6:28 pm
Please log in for more thread options
Traditional (IPsec/PPTP) VPNs won't affect the client behaviour in a way
that it will keep cached information. It's sometimes hard to initiate VPN
connection from an Internet cafe - but if sensitivity of cached information
is a matter of concern, publicly available/unmanaged clients should not be
used to access the information. One should not make assumption that HTTPs
session data won't be cached or intercepted otherwise.

Some new VPN servers create secure sandbox for accessing sensitive
information and cleaning up properly - they use SSL. Key loggers would be of
a concern, still.

--
Svyatoslav Pidgorny, MS MVP - Security, MCSE
-= F1 is the key =-

> SSL is fine, in fact better than traditional VPN's in some ways because
SSL
> wouldn't keep cached copy of your mails after you're done reading em, In
an
> Internet café you shouldn't be bothered that somebody else would be able
to
> read your mails after you've gone.
>
> The thing you should be concerned with is your method of authentication, a
> two factor mode of authentication is always good, however not cheap.
>
> Also, a design consideration, make sure the OWA server seats behind a
> reverse proxy server. So that your outside users talk directly to the
> reverse proxy server, and the proxy server talks to the OWA on their
behalf.
>
>
> > assuming that you only allow the SSL to the Exchange OMA front end and
you
> > follow best practices in locking down the server, its all acceptable.
> >
> > The weak point in the security model has nothing to do with your
question
> > (SSL). The weak point is the IIS server that runs OMA. SSL is bullet
> > proof.
> >
> > Cheers,
> >
>




Posted by James Butler on June 17, 2005, 1:03 am
Please log in for more thread options
Yes I agree key loggers could be a problem, that's why I said:
> The thing you should be concerned with is your method of authentication, a
> two factor mode of authentication is always good, however not cheap.


On 16/6/05 9:28 am, in article #6Upw1kcFHA.132@TK2MSFTNGP10.phx.gbl, "S.

> Traditional (IPsec/PPTP) VPNs won't affect the client behaviour in a way
> that it will keep cached information. It's sometimes hard to initiate VPN
> connection from an Internet cafe - but if sensitivity of cached information
> is a matter of concern, publicly available/unmanaged clients should not be
> used to access the information. One should not make assumption that HTTPs
> session data won't be cached or intercepted otherwise.
>
> Some new VPN servers create secure sandbox for accessing sensitive
> information and cleaning up properly - they use SSL. Key loggers would be of
> a concern, still.



Similar ThreadsPosted
Secure FTP June 15, 2005, 2:16 pm
Best way to secure August 20, 2007, 7:44 pm
Secure VPN access...? June 21, 2005, 5:13 pm
TS Client - How Secure? July 10, 2005, 1:21 am
Secure SFU Server for NIS November 22, 2006, 4:58 am
Secure SSL with LDAP and AD May 20, 2008, 11:23 am
cannot access a secure web site September 27, 2005, 1:15 pm
Secure Remote Desktop August 10, 2006, 11:00 pm
WPA2 with PEAP-TLS - How secure is it? November 5, 2006, 7:42 am
Best practice to secure server????? November 28, 2006, 4:35 am

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap