Skip to main content

DMZ checklist

This is a checklist to use when implementing DMZs.
  • Use the external gateway router to bin unknown or unused protocols that are not required in the DMZ. This prevents the firewall processing from being swamped and acts as a second security skin. This traffic is binned using ACLs.
  • Use private addresses in the DMZ and use the firewall to NAT to the external network. On the external gateway router bin all private addresses.
  • Implement an IPS/IDS.
  • Provide server protection – anti virus, anti spyware and anti rootkits.
  • Data should not be stored in the DMZ that accepts incoming connections from the Internet or 3rd parties. A separate VLAN should exist that is traversed by a firewall to backhaul data for processing.
  • Use reverse proxies in the incoming DMZ. This enables a system that has local data to be protected as it can be moved to an internal local network while still protecting the data.
  • Use protected switch ports. Disable unused ports. Use port security to associate a MAC to a port.
  • Aggregate Netflow data from the network devices and review reports daily.
  • Review logs from network devices and servers. Search for an excessive number of failed logins.
  • Force network devices to use an authentication service like Radius or TACACS+.
  • Don’t deploy AD into the DMZs.
  • Implement separate management VLANs for network devices.
  • Don’t terminate incoming connections from the Internet ord 3rd parties on the internal network.
  • Encrypt all data being backhauled from a DMZ.
  • Do not back and restore servers through the firewalls.


Popular posts from this blog

easywall - Web interface for easy use of the IPTables firewall on Linux systems written in Python3.

Firewalls are becoming increasingly important in today’s world. Hackers and automated scripts are constantly trying to invade your system and use it for Bitcoin mining, botnets or other things. To prevent these attacks, you can use a firewall on your system. IPTables is the strongest firewall in Linux because it can filter packets in the kernel before they reach the application. Using IPTables is not very easy for Linux beginners. We have created easywall - the simple IPTables web interface . The focus of the software is on easy installation and use. Access this neat software over on github: easywall

No Scrubs: The Architecture That Made Unmetered Mitigation Possible

When building a DDoS mitigation service it’s incredibly tempting to think that the solution is scrubbing centers or scrubbing servers. I, too, thought that was a good idea in the beginning, but experience has shown that there are serious pitfalls to this approach. Read the post of at Cloudflare's blog: N o Scrubs: The Architecture That Made Unmetered Mitigation Possible

Should You Buy A UniFi Dream Machine, USG, USG Pro, or Dream Machine Pro?