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.

    https://www.linkedin.com/pulse/my-top-10-posts-pulse-ronald-bartels/


Comments

Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi