Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Sign up!
EnGarde Community
What is the most important Linux security technology?
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Latest Newsletters
Linux Advisory Watch: February 27th, 2015
Linux Security Week: February 23rd, 2015
LinuxSecurity Newsletters
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

Evaluating Your Firewall Print E-mail
User Rating:      How can I rate this item?
Source: - Posted by Vincenzo Ciaglia   
Firewalls Are you an administrator or security analyst who watches over a firewall with a hundred or more rules? Or perhaps a hired gun who must review a firewall with years of crusty buildup? Are you creating a test lab that involves a wide variety of networks, servers, and risks? If you're interested in enterprise-level firewalls, this article will help you make sense of common failures in processes and tools. We'll focus on enterprise-grade business and networking issues that affect firewalls. (Penetration studies and piercing firewalls from the outside will be covered in a later article.)

The Value of Firewalls

Once upon a time, many major institutions felt that they could run without firewalls, concentrating instead on server security. It wasn't long before intruders used all kinds of low-level, network-type attacks against such institutions:

* Intruders might start a TCP connection but never complete the dialogue. Soon the server's TCP connection table would fill with empty connections that must wait for connection timeout values to be exhausted. (Imagine someone phoning you and never saying a word; you would just have to wait until the caller hung up.)

* The attacker might fake a message from one machine to another. The packet/message would tell the character generation (CHARGEN) service to send a return message to the impersonated machine's ECHO service. Much like the Abbott and Costello "Who's on first?" comedy routine, ECHO would echo back, CHARGEN would generate a character back to machine 1, whose ECHO routine would echo back, and so on. Soon, both machines would be locked in this two-way dialogue, like arguing politicians.

* Within ICMP, a message can be sent to a server, directing the server to use the attacker's device as the default gateway. Intruders would send this message to a server to force the server to route through an attack machine that would sniff (review and record) packets. Plain-text protocols such as FTP and Telnet could be hacked even in a switched network. The ICMP redirect is one message that few people remember when securing networks.

Read this full article at

Only registered users can write comments.
Please login or register.

Powered by AkoComment!

< Prev   Next >


Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
D-Link Routers Haunted by Remote Command Injection Bug -
Mozilla Pushes Hot Fix to Remove Superfish Cert From Firefox
The Deadly Game of Cyber Mis-Attribution
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2015 Guardian Digital, Inc. All rights reserved.