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.
Dig Deeper on DMZ Setup and Configuration
Related Q&A from Mike Chapple
Cloud compliance issues are no reason for enterprises not to move to the cloud. Expert Mike Chapple explains why, as well as what to keep in mind ...continue reading
The GAO reported on SEC cybersecurity weaknesses, even though the SEC regulates cybersecurity. Expert Mike Chapple discusses the effects of this ...continue reading
Enterprise compliance can be a burden to manage, which is where a PCI ISA can be helpful. Expert Mike Chapple explains how a PCI Internal Security ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.