If one server in a DMZ network gets attacked from outside, will the other servers be corrupted?

If one server in a DMZ network gets attacked from outside, will the other servers be corrupted?

I need to create five servers in a DMZ network. But if one server gets attacked from outside of the network, will the other servers automatically be corrupted? How can the others be protected if one of them is compromised?

    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

The question you're asking is quite a common one and is a good illustration of why security professionals embrace the "defense-in-depth" philosophy.

You're insightful to point out that the compromise of a single server within a DMZ places all of the other devices in that DMZ at risk. However, it's important to point out that the compromise of one system does not necessarily mean that other servers will "automatically" become compromised. When an attacker gains access to a single server, that system does provide a possible foothold in your network. Relying upon the trust relationships between your DMZ's servers, the hacker can then leverage that foothold to gain access to other systems.

How can the enterprise be protected from this risk? By using security controls other than the network firewall that segments the DMZ. For example, deploy host firewall software on each server within the DMZ, restricting inbound traffic to that which is necessary to meet business requirements. These rules should even apply to outside servers that have been collocated in the DMZ. Similarly, implement all of the other system hardening best practices: ensure that systems are patched properly, practice good account management and deploy antivirus and intrusion detection software on the network.

More information:

This was first published in March 2008

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.