I'm developing a B2B website open to the internet.

I've deployed the website on an application server that is in its own network and is only allowed to communicate to the intranet on two ports:

  • To an Exchange Server and
  • to a SQL Server,

both of which are in the internal network.

I want to limit the damage in the scenario in which the application server gets compromised.

I'm especially concerned with SQL Server, as exploits are known to exist on occasion.

There is the (involved) option to work with two databases, one on the application server and one being internal, and a syncing method between them. In that case, the only connection would be initiated from the local network to the application server rather than the other way round. That would exclude most exploits I believe.

I would like to hear what people find reasonable and what else there is to recommend.

  • With two DBs, would the DB sync be two way or one way? And can you clarify "the only connection would be build from the local network to the app server"? – TTT Sep 27 '17 at 15:10
  • Some intranet worker (eg. SSIS) would connect to both databases and copy data. The data would be copied in both directions, but from the point of view of the isolated server, all db connections would be incoming. I think incoming SQL Server connections are much harder to exploit (you can't call any SQL functions that might have exploits, for example). – John Sep 27 '17 at 15:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.