Re: web service architecture question

From: Jeffrey Hasan (jeff_at_noreply.com)
Date: 08/12/04


Date: Thu, 12 Aug 2004 16:44:10 -0700

Jon,

This level of work is unnecessary for several reasons, because today we have
more options for securing code than we used to. With Code Access Security
there is a lot that you can do to lockdown code. In addition, why not focus
on securing the service interface? Take a look at the Web Services
Enhancements 2.0. It implements WS-Security, which gives you the benefits of
digital signatures and encryption on the Web service requests and responses.
It supports a variety of tokens so you can completely restrict who has
access to your service interface. Clearly, if your application code is so
sensitive, then I am assuming that you are equally concerned about who is
making service requests.

Jeffrey Hasan, MCSD
President, Bluestone Partners, Inc.
-----------------------------------------------
Author of: Expert SOA in C# Using WSE 2.0 (APress, 2004)
http://www.bluestonepartners.com/soa.aspx

"Jon Paugh" <anonymous@discussions.microsoft.com> wrote in message
news:374401c47eee$a5cda310$a501280a@phx.gbl...
> Hi All,
>
> Our customer wants us architecturally to have two
> physical servers - a web server box and an application
> server box. The web server will be exposed outside the
> firewall whereas the application server will only be
> accessible by the web server. Our web server will never
> access the database directly. Our web server will always
> go thru our application server to access the database.
> Our web server will use .NET remoting or web services to
> access the application server. So the benefit of these
> seperate servers is supposed to be added security - the
> application tier is behind a second firewall and more
> secure than the web server. We have a physical seperate
> between our GUI and application logic as well.
>
> So, the questions are:
>
> 1) This looks like a lot of work for us. Right now we
> have a web server that performs application logic and
> directly accesses the database. Is there any way to
> increase the security of our web server without
> seperating out to a seperate web server and application
> server? The security benefit is the only thing I see so
> far...
> 2) If we do seperate into a seperate application server
> and web server, should the web server use .NET remoting
> or web services to access the application server?
> 3) If we go with web services to access the application
> server, what types should we use in the web service
> proxy - the types generated by the proxy, or should we
> change the generated proxy to use the actual types from
> our application...? ( This types question is the worst
> issue to me. We are using an ORM tool so we have pretty
> complex business objects and returning them thru
> serialization to our GUI would be a pain).
>
> Thanks,
>
> Jon Paugh



Relevant Pages

  • [NT] Poisoning Cached HTTPS Documents in Internet Explorer
    ... Get your security news from a reliable source. ... "poison" a user's browser cache with a malicious document that will later ... The attacker can exploit this vulnerability for "replacing" HTML ... to communicate with a malicious web server over HTTPS without the browser ...
    (Securiteam)
  • [NT] Webserver 4D Weak Password Preservation Vulnerability
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... complete Web Server environment written entirely on top of 4th Dimension, ... WS4D web server saves the passwords somewhere insecure. ...
    (Securiteam)
  • Re: 2003 Web Server Security flaw
    ... "Locked-down windows 2003 Web Server used only to host web sites". ... What is your logic/rationale for Media Player being a required install ... The Media Player patch was the ONLY that FAILED. ... > When talking about computer security, there are areas that have no such ...
    (microsoft.public.windows.server.security)
  • Web session tracking security prob. Vulnerable: IIS and ColdFusion (maybe others)
    ... SECURITY PROBLEMS WITH WEB SERVERS' SESSION TRACKING MECHANISMS. ... 2001 we reported the following problem (with specifics to IIS and SITESERVER) to the Microsoft Security Response Center. ... These vulnerabilities, especially when combined with well-known cross-site scripting vulnerabilities, could cause loss of confidentiality, failure of non-repudiation and fraud. ... The browser stores and returns the "ASPSESSIONID" or "CFID/CFTOKEN" values with each subsequent request to the web server. ...
    (Vuln-Dev)
  • Re: Recommended Windows Hosts
    ... disagreement with their business strategy though and their ... >attempt to repair security flaws...". ... My point is that they are patching a damaged architecture. ... >recommended not allowing parent paths on the Web server. ...
    (microsoft.public.frontpage.client)