- Failure to properly configure firewalls. Firewalls are a staple of the network security diet. In a good network design, an enterprise should protect its systems with both network and host firewalls. However, all too often those firewalls are not properly configured and may even be disabled for "temporary" testing that never seems to be finished. Failing to properly configure firewalls creates a foothold for the exploitation of other vulnerabilities.
- Failure to authenticate network users. Are you really sure who is on your network? It's a good idea to use some form of authentication technology, such as 802.1x, to ensure that devices connecting to your network are associated with an authorized user.
- Use of weak (or no) wireless encryption. Believe it or not, many enterprises still use WEP encryption to "protect" their networks. As I mentioned in an earlier article, WEP encryption is fundamentally flawed and should never be relied upon to secure a wireless network. Use WPA encryption instead.
- Failure to patch. Everyone knows that it's important to apply vendor security patches to systems and applications. But not everyone does. In fact, a recent study showed that many Oracle administrators have never applied patches to their systems. This is a bad idea, as hackers keep a close eye on security bulletins, looking for exploitable flaws.
- Contributor David Davis walks you through PIX firewall configuration from scratch.
- Ed Skoudis explains how to develop a patch management policy for third-party applications.
This was first published in October 2008