Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

Firewall Wish List

Or, why you should absolutely perform outbound firewall filtering

5:35 PM -- Firewalls aren't just for blocking people from sending traffic to your network. If you've been using them in that way alone, you are missing out on half their value. Firewalls have become ubiquitous, but they are also rarely used to their entire effectiveness.

You've got one, or 50, sitting in your data center, whirring away, doing whatever packet inspection magic they advertise on the box, but what do you really want in a firewall? You want something that stops malicious activity, you want it to protect your assets, you want it to scale, and you want it to be cost effective. Firewalls have been around for many years, yet they are still misused almost as often as they are used.

When people set up a Web server on their network, they typically open port 80 to the world, but they also open it in both directions. The reason for this is completely unexplained in most cases, since it's entirely unneeded, unless the application somehow needs to contact other Websites. That's generally only needed in the case of blog sites, or sites that use other Web services.

Even in the case of Web services it can be locked down so the only sites it can communicate to are those services. Additionally, patch management sites can also be whitelisted. That way the site retains all its functionality but is far more secure. And why? Web servers never need to connect to the Web, however, one of the most frequently used attacks is creating reverse shells over port 80. In other words, the attacker pulls in PHP-include payloads from other Web servers over port 80.

Unless there is a good reason to allow your Website to make outbound requests to other Websites, you can lock your site down quite a bit by performing egress (outbound) firewall filtering. If you aren't doing it, your network administrators aren't giving you your money's worth. If they haven't done this yet, you may want to revisit your network security architecture and lock down those sites.

— RSnake is a red-blooded lumberjack whose rants can also be found at Ha.ckers and F*the.net. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/21/2020
Cybersecurity Bounces Back, but Talent Still Absent
Simone Petrella, Chief Executive Officer, CyberVista,  9/16/2020
Meet the Computer Scientist Who Helped Push for Paper Ballots
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Latest Comment: Exactly
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-6564
PUBLISHED: 2020-09-21
Inappropriate implementation in permissions in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to spoof the contents of a permission dialog via a crafted HTML page.
CVE-2020-6565
PUBLISHED: 2020-09-21
Inappropriate implementation in Omnibox in Google Chrome on iOS prior to 85.0.4183.83 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.
CVE-2020-6566
PUBLISHED: 2020-09-21
Insufficient policy enforcement in media in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
CVE-2020-6567
PUBLISHED: 2020-09-21
Insufficient validation of untrusted input in command line handling in Google Chrome on Windows prior to 85.0.4183.83 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page.
CVE-2020-6568
PUBLISHED: 2020-09-21
Insufficient policy enforcement in intent handling in Google Chrome on Android prior to 85.0.4183.83 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page.