How should a desktop firewall policy manage open ports?

How should a desktop firewall policy manage open ports?

Do you think that there should be a common desktop firewall policy? If so, what should it be? Should a policy incorporate a port-based firewall that blocks all inbound ports?

    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Yes, organizations should definitely have a standard desktop firewall policy. A good starting point is to employ the "Deny all" setting. The Windows Firewall equivalent is "Don't allow exceptions". Unless there are services on the desktop that must be accessed by other systems, there is no need to have any ports open on the standard productivity workstation. And, if you do have these services (remote administration tools, for example), allow only the bare minimum number of ports and expose them to the smallest possible subnet.

More information:

  • Visit our Firewall Learning Guide.
  • Find out who should manage the firewall.
  • This was first published in December 2006