V
Vadim
Hi,
I am wondering if somebody has any opinion if something is wrong with the
described below scenarion, can be improved, etc....
I think is scenario is very good.
Our asp.net app (connects to SQL Server) is installed at a client's site
using from my point of view the most standard way of security configuration:
IIS is configured for windows authentication with Impersonation=True, IIs
machine is installed in DMZ and connects inside firewall to AD and sql
server.
SQL server is also configured to use windows authentication and user
credentials obviously are propagated from IIS.
I heard complains about this scenarion that if a hacker breaks into IIS
machine they can go directly to sql server inside firewall.
Or maybe there are also other threats using this scenario.
Thank you,
Vadim
I am wondering if somebody has any opinion if something is wrong with the
described below scenarion, can be improved, etc....
I think is scenario is very good.
Our asp.net app (connects to SQL Server) is installed at a client's site
using from my point of view the most standard way of security configuration:
IIS is configured for windows authentication with Impersonation=True, IIs
machine is installed in DMZ and connects inside firewall to AD and sql
server.
SQL server is also configured to use windows authentication and user
credentials obviously are propagated from IIS.
I heard complains about this scenarion that if a hacker breaks into IIS
machine they can go directly to sql server inside firewall.
Or maybe there are also other threats using this scenario.
Thank you,
Vadim