In response to last night's post, MarkF commented that he thought MarkB's original point was about architecture, not data. That is, that you should design architectures assuming that they will end up exposed on the Internet. MarkB responded that yes, he was talking about architecture, but also about data (as I had assumed). In any case, even if you just consider architecture and not data, my point still holds. The design tensions for external facing systems, especially security, are very different from interal systems. Talk to anyone at a big company (or even a medium sized company) and they'll tell you that what they do in the DMZ between firewalls and what they do for internal corporate systems are not the same. In my experience, the cost of safely externalizing a system is high enough that you only want to do it when it is required. If I wanted to expose a heretofore internal system externally, I would redesign it or design a gateway to it. I would never expect to simply expose it because it wasn't designed for that.
Posted
Jun 10 2005, 07:34 AM
by
tim-ewald