nerdexam
EC-Council

312-50V11 · Question #120

Bob, a system administrator at TPNQM SA, concluded one day that a DMZ is not needed if he properly configures the firewall to allow access just to servers/ports, which can have direct internet…

The correct answer is C. Bob is totally wrong. DMZ is always relevant when the company has internet servers and workstations. A DMZ is a network architecture control that remains relevant regardless of firewall type because it provides segmentation that isolates internet-facing servers from internal workstations.

Evading IDS, Firewalls, and Honeypots

Question

Bob, a system administrator at TPNQM SA, concluded one day that a DMZ is not needed if he properly configures the firewall to allow access just to servers/ports, which can have direct internet access, and block the access to workstations. Bob also concluded that DMZ makes sense just when a stateful firewall is available, which is not the case of TPNQM SA. In this context, what can you say?

Options

  • ABob can be right since DMZ does not make sense when combined with stateless firewalls
  • BBob is partially right. He does not need to separate networks if he can create rules by destination IPs,
  • CBob is totally wrong. DMZ is always relevant when the company has internet servers and workstations
  • DBob is partially right. DMZ does not make sense when a stateless firewall is available

How the community answered

(40 responses)
  • A
    23% (9)
  • B
    10% (4)
  • C
    63% (25)
  • D
    5% (2)

Why each option

A DMZ is a network architecture control that remains relevant regardless of firewall type because it provides segmentation that isolates internet-facing servers from internal workstations.

ABob can be right since DMZ does not make sense when combined with stateless firewalls

DMZ provides value with stateless firewalls because network segmentation itself limits lateral movement, regardless of the firewall's ability to track connection state.

BBob is partially right. He does not need to separate networks if he can create rules by destination IPs,

Firewall rules based on destination IPs do not provide the same isolation as a physical or logical DMZ segment, since a compromised DMZ server can still attempt to pivot to internal hosts on the same flat network.

CBob is totally wrong. DMZ is always relevant when the company has internet servers and workstationsCorrect

A DMZ separates publicly accessible servers from internal hosts at the network topology level, which is a defense-in-depth principle independent of whether the firewall is stateful or stateless. Even a stateless firewall enforcing DMZ segmentation is more secure than a flat network, because an attacker who compromises a DMZ server still cannot directly reach internal workstations without crossing an additional network boundary.

DBob is partially right. DMZ does not make sense when a stateless firewall is available

A stateless firewall can still enforce DMZ boundaries using ACLs on routed segments; the DMZ concept is not contingent on stateful inspection capability.

Concept tested: DMZ purpose and applicability with different firewall types

Source: https://csrc.nist.gov/publications/detail/sp/800-41/rev-1/final

Topics

#DMZ#firewall architecture#stateful vs stateless#network segmentation

Community Discussion

No community discussion yet for this question.

Full 312-50V11 Practice