J
John Lee
Hi,
Here is the environment related context:
=========================================================================
Website are hosted in DMZ - subdomain created dmz.companydomain.com
We have our web farm (3-5 web servers) running under one NT Domain account
with least privileges.
Website all 3 level of access: anonymous, registered and verified
We will use form authentication to authenticate registered and verified user
SQL server will be used to host user authentication information and Session
state
All Line of business web services are hosted internally with Windows
authentication only
AzMan is used to perform access check on all public web methods
=========================================================================
My question are:
Is this a good practice? Any obvious flaw?
What is the best way to encrypt session state because it might contain
sensitive data?
If the internal web service trust the NT domain account that hosts the web
site, it means that if someone gain access/control to the site then he could
possibly call any of the web service methods, is this correct? how to
prevent it from happening?
What is the best way to secure public access website that will
retrieve/update internal business data?
Thanks very much!
John
Here is the environment related context:
=========================================================================
Website are hosted in DMZ - subdomain created dmz.companydomain.com
We have our web farm (3-5 web servers) running under one NT Domain account
with least privileges.
Website all 3 level of access: anonymous, registered and verified
We will use form authentication to authenticate registered and verified user
SQL server will be used to host user authentication information and Session
state
All Line of business web services are hosted internally with Windows
authentication only
AzMan is used to perform access check on all public web methods
=========================================================================
My question are:
Is this a good practice? Any obvious flaw?
What is the best way to encrypt session state because it might contain
sensitive data?
If the internal web service trust the NT domain account that hosts the web
site, it means that if someone gain access/control to the site then he could
possibly call any of the web service methods, is this correct? how to
prevent it from happening?
What is the best way to secure public access website that will
retrieve/update internal business data?
Thanks very much!
John